Hi Sarkar,I'd be glad to help u out. I'm stuck with some assignments now :(.. I will get back to u after having a look at your messages tonight.
thanks, Thilina On Wed, Feb 25, 2009 at 1:09 PM, Sarkar, Jayanta (Cognizant) < [email protected]> wrote: > Hi Thilina, > > Many many thanks for your reply and guidance. There is absolutely no > problem in sharing the tcpmon results. With your suggestions below I have > progressed a lot but still it is not working fully. I am attaching the > tcpmon results along with this mail. I would like to inform you the > following points. > > The main service and the kandula service is running in same machine and it > is running under 8080 port. For this I have set the following values in * > "endpoints.conf"* file: > host=127.0.0.1 > port=8081 > tcpmon_enable=true > > COORDINATOR_REPOSITORY=C:/Jayanta/apache-tomcat-6.0.18/webapps/axis2/WEB-INF/testing-repository > > COORDINATOR_AXIS2XML=C:/Jayanta/apache-tomcat-6.0.18/webapps/axis2/WEB-INF/testing-repository/axis2.xml > > PARTICIPANT_REPOSITORY=C:/Jayanta/apache-tomcat-6.0.18/webapps/axis2/WEB-INF/testing-repository/ > > PARTICIPANT_AXIS2_CONF=C:/Jayanta/apache-tomcat-6.0.18/webapps/axis2/WEB-INF/testing-repository/axis2.xml > > KANDULA_LISTENER_REPOSITORY=C:/Jayanta/apache-tomcat-6.0.18/webapps/axis2/WEB-INF/initiator-repository > > KANDULA_LISTENER_AXIS2XML=C:/Jayanta/apache-tomcat-6.0.18/webapps/axis2/WEB-INF/initiator-repository/axis2.xml > KANDULA_LISTENER_PORT=5051 > > One participant service is running in 8060 port and another in 8070 port. > When I set the above same values in the endpoints.conf file in the > participant services I get the tcpmon results as attached in the file * > "tcpmonResults1.txt"*. > > But when I change the port value in the participant side as below: > host=127.0.0.1 > port=8060 > tcpmon_enable=false > > I get the tcpmon results as attached in the tcpmonResults2.txt. > > Also I am attaching the services.xml fine at the participant side. > > The problem is now the prepare or commit methods at the participant side > are not getting called. Could you please look into this and let me know what > next I should do. I have not deployed any kandula related services file > (.aar) at the participant side except the kandula-inflow module. > > * Thanks & regards, > Jayanta Sarkar > Java CoE, Cognizant Technology Solutions > Vnet: 306271, Cell: 91-9432360150 > Email: [email protected] > * > > ------------------------------ > *From:* Thilina Gunarathne > *Sent:* Mon 2/23/2009 9:26 PM > *To:* Sarkar, Jayanta (Cognizant) > *Cc:* Kandula > > *Subject:* Re: Urgent help needed for Axis2 with Kandula2 > > Hi Sarkar, Sending the SOAP envelops from the tcpmon will help a lot to > figure out the issues, hoping that they do not contain any confidential > details.. > > Looks like you have almost got it to working. Can you also let me know the > message sequence? Did you see the vote going on for 2-phase commit and that > the participant services respond to the vote? What was the outcome of the > vote? Apologies for the list of questions, I'm just trying to understand > the issue you are facing. > > For Participant side: >> >> 1. The service class extends KandulaAtomicResource. >> > Hope you are specifying the same class as the kandula resource in the > services.xml. > >> >> 2. Engaged modules addressing and kandula-inflow. >> >> I have deployed the following .aar files at both parent side and >> participant side: >> > You will need to deploy the kandula services only in the coordinator > machine. It can be independent of the parent or the participant services. > >> >> ActivationCoordinator.aar >> AtomicTransactionCoordinator.aar >> > CompletionCoordinator.aar > >> RegistrationCoordinator.aar >> > IIRC you only need the above services for atomic transactions. > > thanks, > Thilina > > >> >> AtomicTransactionParticipant.aar >> BACoordinator.aar >> BACoordinatorCompletionParticipant.aar >> >> InsertOneService.aar >> >> >> Please let me know where I am going wrong. I can send you the resultant >> soap envelopes from the tcpmon. The latest is happening is the call does not >> go to participant services for final commit or rollback. >> >> * Thanks & regards, >> Jayanta Sarkar >> Java CoE, Cognizant Technology Solutions >> Vnet: 306271, Cell: 91-9432360150 >> Email: [email protected] >> * >> >> ------------------------------ >> *From:* Thilina Gunarathne >> *Sent:* Sat 2/21/2009 2:40 AM >> *To:* Kandula; [email protected] >> *Subject:* Fwd: Urgent help needed for Axis2 with Kandula2 >> >> >> >> ---------- Forwarded message ---------- >> From: Thilina Gunarathne <[email protected]> >> Date: Fri, Feb 20, 2009 at 4:09 PM >> Subject: Re: Urgent help needed for Axis2 with Kandula2 >> To: "Sarkar, Jayanta (Cognizant)" <[email protected]> >> >> >> Hi Sarkar, >> Can u explain me what you have done up to now... Do u have the coordinator >> web service deployed? If so does ur parent web service creates a transaction >> (tx.begin() ) with it before calling the clients. Do u have kandula handlers >> engaged in invocation path of the parent web service and in the participant >> web srevices? >> >> thanks, >> Thilina >> >> PS: I prefer if u can use the kandula mailing list for questions. In there >> you will get answered by many more people and the answers u get will be >> useful to many more people too.. >> >> On Fri, Feb 20, 2009 at 4:05 PM, Sarkar, Jayanta (Cognizant) < >> [email protected]> wrote: >> >>> Hi Thilina, >>> >>> I am desperately looking for some urgent help on Kandula2 Atomic >>> Transaction using Axis2 in tomcat server. I have created to participant web >>> services which are updating same database. And I have created one parent web >>> service which calls these two participant web services under one >>> transaction. But it is not working. Could you please guide me what steps >>> need to be followed to set up this? >>> >>> * Thanks & regards, >>> Jayanta Sarkar >>> Java CoE, Cognizant Technology Solutions >>> Vnet: 306271, Cell: 91-9432360150 >>> Email: [email protected] >>> * >>> >>> This e-mail and any files transmitted with it are for the sole use of the >>> intended recipient(s) and may contain confidential and privileged >>> information. >>> If you are not the intended recipient, please contact the sender by reply >>> e-mail and destroy all copies of the original message. >>> Any unauthorised review, use, disclosure, dissemination, forwarding, >>> printing or copying of this email or any action taken in reliance on this >>> e-mail is strictly >>> prohibited and may be unlawful. >>> >> >> >> >> -- >> Thilina Gunarathne - http://thilinag.blogspot.com/ >> >> >> >> -- >> Thilina Gunarathne - http://thilinag.blogspot.com/ >> This e-mail and any files transmitted with it are for the sole use of >> the intended recipient(s) and may contain confidential and privileged >> information. >> If you are not the intended recipient, please contact the sender by reply >> e-mail and destroy all copies of the original message. >> Any unauthorised review, use, disclosure, dissemination, forwarding, >> printing or copying of this email or any action taken in reliance on this >> e-mail is strictly >> prohibited and may be unlawful. >> > > > > -- > Thilina Gunarathne - http://thilinag.blogspot.com/ > > This e-mail and any files transmitted with it are for the sole use of the > intended recipient(s) and may contain confidential and privileged > information. > If you are not the intended recipient, please contact the sender by reply > e-mail and destroy all copies of the original message. > Any unauthorised review, use, disclosure, dissemination, forwarding, > printing or copying of this email or any action taken in reliance on this > e-mail is strictly > prohibited and may be unlawful. > -- Thilina Gunarathne - http://thilinag.blogspot.com
