Can you check to see what jars are in <tomcat-install-dir>/shared/lib ?
You should see something like this:
pluto-1.0.1.jar
jetspeed-api-2.1-dev.jar portals-bridges-common-1.0.1-dev.jar
jetspeed-commons-2.1-dev.jar portlet-api-1.0.jar
I've been building & testing Jetspeed on Linux (RHEL 3) and haven't seen
that particular error, so I don't think it's a Linux specific error.
Also, are you using Maven to deploy to Tomcat or doing so manually?
What you can do to test to see if this is Linux specific is to; copy
your whole tomcat installation, including installed apps & your custom
portal, over to Linux and see if it will run. If your using derby as
your database you will need to copy over the Derby database and edit
your tomcat/conf/Catalina/localhost/<custom-portal-name>.xml to point to
the location of the Derby database.
Luck
Mick
-----Original Message-----
From: MikeCrosby [mailto:[EMAIL PROTECTED]
Sent: Monday, January 22, 2007 4:05 PM
To: jetspeed-user@portals.apache.org
Subject: Re: "j2-admin" servlet context issue on Linux
Thanks for the recommendation. I did as you suggested and thought I
might have found the problem. An exception was thrown when j2-admin was
redeployed stating that it couldn't find the SAXParserFactoryImpl class.
I went ahead and copied the xerces jars to the common\lib directory for
Tomcat and restarted the server.
That didn't seem to resolve the issue. So, I changed the web.xml file
for j2-admin again. The jetspeed.log reported the usual error:
2007-01-22 14:54:47,169 [WORKER_5] ERROR
org.apache.jetspeed.container.invoker.ServletPortletInvoker - Failed to
find Servlet context for Portlet Application: /j2-admin
javax.portlet.PortletException: Failed to find Servlet context for
Portlet
Application: /j2-admin
at
org.apache.jetspeed.container.invoker.ServletPortletInvoker.invoke(Servl
etPortletInvoker.java:188)
at
org.apache.jetspeed.container.invoker.ServletPortletInvoker.render(Servl
etPortletInvoker.java:126)
at
org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl
.java:119)
at
org.apache.jetspeed.container.JetspeedPortletContainerWrapper.renderPort
let(JetspeedPortletContainerWrapper.java:120)
at
org.apache.jetspeed.aggregator.impl.RenderingJobImpl.execute(RenderingJo
bImpl.java:121)
at
org.apache.jetspeed.aggregator.impl.RenderingJobImpl.run(RenderingJobImp
l.java:91)
at
org.apache.jetspeed.aggregator.impl.WorkerImpl$1.run(WorkerImpl.java:174
)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:454)
at
org.apache.jetspeed.aggregator.impl.WorkerImpl.run(WorkerImpl.java:168)
In the catalina.out log, the following is diplayed:
INFO: Remove all registry entries defined for portlet application
j2-admin
INFO: Loading portlet.xml....j2-admin
namespace = http://portals.apache.org/jetspeed
name = service
object =
[EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object =
[EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object = [EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object = [EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object =
[EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object =
[EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object =
[EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object = [EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object = [EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object = [EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object = [EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object =
[EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object = [EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object =
[EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object = [EMAIL PROTECTED]
service = [EMAIL PROTECTED]
namespace = http://portals.apache.org/jetspeed
name = service
object =
[EMAIL PROTECTED]
service =
[EMAIL PROTECTED]
INFO: Loading web.xml....j2-admin
INFO: Registered the portlet application j2-admin
INFO: Registered the portlet application in the search engine...
j2-admin
So, it looks like it's registering, but I don't know why the context
error is happening.
David Sean Taylor wrote:
>
> MikeCrosby wrote:
>> Philip,
>>
>> Thanks for the response. I've ensured that my build.properties file
>> has the following properties set:
>>
>> org.apache.jetspeed.services.autodeployment.user = [admin_username]
>> org.apache.jetspeed.services.autodeployment.password =
>> [admin_password]
>>
>> The admin_username and admin_password have been tested to ensure that
>> I can log into Tomcat (as defined in the tomcat-users.xml file).
>>
>> The deployment.log shows no errors. Also, it appears that the
>> jetspeed-layouts app is being deployed properly since the screen
>> shows the place holders for the j2-admin portlets.
>>
>> If I log into the Tomcat Administration component, I am able to see
>> "j2-admin" listed. I'm just at a loss as to why Jetspeed isn't able
>> to access the portlets.
>>
>> As a side note, I've tried changing the default page back to the psml
>> that ships with Jetspeed. The page loads with the default theme, but
>> none of the portlets will load on the page. All say:
>>
>> Failed to find Servlet context for Portlet Application: [respective
>> portlet]
>>
>> Any other suggestions?
>>
> Edit the j2-admin's web.xml or portlet.xml, change anything, add a new
> line and save it
>
> Tomcat should pick it up and it should redeploy within a few seconds
> Tail the jetspeed.log and catalina.out during redeployment See if
> there are any errors ....
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/%22j2-admin%22-servlet-context-issue-on-Linux-tf30
59100.html#a8509842
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
