javax.naming.NameNotFoundException: The object or context portal:service does not exist.; remaining name 'portal:service/Identification

2 comments



Recently we had faced an issue where all our application portlets suddenly stopped working and starts displaying "Portlet is currently unavailable".

Portlet Error
Error Message


Below is the log trace that from the error logs.

[04/08/11 14:04:50:981 IST] 0000007c SystemErrR javax.naming.Name Not Found Exception: The object or context portal:service does not exist.; remaining name 'portal:service/Identification'

After spending couple of hours, we found that somebody from the team has added new dependency jars to the portlet projects.

Below are the 3 extra jars that were bundling with portlet and making them disabled.
wp.base-6.1.0.jar
wp.engine,impl-6.1.0.jar
wp.model.api-6.1.0.jar

2 comments:

Anonymous said...

Is this the only possible reason for this type of error?

Arun said...

No, there might be other reasons but wrong jars could cause these kind of issues.

Post a Comment

Recent Posts

Popular Posts

© 2011-2019 Web Portal Club