[jboss-user] [Clustering/JBoss] - Re: clustering/JMS problem among machines not using same par

[bstansberry@jboss.com]

What is going on in here?


  | 10:12:57,502 ERROR [STDERR]     at javax.naming.InitialContext.lookup(InitialContext.java:351)
  | 10:12:57,502 ERROR [STDERR]     at kdcs.timers.QuartzJob.jobInvoiceHandlerJob(QuartzJob.java:797)
  | 10:12:57,502 ERROR [STDERR]     at kdcs.timers.QuartzJob.createJobAndTrigger(QuartzJob.java:849)
  | 10:12:57,502 ERROR [STDERR]     at kdcs.timers.QuartzJob.startSingleton(QuartzJob.java:390)
  | 

That is, what environment properties are being passed to new InitialContext(Hashtable props) before the lookup call is made?

You commented that the following are set in hajndi-ds.xml:

jnp.partitionName=${jboss.partition.name:DefaultPartition}
jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4} 

but your stack trace doesn't involve the JMSProviderLoader.  Make sure the equivalent entries are in the environment properties you pass to new InitialContext. I suspect an HA-JNDI auto discovery call is getting a response from a "wizard" server which AIUI is not meant to be involved. If the "wizard" server has a different partition name and you include jnp.partitionName=${jboss.partition.name:DefaultPartition} you won't get an auto discovery response from "wizard" and won't try to connect to it.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208244#4208244

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208244