Re: [enhydra] Postgres driver kills MySQL communication

["Michael Strapp" <mstrapp@xxxxxxxxxxxxx>]

Hi Petr,
   It looks like when the multiserver initializes the Enhydra app, the 
Enhydra app initializes the database manager (possibly triggered by the 
presence of the database configuration in the app's .conf file) and the 
initialization of the database manager is being done at the multiserver 
level, where the system classloader is applicable.  So that's that - even if 
you could get some of the classes to be loaded by the system classloader and 
other classes to be loaded by the application classloader, it would probably 
cause other problems somewhere along the line (probably in the form of 
inexplicable ClassCastException's being thrown).
   So, it looks like the only solution along these lines would be to remove 
the database settings from the Enhdyra app's .conf file entirely (so that 
the multiserver is unaware that it is using DODS at all), and configure the 
app to access "DODS standalone".  As of Enhydra 5.1, DODS was made into a 
separate project so that DODS could be used even in non-Enhydra 
applications - so this would at least be a possible configuration.  However, 
I don't know what would be involved in doing so, as I've never worked with a 
"DODS standalone" configuration myself.

Mike.

----- Original Message ----- 
From: "Petr Stehlik" <pstehlik@xxxxxxxxxx>
To: <enhydra@xxxxxxxxxxxxx>
Sent: Monday, November 01, 2004 10:40 AM
Subject: Re: [enhydra] Postgres driver kills MySQL communication


V Po, 25. 10. 2004 v 17:57, Michael Strapp píše:
>     Actually, I just had an idea that I hadn't thought of before - if you
> remove the jar(s) for the dods classes from the system classpath (or even
> move them out the enhydra5.1 tree to ensure that the regular Enhydra 
> scripts
> can't find them), and explicitly add the dods jars to the 
> Server.ClassPath[]
> setting in the .conf file for each Enhydra app, that would allow the DODS
> classes to be loaded only by the classloader belonging to each individual
> Enhydra app.  With the DODS project having been separated from the main
> Enhydra project, the multiserver hopefully wouldn't have a problem with 
> that
> configuration

Unfortunately, it seems that the multiserver wrapper itself wants the
dods-runtime.jar loaded for some obscure reason:

INFO   | jvm 1    | 2004/11/01 16:29:07 | Failed to start multiServer
INFO   | jvm 1    | 2004/11/01 16:29:07 |
java.lang.NoClassDefFoundError:
com/lutris/appserver/server/sql/DatabaseManager
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
java.lang.Class.getDeclaredConstructors0(Native Method)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
java.lang.Class.privateGetDeclaredConstructors(Class.java:1590)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
java.lang.Class.getConstructor0(Class.java:1762)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
java.lang.Class.newInstance0(Class.java:276)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
java.lang.Class.newInstance(Class.java:259)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
com.lutris.appserver.server.httpPresentation.servlet.HttpPresentationServlet.initApplication(Unknown 
Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
com.lutris.appserver.server.httpPresentation.servlet.HttpPresentationServlet.init(Unknown 
Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.apache.tomcat.core.ServletWrapper$2.method(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.apache.tomcat.core.ServletWrapper.handleInvocation(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.apache.tomcat.core.ServletWrapper.loadServlet(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.apache.tomcat.core.Context.loadServlets(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.apache.tomcat.core.Context.setupLoadableServlet(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.enhydra.servlet.servletManager.ServletManager.start(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.enhydra.servlet.servletManager.ServletManager.startAllContexts(Unknown 
Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.enhydra.servlet.ServletContainer.readConfigFile(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.enhydra.servlet.ServletContainer.start(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
com.lutris.multiServer.MultiServer.start(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
com.lutris.multiServer.MultiServer.main(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
com.lutris.multiServer.Main.start(Unknown Source)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.tanukisoftware.wrapper.WrapperManager.startInner(WrapperManager.java:1737)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.tanukisoftware.wrapper.WrapperManager.handleSocket(WrapperManager.java:2305)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:2602)
INFO   | jvm 1    | 2004/11/01 16:29:07 |       at
java.lang.Thread.run(Thread.java:536)
INFO   | jvm 1    | 2004/11/01 16:29:07 | Exiting the server.
STATUS | wrapper  | 2004/11/01 16:29:10 | <-- Wrapper Stopped

So this idea of removing the dods-runtime.jar from classpath doesn't
seem to work, unfortunately :-(

Petr






--------------------------------------------------------------------------------


> --
> You receive this message as a subscriber of the enhydra@xxxxxxxxxxxxx 
> mailing list.
> To unsubscribe: mailto:enhydra-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws