Raphael,

Thanks for the reply.  The WAR file drops into Tomcat 3.2 and runs just fine, so it is 
a WebSphere issue.

RE: "I expected you have already checked that Websphere uses the new TR.p file that
defines the PoolService and not an old one (that does not define PoolService)."

I didn't modify any properties file, as it ran in Tomcat.. I'll take a look.

RE: "If this is not a configuration file issue, I really don't know how to help
(probably some classloader issue). Jetspeed does not even use the PoolService..."

O.K.. I'll pull by tag and see what I can find.  The issue is somewhat low priority as 
we have a stable code base running in WebSphere, we're mainly trying to keep tabs on 
when things break.  If I can better define the problem as a Turbine issue, I'll post 
it back that way.

Thanks..

mlc


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, May 17, 2001 9:48 AM
To: [EMAIL PROTECTED]
Subject: Re: WebSphere, JetSpeed, And Turbine




"Conneen, Mike" wrote:
>
> Folks,
> (I posted this to the turbine list.. and was directed to this list.. so here
goes...) >
> If I want to pull the source of turbine that is currently running with the
build of JetSpeed, would I pull it by tag (tkd_1a13) or by date (03/29/01)? >

I would do it by tag.

> I ask this because I'm running into problems with the current JetSpeed build
(cvs tree pulled today) on IBM WebSphere 3.5.3 on NT40/SP6.  Please note, the
build DOES work within Tomcat 3.2 final as, I've copied the xalan and xerces to
the tomcat/lib directory, hence it appears to be WebSphere related.  I get the
following error message: >
> Error Message: Server caught unhandled exception from servlet [file]: Server
caught unhandled exception from servlet [jsp11]: Server caught unhandled
exception from servlet [jetspeed]: ServiceBroker: unknown service PoolService
requested > Error Code: 500
> Target Servlet: file
> Error Stack:
>
>
--------------------------------------------------------------------------------
> Root Error-1: ServiceBroker: unknown service PoolService requested
>

I expected you have already checked that Websphere uses the new TR.p file that
defines the PoolService and not an old one (that does not define PoolService).

If this is not a configuration file issue, I really don't know how to help
(probably some classloader issue). Jetspeed does not even use the
PoolService...

> org.apache.turbine.services.InstantiationException: ServiceBroker: unknown
service PoolService requested >         at
org.apache.turbine.services.BaseServiceBroker.getServiceInstance(BaseServiceBrok
er.java:312) >         at
org.apache.turbine.services.BaseServiceBroker.getService(BaseServiceBroker.java:
257) >         at
org.apache.turbine.util.RunDataFactory.putRunData(RunDataFactory.java:233) >
at org.apache.turbine.Turbine.doGet(Turbine.java:517)

--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to