[esb-issues] [JBoss JIRA] Commented: (JBESB-1531) Sometimes the message delivery fails for the first time

Kevin Conner (JIRA) jira-events at lists.jboss.org
Fri Jul 18 12:04:52 EDT 2008


    [ https://jira.jboss.org/jira/browse/JBESB-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12421893#action_12421893 ] 

Kevin Conner commented on JBESB-1531:
-------------------------------------

>From examining the messaging code it would appear that this is the only method that does not protect itself from missing transactions.

For example, the addAck method does the following

     ClientTransaction tx = getTxInternal(xid);
      
      if (tx == null)
      {
         throw new JMSException("There is no transaction with id " + xid);
      }


Whereas addMessage is as follows

      ClientTransaction tx = getTxInternal(xid);
      
      tx.addMessage(sessionId, m);

I will do some more investigation but it is definitely looking like a messaging issue.

> Sometimes the message delivery fails for the first time
> -------------------------------------------------------
>
>                 Key: JBESB-1531
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1531
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Adapters, Rosetta
>    Affects Versions: 4.2.1
>         Environment: standalone-soa-4.2.0.CR2.zip
>            Reporter: Jiri Pechanec
>            Assignee: Kevin Conner
>             Fix For: 4.4
>
>         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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       




More information about the esb-issues mailing list