Perhaps I can help .. on a Linux box multiple Java threads sometimes get
listed as different processes using ps. Are you on a Linux box?
We do NOT create multiple processes for anything .. so what you're
observing is some weird reporting of the threads in the system.
Now that doesn't give
Hi, we're fairly new to Axis2 in general but lately we've been writing a
small web service to test the Sandesha2 WS-RM stack with Axis2. We have
however two questions:
1. Is it normal that it takes about 15 seconds to make 10 synchronous
requests? We are just calling a simple Web service
Toon
I'm surprised you are getting those results. The Sandesha2 code isn't
tuned and the timing parameters are not optimized for fast exchange,
but without Sandesha2 the Axis2 calls should take about 100ms for 10
calls.
Do you have some sample code I can try?
Also I don't understand the
Paul
Thanks for your reply. You're right about the timing, seems there was a
communication problem with my colleague, my appologies. I just tried it
without Sandesha and it is indeed quite fast.
To get back to the listener question what I mean is the seperate listener
logic which comes with
Toon,
as you said the listener uses port 6060 by default, but by providing a
custom configuration context you can change. Furthermore, you can use
the same configuration context across different ServiceClient(s) or even
use the same ServiceClient across different invocations.
Michele
On Wed,
Toon
Two things:
1) you can modify the default Sandesha timing parameters by editing
the module.xml inside META-INF in sandesha2.mar. The default timing
parameters are:
RetransmissionInterval 6s (6000ms)
InactivityTimeout 60s
2) When you do setUseSeparateListener, Axis2 does not spawn a new
