[jboss-jira] [JBoss JIRA] Commented: (JBAS-6431) REGRESSION: org.jboss.test.mdbsessionpoolclear.test.MDBUnitTestCase

Jay Howell (JIRA) jira-events at lists.jboss.org
Thu Jan 29 15:28:44 EST 2009


    [ https://jira.jboss.org/jira/browse/JBAS-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12450307#action_12450307 ] 

Jay Howell commented on JBAS-6431:
----------------------------------

The problem that I see debugging the case is that the onmessage method is marked as non-transactional.

In the JMSActivation in the inflow, we set deliveryTransacted as...

this.isDeliveryTransacted = endpointFactory.isDeliveryTransacted(ONMESSAGE);

Which calls down into JBossMessageEndpoint,

public boolean isDeliveryTransacted(Method method) throws NoSuchMethodException
   {
      boolean result = false;
      int transType = metaData.getMethodTransactionType(method.getName(), method.getParameterTypes(), InvocationType.LOCAL);
      if (transType == MetaData.TX_REQUIRED)
         result = true;
      if (trace)
         log.trace("isDeliveryTransacted " + container.getBeanMetaData().getContainerObjectNameJndiName() + " method=" + method + " result=" + result);
      return result;
   }

So what is happening is that because the the OnMessage is not set for TX_REQUIRED, the it never gets committed.

OnMessage should be set for TX_REQUIRED by default, which should set the return is isDeliveryTransacted=true.

I'm still picking through the case. but I wanted to give you an update.

Jay:) 

> REGRESSION:  org.jboss.test.mdbsessionpoolclear.test.MDBUnitTestCase
> --------------------------------------------------------------------
>
>                 Key: JBAS-6431
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6431
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Shelly McGowan
>            Assignee: Jay Howell
>             Fix For: JBossAS-5.0.1.GA
>
>
> The test case, testMdb, is failing consistently in the AS testsuite runs. 
> junit.framework.AssertionFailedError: expected:<2> but was:<3>
> 	at org.jboss.test.mdbsessionpoolclear.test.MDBUnitTestCase.testMdb(MDBUnitTestCase.java:144)
>  The regression started  to occur after fix JBAS-6343 was committed.  Jay, can you take a look at this failure and comment.   

-- 
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