ws-kandula-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dasarath Weeratunge <dweer...@purdue.edu>
Subject Fwd: Re: Help for Kandula 1
Date Thu, 04 Oct 2007 14:14:56 GMT


----- Forwarded message from Dasarath Weeratunge <dweeratu@purdue.edu> -----
    Date: Thu,  4 Oct 2007 10:14:40 -0400
    From: Dasarath Weeratunge <dweeratu@purdue.edu>
Reply-To: Dasarath Weeratunge <dweeratu@purdue.edu>
 Subject: Re: Help for Kandula 1
      To: Dominik Heller <Dominik.Heller@gmx.net>

Quoting Dominik Heller <Dominik.Heller@gmx.net>:

If the context is missing the problem is with your deployment of handlers.
Also make sure to deploy WS-Addressing handlers.

-- Dasarath



> Hi Hannes,
> so I monitored the whole szenario and this is the outcome. the client
> (initiator) send this message to the web service on the server:
> 
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <credit>
> <ns1:in0 xmlns:ns1="http://ws">0</ns1:in0>
> <ns2:in1 xmlns:ns2="http://ws">100.0</ns2:in1>
> </credit>
> </soapenv:Body>
> </soapenv:Envelope>
> 
> As of my understanding the context of the transaction should be send with it,
> right? The response is an axisfault message and by printing out the Status of
> the transaction on the serverside the value is 6 for NO_TRANSACTION. Any
> idea?
> 
> THX so much
> -Dominik
> 
> -------- Original-Nachricht --------
> > Datum: Thu, 04 Oct 2007 13:36:10 +0200
> > Von: Hannes Erven <hannes@erven.at>
> > An: Dominik Heller <Dominik.Heller@gmx.net>
> > CC: kandula-dev@ws.apache.org
> > Betreff: Re: Help for Kandula 1
> 
> > Hi Dominik,
> > 
> > 
> > > Exception in thread "main" AxisFault
> > >  faultCode:
> > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > >  faultSubcode: 
> > >  faultString: java.rmi.RemoteException
> > >  faultActor: 
> > >  faultNode: 
> > >  faultDetail: 
> > > 	{http://xml.apache.org/axis/}hostname:sal
> > > 
> > > java.rmi.RemoteException
> > [...]
> > > 	at
> >
> kandula.BankOneTestSoapBindingStub.test1(BankOneTestSoapBindingStub.java:98)
> > > 	at com.seitenbau.test.Tester.main(Tester.java:16)
> > > 
> > > --> When the rmi exception occurs after waiting a few seconds I get this
> > message on the console:
> > > 
> > > [BankOneTestSoapBindingImpl] tx1
> > > [CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
> > > _org.apache.kandula.coordinator.at.TransactionManagerImpl@19ba640_
> > > [BankOne] credit(0, 100.0)
> > > [ATCoordinatorImpl] timeout ACTIVE
> > 
> > 
> > This looks more or less good ;-)
> > 
> > I suggest you check the server side logs or console for hints why the 
> > exception is thrown. The log messages you see all originate from the 
> > client and look OK.
> > 
> > In many cases it helps to look at the SOAP traffic using the TCPMonitor 
> > that comes with WTP.
> > 
> > 
> > Gutes Gelingen,
> > -hannes
> 
> -- 
> Psssst! Schon vom neuen GMX MultiMessenger gehört?
> Der kanns mit allen: http://www.gmx.net/de/go/multimessenger
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
> 
> 



----- End forwarded message -----



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


Mime
View raw message