You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Sadhana Jain <Sa...@soa.com> on 2006/09/25 23:09:00 UTC
NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called Network
Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider. When I
run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I see the
correct http ok response when using TCPmon
Between client and the server. However, when using the Network Director
in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from
Networkdirector to the Sandesha's sample service and sent it using curl
and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soap
env:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.l
ang.Null
PointerException</faultstring><detail><ns1:stackTrace
xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at
org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at
org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at
org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the sequence
Identifier in the asyncTest.xml with the one in asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha is
throwing NPE as it generated the CreateSequenceResponse correctly and
the message being
sent is using the sequence ID returned by Sandesha. I think it is a bug
in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to match.
How can I get the latest binary version that is not released yet that
may have the fix for this problem?
Thanks very much for your reply! This problem is currently a road
blocker for us.
Sadhana
Re: NullPointerException with Sandesha1
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi Sadhana,
Thanks for the information. I fixed the problem.
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: Jaliya Ekanayake ; sandesha-dev@ws.apache.org
Sent: Tuesday, September 26, 2006 5:13 PM
Subject: RE: NullPointerException with Sandesha1
Hi Jaliya,
Thanks again for your prompt response! I was able to figure out the problem by putting debug statements in Sandesha's source code.
The problem was that the NetworkDirector was not sending AcksTo element in the CreateSequence message which is a required element as of
2005/02 rm spec. Sandesha was still returning the CreateSequenecResponse ok but was not adding any entry for the sequence id in the acksToMap of SandeshaQueue. When NetworkDirector sent the first ping message, Sandesha's getAcksTo method returned null as it couldn't find the matching acksTo entry
In the map and therefore when the following line in AcknowlwdgementProcessor did the comparison, it returned a nullPointerException:
if (true ==
(storageManager.getAcksTo(seqID).equals(Constants.WSA.NS_ADDRESSING_ANONYMOUS))) {
It will be nice if Sandesha returned an error saying it didn't find an AcksTo entry than throwing an NPE. In any case, thanks very much again for your help
So I could find the real issue.
Best Regards,
Sadhana
------------------------------------------------------------------------------
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Tuesday, September 26, 2006 5:29 AM
To: Sadhana Jain; Jaliya Ekanayake; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Hmm.. Seems like the addressing-SNAPSHOT.jar is not available at the repository location. I just changed the location and now it should work.
Please do a SVN update and build again.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: Jaliya Ekanayake ; sandesha-dev@ws.apache.org
Sent: Tuesday, September 26, 2006 2:00 AM
Subject: RE: NullPointerException with Sandesha1
Hi Jaliya,
Thanks very much for your response. When I build the latest Sandesha's distribution, I get
The following error:
$ maven dist-bin
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download addressing-SNAPSHOT.jar.
Error retrieving artifact from [http://www.apache.org/dist/java-repository/addre
ssing/jars/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error download
ing; status code was: 301
Error retrieving artifact from [ http://cvs.apache.org/repository/addressing/jar
s/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error downloading; stat
us code was: 302
WARNING: Failed to download addressing-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied dependency:
addressing-SNAPSHOT.jar
do you know why I maybe getting this?
Thanks,
Sadhana
----------------------------------------------------------------------------
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Monday, September 25, 2006 6:35 PM
To: Sadhana Jain; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Can you please try the same scenario with a new build. Here are the steps that you need to do.
Take a svn checkout from http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1_0/
use Apache Maven to build the distribution. (command is as follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider. When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I see the correct http ok response when using TCPmon
Between client and the server. However, when using the Network Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from Networkdirector to the Sandesha's sample service and sent it using curl and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.Null
PointerException</faultstring><detail><ns1:stackTrace xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the sequence Identifier in the asyncTest.xml with the one in asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha is throwing NPE as it generated the CreateSequenceResponse correctly and the message being
sent is using the sequence ID returned by Sandesha. I think it is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to match. How can I get the latest binary version that is not released yet that may have the fix for this problem?
Thanks very much for your reply! This problem is currently a road blocker for us.
Sadhana
--------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: NullPointerException with Sandesha1
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi Sadhana,
Thanks for the information. I fixed the problem.
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: Jaliya Ekanayake ; sandesha-dev@ws.apache.org
Sent: Tuesday, September 26, 2006 5:13 PM
Subject: RE: NullPointerException with Sandesha1
Hi Jaliya,
Thanks again for your prompt response! I was able to figure out the problem by putting debug statements in Sandesha's source code.
The problem was that the NetworkDirector was not sending AcksTo element in the CreateSequence message which is a required element as of
2005/02 rm spec. Sandesha was still returning the CreateSequenecResponse ok but was not adding any entry for the sequence id in the acksToMap of SandeshaQueue. When NetworkDirector sent the first ping message, Sandesha's getAcksTo method returned null as it couldn't find the matching acksTo entry
In the map and therefore when the following line in AcknowlwdgementProcessor did the comparison, it returned a nullPointerException:
if (true ==
(storageManager.getAcksTo(seqID).equals(Constants.WSA.NS_ADDRESSING_ANONYMOUS))) {
It will be nice if Sandesha returned an error saying it didn't find an AcksTo entry than throwing an NPE. In any case, thanks very much again for your help
So I could find the real issue.
Best Regards,
Sadhana
------------------------------------------------------------------------------
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Tuesday, September 26, 2006 5:29 AM
To: Sadhana Jain; Jaliya Ekanayake; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Hmm.. Seems like the addressing-SNAPSHOT.jar is not available at the repository location. I just changed the location and now it should work.
Please do a SVN update and build again.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: Jaliya Ekanayake ; sandesha-dev@ws.apache.org
Sent: Tuesday, September 26, 2006 2:00 AM
Subject: RE: NullPointerException with Sandesha1
Hi Jaliya,
Thanks very much for your response. When I build the latest Sandesha's distribution, I get
The following error:
$ maven dist-bin
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download addressing-SNAPSHOT.jar.
Error retrieving artifact from [http://www.apache.org/dist/java-repository/addre
ssing/jars/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error download
ing; status code was: 301
Error retrieving artifact from [ http://cvs.apache.org/repository/addressing/jar
s/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error downloading; stat
us code was: 302
WARNING: Failed to download addressing-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied dependency:
addressing-SNAPSHOT.jar
do you know why I maybe getting this?
Thanks,
Sadhana
----------------------------------------------------------------------------
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Monday, September 25, 2006 6:35 PM
To: Sadhana Jain; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Can you please try the same scenario with a new build. Here are the steps that you need to do.
Take a svn checkout from http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1_0/
use Apache Maven to build the distribution. (command is as follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider. When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I see the correct http ok response when using TCPmon
Between client and the server. However, when using the Network Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from Networkdirector to the Sandesha's sample service and sent it using curl and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.Null
PointerException</faultstring><detail><ns1:stackTrace xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the sequence Identifier in the asyncTest.xml with the one in asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha is throwing NPE as it generated the CreateSequenceResponse correctly and the message being
sent is using the sequence ID returned by Sandesha. I think it is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to match. How can I get the latest binary version that is not released yet that may have the fix for this problem?
Thanks very much for your reply! This problem is currently a road blocker for us.
Sadhana
--------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
RE: NullPointerException with Sandesha1
Posted by Sadhana Jain <Sa...@soa.com>.
Hi Jaliya,
Thanks again for your prompt response! I was able to figure out the
problem by putting debug statements in Sandesha's source code.
The problem was that the NetworkDirector was not sending AcksTo element
in the CreateSequence message which is a required element as of
2005/02 rm spec. Sandesha was still returning the CreateSequenecResponse
ok but was not adding any entry for the sequence id in the acksToMap of
SandeshaQueue. When NetworkDirector sent the first ping message,
Sandesha's getAcksTo method returned null as it couldn't find the
matching acksTo entry
In the map and therefore when the following line in
AcknowlwdgementProcessor did the comparison, it returned a
nullPointerException:
if (true ==
(storageManager.getAcksTo(seqID).equals(Constants.WSA.NS_ADDRESSING_ANON
YMOUS))) {
It will be nice if Sandesha returned an error saying it didn't find an
AcksTo entry than throwing an NPE. In any case, thanks very much again
for your help
So I could find the real issue.
Best Regards,
Sadhana
________________________________
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Tuesday, September 26, 2006 5:29 AM
To: Sadhana Jain; Jaliya Ekanayake; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Hmm.. Seems like the addressing-SNAPSHOT.jar is not available at the
repository location. I just changed the location and now it should work.
Please do a SVN update and build again.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain <ma...@soa.com>
To: Jaliya Ekanayake <ma...@apache.org> ;
sandesha-dev@ws.apache.org
Sent: Tuesday, September 26, 2006 2:00 AM
Subject: RE: NullPointerException with Sandesha1
Hi Jaliya,
Thanks very much for your response. When I build the latest
Sandesha's distribution, I get
The following error:
$ maven dist-bin
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download addressing-SNAPSHOT.jar.
Error retrieving artifact from
[http://www.apache.org/dist/java-repository/addre
ssing/jars/addressing-SNAPSHOT.jar]: java.io.IOException:
Unknown error download
ing; status code was: 301
Error retrieving artifact from [
http://cvs.apache.org/repository/addressing/jar
s/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error
downloading; stat
us code was: 302
WARNING: Failed to download addressing-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied
dependency:
addressing-SNAPSHOT.jar
do you know why I maybe getting this?
Thanks,
Sadhana
________________________________
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Monday, September 25, 2006 6:35 PM
To: Sadhana Jain; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Can you please try the same scenario with a new build. Here are
the steps that you need to do.
Take a svn checkout from
http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1
_0/
<http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_
1_0/>
use Apache Maven to build the distribution. (command is as
follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain <ma...@soa.com>
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary
(called Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM
provider. When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on
Tomcat), I see the correct http ok response when using TCPmon
Between client and the server. However, when using the
Network Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent
from Networkdirector to the Sandesha's sample service and sent it using
curl and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soap
env:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.l
ang.Null
PointerException</faultstring><detail><ns1:stackTrace
xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at
org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at
org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at
org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at
org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change
the sequence Identifier in the asyncTest.xml with the one in
asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why
Sandesha is throwing NPE as it generated the CreateSequenceResponse
correctly and the message being
sent is using the sequence ID returned by Sandesha. I
think it is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't
seem to match. How can I get the latest binary version that is not
released yet that may have the fix for this problem?
Thanks very much for your reply! This problem is
currently a road blocker for us.
Sadhana
________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail:
sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail:
sandesha-dev-help@ws.apache.org
RE: NullPointerException with Sandesha1
Posted by Sadhana Jain <Sa...@soa.com>.
Hi Jaliya,
Thanks again for your prompt response! I was able to figure out the
problem by putting debug statements in Sandesha's source code.
The problem was that the NetworkDirector was not sending AcksTo element
in the CreateSequence message which is a required element as of
2005/02 rm spec. Sandesha was still returning the CreateSequenecResponse
ok but was not adding any entry for the sequence id in the acksToMap of
SandeshaQueue. When NetworkDirector sent the first ping message,
Sandesha's getAcksTo method returned null as it couldn't find the
matching acksTo entry
In the map and therefore when the following line in
AcknowlwdgementProcessor did the comparison, it returned a
nullPointerException:
if (true ==
(storageManager.getAcksTo(seqID).equals(Constants.WSA.NS_ADDRESSING_ANON
YMOUS))) {
It will be nice if Sandesha returned an error saying it didn't find an
AcksTo entry than throwing an NPE. In any case, thanks very much again
for your help
So I could find the real issue.
Best Regards,
Sadhana
________________________________
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Tuesday, September 26, 2006 5:29 AM
To: Sadhana Jain; Jaliya Ekanayake; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Hmm.. Seems like the addressing-SNAPSHOT.jar is not available at the
repository location. I just changed the location and now it should work.
Please do a SVN update and build again.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain <ma...@soa.com>
To: Jaliya Ekanayake <ma...@apache.org> ;
sandesha-dev@ws.apache.org
Sent: Tuesday, September 26, 2006 2:00 AM
Subject: RE: NullPointerException with Sandesha1
Hi Jaliya,
Thanks very much for your response. When I build the latest
Sandesha's distribution, I get
The following error:
$ maven dist-bin
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download addressing-SNAPSHOT.jar.
Error retrieving artifact from
[http://www.apache.org/dist/java-repository/addre
ssing/jars/addressing-SNAPSHOT.jar]: java.io.IOException:
Unknown error download
ing; status code was: 301
Error retrieving artifact from [
http://cvs.apache.org/repository/addressing/jar
s/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error
downloading; stat
us code was: 302
WARNING: Failed to download addressing-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied
dependency:
addressing-SNAPSHOT.jar
do you know why I maybe getting this?
Thanks,
Sadhana
________________________________
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Monday, September 25, 2006 6:35 PM
To: Sadhana Jain; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Can you please try the same scenario with a new build. Here are
the steps that you need to do.
Take a svn checkout from
http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1
_0/
<http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_
1_0/>
use Apache Maven to build the distribution. (command is as
follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain <ma...@soa.com>
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary
(called Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM
provider. When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on
Tomcat), I see the correct http ok response when using TCPmon
Between client and the server. However, when using the
Network Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent
from Networkdirector to the Sandesha's sample service and sent it using
curl and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soap
env:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.l
ang.Null
PointerException</faultstring><detail><ns1:stackTrace
xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at
org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at
org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at
org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at
org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change
the sequence Identifier in the asyncTest.xml with the one in
asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why
Sandesha is throwing NPE as it generated the CreateSequenceResponse
correctly and the message being
sent is using the sequence ID returned by Sandesha. I
think it is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't
seem to match. How can I get the latest binary version that is not
released yet that may have the fix for this problem?
Thanks very much for your reply! This problem is
currently a road blocker for us.
Sadhana
________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail:
sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail:
sandesha-dev-help@ws.apache.org
Re: NullPointerException with Sandesha1
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi Sadhana,
Hmm.. Seems like the addressing-SNAPSHOT.jar is not available at the repository location. I just changed the location and now it should work.
Please do a SVN update and build again.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: Jaliya Ekanayake ; sandesha-dev@ws.apache.org
Sent: Tuesday, September 26, 2006 2:00 AM
Subject: RE: NullPointerException with Sandesha1
Hi Jaliya,
Thanks very much for your response. When I build the latest Sandesha's distribution, I get
The following error:
$ maven dist-bin
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download addressing-SNAPSHOT.jar.
Error retrieving artifact from [http://www.apache.org/dist/java-repository/addre
ssing/jars/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error download
ing; status code was: 301
Error retrieving artifact from [ http://cvs.apache.org/repository/addressing/jar
s/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error downloading; stat
us code was: 302
WARNING: Failed to download addressing-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied dependency:
addressing-SNAPSHOT.jar
do you know why I maybe getting this?
Thanks,
Sadhana
------------------------------------------------------------------------------
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Monday, September 25, 2006 6:35 PM
To: Sadhana Jain; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Can you please try the same scenario with a new build. Here are the steps that you need to do.
Take a svn checkout from http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1_0/
use Apache Maven to build the distribution. (command is as follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider. When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I see the correct http ok response when using TCPmon
Between client and the server. However, when using the Network Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from Networkdirector to the Sandesha's sample service and sent it using curl and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.Null
PointerException</faultstring><detail><ns1:stackTrace xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the sequence Identifier in the asyncTest.xml with the one in asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha is throwing NPE as it generated the CreateSequenceResponse correctly and the message being
sent is using the sequence ID returned by Sandesha. I think it is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to match. How can I get the latest binary version that is not released yet that may have the fix for this problem?
Thanks very much for your reply! This problem is currently a road blocker for us.
Sadhana
----------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: NullPointerException with Sandesha1
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi Sadhana,
Hmm.. Seems like the addressing-SNAPSHOT.jar is not available at the repository location. I just changed the location and now it should work.
Please do a SVN update and build again.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: Jaliya Ekanayake ; sandesha-dev@ws.apache.org
Sent: Tuesday, September 26, 2006 2:00 AM
Subject: RE: NullPointerException with Sandesha1
Hi Jaliya,
Thanks very much for your response. When I build the latest Sandesha's distribution, I get
The following error:
$ maven dist-bin
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download addressing-SNAPSHOT.jar.
Error retrieving artifact from [http://www.apache.org/dist/java-repository/addre
ssing/jars/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error download
ing; status code was: 301
Error retrieving artifact from [ http://cvs.apache.org/repository/addressing/jar
s/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error downloading; stat
us code was: 302
WARNING: Failed to download addressing-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied dependency:
addressing-SNAPSHOT.jar
do you know why I maybe getting this?
Thanks,
Sadhana
------------------------------------------------------------------------------
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Monday, September 25, 2006 6:35 PM
To: Sadhana Jain; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Can you please try the same scenario with a new build. Here are the steps that you need to do.
Take a svn checkout from http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1_0/
use Apache Maven to build the distribution. (command is as follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider. When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I see the correct http ok response when using TCPmon
Between client and the server. However, when using the Network Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from Networkdirector to the Sandesha's sample service and sent it using curl and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.Null
PointerException</faultstring><detail><ns1:stackTrace xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the sequence Identifier in the asyncTest.xml with the one in asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha is throwing NPE as it generated the CreateSequenceResponse correctly and the message being
sent is using the sequence ID returned by Sandesha. I think it is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to match. How can I get the latest binary version that is not released yet that may have the fix for this problem?
Thanks very much for your reply! This problem is currently a road blocker for us.
Sadhana
----------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
RE: NullPointerException with Sandesha1
Posted by Sadhana Jain <Sa...@soa.com>.
Hi Jaliya,
Thanks very much for your response. When I build the latest Sandesha's
distribution, I get
The following error:
$ maven dist-bin
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download addressing-SNAPSHOT.jar.
Error retrieving artifact from
[http://www.apache.org/dist/java-repository/addre
ssing/jars/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error
download
ing; status code was: 301
Error retrieving artifact from [
http://cvs.apache.org/repository/addressing/jar
s/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error
downloading; stat
us code was: 302
WARNING: Failed to download addressing-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied
dependency:
addressing-SNAPSHOT.jar
do you know why I maybe getting this?
Thanks,
Sadhana
________________________________
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Monday, September 25, 2006 6:35 PM
To: Sadhana Jain; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Can you please try the same scenario with a new build. Here are the
steps that you need to do.
Take a svn checkout from
http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1
_0/
<http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_
1_0/>
use Apache Maven to build the distribution. (command is as follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain <ma...@soa.com>
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called
Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider.
When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I
see the correct http ok response when using TCPmon
Between client and the server. However, when using the Network
Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from
Networkdirector to the Sandesha's sample service and sent it using curl
and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soap
env:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.l
ang.Null
PointerException</faultstring><detail><ns1:stackTrace
xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at
org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at
org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at
org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at
org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the
sequence Identifier in the asyncTest.xml with the one in
asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha
is throwing NPE as it generated the CreateSequenceResponse correctly and
the message being
sent is using the sequence ID returned by Sandesha. I think it
is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to
match. How can I get the latest binary version that is not released yet
that may have the fix for this problem?
Thanks very much for your reply! This problem is currently a
road blocker for us.
Sadhana
________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
RE: NullPointerException with Sandesha1
Posted by Sadhana Jain <Sa...@soa.com>.
Hi Jaliya,
Thanks very much for your response. When I build the latest Sandesha's
distribution, I get
The following error:
$ maven dist-bin
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download addressing-SNAPSHOT.jar.
Error retrieving artifact from
[http://www.apache.org/dist/java-repository/addre
ssing/jars/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error
download
ing; status code was: 301
Error retrieving artifact from [
http://cvs.apache.org/repository/addressing/jar
s/addressing-SNAPSHOT.jar]: java.io.IOException: Unknown error
downloading; stat
us code was: 302
WARNING: Failed to download addressing-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied
dependency:
addressing-SNAPSHOT.jar
do you know why I maybe getting this?
Thanks,
Sadhana
________________________________
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Monday, September 25, 2006 6:35 PM
To: Sadhana Jain; sandesha-dev@ws.apache.org
Subject: Re: NullPointerException with Sandesha1
Hi Sadhana,
Can you please try the same scenario with a new build. Here are the
steps that you need to do.
Take a svn checkout from
http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1
_0/
<http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_
1_0/>
use Apache Maven to build the distribution. (command is as follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain <ma...@soa.com>
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called
Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider.
When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I
see the correct http ok response when using TCPmon
Between client and the server. However, when using the Network
Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from
Networkdirector to the Sandesha's sample service and sent it using curl
and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soap
env:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.l
ang.Null
PointerException</faultstring><detail><ns1:stackTrace
xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at
org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at
org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at
org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at
org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the
sequence Identifier in the asyncTest.xml with the one in
asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha
is throwing NPE as it generated the CreateSequenceResponse correctly and
the message being
sent is using the sequence ID returned by Sandesha. I think it
is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to
match. How can I get the latest binary version that is not released yet
that may have the fix for this problem?
Thanks very much for your reply! This problem is currently a
road blocker for us.
Sadhana
________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: NullPointerException with Sandesha1
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi Sadhana,
Can you please try the same scenario with a new build. Here are the steps that you need to do.
Take a svn checkout from http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1_0/
use Apache Maven to build the distribution. (command is as follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider. When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I see the correct http ok response when using TCPmon
Between client and the server. However, when using the Network Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from Networkdirector to the Sandesha's sample service and sent it using curl and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.Null
PointerException</faultstring><detail><ns1:stackTrace xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the sequence Identifier in the asyncTest.xml with the one in asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha is throwing NPE as it generated the CreateSequenceResponse correctly and the message being
sent is using the sequence ID returned by Sandesha. I think it is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to match. How can I get the latest binary version that is not released yet that may have the fix for this problem?
Thanks very much for your reply! This problem is currently a road blocker for us.
Sadhana
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: NullPointerException with Sandesha1
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi Sadhana,
Can you please try the same scenario with a new build. Here are the steps that you need to do.
Take a svn checkout from http://svn.apache.org/repos/asf/webservices/sandesha/branches/sandesha_1_0/
use Apache Maven to build the distribution. (command is as follows)
maven dist-bin
You will find the new Sandesha-1.0.jar in the target directory.
Let us know if the problem is still there.
Thanks,
-Jaliya
----- Original Message -----
From: Sadhana Jain
To: sandesha-dev@ws.apache.org
Sent: Monday, September 25, 2006 5:09 PM
Subject: NullPointerException with Sandesha1
Hi,
I am testing our company's web services intermediary (called Network Director) for the RM capability using
Sandesha's sample implementation of RM client and RM provider. When I run the Sandesha's AsyncPingClient
'Against the Sandehsa's RMSampleService (deployed on Tomcat), I see the correct http ok response when using TCPmon
Between client and the server. However, when using the Network Director in the middle, I get the an NPE from Sandesha.
I captured the message in the tcpmon that is being sent from Networkdirector to the Sandesha's sample service and sent it using curl and
Got the same NPE (see attched message):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://sc
hemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" x
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Faul
t><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.Null
PointerException</faultstring><detail><ns1:stackTrace xmlns:ns1="http://xml.apac
he.org/axis/">java.lang.NullPointerException
at org.apache.sandesha.server.msgprocessors.AcknowledgementProcessor.sen
dAcknowledgement(AcknowledgementProcessor.java:97)
at org.apache.sandesha.server.msgprocessors.CompositeProcessor.processMe
ssage(CompositeProcessor.java:105)
at org.apache.sandesha.ws.rm.providers.RMProvider.processMessage(RMProvi
der.java:120)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453
)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:69
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Am also attaching the message that works and if I change the sequence Identifier in the asyncTest.xml with the one in asyncTest_work.xml, the
asyncTest.xml message also works! I can't explain why Sandesha is throwing NPE as it generated the CreateSequenceResponse correctly and the message being
sent is using the sequence ID returned by Sandesha. I think it is a bug in Sandesha. Have you seen anything like this before?
Also, the source and the binary version I am using don't seem to match. How can I get the latest binary version that is not released yet that may have the fix for this problem?
Thanks very much for your reply! This problem is currently a road blocker for us.
Sadhana
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org