Comments on: EJPPG0003E: ServletContext lookup for /.CreditCounterPartyReviewLog returned the portal context. It has to be a different one.

By: It’s Only Software » How to Diagnose the Awful Websphere Portal EJPPG0003E Error

Wed, 07 May 2008 02:09:33 +0000

[...] by about a hundred different things. If the issue is actually a context issue, you can follow Jamie Mcllroy’s great instructions to try to resolve context root-type [...]

By: Vaibhav

Vaibhav — Sat, 24 Nov 2007 01:52:12 +0000

Thanks a lot!!!!! it worked for me also!!!!

By: mado

mado — Wed, 19 Sep 2007 09:51:57 +0000

I tried the ‘tricks’ the way they’re described above, but nothing happened. So I refreshed the EAR- and the Servers-Project in the RAD Project Explorer (rightclick on project – refresh).

ReDeploy and run…

By: Jayakumar V

Jayakumar V — Tue, 22 May 2007 17:30:39 +0000

Yes this Refresh module Context root in RAD solved this Servlet Context problem. Thanks.

By: onkar

onkar — Mon, 14 May 2007 11:28:30 +0000

i tried ur trick but it hasnt worked in my case. also one more thing i dont get the project text box below the context root.

By: Jessica

Jessica — Wed, 21 Mar 2007 15:43:30 +0000

Oh holy hay-zeus. Thank you. I know that WPS sometimes gets its knickers in a twist about new EARs, but I usually solved it (blindly) by recreating the EAR and rebuilding. This always worked for me until today – reading the “real” reason has saved me hours and a large loss of hair. J

By: Felix

Felix — Wed, 14 Mar 2007 10:55:50 +0000

@Jim: A little late, but maybe it helps someone else: Try to change the classloader settings of your server for that specific application. Switching between “parent first” and “parent last” helps some times.

By: Jim

Jim — Mon, 11 Dec 2006 21:47:35 +0000

Right problem, right symptoms, but this tip did not work for me. Still get the same error. Any other ideas?

By: Ton

Ton — Fri, 17 Nov 2006 14:56:55 +0000

@prabhakar 2: I see now that you deployed into a server. Check the application.xml in the META-INF directory and make sure the element has the correct value.

By: Ton

Ton — Fri, 17 Nov 2006 14:42:28 +0000

Same here – just “portlet not available” and this logmessage. This tip saves my day, thanks!
@prabhakar: see the screenshot; to get here open the EAR project for your portlet, doubleclick application.xml (in META-INF) then under “modules” click on the .war file where your portlet lives. Look to the right to see the Context root and “Refresh” button.