]
Jiri Pechanec commented on JBESB-1531:
--------------------------------------
This issue will probably require live debugging on QE side as it is difficult to create
standalone test case. But to reproduce the problem following conditions must be used
1) There is a service that deploys jBPM process
2) There is a service that starts jBPM process
3) Both services uses TRANSACTED jms-jca provider
Result
NullPointerException is generate probably inside JBM code - not proved, if it is so will
be mostly JBM issue
This issue maybe represents some extrem condition for JBM inside XA transaction
Sometimes the message delivery fails for the first time
-------------------------------------------------------
Key: JBESB-1531
URL:
http://jira.jboss.com/jira/browse/JBESB-1531
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Adapters
Affects Versions: 4.2.1
Environment: standalone-soa-4.2.0.CR2.zip
Reporter: Jiri Pechanec
Assigned To: Mark Little
Attachments: server.log.gz, tc.zip
Sometimes it happens that message is sent to GW but it goes to RDLQ because of
unresponsive EPR.
On the second attempt whel delivery is tried from RDLQ then it succeds. The log says
2008-02-05 11:17:58,037 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Badly formed EPR
[JMSEpr [ PortReference < <wsa:Address
jms://127.0.0.1:1099/queue/quickstart_jca_bpm_esb/>, <wsa:ReferenceProperties
jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>,
<wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>,
<wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs :
org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties
jbossesb:destination-type : queue/>, <wsa:ReferenceProperties
jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties
jbossesb:connection-factory : XAConnectionFactory/>, <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/> > ]] for
Service [FirstServiceESB:SimpleListener] and Message [header: [ To: JMSEpr [ PortReference
< <wsa:Address jms://127.0.0.1:1099/queue/quickstart_jca_bpm_esb/>,
<wsa:ReferenceProperties jbossesb:java.naming.factory.initial :
org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties
jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties
jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>,
<wsa:ReferenceProperties jbossesb:destination-type : queue/>,
<wsa:ReferenceProperties jbossesb:specification-version : 1.1/>,
<wsa:ReferenceProperties jbossesb:connection-factory : XAConnectionFactory/>,
<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: ID:JBM-37377 ]].
java.lang.NullPointerException
Why there is NullPointerException thrown in the courrier first time bu not on redelivery?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: