Eric, Thanks for the pointers. I'll let the list know if I solve the double init and restart problems. It's going to have to wait for a few days. I've just had more work dumped on me.
Many thanks for your "TDK2.2b1 Fulcrum Torque -- some assembly required" posting. This makes things much clearer to me and I'm sure must have been of assistance to others. Thanks again for your time. Regards, Peter On Thu, 2002-04-18 at 20:18, Eric Dobbs wrote: > > On Tuesday, April 16, 2002, at 06:30 AM, Peter Courcoux wrote: > > > I am starting a new project and have decided to give 2.2 a go! > > see also my post about TDK 2.2b1, etc: > <http://nagoya.apache.org:8080/eyebrowse/ReadMsg?listName=turbine- > [EMAIL PROTECTED]&msgNo=3471> > > (complete tangent: Dan, eyebrowse is cool! I like that the mail I sent > only a few minutes ago is already in the archive 8^) > > > > My question is why is turbine trying to double init? Is this a > > configuration problem? Do I need to worry about this? > > I've seen that before when we messed with tomcat's server.xml file to > map / to our webapp. I think Tomcat basically saw our webapp as two > apps: one configured under / per our server.xml config, and the other > configured automagically by Tomcat for everything in the webapps > directory. > > > > 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? > > That conflict would be caused by the little web server that gets started > to listen for XMLRPC requests. Both services were probably configured > to listen on the same port. Fulcrum XMLRPC works fine for the server > side in TDK2.2b1. But if you are going to initiate any XMLRPC calls > from within turbine, you'll need the fixes I mentioned in the "some > assembly required" message. You'll need one of the recent nightly > builds for fulcrum*.jar, and probably also for turbine*.jar > > > > I also note that other services including VelocityTemplate are being > > started from both props files. Is this a problem? Should one be > > disabled? > > Those shouldn't present problems. The services use lazy initialization > so that only the services that you actually use get initialized. So the > ones that aren't getting used by any of your code won't cause any drain > on your system. > > > > 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! > > Don't know what all that is about. Maybe a side effect of double > initialization? > > > Hope that helps. > -Eric > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- Peter Courcoux PGP key ID : 2E50A3C8 Telephone : 07880 605626 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
