glassfish - asadmin start-domain fails when remote JMS queue is unreachable -
i have 2 servers , b running glassfish 3.1.2.2 application server on them. both use jms queue communication, works fine far. if network connection breaks reason, can see in logs of server b (the 1 configured connect remote queue of a) tries reconnect , successful in doing again.
but problem is, if try restart glassfish instance on b while server unreachable, startup process fail after retries , remains stuck in kind of undefined/unusable state, i.e. java process started, ports open applications not started - not administration console.
imho glassfish startup process should not wait queues connect, should done in kind of background process.
has of experienced similar? there can configure/tune fix behaviour?
never mind, seems have fixed :( after restarting computer,removing deployed ear , deploying again worked. haven't experienced behaviour since then.
Comments
Post a Comment