Mike,
I've been digging into the problem and have tried to recreate my steps. So,
let me fill you in so far.
Removed my test server, servlet engine, and webapp from WebSphere.
Recreated the same. Using Jetspeed-1.3a1 WAR file to build webapp using WAS
Tasks/Convert WAR.
Started test server and called Jetspeed through IE browser. Received the
initial URLManager failure.
Stopped test server on WAS. Built Jetspeed.jar using latest CVS source.
Copied into place on WAS. Restarted test server and received the following
error:
initializing service: ResourcesService
java.lang.NoClassDefFoundError:
org/apache/turbine/services/resources/ResourceService
rethrown as org.apache.turbine.services.InstantiationException: A class
referenced by
org.apache.jetspeed.services.resources.VariableResourcesService is
unavailable. Check your jars and classes.
So, I stopped the test server and put the Turbine.jar that came with the
Jetspeed CVS source in place under my webapp. Restarted the test server and
received the following error:
[01.05.08 16:49:05:721 EDT] 89b69389 WebGroup A SRVE0091I: [Servlet
LOG]: "jetspeed: init"
[01.05.08 16:49:05:761 EDT] 89b69389 ServletInstan X Uncaught init()
exception thrown by servlet {0}: {1}
"jetspeed"
javax.servlet.ServletException:
org/apache/velocity/runtime/configuration/Configuration
So, I stopped the test server and put the Velocity.jar that came with the
Jetspeed CVS source in place under my webapp. Restarted the test server and
received the following error:
[01.05.08 16:55:37:264 EDT] 89b69500 WebGroup A SRVE0091I: [Servlet
LOG]: "jetspeed: Turbine: init() failed: java.lang.NullPointerException
at
org.apache.turbine.services.logging.TurbineLoggingService.getLoggingConfig(T
urbineLoggingService.java:153)
Since then I've downloaded the latest Turbine source and have been poking
around and have a configuration problem was has gotten me past the
NullPointerException, so I'm making progress. I've added the following to
the Turbine.properties file
# -------------------------------------------------------------------
#
# L O G S
#
# -------------------------------------------------------------------
# This is the configuration for the logging system. In most cases
# you don't need to modify anything. However, if you wish to add more
# facilities or modify the existing settings, then you can do so.
#
# destination.file: A path relative to the web app root
# -------------------------------------------------------------------
services.LoggingService.facilities=system,debug,security
services.LoggingService.default=system
services.LoggingService.loggingConfig=org.apache.turbine.services.logging.Pr
opertiesLoggingConfig
# A facility for system logging.
services.LoggingService.system.destination.file=/logs/turbine.log
services.LoggingService.system.className=org.apache.turbine.services.logging
.FileLogger
services.LoggingService.system.level=INFO
# A facility for the scheduler service
# To disable started/stopped messages set the level to ERROR
services.LoggingService.scheduler.destination.file=/logs/turbine.log
services.LoggingService.scheduler.className=org.apache.turbine.services.logg
ing.FileLogger
services.LoggingService.scheduler.level=INFO
# A facility for debugging applications. Messages will go both
# to the log file and the server console.
services.LoggingService.debug.destination.file=/logs/turbine.log
services.LoggingService.debug.destination.console=true
services.LoggingService.debug.className=org.apache.turbine.services.logging.
FileLogger
services.LoggingService.debug.level=INFO
# A facility for SQL query logging
# To enable SQL query logging, set the level to DEBUG
services.LoggingService.sql.destination.file=/logs/turbine.log
services.LoggingService.sql.className=org.apache.turbine.services.logging.Fi
leLogger
services.LoggingService.sql.level=ERROR
# A facility for security audit. NOTE! As of 23 Jan 2001
# Turbine does not have any standard security auditing
# functionality. It's up to your application.
services.LoggingService.security.destination.file=/logs/turbine.log
services.LoggingService.security.className=org.apache.turbine.services.loggi
ng.FileLogger
services.LoggingService.security.level=INFO
# An example configuration for automatic log rotation using Log4Java
# This will keep the log file size under 1MB and save up to 5 backup copies
services.LoggingService.rotation.destination.file=/logs/turbine.log
services.LoggingService.rotation.file.size=1048576
services.LoggingService.rotation.file.backups=5
services.LoggingService.rotation.className=org.apache.turbine.services.loggi
ng.Log4JavaLogger
services.LoggingService.rotation.level=INFO
# An example configuration for using *NIX syslogd with Log4Java
services.LoggingService.syslog.destination.syslogd.host=my.syslog.server.com
services.LoggingService.syslog.destination.syslogd.facility=LOG_DAEMON
services.LoggingService.syslog.className=org.apache.turbine.services.logging
.Log4JavaLogger
services.LoggingService.syslog.level=INFO
# An example configuration for using remote Log4Java server
services.LoggingService.remote.destination.remote.host=my.remote.server.com
services.LoggingService.remote.destination.remote.port=1099
services.LoggingService.remote.className=org.apache.turbine.services.logging
.Log4JavaLogger
services.LoggingService.remote.level=INFO
# An example configuration for sending error reports as email with Log4Java
# notes:
# * uses 'mail.server' as SMTP server to send mail through
# * log4j will send the email when an ERROR is logged, with
# 'buffer.size' previous (non-ERROR) logs included in the email
# * configured to log to a file as well otherwise stacktraces are lost
services.LoggingService.email.destination.file=/logs/turbine.log
services.LoggingService.email.destination.email.from=root@localhost
services.LoggingService.email.destination.email.to=root@localhost
services.LoggingService.email.destination.email.subject=Turbine Error Report
services.LoggingService.email.destination.email.buffer.size=512
services.LoggingService.email.className=org.apache.turbine.services.logging.
Log4JavaLogger
services.LoggingService.email.level=INFO
services.LoggingService.classname=org.apache.turbine.services.logging.Turbin
eLoggingService
The latest problem is a series of the following error:
[01.05.09 10:56:43:116 EDT] 89b59062 ServletInstan X Uncaught init()
exception thrown by servlet {0}: {1}
"jetspeed"
javax.servlet.ServletException:
helma/xmlrpc/XmlRpcServer
at javax.servlet.ServletException.<init>(ServletException.java:161)
Sorry for being so long winded, but thought it might be helpful to see where
I've gotten to.
Thanks,
Craig
Before I forget:
OS: NT 4.0
WAS: 3.5.3
Jet: latest CVS
Turbine: latest CVS
Browser: IE 5.5
-----Original Message-----
From: Conneen, Mike [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 09, 2001 9:52 AM
To: - *[EMAIL PROTECTED]
Subject: RE: Websphere
Craig,
Let me build from the latest CSV and see if I get the same error. As we are
using JetSpeed as the base, we are wrestling with trying to set a schedule
to pull, rebuild, and regression test to ensure that our base continues to
work. I'll try to get this done by lunch today.
Another WAS'er had troubles a while back and I ftp'd 100% of my JetSpeed
directory to an internet server where he HTTP'd it off. The file is 10+ mb
(it is full jetspeed tree and may have some build stuff in it). I can also
post the WAR file. Basically, this will get you past your tests, but
doesn't solve the issues of the long haul.
mlc
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2001 2:04 PM
To: [EMAIL PROTECTED]
Subject: FW: Websphere
Sorry, I forgot to include the following
OS: NT 4.0
WAS: 3.5.3
Jet: latest CVS
-----Original Message-----
From: Craig Castelaz
Sent: Tuesday, May 08, 2001 1:34 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Websphere
Mike,
I pulled down the latest Jakarta-Jetspeed CVS project and rebuilt it. I
transferred the Jetspeed.jar onto the Websphere server and attempted to
restart my test webapp. The RegistryManager error seemed to have
disappeared, but a new NoClassDefFound for
org.apache.turbine.RegisterService (I believe that's correct) error started
showing up in the logs. Then it clicked, and I thought, well the
Turbine.jar is out of sync, so I copied all the jars from the
Jakarta-Jetspeed lib folder into my webapp servlet folder. Now I get a
totally different error:
[01.05.08 13:02:00:899 EDT] 89b76c40 WebGroup A SRVE0091I: [Servlet
LOG]: "jetspeed: Turbine: init() failed: java.lang.NullPointerException
at
org.apache.turbine.services.logging.TurbineLoggingService.getLoggingConfig(T
urbineLoggingService.java:153)
at
org.apache.turbine.services.logging.TurbineLoggingService.init(TurbineLoggin
gService.java:127)
at
org.apache.turbine.services.TurbineBaseService.init(TurbineBaseService.java:
112)
at
org.apache.turbine.services.BaseInitableBroker.initClass(BaseInitableBroker.
java:152)
at
org.apache.turbine.services.BaseServiceBroker.initService(BaseServiceBroker.
java:121)
at
org.apache.turbine.services.TurbineServices.initPrimaryServices(TurbineServi
ces.java:181)
at org.apache.turbine.Turbine.init(Turbine.java:180)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doInit(ServletManager.ja
va:604)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(StrictLifecycleSe
rvlet.java:136)
at
com.ibm.servlet.engine.webapp.PreInitializedServletState.init(StrictLifecycl
eServlet.java:244)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(StrictLifecycleSer
vlet.java:102)
at
com.ibm.servlet.engine.webapp.ServletInstance.init(ServletManager.java:284)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at
com.ibm.servlet.engine.webapp.ServletManager.addServlet(ServletManager.java:
76)
at
com.ibm.servlet.engine.webapp.WebAppServletManager.loadServlet(WebAppServlet
Manager.java:91)
at
com.ibm.servlet.engine.webapp.WebAppServletManager.loadAutoLoadServlets(WebA
ppServletManager.java:158)
at
com.ibm.servlet.engine.webapp.WebApp.loadServletManager(WebApp.java:802)
at com.ibm.servlet.engine.webapp.WebApp.init(WebApp.java:89)
at com.ibm.servlet.engine.srt.WebGroup.loadWebApp(WebGroup.java:121)
at com.ibm.servlet.engine.srt.WebGroup.init(WebGroup.java:82)
at
com.ibm.servlet.engine.ServletHost.addWebGroup(ServletHost.java:109)
at
com.ibm.servlet.engine.ServletEngineDynamicUpdateSupport.addWebGroup(Servlet
EngineDynamicUpdateSupport.java:126)
at
com.ibm.ejs.sm.active.ActiveServletGroup.startAction(ActiveServletGroup.java
:76)
at
com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at
com.ibm.ejs.sm.active.ActiveObject.operateOnContainedObjects(ActiveObject.ja
va:584)
at
com.ibm.ejs.sm.active.ActiveServletEngine.startAction(ActiveServletEngine.ja
va:60)
at
com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at
com.ibm.ejs.sm.active.ActiveObject.operateOnContainedObjects(ActiveObject.ja
va:584)
at
com.ibm.ejs.sm.active.ActiveEJBServer.startAction(ActiveEJBServer.java:96)
at
com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.ja
va:93)
at
com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java:6
2)
at
com.ibm.ejs.sm.agent._AdminAgentImpl_Tie._invoke(_AdminAgentImpl_Tie.java:80
)
at
com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.ja
va:506)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:2261)
at com.ibm.CORBA.iiop.WorkerThread.run(WorkerThread.java:195)
at
com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java:535)
"
Is this by any chance the Turbine error you mentioned?
Craig
-----Original Message-----
From: Conneen, Mike [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 08, 2001 10:04 AM
To: - *[EMAIL PROTECTED]
Subject: RE: Websphere
Craig,
It is more the possible. We have built a few intra-net prototype
applications on top of it. It runs rather smooth once all the configuration
bugs are worked out!
Again, there has been fixes made to the base to get it to work within WAS,
and these have been migrated towards turbine for the base servlet services.
I pulled the tree a week or so ago, and it would NOT run as there was a
turbine error. I posted a question to that list and Jon was kind enough to
post the fix back in.
Also, there are IBM Developers that are working on the Jetspeed code.
Hence, they are most interested in getting these prototype applications out
the door to help drive better business cases.
So, if you run into more issues, feel free to post back to the list, and
please provide version (OS, WAS, Jetspeed) information as well.
-----Original Message-----
<snip
href=http://www.mail-archive.com/jetspeed-user%40jakarta.apache.org/msg00023
.html
/>
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
