You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kandula-dev@ws.apache.org by ahua <ps...@163.com> on 2007/07/06 10:27:12 UTC
some problems about the Kandula bankone sample project
I am a developer in IBM company.I user your kandula project and find some
bugs,now there is a null pointer problem.for example,response me
soon,pls.thanks.and tell me why to happen the thing.
[CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
Exception in thread "main" AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.NullPointerException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:IBM-S50
java.lang.NullPointerException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
at
org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:54)
at
org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
at
org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:69)
at
org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionImpl.java:172)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(TransactionManagerImpl.java:63)
at test1.BankOne.main(BankOne.java:34)
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11460432
Sent from the Kandula mailing list archive at Nabble.com.
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
why
ahua wrote:
>
> I am a developer in IBM company.I user your kandula project and find some
> bugs,now there is a null pointer problem.for example,response me
> soon,pls.thanks.and tell me why to happen the thing.
>
> [CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
> Exception in thread "main" AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.lang.NullPointerException
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}hostname:IBM-S50
>
> java.lang.NullPointerException
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
> at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
> at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at javax.xml.parsers.SAXParser.parse(Unknown Source)
> at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
> at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
> at
> org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:54)
> at
> org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
> at
> org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:69)
> at
> org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionImpl.java:172)
> at
> org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(TransactionManagerImpl.java:63)
> at test1.BankOne.main(BankOne.java:34)
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11460434
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
this is the client code.
public class BankOne {
public static void main(String[] args) throws Exception {
TransactionManagerImpl tm = TransactionManagerImpl.getInstance();
tm.begin();
bankone.BankOne bank = null;
try {
bank = new BankOneServiceLocator().getBankOne();
} catch (ServiceException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
}
try {
System.out.println("%%"+bank.credit(1001, 10));
System.out.println("asdf"+bank.debit(1002, 10));
System.out.println("the result is ...................." +
bank.getBalance(0));
}catch (Exception e) {
tm.rollback();
e.printStackTrace();
}
tm.commit();
}
}
ahua wrote:
>
> I deployed the bankone sample project by the step by step ,but it happened
> on the below.why did it happen? who can help me to resolve it? Thanks.
>
> ahua wrote:
>>
>> I am a developer in IBM company.I user your kandula project and find some
>> bugs,now there is a null pointer problem.for example,response me
>> soon,pls.thanks.and tell me why to happen the thing.
>>
>> [CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
>> Exception in thread "main" AxisFault
>> faultCode:
>> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>> faultSubcode:
>> faultString: java.lang.NullPointerException
>> faultActor:
>> faultNode:
>> faultDetail:
>> {http://xml.apache.org/axis/}hostname:IBM-S50
>>
>> java.lang.NullPointerException
>> at
>> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>> at
>> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>> at
>> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>> at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>> Source)
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>> at javax.xml.parsers.SAXParser.parse(Unknown Source)
>> at
>> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>> at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>> at
>> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
>> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>> at
>> org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
>> at
>> org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:54)
>> at
>> org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
>> at
>> org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:69)
>> at
>> org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionImpl.java:172)
>> at
>> org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(TransactionManagerImpl.java:63)
>> at test1.BankOne.main(BankOne.java:34)
>>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11460441
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
I deployed the bankone sample project by the step by step ,but it happened on
the below.why did it happen? who can help me to resolve it? Thanks.
ahua wrote:
>
> I am a developer in IBM company.I user your kandula project and find some
> bugs,now there is a null pointer problem.for example,response me
> soon,pls.thanks.and tell me why to happen the thing.
>
> [CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
> Exception in thread "main" AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.lang.NullPointerException
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}hostname:IBM-S50
>
> java.lang.NullPointerException
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
> at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
> at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at javax.xml.parsers.SAXParser.parse(Unknown Source)
> at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
> at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub.registerOperation(RegistrationPortTypeRPCBindingStub.java:290)
> at
> org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:54)
> at
> org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
> at
> org.apache.kandula.coordinator.at.TransactionImpl.register(TransactionImpl.java:69)
> at
> org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionImpl.java:172)
> at
> org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(TransactionManagerImpl.java:63)
> at test1.BankOne.main(BankOne.java:34)
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11460439
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
I have added the client-config.wsdd file into the classes directory,but the
console alert the something on the below,why did it happen?but it timeouts.
pls response me soon.
[CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
params: http://schemas.xmlsoap.org/ws/2004/10/wsat/Completion
params: Address: http://localhost:8080/axis/services/completionInitiator
Reference property[0]:
<ns1:CallbackRef xmlns:ns1="http://ws.apache.org/kandula"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="xsd:string">uuid:48499ea0-2dbf-11dc-b0e0-b1132b7fdfb9</ns1:CallbackRef>
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Exception in thread "main" java.lang.RuntimeException:
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:155)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Caused by: org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
... 2 more
Hannes Erven-2 wrote:
>
> Hi ahua,
>
>
> are you using Kandula_1, and which version?
>
> I guess you did not put the client-config.wsdd file into the classpath
> of the sample, can you please check?
>
>
> -hannes
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11495074
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
Witch jar file will I put the client-config.wsdd into?
Hannes Erven-2 wrote:
>
> Hi ahua,
>
>
> are you using Kandula_1, and which version?
>
> I guess you did not put the client-config.wsdd file into the classpath
> of the sample, can you please check?
>
>
> -hannes
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11494817
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by Hannes Erven <ha...@erven.at>.
Hi ahua,
are you using Kandula_1, and which version?
I guess you did not put the client-config.wsdd file into the classpath
of the sample, can you please check?
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Exception in thread "main" java.lang.RuntimeException:
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:155)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Caused by: org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
... 2 more
Dasarath Weeratunge-3 wrote:
>
> Quoting ahua <ps...@163.com>:
>
> If the working directory is in your classpath, you can include client-
> config.wsdd there (on the client side). If this is the first time you are
> using
> Axis, I recommend that you go through some Axis tutorials first. The
> Kandula-1
> docs assume that you are familiar with Apache Axis. Furthermore, please
> monitor
> your messages using TCP monitor and let us know exactly where you
> experience
> difficulties during a particular test scenario. If you post specific
> questions
> you are likely to get more informative answers.
>
> --dasarath
>
>>
>> the client can connect the server,but it timeout ,what will I do
>> ?response
>> me soon,pls. Thanks.
>>
>> Dasarath Weeratunge-3 wrote:
>> >
>> > Quoting Hannes Erven <ha...@erven.at>:
>> >
>> > Yes, please do check whether your ws-addressing handler is able to add
>> > in the references to the outgoing messages. It could happen either as a
>> > result
>> > of you not putting in the client .wsdd file in the right place or not
>> > deploying the *correct* version of the handlers for both ws-addressing
>> and
>> > kandula. Just see whether the registration message carries a
>> transaction
>> > identifier in the header.
>> >
>> > thanks,
>> > --dasarath
>> >
>> >
>> >> Hi ahua,
>> >>
>> >>
>> >> are you using Kandula_1, and which version?
>> >>
>> >> I guess you did not put the client-config.wsdd file into the classpath
>> >> of the sample, can you please check?
>> >>
>> >>
>> >> -hannes
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-
> tf4034220.html#a11495049
>> Sent from the Kandula mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11495829
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
the client can connect the server,but it timeout ,what will I do ?response
me soon,pls. Thanks.
Dasarath Weeratunge-3 wrote:
>
> Quoting Hannes Erven <ha...@erven.at>:
>
> Yes, please do check whether your ws-addressing handler is able to add
> in the references to the outgoing messages. It could happen either as a
> result
> of you not putting in the client .wsdd file in the right place or not
> deploying the *correct* version of the handlers for both ws-addressing and
> kandula. Just see whether the registration message carries a transaction
> identifier in the header.
>
> thanks,
> --dasarath
>
>
>> Hi ahua,
>>
>>
>> are you using Kandula_1, and which version?
>>
>> I guess you did not put the client-config.wsdd file into the classpath
>> of the sample, can you please check?
>>
>>
>> -hannes
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11495049
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
I have added the client-config.wsdd file into the classes directory,but the
console alert the something on the below,why did it happen?but it timeouts.
pls response me soon.
[CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
params: http://schemas.xmlsoap.org/ws/2004/10/wsat/Completion
params: Address: http://localhost:8080/axis/services/completionInitiator
Reference property[0]:
<ns1:CallbackRef xmlns:ns1="http://ws.apache.org/kandula"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="xsd:string">uuid:48499ea0-2dbf-11dc-b0e0-b1132b7fdfb9</ns1:CallbackRef>
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Exception in thread "main" java.lang.RuntimeException:
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:155)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Caused by: org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
... 2 more
Dasarath Weeratunge-3 wrote:
>
> Quoting Hannes Erven <ha...@erven.at>:
>
> Yes, please do check whether your ws-addressing handler is able to add
> in the references to the outgoing messages. It could happen either as a
> result
> of you not putting in the client .wsdd file in the right place or not
> deploying the *correct* version of the handlers for both ws-addressing and
> kandula. Just see whether the registration message carries a transaction
> identifier in the header.
>
> thanks,
> --dasarath
>
>
>> Hi ahua,
>>
>>
>> are you using Kandula_1, and which version?
>>
>> I guess you did not put the client-config.wsdd file into the classpath
>> of the sample, can you please check?
>>
>>
>> -hannes
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11495064
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
if I monitor the soap message,Witch port will been monitored?
Dasarath Weeratunge-3 wrote:
>
> Quoting ahua <ps...@163.com>:
>
> If the working directory is in your classpath, you can include client-
> config.wsdd there (on the client side). If this is the first time you are
> using
> Axis, I recommend that you go through some Axis tutorials first. The
> Kandula-1
> docs assume that you are familiar with Apache Axis. Furthermore, please
> monitor
> your messages using TCP monitor and let us know exactly where you
> experience
> difficulties during a particular test scenario. If you post specific
> questions
> you are likely to get more informative answers.
>
> --dasarath
>
>>
>> the client can connect the server,but it timeout ,what will I do
>> ?response
>> me soon,pls. Thanks.
>>
>> Dasarath Weeratunge-3 wrote:
>> >
>> > Quoting Hannes Erven <ha...@erven.at>:
>> >
>> > Yes, please do check whether your ws-addressing handler is able to add
>> > in the references to the outgoing messages. It could happen either as a
>> > result
>> > of you not putting in the client .wsdd file in the right place or not
>> > deploying the *correct* version of the handlers for both ws-addressing
>> and
>> > kandula. Just see whether the registration message carries a
>> transaction
>> > identifier in the header.
>> >
>> > thanks,
>> > --dasarath
>> >
>> >
>> >> Hi ahua,
>> >>
>> >>
>> >> are you using Kandula_1, and which version?
>> >>
>> >> I guess you did not put the client-config.wsdd file into the classpath
>> >> of the sample, can you please check?
>> >>
>> >>
>> >> -hannes
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-
> tf4034220.html#a11495049
>> Sent from the Kandula mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11495708
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
I have added the client-config.wsdd file into the classes directory,but the
console alert the something on the below,why did it happen?pls response me
soon.
[CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
params: http://schemas.xmlsoap.org/ws/2004/10/wsat/Completion
params: Address: http://localhost:8080/axis/services/completionInitiator
Reference property[0]:
<ns1:CallbackRef xmlns:ns1="http://ws.apache.org/kandula"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="xsd:string">uuid:48499ea0-2dbf-11dc-b0e0-b1132b7fdfb9</ns1:CallbackRef>
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Exception in thread "main" java.lang.RuntimeException:
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:155)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Caused by: org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
... 2 more
Dasarath Weeratunge-3 wrote:
>
> Quoting Hannes Erven <ha...@erven.at>:
>
> Yes, please do check whether your ws-addressing handler is able to add
> in the references to the outgoing messages. It could happen either as a
> result
> of you not putting in the client .wsdd file in the right place or not
> deploying the *correct* version of the handlers for both ws-addressing and
> kandula. Just see whether the registration message carries a transaction
> identifier in the header.
>
> thanks,
> --dasarath
>
>
>> Hi ahua,
>>
>>
>> are you using Kandula_1, and which version?
>>
>> I guess you did not put the client-config.wsdd file into the classpath
>> of the sample, can you please check?
>>
>>
>> -hannes
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11494896
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: some problems about the Kandula bankone sample project
Posted by ahua <ps...@163.com>.
[CallbackRegistry] registerCallback: timeout= 0 callbacks.size= 0
params: http://schemas.xmlsoap.org/ws/2004/10/wsat/Completion
params: Address: http://localhost:8080/axis/services/completionInitiator
Reference property[0]:
<ns1:CallbackRef xmlns:ns1="http://ws.apache.org/kandula"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="xsd:string">uuid:3d13a730-2e03-11dc-882a-f39719131027</ns1:CallbackRef>
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Exception in thread "main" java.lang.RuntimeException:
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:155)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.rollback(TransactionManagerImpl.java:71)
at test1.BankOne.main(BankOne.java:33)
Caused by: org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.rollback(TransactionImpl.java:148)
... 2 more
Dasarath Weeratunge-3 wrote:
>
> Quoting ahua <ps...@163.com>:
>
> If the working directory is in your classpath, you can include client-
> config.wsdd there (on the client side). If this is the first time you are
> using
> Axis, I recommend that you go through some Axis tutorials first. The
> Kandula-1
> docs assume that you are familiar with Apache Axis. Furthermore, please
> monitor
> your messages using TCP monitor and let us know exactly where you
> experience
> difficulties during a particular test scenario. If you post specific
> questions
> you are likely to get more informative answers.
>
> --dasarath
>
>>
>> the client can connect the server,but it timeout ,what will I do
>> ?response
>> me soon,pls. Thanks.
>>
>> Dasarath Weeratunge-3 wrote:
>> >
>> > Quoting Hannes Erven <ha...@erven.at>:
>> >
>> > Yes, please do check whether your ws-addressing handler is able to add
>> > in the references to the outgoing messages. It could happen either as a
>> > result
>> > of you not putting in the client .wsdd file in the right place or not
>> > deploying the *correct* version of the handlers for both ws-addressing
>> and
>> > kandula. Just see whether the registration message carries a
>> transaction
>> > identifier in the header.
>> >
>> > thanks,
>> > --dasarath
>> >
>> >
>> >> Hi ahua,
>> >>
>> >>
>> >> are you using Kandula_1, and which version?
>> >>
>> >> I guess you did not put the client-config.wsdd file into the classpath
>> >> of the sample, can you please check?
>> >>
>> >>
>> >> -hannes
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: kandula-dev-help@ws.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-
> tf4034220.html#a11495049
>> Sent from the Kandula mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/some-problems-about-the-Kandula-bankone-sample-project-tf4034220.html#a11498975
Sent from the Kandula mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org