[jboss-jira] [JBoss JIRA] Updated: (JBAS-3138) HAJNDI lookup fails intermittently from twiddle
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Mon Dec 15 18:30:54 EST 2008
[ https://jira.jboss.org/jira/browse/JBAS-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated JBAS-3138:
-----------------------------------
"Backlog" is correct Fix Version; "No Release" is for stuff that logically doesn't belong to a release.
> HAJNDI lookup fails intermittently from twiddle
> -----------------------------------------------
>
> Key: JBAS-3138
> URL: https://jira.jboss.org/jira/browse/JBAS-3138
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering, JMX, Naming
> Affects Versions: JBossAS-4.0.4.CR2, JBossAS-5.0.0.Beta1
> Environment: This bug is present in JBoss 3.2.6 and 4.0.3. To produce setup a two node cluster, such as in the lab-clustering. This bug is reproducable on Windows XP, Linux WS3, & Solaris 10.
> Reporter: Brian Stansberry
> Priority: Minor
> Fix For: Backlog
>
>
> Brian Egge reported in JBCLUSTER-83:
> Running twiddle against the HAJNDI port will sometimes fail, and sometimes work. It does not matter if you query the server which has the component, or the failover server. Both produce the same result. Using the standard JDNI port always works, if you query the correct server. Using the HAJNDI fails ~50% of the time:
> C:\JBossAdvancedJ2EE\labs\jboss-4.x\bin>twiddle --server=jnp://localhost:1200 get "jboss.mq.destination:name=A,service=Queue" ReceiversCount QueueName
> ReceiversCount=0
> QueueName=A
> C:\JBossAdvancedJ2EE\labs\jboss-4.x\bin>twiddle --server=jnp://localhost:1200 get "jboss.mq.destination:name=A,service=Queue" ReceiversCount QueueName
> ReceiversCount=0
> QueueName=A
> C:\JBossAdvancedJ2EE\labs\jboss-4.x\bin>twiddle --server=jnp://localhost:1200 get "jboss.mq.destination:name=A,service=Queue" ReceiversCount QueueName
> 12:26:40,320 ERROR [Twiddle] Exec failed
> javax.management.InstanceNotFoundException: jboss.mq.destination:name=A,service=Queue is not registered.
> at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:508)
> at org.jboss.mx.server.MBeanServerImpl.getAttributes(MBeanServerImpl.java:547)
> at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:251)
> at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:164)
> at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:805)
> at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406)
> at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> at sun.rmi.transport.Transport$1.run(Transport.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
> at java.lang.Thread.run(Thread.java:595)
> The JNDI port always works:
> C:\JBossAdvancedJ2EE\labs\jboss-4.x\bin>twiddle --server=jnp://localhost:1199 get jboss.mq.destination:name=A,service=Queue" ReceiversCount QueueName
> ReceiversCount=0
> QueueName=A
> C:\JBossAdvancedJ2EE\labs\jboss-4.x\bin>twiddle --server=jnp://localhost:1199 get "jboss.mq.destination:name=A,service=Queue" ReceiversCount QueueName
> ReceiversCount=0
> QueueName=A
> * In these examples, clust2 is running using the bind config port-01, which adds 100 to the ports. The bug is the same when on a single machine or multiple. The above examples are the same when using 1099/1100.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list