[JBoss-user] [Messaging, JMS JBossMQ] - Re: JNDI service loses bindings

2004-11-23 Thread bene.net 
Hi Adrian,

thanks a lot for your reply!

An interesting fact to notice is that the problem occurs without any 
modification of JBoss configuration and without anyone deploying anything. 
1. JBoss startup - no exceptions (I assume the jndi context is correctly 
configured then)
2. JBoss is just running for lets say 40 days (I don't know the exact time yet, 
probably its different on each instance) even without load (no message is 
posted to the queue at all!)
3. No files are deployed, undeployed or redeployed. No configuration files are 
modified during the whole 40 days.
4. Suddenly the bindings are missing.

We set up a SNMP monitoring for the JMS queue, so if the problem occurs again 
on one of the over 60 JBoss instances, we will immediately be notified. We are 
hoping to find a hint what event causes the bindings to be removed.

With kind regards,
Ben


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856054#3856054

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856054


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] [Messaging, JMS JBossMQ] - JNDI service loses bindings

2004-11-19 Thread bene.net 
we are using JBoss (build: CVSTag=JBoss_3_2_1 date=200305041533) on over 60 
servers at a customer site.
OS is Linux 2.4.19-4GB, Java VM 1.4.1_02-b06

After JBoss startup the JNDI tree contains the following bindings, whereas 
after a certain time the same JNDI tree does no longer contain them (listings 
received from jmx-console):
java namespace:
java:/XAConnectionFactory
java:/ConnectionFactory
java:/jaas/jbossmq

global namespace:
  +- OIL2XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
  +- HTTPXAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
  +- ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
  +- HTTPConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
  +- XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
  +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
  +- UILXAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
  +- RMIXAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
  +- UIL2XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
  +- topic (class: org.jnp.interfaces.NamingContext)
  |   +- testDurableTopic (class: org.jboss.mq.SpyTopic)
  |   +- testTopic (class: org.jboss.mq.SpyTopic)
  |   +- securedTopic (class: org.jboss.mq.SpyTopic)
  +- queue (class: org.jnp.interfaces.NamingContext)
  |   +- A (class: org.jboss.mq.SpyQueue)
  |   +- ReplicationQueue (class: org.jboss.mq.SpyQueue)
  |   +- testQueue (class: org.jboss.mq.SpyQueue)
  |   +- ex (class: org.jboss.mq.SpyQueue)
  |   +- DLQ (class: org.jboss.mq.SpyQueue)
  |   +- D (class: org.jboss.mq.SpyQueue)
  |   +- C (class: org.jboss.mq.SpyQueue)
  |   +- B (class: org.jboss.mq.SpyQueue)
  +- UIL2ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
  +- UILConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
  +- RMIConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
  +- OIL2ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)

What event causes the JNDI service to lose the JMS related bindings?
The missing bindings causes a an exception (given below) which is repeated 
every 10 seconds, which causes my logfiles to grow very fast. This is the 
reason why I could not yet identify which event caused the loss of the bindings.

The following exception does not occur on JBoss startup! (thus this topic is 
not related to all the other 'XAConnectionFactory not bound' posts I found)


  | INFO; 2004-11-17 20:01:46,039; 
[org.jboss.system.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:265)]; 
Destroying
  |   INFO; 2004-11-17 20:01:46,043; 
[org.jboss.system.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:283)]; 
Destroyed
  |  DEBUG; 2004-11-17 20:01:46,047; 
[org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:383)];
 Initializing
  |  DEBUG; 2004-11-17 20:01:46,051; 
[org.jboss.ejb.plugins.jms.JMSContainerInvoker.getJMSProviderAdapter(JMSContainerInvoker.java:804)];
 Looking up provider adapter: java:/DefaultJMSProvider
  |  DEBUG; 2004-11-17 20:01:46,056; 
[org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:387)];
 Provider adapter: [EMAIL PROTECTED]
  |  TRACE; 2004-11-17 20:01:46,062; 
[org.jboss.system.ServiceMBeanSupport.init(ServiceMBeanSupport.java:70)]; 
Constructing
  |   INFO; 2004-11-17 20:01:46,066; 
[org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:154)]; 
Creating
  |  DEBUG; 2004-11-17 20:01:46,070; 
[org.jboss.jms.jndi.JBossMQProvider.getInitialContext(JBossMQProvider.java:89)];
 no provider url; connecting to local JNDI
  |  DEBUG; 2004-11-17 20:01:46,094; 
[org.jboss.jms.jndi.JBossMQProvider.getInitialContext(JBossMQProvider.java:106)];
 created context: [EMAIL PROTECTED]
  |  ERROR; 2004-11-17 20:01:46,099; 
[org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:163)]; 
Initialization failed
  |  javax.jms.JMSException: Error creating the dlq connection: 
XAConnectionFactory not bound
  | at 
org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
  | at 
org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
  | at 
org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:394)
  | at 
org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:579)
  | at 
org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1079)
  | at 
org.jboss.ejb.plugins.jms.JMSContainerInvoker$1.run(JMSContainerInvoker.java:591)
  |  INFO; 2004-11-17 20:01:46,105; 
[org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1082)];
 Reconnected to JMS provider
  |   WARN; 2004-11-17 20:01:46,110; 
[org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1059)];
 JMS provider failure detected: 
  |  javax.jms.JMSException: