You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by sultanat <as...@yahoo.com> on 2008/05/23 00:24:19 UTC
Axis2 1.4 not Thread safe (possible bug)
People,
I created a web service using Axis2 1.4 and was accessing it with multiple
Threads. It appears that
the SOAP xml during parsing was getting corrupt and throwing all kinds of
exceptons like
invalid XML, expecting some other element etc...
I tried the same test with same web service using Axis2 1.3 but I did not
get any of the errors mentioned above.
Is there anything which I am missing or is this a bug in Axis2 1.4 ?
--
View this message in context: http://www.nabble.com/Axis2-1.4-not-Thread-safe-%28possible-bug%29-tp17414803p17414803.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 1.4 not Thread safe (possible bug)
Posted by Eran Chinthaka <er...@gmail.com>.
Sounds like you are about to volunteer to fix this. Great, welcome to Axis2
;)
On Thu, May 29, 2008 at 4:58 PM, sultanat <as...@yahoo.com> wrote:
>
> Is someone working to fix this bug?
>
> asankha wrote:
> >
> > Chuck Brinkman wrote:
> >> We are seeing responses of one type that have the body of another type.
> >> For example say we have serviceA that returns a serviceAresponse and
> >> serviceB that returns a serviceBresponse. We have captured the network
> >> packet and see things like serviceAresponse that has the data from a
> >> serviceBresponse. It appears to be related to a flash client we have.
> >> The flash client will open a connection and can send a second request
> >> using the original connection before it gets a response or a timeout
> from
> >> the first request. I'm still working on the issue but it is in some way
> >> good to know that I'm not the only one thinking Axis2 has a thread
> safety
> >> issue.
> >>
> > Your flash client is using HTTP pipelining
> > <http://en.wikipedia.org/wiki/HTTP_pipelining> and this seems like a
> > limitation/bug on the http/s transport, and not necessarily an Axis2
> > thread safety issue. Can you post the tcpdump traces you have?
> >
> > asankha
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-1.4-not-Thread-safe-%28possible-bug%29-tp17414803p17548699.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
With Mettha,
Eran Chinthaka
--------------------------------------------------------------------
Health is the greatest gift; contentment is the greatest wealth; trusting is
the best relationship; nirvana is the highest joy. - Dhammapada
Re: Axis2 1.4 not Thread safe (possible bug)
Posted by "Asankha C. Perera" <as...@wso2.com>.
sultanat wrote:
> Is someone working to fix this bug?
>
This is not a bug as I see this.. but a case where the http/s transport
does not yet support pipelining. It would be easier to turn this off
from your client side.
asankha
> asankha wrote:
>
>> Chuck Brinkman wrote:
>>
>>> We are seeing responses of one type that have the body of another type.
>>> For example say we have serviceA that returns a serviceAresponse and
>>> serviceB that returns a serviceBresponse. We have captured the network
>>> packet and see things like serviceAresponse that has the data from a
>>> serviceBresponse. It appears to be related to a flash client we have.
>>> The flash client will open a connection and can send a second request
>>> using the original connection before it gets a response or a timeout from
>>> the first request. I'm still working on the issue but it is in some way
>>> good to know that I'm not the only one thinking Axis2 has a thread safety
>>> issue.
>>>
>>>
>> Your flash client is using HTTP pipelining
>> <http://en.wikipedia.org/wiki/HTTP_pipelining> and this seems like a
>> limitation/bug on the http/s transport, and not necessarily an Axis2
>> thread safety issue. Can you post the tcpdump traces you have?
>>
>> asankha
>>
>>
>>
>
>
Re: Axis2 1.4 not Thread safe (possible bug)
Posted by sultanat <as...@yahoo.com>.
Is someone working to fix this bug?
asankha wrote:
>
> Chuck Brinkman wrote:
>> We are seeing responses of one type that have the body of another type.
>> For example say we have serviceA that returns a serviceAresponse and
>> serviceB that returns a serviceBresponse. We have captured the network
>> packet and see things like serviceAresponse that has the data from a
>> serviceBresponse. It appears to be related to a flash client we have.
>> The flash client will open a connection and can send a second request
>> using the original connection before it gets a response or a timeout from
>> the first request. I'm still working on the issue but it is in some way
>> good to know that I'm not the only one thinking Axis2 has a thread safety
>> issue.
>>
> Your flash client is using HTTP pipelining
> <http://en.wikipedia.org/wiki/HTTP_pipelining> and this seems like a
> limitation/bug on the http/s transport, and not necessarily an Axis2
> thread safety issue. Can you post the tcpdump traces you have?
>
> asankha
>
>
--
View this message in context: http://www.nabble.com/Axis2-1.4-not-Thread-safe-%28possible-bug%29-tp17414803p17548699.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 1.4 not Thread safe (possible bug)
Posted by "Asankha C. Perera" <as...@wso2.com>.
Chuck Brinkman wrote:
> We are seeing responses of one type that have the body of another type. For example say we have serviceA that returns a serviceAresponse and serviceB that returns a serviceBresponse. We have captured the network packet and see things like serviceAresponse that has the data from a serviceBresponse. It appears to be related to a flash client we have. The flash client will open a connection and can send a second request using the original connection before it gets a response or a timeout from the first request. I'm still working on the issue but it is in some way good to know that I'm not the only one thinking Axis2 has a thread safety issue.
>
Your flash client is using HTTP pipelining
<http://en.wikipedia.org/wiki/HTTP_pipelining> and this seems like a
limitation/bug on the http/s transport, and not necessarily an Axis2
thread safety issue. Can you post the tcpdump traces you have?
asankha
Re: Axis2 1.4 source: errors when compiling
Posted by Seref Arikan <se...@kurumsalteknoloji.com>.
Hi Keith,
I know I owe the list members an apology. That was not the most clear
description of the problem.
This is my Windows XP SP2 development laptop, with JDK 1.5 and Maven 2.
I have a system variable named MAVEN_HOME which points to root of my
Maven dir.
mvn -v in the command prompt gives the following:
Maven version: 2.0.7
Java version: 1.5.0_07
OS name: "windows xp" version: "5.1" arch: "x86"
jdk_home environment variable also exists, and points to my jdk root
folder. In case you need more details, I'd be more than happy to provide
them. Thanks for your kind response
Cheers
Seref
keith chapman wrote:
> Hi Seref,
>
> Can you send us some information about your environment please.
> Platform and JDK Version, Which JDK as well would help.
>
> Thanks,
> Keith.
>
> On Sun, May 25, 2008 at 1:40 PM, Seref Arikan
> <serefarikan@kurumsalteknoloji.com
> <ma...@kurumsalteknoloji.com>> wrote:
>
> Hi,
> I've downloaded Axis2 1.4 source, I've setup maven2 and when I do
> mvn clean install, I get:
> Tests run: 313, Failures: 7, Errors: 0, Skipped: 0
> as a result. Any ideas? Is this a known issue?
>
> All the best
> Seref
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 1.4 source: errors when compiling
Posted by keith chapman <ke...@gmail.com>.
Hi Seref,
Can you send us some information about your environment please. Platform and
JDK Version, Which JDK as well would help.
Thanks,
Keith.
On Sun, May 25, 2008 at 1:40 PM, Seref Arikan <
serefarikan@kurumsalteknoloji.com> wrote:
> Hi,
> I've downloaded Axis2 1.4 source, I've setup maven2 and when I do mvn clean
> install, I get:
> Tests run: 313, Failures: 7, Errors: 0, Skipped: 0
> as a result. Any ideas? Is this a known issue?
>
> All the best
> Seref
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Axis2 1.4 source: errors when compiling
Posted by Seref Arikan <se...@kurumsalteknoloji.com>.
Hi,
I've downloaded Axis2 1.4 source, I've setup maven2 and when I do mvn
clean install, I get:
Tests run: 313, Failures: 7, Errors: 0, Skipped: 0
as a result. Any ideas? Is this a known issue?
All the best
Seref
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Axis2 1.4 not Thread safe (possible bug)
Posted by "Vinh Nguyen (vinguye2)" <vi...@cisco.com>.
Hi,
One thing to point out is that the Xerces DOM parser/builder is not
thread-safe. So any object that is backed by a Xerces-based Document is
not thread-safe. I'm not sure though if this is common throughout
Axis2, or just to a specific data binding option used.
-Vinh
-----Original Message-----
From: Michele Mazzucco [mailto:Michele.Mazzucco@ncl.ac.uk]
Sent: Saturday, May 24, 2008 6:06 AM
To: axis-user@ws.apache.org
Subject: RE: Axis2 1.4 not Thread safe (possible bug)
Chuck,
some components are thread safe, others are not (for example
ServiceClient).
Can you please post some relevant code?
Thanks,
Michele
On Fri, 2008-05-23 at 16:23 -0400, Chuck Brinkman wrote:
> Michele,
>
> In my opinion Axis2 is not thread safe. We are seeing responses of
one type that have the body of another type. For example say we have
serviceA that returns a serviceAresponse and serviceB that returns a
serviceBresponse. We have captured the network packet and see things
like serviceAresponse that has the data from a serviceBresponse. It
appears to be related to a flash client we have. The flash client will
open a connection and can send a second request using the original
connection before it gets a response or a timeout from the first
request. I'm still working on the issue but it is in some way good to
know that I'm not the only one thinking Axis2 has a thread safety
issue.
>
> Chuck
>
>
>
>
> ----------------------------------------
> > From: Michele.Mazzucco@ncl.ac.uk
> > Subject: Re: Axis2 1.4 not Thread safe (possible bug)
> > Date: Fri, 23 May 2008 17:56:54 +0100
> > To: axis-user@ws.apache.org
> >
> > I can only see a NullPointerException.
> >
> > Michele
> >
> >
> > On 23 May 2008, at 14:31, sultanat wrote:
> >
> >>
> >> Please see one of the errors we got during multiple threaded
> >> processing:
> >> The requests sent were valid SOAP xmls sent via AXIS client.
> >>
> >> org.apache.axis2.AxisFault
> >> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
> >> at
> >> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM
> >> (TokenServiceMessageReceiverInOut.java:149)
> >> at
> >> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.invokeBu
> >> sin
> >> essLogic(TokenServiceMessageReceiverInOut.java:43)
> >> at
> >> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusin
> >> ess
> >> Logic(AbstractInOutMessageReceiver.java:40)
> >> at
> >> org.apache.axis2.receivers.AbstractMessageReceiver.receive
> >> (AbstractMessageReceiver.java:100)
> >> at org.apache.axis2.engine.AxisEngine.receive
> >> (AxisEngine.java:176)
> >> at
> >> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostR
> >> equ
> >> est(HTTPTransportUtils.java:275)
> >> at
> >>
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:
> >> 131)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:
> >> 709)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:
> >> 802)
> >> at
> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
> >> (ApplicationFilterChain.java:237)
> >> at
> >> org.apache.catalina.core.ApplicationFilterChain.doFilter
> >> (ApplicationFilterChain.java:157)
> >> at
> >> org.apache.catalina.core.StandardWrapperValve.invoke
> >> (StandardWrapperValve.java:214)
> >> at
> >> org.apache.catalina.core.StandardContextValve.invoke
> >> (StandardContextValve.java:178)
> >> at
> >> org.apache.catalina.core.StandardHostValve.invoke
> >> (StandardHostValve.java:126)
> >> at
> >> org.apache.catalina.valves.ErrorReportValve.invoke
> >> (ErrorReportValve.java:105)
> >> at
> >> org.apache.catalina.core.StandardEngineValve.invoke
> >> (StandardEngineValve.java:107)
> >> at
> >> org.apache.catalina.connector.CoyoteAdapter.service
> >> (CoyoteAdapter.java:148)
> >> at
> >> org.apache.coyote.http11.Http11Processor.process
> >> (Http11Processor.java:825)
> >> at
> >> org.apache.coyote.http11.Http11Protocol
> >> $Http11ConnectionHandler.processConnection(Http11Protocol.java:731)
> >> at
> >> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket
> >> (PoolTcpEndpoint.java:526)
> >> at
> >> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
> >> (LeaderFollowerWorkerThread.java:80)
> >> at
> >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> >> (ThreadPool.java:684)
> >> at java.lang.Thread.run(Thread.java:595)
> >> Caused by: java.lang.NullPointerException
> >> at
> >> org.apache.axis2.databinding.utils.ConverterUtil.convertToString
> >> (ConverterUtil.java:337)
> >> at
> >> com.atx.tokenserver.token.xsd.DealerCode_type1.setDealerCode_type0
> >> (DealerCode_type1.java:59)
> >> at
> >> com.atx.tokenserver.token.xsd.DealerCode_type1$Factory.parse
> >> (DealerCode_type1.java:417)
> >> at
> >> com.atx.tokenserver.token.xsd.NewTokenRequest$Factory.parse
> >> (NewTokenRequest.java:525)
> >> at
> >> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM
> >> (TokenServiceMessageReceiverInOut.java:136)
> >> ... 22 more
> >>
> >>
> >> Michele Mazzucco-2 wrote:
> >>>
> >>> Please post more information (stack trace, etc.)
> >>>
> >>>
> >>> Michele
> >>>
> >>>
> >>> On 22 May 2008, at 23:24, sultanat wrote:
> >>>
> >>>>
> >>>>
> >>>> People,
> >>>> I created a web service using Axis2 1.4 and was accessing it with
> >>>> multiple Threads. It appears that the SOAP xml during parsing was
> >>>> getting corrupt and throwing all kinds of exceptons like invalid
> >>>> XML, expecting some other element etc...
> >>>>
> >>>> I tried the same test with same web service using Axis2 1.3 but I
> >>>> did not get any of the errors mentioned above.
> >>>> Is there anything which I am missing or is this a bug in Axis2
1.4 ?
> >>>> --
> >>>> View this message in context:
> >>>> http://www.nabble.com/Axis2-1.4-not-
> >>>> Thread-safe-%28possible-bug%29-tp17414803p17414803.html
> >>>> Sent from the Axis - User mailing list archive at Nabble.com.
> >>>>
> >>>>
> >>>> -----------------------------------------------------------------
> >>>> ---
> >>>> -
> >>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >>>> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>>>
> >>>
> >>>
> >>> ------------------------------------------------------------------
> >>> --- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >>> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>>
> >>>
> >>>
> >>
> >> --
> >> View this message in context: http://www.nabble.com/Axis2-1.4-not-
> >> Thread-safe-%28possible-bug%29-tp17414803p17425676.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
> _________________________________________________________________
> Change the world with e-mail. Join the i'm Initiative from Microsoft.
> http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_Change
> World
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Axis2 1.4 not Thread safe (possible bug)
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Chuck,
some components are thread safe, others are not (for example
ServiceClient).
Can you please post some relevant code?
Thanks,
Michele
On Fri, 2008-05-23 at 16:23 -0400, Chuck Brinkman wrote:
> Michele,
>
> In my opinion Axis2 is not thread safe. We are seeing responses of one type that have the body of another type. For example say we have serviceA that returns a serviceAresponse and serviceB that returns a serviceBresponse. We have captured the network packet and see things like serviceAresponse that has the data from a serviceBresponse. It appears to be related to a flash client we have. The flash client will open a connection and can send a second request using the original connection before it gets a response or a timeout from the first request. I'm still working on the issue but it is in some way good to know that I'm not the only one thinking Axis2 has a thread safety issue.
>
> Chuck
>
>
>
>
> ----------------------------------------
> > From: Michele.Mazzucco@ncl.ac.uk
> > Subject: Re: Axis2 1.4 not Thread safe (possible bug)
> > Date: Fri, 23 May 2008 17:56:54 +0100
> > To: axis-user@ws.apache.org
> >
> > I can only see a NullPointerException.
> >
> > Michele
> >
> >
> > On 23 May 2008, at 14:31, sultanat wrote:
> >
> >>
> >> Please see one of the errors we got during multiple threaded
> >> processing:
> >> The requests sent were valid SOAP xmls sent via AXIS client.
> >>
> >> org.apache.axis2.AxisFault
> >> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
> >> at
> >> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM
> >> (TokenServiceMessageReceiverInOut.java:149)
> >> at
> >> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.invokeBusin
> >> essLogic(TokenServiceMessageReceiverInOut.java:43)
> >> at
> >> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusiness
> >> Logic(AbstractInOutMessageReceiver.java:40)
> >> at
> >> org.apache.axis2.receivers.AbstractMessageReceiver.receive
> >> (AbstractMessageReceiver.java:100)
> >> at org.apache.axis2.engine.AxisEngine.receive
> >> (AxisEngine.java:176)
> >> at
> >> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequ
> >> est(HTTPTransportUtils.java:275)
> >> at
> >> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:
> >> 131)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:
> >> 709)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:
> >> 802)
> >> at
> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
> >> (ApplicationFilterChain.java:237)
> >> at
> >> org.apache.catalina.core.ApplicationFilterChain.doFilter
> >> (ApplicationFilterChain.java:157)
> >> at
> >> org.apache.catalina.core.StandardWrapperValve.invoke
> >> (StandardWrapperValve.java:214)
> >> at
> >> org.apache.catalina.core.StandardContextValve.invoke
> >> (StandardContextValve.java:178)
> >> at
> >> org.apache.catalina.core.StandardHostValve.invoke
> >> (StandardHostValve.java:126)
> >> at
> >> org.apache.catalina.valves.ErrorReportValve.invoke
> >> (ErrorReportValve.java:105)
> >> at
> >> org.apache.catalina.core.StandardEngineValve.invoke
> >> (StandardEngineValve.java:107)
> >> at
> >> org.apache.catalina.connector.CoyoteAdapter.service
> >> (CoyoteAdapter.java:148)
> >> at
> >> org.apache.coyote.http11.Http11Processor.process
> >> (Http11Processor.java:825)
> >> at
> >> org.apache.coyote.http11.Http11Protocol
> >> $Http11ConnectionHandler.processConnection(Http11Protocol.java:731)
> >> at
> >> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket
> >> (PoolTcpEndpoint.java:526)
> >> at
> >> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
> >> (LeaderFollowerWorkerThread.java:80)
> >> at
> >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> >> (ThreadPool.java:684)
> >> at java.lang.Thread.run(Thread.java:595)
> >> Caused by: java.lang.NullPointerException
> >> at
> >> org.apache.axis2.databinding.utils.ConverterUtil.convertToString
> >> (ConverterUtil.java:337)
> >> at
> >> com.atx.tokenserver.token.xsd.DealerCode_type1.setDealerCode_type0
> >> (DealerCode_type1.java:59)
> >> at
> >> com.atx.tokenserver.token.xsd.DealerCode_type1$Factory.parse
> >> (DealerCode_type1.java:417)
> >> at
> >> com.atx.tokenserver.token.xsd.NewTokenRequest$Factory.parse
> >> (NewTokenRequest.java:525)
> >> at
> >> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM
> >> (TokenServiceMessageReceiverInOut.java:136)
> >> ... 22 more
> >>
> >>
> >> Michele Mazzucco-2 wrote:
> >>>
> >>> Please post more information (stack trace, etc.)
> >>>
> >>>
> >>> Michele
> >>>
> >>>
> >>> On 22 May 2008, at 23:24, sultanat wrote:
> >>>
> >>>>
> >>>>
> >>>> People,
> >>>> I created a web service using Axis2 1.4 and was accessing it with
> >>>> multiple
> >>>> Threads. It appears that
> >>>> the SOAP xml during parsing was getting corrupt and throwing all
> >>>> kinds of
> >>>> exceptons like
> >>>> invalid XML, expecting some other element etc...
> >>>>
> >>>> I tried the same test with same web service using Axis2 1.3 but I
> >>>> did not
> >>>> get any of the errors mentioned above.
> >>>> Is there anything which I am missing or is this a bug in Axis2 1.4 ?
> >>>> --
> >>>> View this message in context: http://www.nabble.com/Axis2-1.4-not-
> >>>> Thread-safe-%28possible-bug%29-tp17414803p17414803.html
> >>>> Sent from the Axis - User mailing list archive at Nabble.com.
> >>>>
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> -
> >>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >>>> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >>> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>>
> >>>
> >>>
> >>
> >> --
> >> View this message in context: http://www.nabble.com/Axis2-1.4-not-
> >> Thread-safe-%28possible-bug%29-tp17414803p17425676.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
> _________________________________________________________________
> Change the world with e-mail. Join the i’m Initiative from Microsoft.
> http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ChangeWorld
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Axis2 1.4 not Thread safe (possible bug)
Posted by Chuck Brinkman <ce...@hotmail.com>.
Michele,
In my opinion Axis2 is not thread safe. We are seeing responses of one type that have the body of another type. For example say we have serviceA that returns a serviceAresponse and serviceB that returns a serviceBresponse. We have captured the network packet and see things like serviceAresponse that has the data from a serviceBresponse. It appears to be related to a flash client we have. The flash client will open a connection and can send a second request using the original connection before it gets a response or a timeout from the first request. I'm still working on the issue but it is in some way good to know that I'm not the only one thinking Axis2 has a thread safety issue.
Chuck
----------------------------------------
> From: Michele.Mazzucco@ncl.ac.uk
> Subject: Re: Axis2 1.4 not Thread safe (possible bug)
> Date: Fri, 23 May 2008 17:56:54 +0100
> To: axis-user@ws.apache.org
>
> I can only see a NullPointerException.
>
> Michele
>
>
> On 23 May 2008, at 14:31, sultanat wrote:
>
>>
>> Please see one of the errors we got during multiple threaded
>> processing:
>> The requests sent were valid SOAP xmls sent via AXIS client.
>>
>> org.apache.axis2.AxisFault
>> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>> at
>> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM
>> (TokenServiceMessageReceiverInOut.java:149)
>> at
>> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.invokeBusin
>> essLogic(TokenServiceMessageReceiverInOut.java:43)
>> at
>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusiness
>> Logic(AbstractInOutMessageReceiver.java:40)
>> at
>> org.apache.axis2.receivers.AbstractMessageReceiver.receive
>> (AbstractMessageReceiver.java:100)
>> at org.apache.axis2.engine.AxisEngine.receive
>> (AxisEngine.java:176)
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequ
>> est(HTTPTransportUtils.java:275)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:
>> 131)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:
>> 709)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:
>> 802)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
>> (ApplicationFilterChain.java:237)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter
>> (ApplicationFilterChain.java:157)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke
>> (StandardWrapperValve.java:214)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke
>> (StandardContextValve.java:178)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke
>> (StandardHostValve.java:126)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke
>> (ErrorReportValve.java:105)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke
>> (StandardEngineValve.java:107)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service
>> (CoyoteAdapter.java:148)
>> at
>> org.apache.coyote.http11.Http11Processor.process
>> (Http11Processor.java:825)
>> at
>> org.apache.coyote.http11.Http11Protocol
>> $Http11ConnectionHandler.processConnection(Http11Protocol.java:731)
>> at
>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket
>> (PoolTcpEndpoint.java:526)
>> at
>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
>> (LeaderFollowerWorkerThread.java:80)
>> at
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
>> (ThreadPool.java:684)
>> at java.lang.Thread.run(Thread.java:595)
>> Caused by: java.lang.NullPointerException
>> at
>> org.apache.axis2.databinding.utils.ConverterUtil.convertToString
>> (ConverterUtil.java:337)
>> at
>> com.atx.tokenserver.token.xsd.DealerCode_type1.setDealerCode_type0
>> (DealerCode_type1.java:59)
>> at
>> com.atx.tokenserver.token.xsd.DealerCode_type1$Factory.parse
>> (DealerCode_type1.java:417)
>> at
>> com.atx.tokenserver.token.xsd.NewTokenRequest$Factory.parse
>> (NewTokenRequest.java:525)
>> at
>> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM
>> (TokenServiceMessageReceiverInOut.java:136)
>> ... 22 more
>>
>>
>> Michele Mazzucco-2 wrote:
>>>
>>> Please post more information (stack trace, etc.)
>>>
>>>
>>> Michele
>>>
>>>
>>> On 22 May 2008, at 23:24, sultanat wrote:
>>>
>>>>
>>>>
>>>> People,
>>>> I created a web service using Axis2 1.4 and was accessing it with
>>>> multiple
>>>> Threads. It appears that
>>>> the SOAP xml during parsing was getting corrupt and throwing all
>>>> kinds of
>>>> exceptons like
>>>> invalid XML, expecting some other element etc...
>>>>
>>>> I tried the same test with same web service using Axis2 1.3 but I
>>>> did not
>>>> get any of the errors mentioned above.
>>>> Is there anything which I am missing or is this a bug in Axis2 1.4 ?
>>>> --
>>>> View this message in context: http://www.nabble.com/Axis2-1.4-not-
>>>> Thread-safe-%28possible-bug%29-tp17414803p17414803.html
>>>> Sent from the Axis - User mailing list archive at Nabble.com.
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Axis2-1.4-not-
>> Thread-safe-%28possible-bug%29-tp17414803p17425676.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
_________________________________________________________________
Change the world with e-mail. Join the i’m Initiative from Microsoft.
http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ChangeWorld
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 1.4 not Thread safe (possible bug)
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
I can only see a NullPointerException.
Michele
On 23 May 2008, at 14:31, sultanat wrote:
>
> Please see one of the errors we got during multiple threaded
> processing:
> The requests sent were valid SOAP xmls sent via AXIS client.
>
> org.apache.axis2.AxisFault
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
> at
> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM
> (TokenServiceMessageReceiverInOut.java:149)
> at
> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.invokeBusin
> essLogic(TokenServiceMessageReceiverInOut.java:43)
> at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusiness
> Logic(AbstractInOutMessageReceiver.java:40)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive
> (AbstractMessageReceiver.java:100)
> at org.apache.axis2.engine.AxisEngine.receive
> (AxisEngine.java:176)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequ
> est(HTTPTransportUtils.java:275)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:
> 131)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:
> 709)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:
> 802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
> (ApplicationFilterChain.java:237)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter
> (ApplicationFilterChain.java:157)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke
> (StandardWrapperValve.java:214)
> at
> org.apache.catalina.core.StandardContextValve.invoke
> (StandardContextValve.java:178)
> at
> org.apache.catalina.core.StandardHostValve.invoke
> (StandardHostValve.java:126)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke
> (ErrorReportValve.java:105)
> at
> org.apache.catalina.core.StandardEngineValve.invoke
> (StandardEngineValve.java:107)
> at
> org.apache.catalina.connector.CoyoteAdapter.service
> (CoyoteAdapter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process
> (Http11Processor.java:825)
> at
> org.apache.coyote.http11.Http11Protocol
> $Http11ConnectionHandler.processConnection(Http11Protocol.java:731)
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket
> (PoolTcpEndpoint.java:526)
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
> (LeaderFollowerWorkerThread.java:80)
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.NullPointerException
> at
> org.apache.axis2.databinding.utils.ConverterUtil.convertToString
> (ConverterUtil.java:337)
> at
> com.atx.tokenserver.token.xsd.DealerCode_type1.setDealerCode_type0
> (DealerCode_type1.java:59)
> at
> com.atx.tokenserver.token.xsd.DealerCode_type1$Factory.parse
> (DealerCode_type1.java:417)
> at
> com.atx.tokenserver.token.xsd.NewTokenRequest$Factory.parse
> (NewTokenRequest.java:525)
> at
> com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM
> (TokenServiceMessageReceiverInOut.java:136)
> ... 22 more
>
>
> Michele Mazzucco-2 wrote:
>>
>> Please post more information (stack trace, etc.)
>>
>>
>> Michele
>>
>>
>> On 22 May 2008, at 23:24, sultanat wrote:
>>
>>>
>>>
>>> People,
>>> I created a web service using Axis2 1.4 and was accessing it with
>>> multiple
>>> Threads. It appears that
>>> the SOAP xml during parsing was getting corrupt and throwing all
>>> kinds of
>>> exceptons like
>>> invalid XML, expecting some other element etc...
>>>
>>> I tried the same test with same web service using Axis2 1.3 but I
>>> did not
>>> get any of the errors mentioned above.
>>> Is there anything which I am missing or is this a bug in Axis2 1.4 ?
>>> --
>>> View this message in context: http://www.nabble.com/Axis2-1.4-not-
>>> Thread-safe-%28possible-bug%29-tp17414803p17414803.html
>>> Sent from the Axis - User mailing list archive at Nabble.com.
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Axis2-1.4-not-
> Thread-safe-%28possible-bug%29-tp17414803p17425676.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 1.4 not Thread safe (possible bug)
Posted by sultanat <as...@yahoo.com>.
Please see one of the errors we got during multiple threaded processing:
The requests sent were valid SOAP xmls sent via AXIS client.
org.apache.axis2.AxisFault
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM(TokenServiceMessageReceiverInOut.java:149)
at
com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.invokeBusinessLogic(TokenServiceMessageReceiverInOut.java:43)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:731)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
org.apache.axis2.databinding.utils.ConverterUtil.convertToString(ConverterUtil.java:337)
at
com.atx.tokenserver.token.xsd.DealerCode_type1.setDealerCode_type0(DealerCode_type1.java:59)
at
com.atx.tokenserver.token.xsd.DealerCode_type1$Factory.parse(DealerCode_type1.java:417)
at
com.atx.tokenserver.token.xsd.NewTokenRequest$Factory.parse(NewTokenRequest.java:525)
at
com.atx.tokenserver.token.TokenServiceMessageReceiverInOut.fromOM(TokenServiceMessageReceiverInOut.java:136)
... 22 more
Michele Mazzucco-2 wrote:
>
> Please post more information (stack trace, etc.)
>
>
> Michele
>
>
> On 22 May 2008, at 23:24, sultanat wrote:
>
>>
>>
>> People,
>> I created a web service using Axis2 1.4 and was accessing it with
>> multiple
>> Threads. It appears that
>> the SOAP xml during parsing was getting corrupt and throwing all
>> kinds of
>> exceptons like
>> invalid XML, expecting some other element etc...
>>
>> I tried the same test with same web service using Axis2 1.3 but I
>> did not
>> get any of the errors mentioned above.
>> Is there anything which I am missing or is this a bug in Axis2 1.4 ?
>> --
>> View this message in context: http://www.nabble.com/Axis2-1.4-not-
>> Thread-safe-%28possible-bug%29-tp17414803p17414803.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Axis2-1.4-not-Thread-safe-%28possible-bug%29-tp17414803p17425676.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 1.4 not Thread safe (possible bug)
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Please post more information (stack trace, etc.)
Michele
On 22 May 2008, at 23:24, sultanat wrote:
>
>
> People,
> I created a web service using Axis2 1.4 and was accessing it with
> multiple
> Threads. It appears that
> the SOAP xml during parsing was getting corrupt and throwing all
> kinds of
> exceptons like
> invalid XML, expecting some other element etc...
>
> I tried the same test with same web service using Axis2 1.3 but I
> did not
> get any of the errors mentioned above.
> Is there anything which I am missing or is this a bug in Axis2 1.4 ?
> --
> View this message in context: http://www.nabble.com/Axis2-1.4-not-
> Thread-safe-%28possible-bug%29-tp17414803p17414803.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org