Hi all,
I am starting a new project and have decided to give 2.2 a go!
I'm using RedHat 7.2, mySQL, JDK-1.3.1_02.
Several issues have come up that I do not understand. Any pointers would
be much appreciated.
Firstly,
A look thru the application turbine.log file shows the following :-
[Tue Apr 16 10:48:50 BST 2002] -- INFO -- Start Initializing service
(late): TemplateService
[Tue Apr 16 10:48:50 BST 2002] -- INFO -- Finish Initializing
service (late): TemplateService
[Tue Apr 16 10:48:50 BST 2002] -- INFO -- Finish Initializing
service (early): VelocityService
[Tue Apr 16 10:48:50 BST 2002] -- INFO -- Finished initializing all
services!
[Tue Apr 16 10:48:52 BST 2002] -- INFO -- Turbine: init() Ready to
Rumble!
[Tue Apr 16 10:48:52 BST 2002] -- INFO -- init
[Tue Apr 16 10:48:52 BST 2002] -- INFO -- Double initializaton of
Turbine was attempted!
[Tue Apr 16 10:51:23 BST 2002] -- INFO -- Start Initializing service
(late): RunDataService
[Tue Apr 16 10:51:23 BST 2002] -- INFO -- Finish Initializing
service (late): RunDataService
[Tue Apr 16 10:51:23 BST 2002] -- INFO -- Start Initializing service
(late): PoolService
[Tue Apr 16 10:51:23 BST 2002] -- INFO -- Finish Initializing
service (late): PoolService
[Tue Apr 16 10:51:23 BST 2002] -- INFO -- Start Initializing service
(late): FactoryService
My question is why is turbine trying to double init? Is this a
configuration problem? Do I need to worry about this?
Secondly,
the xml-rpc service was being initialised once from the entry in
TurbineResources.properties and again from Fulcrum.properties. This
caused a exception and slowed startup considerably. I have removed the
entry in TurbineResources.props. and this has solved this problem. Does
anyone know if there are any gotcha's with this?
I also note that other services including VelocityTemplate are being
started from both props files. Is this a problem? Should one be
disabled?
Thirdly,
When unconvinced that class reloading is working I restart catalina. The
tdk2.2 container will not shut down cleanly and restart. catalina.out
shows:
Stopping service Tomcat-Standalone
java.lang.NullPointerException
at org.apache.turbine.om.peer.BasePeer.doUpdate(BasePeer.java:1655)
at org.apache.turbine.om.peer.BasePeer.doUpdate(BasePeer.java:1594)
at
org.apache.turbine.om.security.peer.TurbineUserPeer.doUpdate(TurbineUserPeer.java:469)
at
org.apache.turbine.services.security.db.DBUserManager.store(DBUserManager.java:272)
rethrown as org.apache.turbine.util.security.DataBackendException:
Failed to save user object
at
org.apache.turbine.services.security.db.DBUserManager.store(DBUserManager.java:276)
Then on restart
Catalina.start: LifecycleException: Error creating server socket
(java.net.BindException): java.net.BindException: Address already
in use
LifecycleException: Error creating server socket
(java.net.BindException): java.net.BindException: Address already
in use
at
org.apache.catalina.connector.warp.WarpConnector.initialize(WarpConnector.java:491)
at
org.apache.catalina.core.StandardService.initialize(StandardService.java:454)
at
org.apache.catalina.core.StandardServer.initialize(StandardServer.java:553)
at org.apache.catalina.startup.Catalina.start(Catalina.java:780)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
----- Root Cause -----
java.net.BindException: Address already in use
The turbine.log shows:-
[Tue Apr 16 10:44:38 BST 2002] -- ERROR --
TurbineUser.valueUnbobund(): Failed to save user object
Exception: org.apache.turbine.util.security.DataBackendException:
Failed to save user object
This one is a real pain as I haven't found out how to get round this
yet!
Has anyone seen this before?
Sorry for the long post. I haven't seen anything in the archives on
this. I hope others will benefit from any pointers.
Many thanks for any assistance.
Peter
--
Peter Courcoux
PGP key ID : 2E50A3C8
Telephone : 07880 605626
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
