RE: JMS timeout

[jsheh]

setting this on the stub, did it for me.
   
options.setProperty(JMSConstants.JMS_WAIT_REPLY,Long.valueOf("some_value_inmillisecs"));

hope it helps.


mgainty wrote:
> 
> 
> take a look at JMSEndpoint javadoc at
> http://ws.apache.org/axis/java/apiDocs/org/apache/axis/transport/jms/JMSEndpoint.html
> 
> you can specfy timeout via 2nd parameter to call method
>  
> byte[]
> call(byte[] message,
>  long timeout)
> 
> 
> 
> Anyone else?
> Martin 
> __ 
> Disclaimer and confidentiality note 
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and
> Sender does not endorse distribution to any party other than intended
> recipient. Sender does not necessarily endorse content contained within
> this transmission. 
> 
> 
> Date: Tue, 12 Aug 2008 08:13:21 -0700
> From: el-al...@intalio.com
> To: axis-user@ws.apache.org
> Subject: JMS timeout
> 
> Hi everybody,
> I have set up my JMS transport, and I would like now to call a service via
> JMS.
> 
> The problem is this service needs more than 20 seconds to answer back, and
> the timeout for this transport is set to 3ms.
> 
> How can I modify the timeout?
> 
> Thanks in advance
> Ihab
> 
> 
> _
> Get more from your digital life.  Find out how.
> http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008
> 

-- 
View this message in context: 
http://www.nabble.com/JMS-timeout-tp18946364p26027126.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: JMS timeout

[Ihab EL-ALAMI]

Hi again,
Setting the JMS_WAIT_REPLY as mentionned below unfortunatly did not work.
Hence I tried to read the code of the JMSSender, and I did not see where we
read the AxisConfiguration ( that I am guessing it represents the axis2.xml)
or any other configuration to set the parameter JMS_WAIT_REPLY.

Of course I am no Axis2 expert, so I might have easily missed something :)

I hope somebody can confirm that this is indeed not possible or give me a
way to set the timeout statically and not programatically.

Another way would be the ability to access the MessageContext from a
configuration file and changing it from there. Is that possible?

Thanks again


On Fri, Aug 15, 2008 at 6:22 PM, Martin Gainty <[EMAIL PROTECTED]> wrote:

>  config the JMS_WAIT_REPLY parameter for JMSSender in the axis2.xml
> configuration file e.g.
>
> 
>  
> 1000
> 
>
> Martin
> __
> Disclaimer and confidentiality note
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>
>
> --
> Date: Fri, 15 Aug 2008 16:49:57 -0700
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: Re: JMS timeout
>
>
> Thanks Asankha!
> But I did try that before and it did not work.
> Where should I put it exactly? in the Receiver or Sender? can you please
> give me an example of axis2.xml with the modification just to make sure I am
> doing the correct thing?
> Thanks again
>
>
> On Tue, Aug 12, 2008 at 9:48 AM, Asankha C. Perera <[EMAIL PROTECTED]>wrote:
>
>  Hi Ihab
>
> Please set the message context property "JMS_WAIT_REPLY" to what you desire
> (in ms). This will override the default timeout
>
> asankha
>
> Ihab EL-ALAMI wrote:
>
> Thanks for your prompt reply,
> But  actually I am not doing that programmatically.
> Is there a way to specify that statically from the axis2.xml file for
> instance?
>
> Ihab EL ALAMI
> Process Expert
> Intalio, The Open Source BPMS Company
>
>  Date: Tue, 12 Aug 2008 08:13:21 -0700
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: JMS timeout
>
> Hi everybody,
> I have set up my JMS transport, and I would like now to call a service via
> JMS.
>
> The problem is this service needs more than 20 seconds to answer back, and
> the timeout for this transport is set to 3ms.
> How can I modify the timeout?
>
> Thanks in advance
> Ihab
>
>  --
> Get more from your digital life. Find out 
> how.<http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008>
>
>
>
> --
> Asankha C. Perera
>
> WSO2 - http://wso2.org
> http://esbmagic.blogspot.com
>
>
>
> --
> Talk to your Yahoo! Friends via Windows Live Messenger. Find Out 
> How<http://www.windowslive.com/explore/messenger?ocid=TXT_TAGLM_WL_messenger_yahoo_082008>
>

Re: JMS timeout

[Asankha C. Perera]

Hi Ihab

But I did try that before and it did not work.
Where should I put it exactly? in the Receiver or Sender? can you 
please give me an example of axis2.xml with the modification just to 
make sure I am doing the correct thing?
These need to be set as Axis2 "MessageContext" properties.. not on your 
axis2.xml


thanks
asankha



On Tue, Aug 12, 2008 at 9:48 AM, Asankha C. Perera <[EMAIL PROTECTED] 
> wrote:


Hi Ihab

Please set the message context property "JMS_WAIT_REPLY" to what
you desire (in ms). This will override the default timeout

asankha

Ihab EL-ALAMI wrote:

Thanks for your prompt reply,
But  actually I am not doing that programmatically.
Is there a way to specify that statically from the axis2.xml file
for instance?

Ihab EL ALAMI
Process Expert
Intalio, The Open Source BPMS Company

Date: Tue, 12 Aug 2008 08:13:21 -0700
From: [EMAIL PROTECTED] 
To: axis-user@ws.apache.org 
Subject: JMS timeout


Hi everybody,
I have set up my JMS transport, and I would like now to call
a service via JMS.

The problem is this service needs more than 20 seconds to
answer back, and the timeout for this transport is set to
3ms.
How can I modify the timeout?

Thanks in advance
Ihab


Get more from your digital life. Find out how.





-- 
Asankha C. Perera


WSO2 - http://wso2.org
http://esbmagic.blogspot.com




--
Asankha C. Perera

WSO2 - http://wso2.org
http://esbmagic.blogspot.com

RE: JMS timeout

[Martin Gainty]

config the JMS_WAIT_REPLY parameter for JMSSender in the axis2.xml 
configuration file e.g.


 
1000


Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


Date: Fri, 15 Aug 2008 16:49:57 -0700
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: JMS timeout

Thanks Asankha!
But I did try that before and it did not work.
Where
should I put it exactly? in the Receiver or Sender? can you please give
me an example of axis2.xml with the modification just to make sure I am doing 
the
correct thing?

Thanks again

On Tue, Aug 12, 2008 at 9:48 AM, Asankha C. Perera <[EMAIL PROTECTED]> wrote:




  
  


Hi Ihab



Please set the message context property "JMS_WAIT_REPLY" to what you
desire (in ms). This will override the default timeout



asankha



Ihab EL-ALAMI wrote:

  Thanks for your prompt reply,

But  actually I am not doing that programmatically.

Is there a way to specify that statically from the axis2.xml file for
instance?

  
Ihab EL ALAMI

Process Expert

Intalio, The Open Source BPMS Company

  

  
  
Date: Tue, 12 Aug 2008 08:13:21 -0700

From: [EMAIL PROTECTED]

To: axis-user@ws.apache.org

Subject: JMS timeout





Hi everybody,

I have set up my JMS transport, and I would like now to call a service
via JMS.



The problem is this service needs more than 20 seconds to answer back,
and the timeout for this transport is set to 3ms.

How can I modify the timeout?



Thanks in advance

Ihab






Get more from your digital life. Find out how.
  
  
  

  



-- 


Asankha C. Perera 



WSO2 - http://wso2.org

http://esbmagic.blogspot.com









_
Talk to your Yahoo! Friends via Windows Live Messenger.  Find out how.
http://www.windowslive.com/explore/messenger?ocid=TXT_TAGLM_WL_messenger_yahoo_082008

Re: JMS timeout

[Ihab EL-ALAMI]

Thanks Asankha!
But I did try that before and it did not work.
Where should I put it exactly? in the Receiver or Sender? can you please
give me an example of axis2.xml with the modification just to make sure I am
doing the correct thing?
Thanks again


On Tue, Aug 12, 2008 at 9:48 AM, Asankha C. Perera <[EMAIL PROTECTED]> wrote:

>  Hi Ihab
>
> Please set the message context property "JMS_WAIT_REPLY" to what you desire
> (in ms). This will override the default timeout
>
> asankha
>
> Ihab EL-ALAMI wrote:
>
> Thanks for your prompt reply,
> But  actually I am not doing that programmatically.
> Is there a way to specify that statically from the axis2.xml file for
> instance?
>
> Ihab EL ALAMI
> Process Expert
> Intalio, The Open Source BPMS Company
>
>  Date: Tue, 12 Aug 2008 08:13:21 -0700
>> From: [EMAIL PROTECTED]
>> To: axis-user@ws.apache.org
>> Subject: JMS timeout
>>
>> Hi everybody,
>> I have set up my JMS transport, and I would like now to call a service via
>> JMS.
>>
>> The problem is this service needs more than 20 seconds to answer back, and
>> the timeout for this transport is set to 3ms.
>> How can I modify the timeout?
>>
>> Thanks in advance
>> Ihab
>>
>>  --
>> Get more from your digital life. Find out 
>> how.
>>
>
>
> --
> Asankha C. Perera
>
> WSO2 - http://wso2.org
> http://esbmagic.blogspot.com
>
>

Re: JMS timeout

[Ihab EL-ALAMI]

Thanks Asankha!
But I did try that before and it did not work.
Where should I put it exactly? in the Receiver or Sender? can you please
give me an example with the modification just to make sure I am doing the
correct thing?
Thanks again


Ihab EL ALAMI
Process Expert
Intalio, The Open Source BPMS Company


On Tue, Aug 12, 2008 at 9:48 AM, Asankha C. Perera <[EMAIL PROTECTED]> wrote:

>  Hi Ihab
>
> Please set the message context property "JMS_WAIT_REPLY" to what you desire
> (in ms). This will override the default timeout
>
> asankha
>
> Ihab EL-ALAMI wrote:
>
> Thanks for your prompt reply,
> But  actually I am not doing that programmatically.
> Is there a way to specify that statically from the axis2.xml file for
> instance?
>
> Ihab EL ALAMI
> Process Expert
> Intalio, The Open Source BPMS Company
>
>  Date: Tue, 12 Aug 2008 08:13:21 -0700
>> From: [EMAIL PROTECTED]
>> To: axis-user@ws.apache.org
>> Subject: JMS timeout
>>
>> Hi everybody,
>> I have set up my JMS transport, and I would like now to call a service via
>> JMS.
>>
>> The problem is this service needs more than 20 seconds to answer back, and
>> the timeout for this transport is set to 3ms.
>> How can I modify the timeout?
>>
>> Thanks in advance
>> Ihab
>>
>>  --
>> Get more from your digital life. Find out 
>> how.
>>
>
>
> --
> Asankha C. Perera
>
> WSO2 - http://wso2.org
> http://esbmagic.blogspot.com
>
>

Re: JMS timeout

[Asankha C. Perera]

Hi Ihab

Please set the message context property "JMS_WAIT_REPLY" to what you 
desire (in ms). This will override the default timeout


asankha

Ihab EL-ALAMI wrote:

Thanks for your prompt reply,
But  actually I am not doing that programmatically.
Is there a way to specify that statically from the axis2.xml file for 
instance?


Ihab EL ALAMI
Process Expert
Intalio, The Open Source BPMS Company

Date: Tue, 12 Aug 2008 08:13:21 -0700
From: [EMAIL PROTECTED] 
To: axis-user@ws.apache.org 
Subject: JMS timeout


Hi everybody,
I have set up my JMS transport, and I would like now to call a
service via JMS.

The problem is this service needs more than 20 seconds to answer
back, and the timeout for this transport is set to 3ms.
How can I modify the timeout?

Thanks in advance
Ihab


Get more from your digital life. Find out how.





--
Asankha C. Perera

WSO2 - http://wso2.org
http://esbmagic.blogspot.com

Re: JMS timeout

[Ihab EL-ALAMI]

Thanks for your prompt reply,
But  actually I am not doing that programmatically.
Is there a way to specify that statically from the axis2.xml file for
instance?

Ihab EL ALAMI
Process Expert
Intalio, The Open Source BPMS Company


On Tue, Aug 12, 2008 at 8:46 AM, Martin Gainty <[EMAIL PROTECTED]> wrote:

>  take a look at JMSEndpoint javadoc at
>
> http://ws.apache.org/axis/java/apiDocs/org/apache/axis/transport/jms/JMSEndpoint.html
>
> you can specfy timeout via 2nd parameter to call method
>   byte[] *call*(byte[] message, long timeout)
>
> Anyone else?
> Martin
> __
> Disclaimer and confidentiality note
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>
>
> --
> Date: Tue, 12 Aug 2008 08:13:21 -0700
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: JMS timeout
>
>
> Hi everybody,
> I have set up my JMS transport, and I would like now to call a service via
> JMS.
>
> The problem is this service needs more than 20 seconds to answer back, and
> the timeout for this transport is set to 3ms.
> How can I modify the timeout?
>
> Thanks in advance
> Ihab
>
> --
> Get more from your digital life. Find out 
> how.
>

RE: JMS timeout

[Martin Gainty]

take a look at JMSEndpoint javadoc at
http://ws.apache.org/axis/java/apiDocs/org/apache/axis/transport/jms/JMSEndpoint.html

you can specfy timeout via 2nd parameter to call method
 
byte[]
call(byte[] message,
 long timeout)



Anyone else?
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


Date: Tue, 12 Aug 2008 08:13:21 -0700
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: JMS timeout

Hi everybody,
I have set up my JMS transport, and I would like now to call a service via JMS.

The problem is this service needs more than 20 seconds to answer back, and the 
timeout for this transport is set to 3ms.

How can I modify the timeout?

Thanks in advance
Ihab


_
Get more from your digital life.  Find out how.
http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008