users@glassfish.java.net

Glassfish cluster startup errors

From: <glassfish_at_javadesktop.org>
Date: Tue, 27 Nov 2007 22:25:16 PST

Every time I start my cluster, the following errors show up in the logs. Does anybody know:

1) What do they mean?
2) Why is it happening?
3) Is it a problem?

Here are the errors:

[root_at_glassfish1 ~]# asadmin start-cluster cluster1
The clustered instance, g1-i1, was successfully started.
error 0 [#|2007-11-29T00:44:06.910-0500|WARNING|sun-appserver9.1|javax.jms|_ThreadID=10;_ThreadName=main;_RequestID=edf72a64-d5b8-418c-b962-952255fbb9b7;|[C4003]: Error occurred on connection creation [localhost:37676]. - cause: java.net.ConnectException: Connection refused|#]

error 1 [#|2007-11-29T00:44:10.307-0500|WARNING|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=12;_ThreadName=pool-1-thread-4;TimerBean;_RequestID=5bd0273b-a4ef-43ca-aa62-e35da861df88;|EJB5108:Unable to initialize EJB Timer Service. The likely cause is the database has not been started or the timer database table has not been created.|#]

error 2 [#|2007-11-29T00:44:10.976-0500|WARNING|sun-appserver9.1|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;__CallFlowPool;_RequestID=edf72a64-d5b8-418c-b962-952255fbb9b7;|RAR5005:Error in accessing XA resource with JNDI name [__CallFlowPool] for recovery|#]

The clustered instance, g2-i1, was successfully started.
error 0 [#|2007-11-28T00:45:53.340-0500|WARNING|sun-appserver9.1|javax.jms|_ThreadID=10;_ThreadName=main;_RequestID=53d25f8d-333a-4b54-b459-ecdaa3aa6931;|[C4003]: Error occurred on connection creation [localhost:37676]. - cause: java.net.ConnectException: Connection refused|#]

error 1 [#|2007-11-28T00:45:55.731-0500|WARNING|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=12;_ThreadName=pool-1-thread-4;TimerBean;_RequestID=1a58eab6-8d54-417c-8598-4b9936d2e9dc;|EJB5108:Unable to initialize EJB Timer Service. The likely cause is the database has not been started or the timer database table has not been created.|#]

error 2 [#|2007-11-28T00:45:56.473-0500|WARNING|sun-appserver9.1|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;__CallFlowPool;_RequestID=53d25f8d-333a-4b54-b459-ecdaa3aa6931;|RAR5005:Error in accessing XA resource with JNDI name [__CallFlowPool] for recovery|#]

The clustered instance, g3-i1, was successfully started.
error 0 [#|2007-11-28T00:53:38.883-0500|WARNING|sun-appserver9.1|javax.jms|_ThreadID=10;_ThreadName=main;_RequestID=268c06df-2c03-4044-865b-2a4465ed13be;|[C4003]: Error occurred on connection creation [localhost:37676]. - cause: java.net.ConnectException: Connection refused|#]

error 1 [#|2007-11-28T00:53:41.194-0500|WARNING|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=15;_ThreadName=pool-1-thread-3;TimerBean;_RequestID=dacc7ec0-c43a-4806-81b6-f50d093ab07e;|EJB5108:Unable to initialize EJB Timer Service. The likely cause is the database has not been started or the timer database table has not been created.|#]

error 2 [#|2007-11-28T00:53:42.040-0500|WARNING|sun-appserver9.1|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;__CallFlowPool;_RequestID=268c06df-2c03-4044-865b-2a4465ed13be;|RAR5005:Error in accessing XA resource with JNDI name [__CallFlowPool] for recovery|#]

Command start-cluster executed successfully.

I've tried using "asadmin start-database" but the the error with "...likely cause is the database has not been started..." still occurs.

I'm not using EJB Timer or JMS in my application. Can I safely disable these so the errors will go away? Or are they used by the admin GUI in some fashion? Also, what is the __CallFlowPool and do I need it?

Thanks!
[Message sent by forum member 'rwillie6' (rwillie6)]

http://forums.java.net/jive/thread.jspa?messageID=247509