-
1. Re: Problem while shutting down JBoss Server with JBossESB
marklittle Apr 8, 2008 1:09 PM (in response to puneetjain)How did you shutdown AS and how reproducible is this?
-
2. Re: Problem while shutting down JBoss Server with JBossESB
puneetjain Apr 8, 2008 5:33 PM (in response to puneetjain)Hi,
Thanks for your reply
I shutdown the JBoss Application server by pressing Ctrl+C.
The exception comes every time I shutdown my server.
Thanks,
Puneet -
3. Re: Problem while shutting down JBoss Server with JBossESB
tfennelly Apr 9, 2008 6:53 AM (in response to puneetjain)First off... the ESB is not yet "certified" to run on v4.2.2.GA of JBoss AS. But anyway....
Do you get this exception on shutdown of a clean AS?
Do you get this exception on shutdown of a clean AS + JBoss ESB Components (minus Your.esb)?
Do you get this exception on shutdown of a clean AS + JBoss ESB Components + Your.esb? -
4. Re: Problem while shutting down JBoss Server with JBossESB
puneetjain Apr 9, 2008 7:25 AM (in response to puneetjain)Hi tfennelly,
Thanks for you help.
I got this exception on Shutting down of Clean AS + JBoss ESB Components + My .esb.
Secondly, I have tried to write my application with new HttpRouter. Its working fine.
I went through the documentation as well as the javadoc of Jboss4.2.1GA but have not been able to find any router other than HttpRouter.
Is HttpRouter the most efficient way to call an external Http page using JBoss ESB or else is there any other router available? Please help.
My senerio is:
[Browser]---http--->[JBossESB(on JBossAS)]-----http--->[Servlet]----->[EJB3]
Thanks,
Puneet -
5. Re: Problem while shutting down JBoss Server with JBossESB
tfennelly Apr 9, 2008 7:30 AM (in response to puneetjain)Can you answer the other questions too please...
Do you get this exception on shutdown of a clean AS?
Do you get this exception on shutdown of a clean AS + JBoss ESB Components (minus Your.esb)?
As for the Router questions, please create another thread and we can discuss that there. -
6. Re: Problem while shutting down JBoss Server with JBossESB
puneetjain Apr 10, 2008 2:08 AM (in response to puneetjain)Hi tfennelly,
Thanks for your valuable time, your inputs helped me a lot in my work.
I have checked the Application Server for all three scenarios. The exception is raised for last two scenarios i.e.:
Clean AS + JBossESB Components and
Clean AS + JBossESB Components + My .esb file.
Secondly, I observed that if we hot deploy the JBossESB components by executing 'ant deploy' command from <jbossesb_home>/install directory, server throws an exception while deploying jbpm package.11:04:14,383 INFO [JBoss4ESBDeployer] create esb service, jbpm.esb 11:04:14,414 INFO [CallbackQueue] Bound to JNDI name: queue/CallbackQueue 11:04:14,430 INFO [JbpmConfiguration] using jbpm configuration resource 'jbpm.cfg.xml' 11:04:14,539 INFO [StaleObjectLogConfigurer] stale object exceptions will be hidden from logging 11:04:14,633 WARN [ServiceController] Problem starting service jboss:service=h2,database=jbpmDB java.lang.ClassNotFoundException: No ClassLoaders found for: org.h2.Driver at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.internal.soa.esb.dependencies.H2Database.getConnection(H2Database.java:302)
The exception may be thrown because JBoss Application Server couldn’t load the h2.jar at runtime which is required for org.h2.Driver class.
Please have a look.
Thanks,
Puneet -
7. Re: Problem while shutting down JBoss Server with JBossESB
kconner Apr 16, 2008 2:13 PM (in response to puneetjain)The original stack trace is caused by the mail JCA adapter and is not a part of the ESB. Are you using this adapter in your application?
You will not be able to 'hot deploy' the core services using that script as the h2.jar is placed into the /lib directory of the server instance. The jars in this directory are not hot deployable. If you were to place the jar in that directory before starting up the application server then it should work.
Kev