RE: JMS/SOAP axis2
Hi Chathura,
Are you still looking into the following JMS issue with ADB? Should I
enter a bug?
Thanks
Kamal Kang
>>I ran the same test with XMLBeans few months back, I didn't have any
>>issues.
kamal
>>From: Chathura Herath [mailto:[EMAIL PROTECTED]
>>Sent: Saturday, June 23, 2007 1:01 PM
>>To: axis-user@ws.apache.org
>>Subject: Re: JMS/SOAP axis2
>>This looks familiar to some of the problems i have seen in JSON. I
>>assume you are using ADB for data binding, are u?
>>If so could you try -d xmlbeans and see whether it works. This may
>>not solve your problem completely, but it would give us an idea.
>>Thanks
>>Chathura
From: Kang, Kamaljeet K. [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 21, 2007 5:57 PM
To: axis-user@ws.apache.org
Subject: JMS/SOAP axis2
Hi,
I am trying to test a webservice with JMS transport. The service works
perfectly fine with HTTP but with JMS it gives the following exception
during unmarshling. Looks like localName is incorrect. Is it a bug?
OMElelment BodyBy the StaxSOAPModelBuilder
1-Jun 15:44:40,552 DEBUG builder.StAXOMBuilder [JMSWorker-1] -
START_ELEMENT: {
mf854.v1}notify:notify
1-Jun 15:44:40,552 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] -
Build the
OMElelment notifyBy the StaxSOAPModelBuilder
1-Jun 15:44:40,552 DEBUG engine.AxisEngine [JMSWorker-1] -
[MessageContext: log
D=urn:uuid:4153845C2D42C4D72B1182455081080] receive:null
1-Jun 15:44:40,552 DEBUG addressing.AddressingValidationHandler
[JMSWorker-1] -
invoke: IS_ADDR_INFO_ALREADY_PROCESSED=null
1-Jun 15:44:40,552 DEBUG addressing.AddressingValidationHandler
[JMSWorker-1] -
checkUsingAddressing: WSAddressingFlag=unspecified
1-Jun 15:51:30,779 DEBUG builder.StAXOMBuilder [JMSWorker-1] -
START_ELEMENT: {
mf854.v1}TopicExpression_T:TopicExpression_T (it should be topic)
1-Jun 15:51:30,779 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] -
Build the
OMElelment TopicExpression_TBy the StaxSOAPModelBuilder
1-Jun 15:52:48,088 ERROR jms.JMSMessageReceiver [JMSWorker-1] - JMS
Worker [JMS
orker-1] Encountered an Axis Fault : java.lang.RuntimeException:
Unexpected sub
lement TopicExpression_T; nested exception is:
java.lang.RuntimeException: java.lang.RuntimeException:
Unexpected subel
ment TopicExpression_T
rg.apache.axis2.AxisFault: java.lang.RuntimeException: Unexpected
subelement To
icExpression_T; nested exception is:
java.lang.RuntimeException: java.lang.RuntimeException:
Unexpected subel
ment TopicExpression_T
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
at
org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
ly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:55
)
at
org.apache.axis2.receivers.AbstractInMessageReceiver.receive(Abstract
nMessageReceiver.java:35)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:186)
Kamal
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
RE: JMS/SOAP axis2
I ran the same test with XMLBeans few months back, I didn't have any
issues.
kamal
-Original Message-
From: Chathura Herath [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 23, 2007 1:01 PM
To: axis-user@ws.apache.org
Subject: Re: JMS/SOAP axis2
This looks familiar to some of the problems i have seen in JSON. I
assume you are using ADB for data binding, are u?
If so could you try -d xmlbeans and see whether it works. This may
not solve your problem completely, but it would give us an idea.
Thanks
Chathura
On 6/21/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi,
>
> I am trying to test a webservice with JMS transport. The service works
> perfectly fine with HTTP but with JMS it gives the following exception
> during unmarshling. Looks like localName is incorrect. Is it a bug?
>
>
> OMElelment BodyBy the StaxSOAPModelBuilder
> 1-Jun 15:44:40,552 DEBUG builder.StAXOMBuilder [JMSWorker-1] -
> START_ELEMENT: {
> mf854.v1}notify:notify
> 1-Jun 15:44:40,552 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] -
Build
> the
> OMElelment notifyBy the StaxSOAPModelBuilder
> 1-Jun 15:44:40,552 DEBUG engine.AxisEngine [JMSWorker-1] -
[MessageContext:
> log
> D=urn:uuid:4153845C2D42C4D72B1182455081080] receive:null
> 1-Jun 15:44:40,552 DEBUG
> addressing.AddressingValidationHandler [JMSWorker-1] -
> invoke: IS_ADDR_INFO_ALREADY_PROCESSED=null
> 1-Jun 15:44:40,552 DEBUG
> addressing.AddressingValidationHandler [JMSWorker-1] -
> checkUsingAddressing: WSAddressingFlag=unspecified
> 1-Jun 15:51:30,779 DEBUG builder.StAXOMBuilder [JMSWorker-1] -
> START_ELEMENT: {
> mf854.v1}TopicExpression_T:TopicExpression_T (it should be
> topic)
> 1-Jun 15:51:30,779 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] -
Build
> the
> OMElelment TopicExpression_TBy the StaxSOAPModelBuilder
> 1-Jun 15:52:48,088 ERROR jms.JMSMessageReceiver [JMSWorker-1] - JMS
Worker
> [JMS
> orker-1] Encountered an Axis Fault : java.lang.RuntimeException:
Unexpected
> sub
> lement TopicExpression_T; nested exception is:
>java.lang.RuntimeException: java.lang.RuntimeException:
Unexpected
> subel
> ment TopicExpression_T
> rg.apache.axis2.AxisFault: java.lang.RuntimeException: Unexpected
subelement
> To
> icExpression_T; nested exception is:
>java.lang.RuntimeException: java.lang.RuntimeException:
Unexpected
> subel
> ment TopicExpression_T
>at
> org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
>at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
>
ly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:55
)
>at
> org.apache.axis2.receivers.AbstractInMessageReceiver.receive(Abstract
> nMessageReceiver.java:35)
>at
> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:186)
> Kamal
>
>
>
>
>
> The information contained in this message may be privileged
> and confidential and protected from disclosure. If the reader
> of this message is not the intended recipient, or an employee
> or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that any reproduction,
> dissemination or distribution of this communication is strictly
> prohibited. If you have received this communication in error,
> please notify us immediately by replying to the message and
> deleting it from your computer. Thank you. Tellabs
>
>
>
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JMS/SOAP axis2
Hi,
I am trying to test a webservice with JMS transport. The service works
perfectly fine with HTTP but with JMS it gives the following exception during
unmarshling. Looks like localName is incorrect. Is it a bug?
OMElelment BodyBy the StaxSOAPModelBuilder
1-Jun 15:44:40,552 DEBUG builder.StAXOMBuilder [JMSWorker-1] - START_ELEMENT: {
mf854.v1}notify:notify
1-Jun 15:44:40,552 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] - Build the
OMElelment notifyBy the StaxSOAPModelBuilder
1-Jun 15:44:40,552 DEBUG engine.AxisEngine [JMSWorker-1] - [MessageContext: log
D=urn:uuid:4153845C2D42C4D72B1182455081080] receive:null
1-Jun 15:44:40,552 DEBUG addressing.AddressingValidationHandler [JMSWorker-1] -
invoke: IS_ADDR_INFO_ALREADY_PROCESSED=null
1-Jun 15:44:40,552 DEBUG addressing.AddressingValidationHandler [JMSWorker-1] -
checkUsingAddressing: WSAddressingFlag=unspecified
1-Jun 15:51:30,779 DEBUG builder.StAXOMBuilder [JMSWorker-1] - START_ELEMENT: {
mf854.v1}TopicExpression_T:TopicExpression_T (it should be topic)
1-Jun 15:51:30,779 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] - Build the
OMElelment TopicExpression_TBy the StaxSOAPModelBuilder
1-Jun 15:52:48,088 ERROR jms.JMSMessageReceiver [JMSWorker-1] - JMS Worker [JMS
orker-1] Encountered an Axis Fault : java.lang.RuntimeException: Unexpected sub
lement TopicExpression_T; nested exception is:
java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subel
ment TopicExpression_T
rg.apache.axis2.AxisFault: java.lang.RuntimeException: Unexpected subelement To
icExpression_T; nested exception is:
java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subel
ment TopicExpression_T
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
at org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
ly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:55)
at org.apache.axis2.receivers.AbstractInMessageReceiver.receive(Abstract
nMessageReceiver.java:35)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:186)
Kamal
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
RE: Transport out has not been set
I checked again, I have all the jar files from ActiveMQ and Axis2 in my
classpath.
Thanks
Kamal
-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 13, 2007 2:05 PM
To: axis-user@ws.apache.org
Subject: Re: Transport out has not been set
May be you have not added dependent jars which JMS required to the
classpath.
Thanks
Deepal
Kang, Kamaljeet K. wrote:
>
> Hi,
>
>
>
> I am trying to test axis2 with JMS transport. I followed the
> instructions as per 'jms-transport.html'. The server initializes fine
> and I see the JMS queue gets created on the JMS broker but when I try
> to call a method on stub I get the following exception.
>
>
>
> org.apache.axis2.AxisFault: Transport out has not been set
>
> at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:507)
>
> at
>
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:309)
>
> at
>
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:273)
>
> at org.hello.HelloStub.Hello(HelloStub.java:173)
>
> at org.hello.HelloStub.main(HelloStub.java:462)
>
>
>
> String url =
>
"jms:/Hello?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFacto
ry&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialC
ontextFactory&java.naming.provider.url=tcp://localhost:61616";
>
>
> HelloStub hStub = new HelloStub(url);
>
>HelloResponse hRes = hStub.Hello("Test");
>
> System.out.println("Response is " +
> hRes.getStringout());
>
>
>
> Can someone please help me with this?
>
>
>
>
>
> Thanks
>
>
>
> Kamal
>
>
> The information contained in this message may be privileged
> and confidential and protected from disclosure. If the reader
> of this message is not the intended recipient, or an employee
> or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that any reproduction,
> dissemination or distribution of this communication is strictly
> prohibited. If you have received this communication in error,
> please notify us immediately by replying to the message and
> deleting it from your computer. Thank you. Tellabs
>
>
--
Thanks,
Deepal
"The highest tower is built one brick at a time"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Transport out has not been set
Hi,
I am trying to test axis2 with JMS transport. I followed the
instructions as per 'jms-transport.html'. The server initializes fine
and I see the JMS queue gets created on the JMS broker but when I try to
call a method on stub I get the following exception.
org.apache.axis2.AxisFault: Transport out has not been set
at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:507)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:309)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:273)
at org.hello.HelloStub.Hello(HelloStub.java:173)
at org.hello.HelloStub.main(HelloStub.java:462)
String url =
"jms:/Hello?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFacto
ry&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialC
ontextFactory&java.naming.provider.url=tcp://localhost:61616";
HelloStub hStub = new HelloStub(url);
HelloResponse hRes = hStub.Hello("Test");
System.out.println("Response is " +
hRes.getStringout());
Can someone please help me with this?
Thanks
Kamal
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
RE: AbstractHTTPSender not releasing connection
I just tested the example code in HttpClient, 'MultiThreadedExample.java' (modified so that it runs forever). It reuses the pool of connections. I do not see it creating new connection all the time. Should I enter a bug? kamal -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, May 04, 2007 11:26 AM To: axis-user@ws.apache.org Subject: Re: AbstractHTTPSender not releasing connection Ok then try this tactic. Can you get hold of the OperationContext for each invocation? Typically you can use myServiceContext.getLastOperationContext() to get the last OperationContext. You will have to start caching them though by calling myServiceClient.setCachingOperationContext(true) or you can create the OperationContext by calling myServiceContext.createOperationContext as well. Either way after the invocation is done you can call the following snippet to cleanup the HttpMethod. myOperationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VAL UE); _messageContext.getTransportOut().getSender().cleanup(_messageContext); thanks, dims On 5/4/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Dims, > > what do you mean by "calling the complete method"?. In this scenario I'm > using simple ServiceClient(s) sharing the same conf. context and > attached to custom callbacks (I'm reusing the same ServiceClients for > thousands of asynchronous requests). > For my knowledge (see the link below) the cleanup (on the ServiceClient) > should be called only at the end which, as I said, is after receiving > thousands of responses. > Are you then suggesting me to share an OperationClient for all my > requests and to free resources as soon as I receive the response? > > Thanks, > Michele > > http://www.nabble.com/-Axis2--ServiceClient-question-tf2496516.html#a907 8044 > > On Fri, 2007-05-04 at 10:56 -0400, Davanum Srinivas wrote: > > Michele, > > > > Are you calling the complete method in OperationClient? that calls the > > cleanup method in the TransportSender. I believe we are doing that > > automatically in generated stubs as well where we generate the > > following call. > > > > _messageContext.getTransportOut().getSender().cleanup(_messageContext); > > > > that calls the releaseConnection on the HttpMethod. > > > > -- dims > > > > On 5/4/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > > But that workaround works only on Windows :( > > > > > > Michele > > > > > > On Fri, 2007-05-04 at 10:18 -0400, Davanum Srinivas wrote: > > > > Guess the only work around is the tuning parameters as mentioned > > > > there...so it's a no-op fo us. There's nothing we can do..is there? > > > > > > > > -- dims > > > > > > > > On 5/4/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > > > > Dims, > > > > > > > > > > please see here > > > > > https://issues.apache.org/jira/browse/AXIS2-2593 > > > > > > > > > > > > > > > Michele > > > > > > > > > > On Fri, 2007-05-04 at 09:59 -0400, Davanum Srinivas wrote: > > > > > > Michele, > > > > > > > > > > > > Here's what is see in the http client code: > > > > > > http://svn.apache.org/repos/asf/jakarta/commons/proper/httpclient/trunk/ src/java/org/apache/commons/httpclient/MultiThreadedHttpConnectionManage r.java > > > > > > > > > > > >/** The default maximum number of connections allowed per host */ > > > > > > public static final int DEFAULT_MAX_HOST_CONNECTIONS = 2; // Per > > > > > > RFC 2616 sec 8.1.4 > > > > > > > > > > > > /** The default maximum number of connections allowed overall */ > > > > > > public static final int DEFAULT_MAX_TOTAL_CONNECTIONS = 20; > > > > > > > > > > > > Could the new threads being created because the old ones are still in > > > > > > progress? can you bump up the default limits and try? > > > > > > > > > > > > -- dims > > > > > > > > > > > > On 5/4/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > > > > > > Dims, > > > > > > > > > > > > > > even if the HttpClient is cached new connections are created every 3/4 > > > > > > > requests. > > > > > > > > > > > > > > Michele > > > > > > > > > &g
RE: AbstractHTTPSender not releasing connection
Is it okay not to release the connection back to the pool?
This is from HttpClient site
>>To safely ensure connection release HttpClient should be used in the
>>following manner
>>// and then from inside some thread executing a method
GetMethod get = new GetMethod("http://jakarta.apache.org/";);
try {
client.executeMethod(get);
// print response to stdout
System.out.println(get.getResponseBodyAsStream());
} finally {
// be sure the connection is released back to the connection
// manager
get.releaseConnection();
}
Kamal
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, May 04, 2007 10:18 AM
To: axis-user@ws.apache.org
Subject: Re: AbstractHTTPSender not releasing connection
Guess the only work around is the tuning parameters as mentioned
there...so it's a no-op fo us. There's nothing we can do..is there?
-- dims
On 5/4/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
> Dims,
>
> please see here
> https://issues.apache.org/jira/browse/AXIS2-2593
>
>
> Michele
>
> On Fri, 2007-05-04 at 09:59 -0400, Davanum Srinivas wrote:
> > Michele,
> >
> > Here's what is see in the http client code:
> >
http://svn.apache.org/repos/asf/jakarta/commons/proper/httpclient/trunk/
src/java/org/apache/commons/httpclient/MultiThreadedHttpConnectionManage
r.java
> >
> >/** The default maximum number of connections allowed per host */
> > public static final int DEFAULT_MAX_HOST_CONNECTIONS = 2; //
Per
> > RFC 2616 sec 8.1.4
> >
> > /** The default maximum number of connections allowed overall */
> > public static final int DEFAULT_MAX_TOTAL_CONNECTIONS = 20;
> >
> > Could the new threads being created because the old ones are still
in
> > progress? can you bump up the default limits and try?
> >
> > -- dims
> >
> > On 5/4/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
> > > Dims,
> > >
> > > even if the HttpClient is cached new connections are created every
3/4
> > > requests.
> > >
> > > Michele
> > >
> > > On Fri, 2007-05-04 at 09:44 -0400, Davanum Srinivas wrote:
> > > > Kamaljeet,
> > > >
> > > > can you try the 2nd option here:
> > > > http://wso2.org/library/87
> > > >
> > > > -- dims
> > > >
> > > > On 5/4/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
> > > > > Hi,
> > > > >
> > > > > I turned the HttpClient log on and from the log it looks like
new
> > > > > connection is created for every request. I am sending request
every 1
> > > > > sec so connection shouldn't idle out. I think,
AbstractHTTPSender is not
> > > > > releasing the connection back to the pool so
> > > > > 'MultiThreadedHttpConnectionManager cleanup' thread is
trashing it after
> > > > > 1 use.
> > > > >
> > > > >
> > > > >
> > > > > >>>>>>>> Log
> > > > >
> > > > > 04-May 08:11:22,184 DEBUG
httpclient.MultiThreadedHttpConnectionManager
> > > > > [PRIMARY_SUBSCRIBER_FAULT_TOPIC] - Unable to get a connection,
> > > > > waiting...,
hostConfig=HostConfiguration[host=http://localhost:8081]
> > > > > **ProbCause*PROP_TEST
> > > > > 04-May 08:52:15,369 DEBUG
httpclient.MultiThreadedHttpConnectionManager
> > > > > [MultiThreadedHttpConnectionManager cleanup] - Connection
reclaimed by
> > > > > garbage collector,
> > > > > hostConfig=HostConfiguration[host=http://localhost:8081]
> > > > > 04-May 08:52:15,369 DEBUG
httpclient.MultiThreadedHttpConnectionManager
> > > > > [MultiThreadedHttpConnectionManager cleanup] - enter
> > > > >
HttpConnectionManager.ConnectionPool.getHostPool(HostConfiguration)
> > > > > 04-May 08:52:15,369 DEBUG
httpclient.MultiThreadedHttpConnectionManager
> > > > > [MultiThreadedHttpConnectionManager cleanup] - enter
> > > > >
HttpConnectionManager.ConnectionPool.getHostPool(HostConfiguration)
> > > > > 04-May 08:52:15,369 DEBUG
httpclient.MultiThreadedHttpConnectionManager
> > > > > [MultiThreadedHttpConnectionManager cleanup] - Notifying
thread waiting
> > > > > on host pool,
hostConfig=HostConfiguration[host=http://localhost:8081]
> > > > > 04-May 08:52:15,369 DEBUG
httpclient.MultiThreadedHttpConn
RE: AbstractHTTPSender not releasing connection
Hi, I turned the HttpClient log on and from the log it looks like new connection is created for every request. I am sending request every 1 sec so connection shouldn't idle out. I think, AbstractHTTPSender is not releasing the connection back to the pool so 'MultiThreadedHttpConnectionManager cleanup' thread is trashing it after 1 use. >>>>>>>> Log 04-May 08:11:22,184 DEBUG httpclient.MultiThreadedHttpConnectionManager [PRIMARY_SUBSCRIBER_FAULT_TOPIC] - Unable to get a connection, waiting..., hostConfig=HostConfiguration[host=http://localhost:8081] **ProbCause*PROP_TEST 04-May 08:52:15,369 DEBUG httpclient.MultiThreadedHttpConnectionManager [MultiThreadedHttpConnectionManager cleanup] - Connection reclaimed by garbage collector, hostConfig=HostConfiguration[host=http://localhost:8081] 04-May 08:52:15,369 DEBUG httpclient.MultiThreadedHttpConnectionManager [MultiThreadedHttpConnectionManager cleanup] - enter HttpConnectionManager.ConnectionPool.getHostPool(HostConfiguration) 04-May 08:52:15,369 DEBUG httpclient.MultiThreadedHttpConnectionManager [MultiThreadedHttpConnectionManager cleanup] - enter HttpConnectionManager.ConnectionPool.getHostPool(HostConfiguration) 04-May 08:52:15,369 DEBUG httpclient.MultiThreadedHttpConnectionManager [MultiThreadedHttpConnectionManager cleanup] - Notifying thread waiting on host pool, hostConfig=HostConfiguration[host=http://localhost:8081] 04-May 08:52:15,369 DEBUG httpclient.MultiThreadedHttpConnectionManager [PRIMARY_SUBSCRIBER_FAULT_TOPIC] - enter HttpConnectionManager.ConnectionPool.getHostPool(HostConfiguration) 04-May 08:52:15,369 DEBUG httpclient.MultiThreadedHttpConnectionManager [PRIMARY_SUBSCRIBER_FAULT_TOPIC] - Allocating new connection, hostConfig=HostConfiguration[host=http://localhost:8081] 04-May 08:52:15,369 DEBUG httpclient.HttpMethodDirector [PRIMARY_SUBSCRIBER_FAULT_TOPIC] - Attempt number 1 to process request Thanks Kamal -Original Message- From: Michele Mazzucco [mailto:[EMAIL PROTECTED] Sent: Friday, May 04, 2007 4:22 AM To: axis-user@ws.apache.org Subject: Re: AbstractHTTPSender not releasing connection Hi Kamal, HttpClient by default uses persistent (keep alive) connections, however every few requests a new connection is created. Michele On Thu, 2007-05-03 at 16:15 -0400, Kang, Kamaljeet K. wrote: > Hi, > > As per HTTPClient documentation if you are using > MultiThreadedhttpConnectionManager then for every > HttpClient.executeMethod there has to be corresponding > 'releaseConnection' call. I do not see AbstractHttpSender releasing > connection anywhere in the code. Is this the reason why even after using > REUSE_HTTP_CLIENT, we see new HTTP connection created for every > request/response? > > > > Thanks > > Kamal > > The information contained in this message may be privileged > and confidential and protected from disclosure. If the reader > of this message is not the intended recipient, or an employee > or agent responsible for delivering this message to the > intended recipient, you are hereby notified that any reproduction, > dissemination or distribution of this communication is strictly > prohibited. If you have received this communication in error, > please notify us immediately by replying to the message and > deleting it from your computer. Thank you. Tellabs > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AbstractHTTPSender not releasing connection
Hi, As per HTTPClient documentation if you are using MultiThreadedhttpConnectionManager then for every HttpClient.executeMethod there has to be corresponding 'releaseConnection' call. I do not see AbstractHttpSender releasing connection anywhere in the code. Is this the reason why even after using REUSE_HTTP_CLIENT, we see new HTTP connection created for every request/response? Thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
REUSE_HTTP_CLIENT
Hi, I have set REUSE_HTTP_CLIENT to 'true' in my stub but I still see from netstat that new HTTP Connections are being created. I see connections being reused sometimes but after 2-3 requests it creates new connections. Do we need to do something else for persistent HTTP connection? Thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache Axis 2: how to get header? Options
These are the changes I did to get Response SOAP header.
1) Save header in the message context in the skeleton implementation.
MessageContext inMsgContext = MessageContext.getCurrentMessageContext();
OperationContext operationContext =
inMsgContext.getOperationContext();
MessageContext outMessageContext = operationContext
.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
outMessageContext.setEnvelope(createSOAPEnvelope());
OMNode outHeaderNode = toOM(outHeader);
outMessageContext.getEnvelope().getHeader().addChild(outHeaderNode);
2) Modified autogenerated *InOutReceiver classes to not create new Envelope if
Envelope is already there in the context (modified whereever
factory.getDefaultEnvelope() is called)
3) Modified Stub to save the return message context
org.apache.axis2.context.MessageContext _returnMessageContext =
_operationClient.getMessageContext(
org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_IN_VALUE);
org.apache.axiom.soap.SOAPEnvelope _returnEnv =
_returnMessageContext.getEnvelope();
// Added this line
_serviceClient.getServiceContext().setLastOperationContext(_operationClient.getOperationContext());
4) Finally you can get the Response Header from stub
OperationContext oprCtxt =
stub._getServiceClient().getLastOperationContext();
MessageContext inMsgContext =
oprCtxt.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
SOAPHeader header = inMsgContext.getEnvelope().getHeader();
return
Header_T.Factory.parse(header.getFirstElement().getXMLStreamReaderWithoutCaching());
Not sure if there is any easier way but finally this worked for me.
Let me know if you need more help with this.
Kamal Kang
-Original Message-
From: José Antonio Sánchez [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 3:56 PM
To: axis-user@ws.apache.org
Subject: Re: Apache Axis 2: how to get header? Options
AFAIK you have to modify the stub code and get headers from there. In
Axis2 1.2 there is an operation in the generated stub to get the last
operation context (and so the envelope object) but it didn't work for
me.
On 4/19/07, craig wickesser <[EMAIL PROTECTED]> wrote:
> anyone???
>
>
> On 4/18/07, craig wickesser <[EMAIL PROTECTED]> wrote:
> > Hi...I have a client which I am using to access a web service The
> > code I have is...
> >
> >
> > MyStub stub = new MyStub();
> > HelloWorldDocument reqDoc =
> HellWorldDocument.Factory.newInstance();
> > reqDoc.setName("bob");
> >
> >
> > HelloWorldResponseDocumnet resp = stub.SayHello(reqDoc);
> >
> >
> > The SOAP XML response is in the following form...
> >
> >
> >
> >
> >
> >
> >
> > string
> > string
> >
> >
> >
> >
> > .
> >
> >
> >
> >
> >
> > My issue is I need to get stuff from the UserInfo headerhow can I
> > get that? Currently all I can get is the HelloWorldResponse from the
> > "body".
> >
> > Thanks!
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
--
Saludos.
José Antonio Sánchez
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Operation Not found EPR...
I had a similar error recently and I wasn't using ws-addressing. It was because of typo in in services.xml. kamal -Original Message- From: Michele Mazzucco [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 03, 2007 4:26 AM To: axis-user@ws.apache.org Subject: Re: Operation Not found EPR... EPR means endpoint reference. It's the "url" where your service is available. Milan, if the error message says WSA action = it means that you are using ws-addressing. Michele On Tue, 2007-04-03 at 01:04 -0700, Milan Tomic wrote: > No, I'm not using WS-addressing. Is this error message described somewhere in documentation? What does it mean? Which operation was not found? What is "EPR"? > > Best regards, > Milan > > > - Original Message > From: Michele Mazzucco <[EMAIL PROTECTED]> > To: axis-user@ws.apache.org > Sent: Monday, April 2, 2007 4:36:04 PM > Subject: Re: Operation Not found EPR... > > Milan, > > are you using WS-addressing? If so you have to specify the SOAP action > on the client side (use options.setAction()), which is the value > specified in services.xml as actionMapping element. > > Michele > > On Mon, 2007-04-02 at 06:55 -0700, Milan Tomic wrote: > > I got this error message: > > > > "javax.xml.rpc.soap.SOAPFaultException: Operation Not found EPR is http://localhost:8080/axis2/services/MyWebService and WSA Action = " > > > > > > but I don't know what does it mean? What went wrong? :( > > > > > > Thank you in advance, > > Milan > > > > > > > > > > > > > > Get your own web address. > > Have a HUGE year through Yahoo! Small Business. > > http://smallbusiness.yahoo.com/domains/?p=BESTDEAL > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > Don't pick lemons. > See all the new 2007 cars at Yahoo! Autos. > http://autos.yahoo.com/new_cars.html > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: soap header in stub
Thanks Charitha. Actually, I had read the earlier discussion regarding this topic. (http://marc.info/?l=axis-user&m=116492371225455&w=2) And I thought by now the following should be working. >>A stub uses an operation client inside each method. The life of the >>operation client is thus equal to the life of that method call. An >>option would be to add a method to ServiceClient() to get the "last" >>used operation client. Then one could get the last operation client, >>get the appropriate message context from that and grab whatever info >>needed. >>We could implement this fairly trivially by making operationClient an >>instance variable of ServiceClient and updating that whenever a new one >>is created. ServiceClient is already declared to be not thread safe so >>this should work ok (I think). >> Sanjiva Kamal -Original Message- From: Charitha Kankanamge [mailto:[EMAIL PROTECTED] Sent: Monday, April 02, 2007 11:06 PM To: axis-user@ws.apache.org Subject: Re: soap header in stub Hi Kang, AFAIK you won't be able to retrieve SOAP headers using serviceClient. Because, with service clients you can only access SOAP body or the pay load. Though you can add SOAP headers, you do not have a way to retrieve SOAP header from service client. Have a look at http://www-128.ibm.com/developerworks/webservices/library/ws-soa-axis2-1 / for more information on this. You can use operationClient to retrieve the SOAP headers. See http://wso2.org/library/290 Also, the same topic was discussed in the following url. http://marc.info/?l=axis-user&m=116492371225455&w=2 regards Charitha Kang, Kamaljeet K. wrote: >Hi, > >I am trying to retrieve soap header of the response from stub using >serviceClient.getLastOperationContext() but OperationContext is always >null. > >Is this the right way to retrieve soap header in stub? > >Thanks > >Kamal > >The information contained in this message may be privileged >and confidential and protected from disclosure. If the reader >of this message is not the intended recipient, or an employee >or agent responsible for delivering this message to the >intended recipient, you are hereby notified that any reproduction, >dissemination or distribution of this communication is strictly >prohibited. If you have received this communication in error, >please notify us immediately by replying to the message and >deleting it from your computer. Thank you. Tellabs > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
soap header in stub
Hi, I am trying to retrieve soap header of the response from stub using serviceClient.getLastOperationContext() but OperationContext is always null. Is this the right way to retrieve soap header in stub? Thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: adding soapheader
>>One possibility is to use a handler in the outflow to add the header
>>for your outgoing message. This document[1] explains how you can write
>>a handler and pack it in a module..
Why do we have to add another handler to add soapheader in outbound
messages? Shouldn't this be part of axis2 framework?
kamal
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 22, 2007 10:00 PM
To: axis-user@ws.apache.org
Subject: Re: adding soapheader
> I am trying to add SOAP header in outbound messages in the skeleton
impl
> class. I auto-generated code from wsdl and I am using ADB binding.
>
> I tried the following suggestion but I am getting null pointer at
> outMessageContext.getEnvelope(). It looks like envelope is added later
> on in MessageReceiverInOut class. Any other suggestion?
Yes... It is added after invoking the service.. Sorry.. This didn't
come to my mind when I was replying to you earlier...
One possibility is to use a handler in the outflow to add the header
for your outgoing message. This document[1] explains how you can write
a handler and pack it in a module..
~Thilina
[1]http://ws.apache.org/axis2/1_1_1/modules.html
>
>
> Thanks
>
> Kamal
>
> -Original Message-
> From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 25, 2007 1:22 PM
> To: axis-user@ws.apache.org
> Subject: Re: setOperationContext
>
> Try the following,
>
> MessageContext inMessageContext =
> MessageContext.getCurrentMessageContext();
> OperationContext operationContext =
> inMessageContext.getOperationContext();
> MessageContext outMessageContext = operationContext
> .getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
>
>
outMessageContext.getEnvelope().getHeader().addHeaderBlock("xxx",namespa
> ce);
>
> Thanks,
> Thilina
>
> On 2/24/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
> > Thanks. It works.
> > Another question, how do set the response soap header?
> >
> > kamal
> >
> > -Original Message-
> > From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> > Sent: Friday, February 23, 2007 10:13 AM
> > To: axis-user@ws.apache.org
> > Subject: Re: setOperationContext
> >
> > Hi Michele;
> > Yes we are store that in ThreadLocal.
> >
> > Thanks
> > Deepal
> >
> > >Those info should be stored into a ThreadLocal (tomcat uses a new
> > thread
> > >for each received request).
> > >
> > >Michele
> > >
> > >On Fri, 2007-02-23 at 09:46 -0500, Punnoose, Roshan wrote:
> > >
> > >
> > >>If this is a static method, how can multiple requests to one
service
> > >>work? Just wondering, how I could access the MessageId for
different
> > >>requests to the same service. Thanks!
> > >>
> > >>Roshan Punnoose
> > >>Phone: 301-497-6039
> > >>-Original Message-
> > >>From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> > >>Sent: Thursday, February 22, 2007 11:06 PM
> > >>To: axis-user@ws.apache.org
> > >>Subject: Re: setOperationContext
> > >>
> > >>That's outdated!. please use MessageContext.getCurrentContext()
from
> > >>inside your service method (when Axis2 calls your service method.)
> > >>
> > >>thanks,
> > >>dims
> > >>
> > >>On 2/22/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
> > >>
> > >>
> > >>>Hi,
> > >>>
> > >>>I would like to access service context on the skeleton side. I
> > >>>
> > >>>
> > >>followed
> > >>
> > >>
> > >>>the documentation ("http://wso2.org/library/259";) and added
> > >>>'setOperationContext(OperationContext opCtxt)' in the skeleton
> class
> > >>>
> > >>>
> > >>but
> > >>
> > >>
> > >>>the method is never called. Is this the correct way to access
> Context
> > >>>
> > >>>
> > >>on
> > >>
> > >>
> > >>>the server side?
> > >>>
> > >>>
> > >>>Thanks
> > >>>
> > >>>Kamal Kang
> > >>>
> > >>>
> > >>>The information contained in this mes
adding soapheader
Hi,
I am trying to add SOAP header in outbound messages in the skeleton impl
class. I auto-generated code from wsdl and I am using ADB binding.
I tried the following suggestion but I am getting null pointer at
outMessageContext.getEnvelope(). It looks like envelope is added later
on in MessageReceiverInOut class. Any other suggestion?
Thanks
Kamal
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 25, 2007 1:22 PM
To: axis-user@ws.apache.org
Subject: Re: setOperationContext
Try the following,
MessageContext inMessageContext =
MessageContext.getCurrentMessageContext();
OperationContext operationContext =
inMessageContext.getOperationContext();
MessageContext outMessageContext = operationContext
.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
outMessageContext.getEnvelope().getHeader().addHeaderBlock("xxx",namespa
ce);
Thanks,
Thilina
On 2/24/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
> Thanks. It works.
> Another question, how do set the response soap header?
>
> kamal
>
> -Original Message-
> From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 23, 2007 10:13 AM
> To: axis-user@ws.apache.org
> Subject: Re: setOperationContext
>
> Hi Michele;
> Yes we are store that in ThreadLocal.
>
> Thanks
> Deepal
>
> >Those info should be stored into a ThreadLocal (tomcat uses a new
> thread
> >for each received request).
> >
> >Michele
> >
> >On Fri, 2007-02-23 at 09:46 -0500, Punnoose, Roshan wrote:
> >
> >
> >>If this is a static method, how can multiple requests to one service
> >>work? Just wondering, how I could access the MessageId for different
> >>requests to the same service. Thanks!
> >>
> >>Roshan Punnoose
> >>Phone: 301-497-6039
> >>-Original Message-
> >>From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> >>Sent: Thursday, February 22, 2007 11:06 PM
> >>To: axis-user@ws.apache.org
> >>Subject: Re: setOperationContext
> >>
> >>That's outdated!. please use MessageContext.getCurrentContext() from
> >>inside your service method (when Axis2 calls your service method.)
> >>
> >>thanks,
> >>dims
> >>
> >>On 2/22/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>I would like to access service context on the skeleton side. I
> >>>
> >>>
> >>followed
> >>
> >>
> >>>the documentation ("http://wso2.org/library/259";) and added
> >>>'setOperationContext(OperationContext opCtxt)' in the skeleton
class
> >>>
> >>>
> >>but
> >>
> >>
> >>>the method is never called. Is this the correct way to access
Context
> >>>
> >>>
> >>on
> >>
> >>
> >>>the server side?
> >>>
> >>>
> >>>Thanks
> >>>
> >>>Kamal Kang
> >>>
> >>>
> >>>The information contained in this message may be privileged
> >>>and confidential and protected from disclosure. If the reader
> >>>of this message is not the intended recipient, or an employee
> >>>or agent responsible for delivering this message to the
> >>>intended recipient, you are hereby notified that any reproduction,
> >>>dissemination or distribution of this communication is strictly
> >>>prohibited. If you have received this communication in error,
> >>>please notify us immediately by replying to the message and
> >>>deleting it from your computer. Thank you. Tellabs
> >>>
> >>>
>
>>>-
> >>>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >>>
>
>>-
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
ADB , serializable java beans
Hi, I would like the java beans generated by ADB to implement 'Serializable' interface. Do I modify 'PlainBeanTemplate.xsl' and schema-compile.properties in axis2-adb-codegen? Thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: setOperationContext
Thanks. It works.
Another question, how do set the response soap header?
kamal
-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Friday, February 23, 2007 10:13 AM
To: axis-user@ws.apache.org
Subject: Re: setOperationContext
Hi Michele;
Yes we are store that in ThreadLocal.
Thanks
Deepal
>Those info should be stored into a ThreadLocal (tomcat uses a new
thread
>for each received request).
>
>Michele
>
>On Fri, 2007-02-23 at 09:46 -0500, Punnoose, Roshan wrote:
>
>
>>If this is a static method, how can multiple requests to one service
>>work? Just wondering, how I could access the MessageId for different
>>requests to the same service. Thanks!
>>
>>Roshan Punnoose
>>Phone: 301-497-6039
>>-Original Message-
>>From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
>>Sent: Thursday, February 22, 2007 11:06 PM
>>To: axis-user@ws.apache.org
>>Subject: Re: setOperationContext
>>
>>That's outdated!. please use MessageContext.getCurrentContext() from
>>inside your service method (when Axis2 calls your service method.)
>>
>>thanks,
>>dims
>>
>>On 2/22/07, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
>>
>>
>>>Hi,
>>>
>>>I would like to access service context on the skeleton side. I
>>>
>>>
>>followed
>>
>>
>>>the documentation ("http://wso2.org/library/259";) and added
>>>'setOperationContext(OperationContext opCtxt)' in the skeleton class
>>>
>>>
>>but
>>
>>
>>>the method is never called. Is this the correct way to access Context
>>>
>>>
>>on
>>
>>
>>>the server side?
>>>
>>>
>>>Thanks
>>>
>>>Kamal Kang
>>>
>>>
>>>The information contained in this message may be privileged
>>>and confidential and protected from disclosure. If the reader
>>>of this message is not the intended recipient, or an employee
>>>or agent responsible for delivering this message to the
>>>intended recipient, you are hereby notified that any reproduction,
>>>dissemination or distribution of this communication is strictly
>>>prohibited. If you have received this communication in error,
>>>please notify us immediately by replying to the message and
>>>deleting it from your computer. Thank you. Tellabs
>>>
>>>
>>>-
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
--
Thanks,
Deepal
"The highest tower is built one brick at a time"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
setOperationContext
Hi,
I would like to access service context on the skeleton side. I followed
the documentation ("http://wso2.org/library/259";) and added
'setOperationContext(OperationContext opCtxt)' in the skeleton class but
the method is never called. Is this the correct way to access Context on
the server side?
Thanks
Kamal Kang
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
SoapMonitor NullPointerException
Hi, Enabling SOAPMonitor is throwing NPE and causing an operation to fail. It works fine if SOAPMonitor is not enabled. Why would failure in SOAPMonitor module result in operation failure? org.apache.axis2.AxisFault: java.lang.NullPointerException at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java :396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:352) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:273) at tellabs.mtosi.DiscoveryServiceStub.getAllCapabilities(DiscoveryServiceSt ub.java:170) at tellabs.mtosi.DiscoveryServiceStub.main(DiscoveryServiceStub.java:464) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: java.lang.NullPointerException; nested exception is: java.lang.NullPointerException at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:319) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:228) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2 12) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:81 8) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( Http11Protocol.java:624) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:4 67) at com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.jav a:229) at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeAttribute(MTOMXMLStrea mWriter.java:134) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSeri alizerUtil.java:387) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSeri alizerUtil.java:171) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI mpl.java:803) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMS ourcedElementImpl.java:555) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI mpl.java:792) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMS ourcedElementImpl.java:546) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI mpl.java:807) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI mpl.java:792) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI mpl.java:807) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPE nvelopeImpl.java:180) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI mpl.java:792) at org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) at org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java: 951) kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to turn debug on
Hi, Can somebody please let me know how can I turn the debug messages on for Axis2 in Tomcat5. Thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiple parts in message
Hi,
I have a following wsdl
The getAllCapabilities request message.
The getAllCapabilities response message.
The MTOSI Discovery interface (porttype)
...
http://schemas.xmlsoap.org/soap/http"; />
The skeleton code generated by JAX-WS 2.1 is as follows
@WebService(serviceName = "DiscoveryService", portName =
"DiscoveryServiceHttp", endpointInterface =
"ws.v1.tmf854.DiscoveryService", targetNamespace = "tmf854.v1.ws",
wsdlLocation = "WEB-INF/wsdl/DiscoverServiceImpl/DiscoveryService.wsdl")
public class DiscoverServiceImpl implements
ws.v1.tmf854.DiscoveryService {
/** Creates a new instance of DiscoverServiceImpl */
public DiscoverServiceImpl() {
}
public ws.v1.tmf854.GetAllCapabilitiesResponseT
getAllCapabilities(javax.xml.ws.Holder
mtosiHeader, ws.v1.tmf854.GetAllCapabilitiesT mtosiBody) throws
ws.v1.tmf854.ProcessingFailureException {
return null;
}
}
And the code generated by axis 2 (1.1.1) is as follows
public class DiscoveryServiceSkeleton{
/**
* Auto generated method signature
* @param param0
*/
public ws.v1.tmf854.GetAllCapabilitiesResponseT
getAllCapabilities
(
ws.v1.tmf854.GetAllCapabilitiesT param0
)
throws ProcessingFailureExceptionException{
//Todo fill this with the necessary business logic
throw new
java.lang.UnsupportedOperationException("Please implement " +
this.getClass().getName() + "#getAllCapabilities");
}
}
Why the code generated by axis is missing header in request and
response?
Thanks
Kamal kang
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
Oneway msg/JMS transport
Hi, I have one way message as defined I am using JMS as transport, auto generated the code, the client seems to be waiting for the reply. Nov 21, 2006 3:43:14 PM org.apache.axis2.transport.jms.JMSSender invoke WARNING: Did not receive a JMS response within 3 ms to destination : queue://TestTopic Is it a bug? Thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Standalone axis
Title: Standalone axis Hi, I just want to setup webservice with JMS as transport and I do not want to install Tomcat or other application server. Can somebody please show me how to do this? Also, can somebody tell me if there is any documentation of 'savan'. kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs
WSDL2Java support JMS binding
Title: Re: [Axis2] Help using AXIOMXPath Hi, I would like to know, when is axis2 WSDL2Java tool going to support JMS binding from WSIF? thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs
Compilation errors with the generated code
Hi, Can somebody help me with the following compilation errors. I am using Axis2 and have included all the axis2\lib\jarfiles in the classpath. compile.src: [javac] Compiling 216 source files to D:\mtosi\test\wsdl2java\build\classes [javac] D:\mtosi\test\wsdl2java\src\tellabs\mtosi\ConfigurationServiceMessageRec eiverInOut.java:83: cannot find symbol [javac] symbol : method newXMLStreamReader() [javac] location: interface org.apache.axiom.om.OMElement [javac] (org.apache.axiom.om.OMAbstractFactory.getOMFactory(),new org.apache.axis2.util.StreamWrapper(param.newXMLStreamReader())) ; [javac] ^ [javac] D:\mtosi\test\wsdl2java\src\tellabs\mtosi\ConfigurationServiceMessageRec eiverInOut.java:120: cannot find symbol [javac] symbol : variable Factory [javac] location: interface org.apache.axiom.om.OMElement [javac] return org.apache.axiom.om.OMElement.Factory.parse( [javac] ^ [javac] D:\mtosi\test\wsdl2java\src\tellabs\mtosi\ConfigurationServiceMessageRec eiverInOut.java:124: cannot find symbol [javac] symbol : variable Factory [javac] location: interface org.apache.axiom.om.OMElement [javac] return org.apache.axiom.om.OMElement.Factory.parse( [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: D:\mtosi\test\wsdl2java\src\tellabs\mtosi\ConfigurationServiceMessageRec eiverInOut.java uses unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 3 errors Thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SOAP/JMS document
Hi, Is there a document regarding SOAP over JMS with Axis2? Thanks kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Parsing multiple wsdls sequentially
Hi, I am a rookie in axis wsdl parsing. I have extened axis (basically emitter) for parsing of wsdls to my custom format. The problem I am facing with parsing, is tht If I have two wsdls " foo.wsdl" and "doo.wsdl". Where "foo.wsdl" imports "doo.wsdl". Now if I try parsing sequentially foo.wsdl, and doo.wsdl(in one session, ie passing parameters to axis emitter one after the other). Then, "foo.wsdl" is parsed correctly, but then axis refuses to parse "doo.wsdl" (Saying tht its already parsed). Can any of you axis experts please provide information on a work around for this. Looking forward to your suggestions.TIA,rgdsKamaljeet
