Mailing-List: contact kandula-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <1824201234.1237132610542.JavaMail.jira@brutus>
Date: Sun, 15 Mar 2009 08:56:50 -0700 (PDT)
From: "Thilina Gunarathne (JIRA)" <jira@apache.org>
To: kandula-dev@ws.apache.org
Subject: [jira] Commented: (KAND-7) Prepare method is not getting called due
 to code issue in TransactionInHandler class for AtomicTransaction
In-Reply-To: <931358358.1237026470690.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KAND-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682158#action_12682158 ] 

Thilina Gunarathne commented on KAND-7:
---------------------------------------

Hi Jayanta,
This is great... I'll look in to it. 

You need to submit this change as a patch. You can generate the patch using "svn diff > patch.txt".  Then attach the patch to this Jira. When attaching make sure to check the box which gives the copyrights to Apache.  These steps are needed for the legal aspects.

Keep up the good work!!!

thanks,
Thilina


> Prepare method is not getting called due to code issue in TransactionInHandler class for AtomicTransaction
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: KAND-7
>                 URL: https://issues.apache.org/jira/browse/KAND-7
>             Project: Kandula
>          Issue Type: Bug
>         Environment: Tomcat server, Axis2, Kandula2, JDK1.6
>            Reporter: Jayanta Sarkar
>            Assignee: Thilina Gunarathne
>            Priority: Blocker
>
> Two participant services have been hosted in two tomcat servers which are inserting data in two different tables in the same database.
> The main service calls these two participant services one by one within same transaction.
> In tcpmon it has been observed that all the call flow works fine but when the prepare message goes to the participant services the prepare method does not get executed. After going through the source code that the following code fix inside TransactionInHandler class under org.apache.kandula.participant package. The code to be addes is marked after "//added by Jayanta".
> public InvocationResponse invoke(MessageContext msgContext) throws AxisFault {
> KandulaResource resource;
> String wsaAction = msgContext.getWSAAction();
> if (!(Constants.WS_COOR_CREATE_COORDINATIONCONTEXT.equals(wsaAction)) 
> && !(Constants.
> WS_COOR_REGISTER.equals(wsaAction)) 
> && !(Constants.
> WS_AT_COMMIT.equals(wsaAction)) && !(Constants.WS_AT_ROLLBACK.equals(wsaAction)) 
> //added by Jayanta 
> &&!(Constants.WS_AT_PREPARE.equals(wsaAction))){
> If the above line is added then it works fine. The prepare method gets called. Then the commit method gets called. In case exception the rollback method also works fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org