What if you were to start JavaDB as a service and make it a dependency
for the
GlassFish service?
http://support.microsoft.com/kb/193888
That sounds like exactly what the problem is. I don't really
know how we could
do anything on the OpenESB side to get around this, the timing of starting up
GF and
JavaDB is entirely controlled by GlassFish.
Frank Niedermann wrote:
Hi Mark,
I found out that the issue is related to the starting of GlassFish as
Windows Service:
http://wiki.glassfish.java.net/Wiki.jsp?page=FaqRunAsWindowsService
If we start GlassFish in NetBeans under the Servers tab it works,
BPEL-engine starts normally.
If we start GlassFish as Windows Service it won't work, BPEL-engine stays in
status stopped.
I have attached the server.log file of both actions above (NetBeans /
Windows Service).
*
http://n2.nabble.com/file/n3773680/MonitoringEnabled-NetBeans-BpelStarted_server.log
MonitoringEnabled-NetBeans-BpelStarted_server.log
*
http://n2.nabble.com/file/n3773680/MonitoringEnabled-WindowsService-BpelStopped_server.log
MonitoringEnabled-WindowsService-BpelStopped_server.log
What I see in the logs is that the BPEL-engine tries to connect to the
JavaDB on port 1527
which does not work:
[#|2009-10-06T09:57:54.604+0200|WARNING|sun-appserver2.1|javax.enterprise.resource.resourceadapter|_ThreadID=20;_ThreadName=sun-bpel-engine;bpelseNonXAPool;Connection
could not be allocated because: java.net.ConnectException: Fehler beim
Herstellen der Verbindung zum Server localhost am Port 1527. Nachricht:
Connection refused:
connect.;_RequestID=8f464842-30d8-4a1a-bda3-c96c92713617;|RAR5038:Unexpected
exception while creating resource for pool bpelseNonXAPool. Exception :
Connection could not be allocated because: java.net.ConnectException: Fehler
beim Herstellen der Verbindung zum Server localhost am Port 1527. Nachricht:
Connection refused: connect.|#]
I guess the Windows Service does not start the JavaDB or it starts too late
after the BPEL-engine,
could that be the reason?
Thanks,
Frank
Mark S White wrote:
Can you provide the server.log so that we can look to see if something
is going wrong?
Frank Niedermann wrote:
Hi,
we have enabled BPEL-monitoring in the GlassFish admin interface:
http://n2.nabble.com/file/n3768267/bpel-monitoring.jpg
After we have done this the BPEL-engine will not automatically start any
more if we restart GlassFish:
http://n2.nabble.com/file/n3768267/bpel-stopped.jpg
This behavior is reproduceable, if we disable BPEL-monitoring and restart
GlassFish the BPEL-engine will start as expected.
It is possible to manually start the BPEL-engine after GlassFish has
started, but we need to have all required components starting
automatically
because our backup software will reboot the machines on the weekend ...
Can somebody confirm this behavior or are we expecting some local issues?
Thanks,
Frank
--
OpenESB Community (http://open-esb.org)
Check out my blog (http://blogs.sun.com/mwhite)
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email] For additional
commands, e-mail: [hidden email]
