users@glassfish.java.net

Re: Glassfish v2 clustering problem with JMS

From: <glassfish_at_javadesktop.org>
Date: Mon, 06 Aug 2007 13:17:49 PDT

Ah. Thanks for domain.xml.

It seems that the section:

<server config-ref="cluster1-config" lb-weight="100" name="instance-ONE" node-agent-ref="cluster1-nodeagent">
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="MEjbApp"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="__ejb_container_timer_app"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="__JWSappclients"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="WSTXServices"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="JBIFramework"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="clusterjsp" virtual-servers="server"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="j2core"/>
<resource-ref enabled="true" ref="jdbc/__CallFlowPool"/>
<resource-ref enabled="true" ref="jdbc/j2core"/>
<resource-ref enabled="true" ref="jdbc/isppower"/>
<resource-ref enabled="true" ref="jms/QueueConnectionFactory"/>
<resource-ref enabled="false" ref="jms/StatementMDB"/>
<resource-ref enabled="false" ref="jms/AuditQueue"/>
<resource-ref enabled="false" ref="jms/ISPCollectionInfoChangeQueue"/>
<resource-ref enabled="false" ref="jms/ISPCustomerChangeQueue"/>
<resource-ref enabled="false" ref="jms/ISPCustomerMigrateQueue"/>
<resource-ref enabled="false" ref="jms/ISPJournalItemChangeQueue"/>
<resource-ref enabled="false" ref="mail/ZumaMailSession"/>
<resource-ref enabled="false" ref="jms/StatementMDBFactory"/>
<resource-ref enabled="false" ref="jms/TaskRunnerMDBFactory"/>
<resource-ref enabled="false" ref="jms/TaskRunnerMDB"/>
<system-property name="HTTP_LISTENER_PORT" value="1110"/>
<system-property name="HTTP_SSL_LISTENER_PORT" value="2220"/>
<system-property name="IIOP_SSL_LISTENER_PORT" value="4440"/>
<system-property name="IIOP_LISTENER_PORT" value="3330"/>
<system-property name="JMX_SYSTEM_CONNECTOR_PORT" value="8687"/>
<system-property name="IIOP_SSL_MUTUALAUTH_PORT" value="5550"/>
</server>

misses the JMS_PROVIDER_PORT.

Can you please do the following:

- start the doman.
- asadmin create-system-properties --target instance-ONE JMS_PROVIER_PORT=12345 (or any available port).
- start the node-agent thus: [b]asadmin start-node-agent --syncinstances node-agent-name[/b].
  this will in turn start your cluster.

This seems to be a bug and I am curious how you missed this system property because it
should have been taken care of, automatically.

Regards,
Kedar
[Message sent by forum member 'km' (km)]

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