[JBoss JIRA] Created: (JBESB-2519) ServiceClient hides some errors which makes debugging config problems difficult
by toby cabot (JIRA)
ServiceClient hides some errors which makes debugging config problems difficult
-------------------------------------------------------------------------------
Key: JBESB-2519
URL: https://jira.jboss.org/jira/browse/JBESB-2519
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.4
Reporter: toby cabot
Priority: Minor
I …
[View More]accidentally mis-configured a node with a "-b" bind address of "0.0.0.0". This causes a pretty obvious problem for other nodes that want to connect to it - they try to connect to themselves. Unfortunately ServiceClient swallows the error data and just emits "Failed to get JMS Session from pool" which can have 3 different causes. For example:
2009-04-13 09:52:30,937 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Caught service lookup exception for EPR [JMSEpr [ PortReference < <wsa:Address jms://10.18.2.178:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.18.2.178:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] and Service [JBossESB-Internal:DeadLetterService] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://10.18.2.178:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.18.2.178:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 05576e08-115c-4233-b417-262b7b174c47 RelatesTo: jms:correlationID#05576e08-115c-4233-b417-262b7b174c47 ]]. Failed to get JMS Session from pool.
--
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
[View Less]
15 years, 10 months
[JBoss JIRA] Created: (JBESB-2522) twiddle get for ServiceMessageCounter causes NPE
by toby cabot (JIRA)
twiddle get for ServiceMessageCounter causes NPE
------------------------------------------------
Key: JBESB-2522
URL: https://jira.jboss.org/jira/browse/JBESB-2522
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.4
Reporter: toby cabot
Using twiddle to "get" ServiceMessageCounter properties trips a NullPointerException:
jboss-4.2.1.GA/bin$ ./twiddle.sh get jboss.…
[View More]esb:category=MessageCounter,deployment=jbossesb.esb,service-name=DeadLetterService
11:39:24,423 ERROR [Twiddle] Exec failed
java.lang.NullPointerException
at org.jboss.soa.esb.listeners.message.ServiceMessageCounter.getAttributes(ServiceMessageCounter.java:300)
at org.jboss.mx.server.RawDynamicInvoker.getAttributes(RawDynamicInvoker.java:140)
at org.jboss.mx.server.MBeanServerImpl.getAttributes(MBeanServerImpl.java:571)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
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:266)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
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:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
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:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
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:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:613)
--
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
[View Less]
15 years, 10 months
[JBoss JIRA] Created: (JBESB-2525) HttpRouter fire java.lang.NullPointerException if the Response is empty (204)
by Jurij (JIRA)
HttpRouter fire java.lang.NullPointerException if the Response is empty (204)
-----------------------------------------------------------------------------
Key: JBESB-2525
URL: https://jira.jboss.org/jira/browse/JBESB-2525
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Debian
Reporter: Jurij
[2009-04-16 18:04:53,353][DEBUG][pool-61-thread-2][header]<< "HTTP/1.…
[View More]1 204 No Content [\r][\n]"
[2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Content-Length: 000000000000000[\r][\n]"
[2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Server: IBM_CICS_Transaction_Server/3.1.0(zOS)[\r][\n]"
[2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Date: Thu, 16 Apr 2009 16:04:53 GMT[\r][\n]"
java.lang.NullPointerException
at org.jboss.soa.esb.actions.routing.http.HttpRouter.process(HttpRouter.java:118)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--
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
[View Less]
15 years, 10 months
[JBoss JIRA] Created: (JBESB-2503) Fix JMSEpr address encoding
by Kevin Conner (JIRA)
Fix JMSEpr address encoding
---------------------------
Key: JBESB-2503
URL: https://jira.jboss.org/jira/browse/JBESB-2503
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.4 CP2
Reporter: Kevin Conner
Fix For: 4.4 CP3
The JMSEpr encodes the JNDI URI/destination name but the code currently assumes that the URI consists of …
[View More]just a host:port pair rather than a full URI.
As a consequence, addresses such as jms://localhost:1414/SYSTEM.DEF.SVRCONN/queue/pt_bpmo1_start_esb are interpreted with a queue name of SYSTEM.DEF.SVRCONN/queue/pt_bpmo1_start_esb.
We need to modify the address encoding to make sure that the URI/destination name can be correctly encoded and retrieved from this information.
--
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
[View Less]
15 years, 10 months