See http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/2182/changes
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
+1
it will be more convenient and more closer to real user requirements. 1 hour
is to much. I think 1min is more appropriate.
On Sun, May 16, 2010 at 10:17 AM, Supun Kamburugamuva supu...@gmail.comwrote:
At the moment default endpoint suspension time is set to 60 * 60 * 1000
miliseconds.
What about the metrics != null part of the condition?
Andreas
On Sun, May 16, 2010 at 03:55, Ruwan Linton ruwan.lin...@gmail.com wrote:
Hi Andreas,
Although the existing code calls requestCompletionTime unnecessarily even
before the encoder gets completed, it captures the
See
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-nhttp-transport/2183/
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail:
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/2183/
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
See
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-nhttp-transport/2184/
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail:
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/2184/
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
On Sun, May 16, 2010 at 12:17 PM, Miyuru miyur...@gmail.com wrote:
+1
it will be more convenient and more closer to real user requirements.
Not exactly. IMO 1 hour is suitable for most production scenarios. In a real
system, if an endpoint gets suspended, that usually means something has
I think Even for a production scenario setting this to 1 hour is too much.
Normally if a sever crashes it doesn't take 1 hour to restart it. Also from
synapse point of view it is always better to try the failed endpoint more
frequently than waiting for 1 hour dropping messages.
Thanks,
Supun..
No worries to have. The failure was caused by a build of
axis2-transports-trunk running on the same slave at the same time
(causing java.lang.NoClassDefFoundError:
org/apache/axis2/transport/base/MetricsCollector in Synapse).
Andreas
On Sun, May 16, 2010 at 10:13, Apache Hudson Server
Right, metrics != null has nothing to do with this, ideally it should be
outside of that block. I will fix it.
Thanks,
Ruwan
On Sun, May 16, 2010 at 1:15 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
What about the metrics != null part of the condition?
Andreas
On Sun, May 16, 2010
On Sun, May 16, 2010 at 2:48 PM, Supun Kamburugamuva supu...@gmail.comwrote:
I think Even for a production scenario setting this to 1 hour is too much.
Normally if a sever crashes it doesn't take 1 hour to restart it. Also from
synapse point of view it is always better to try the failed
I am not that concerned about the default suspension time (since it is
anyway configurable), rather we should give the control over JMX to
enable/activate endpoints.
I prefer keeping it as it is, but do not have any arguments.
Thanks,
Ruwan
On Sun, May 16, 2010 at 2:48 PM, Supun Kamburugamuva
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/2189/
--
[...truncated 251 lines...]
Downloading:
http://repository.apache.org/snapshots/org/apache/axis2/axis2-transport-local/SNAPSHOT/axis2-transport-local-SNAPSHOT.pom
3K downloaded
The FIX Transport Would Apply the Acceptor Logging and Message Store
Configurations to the Initiators
-
Key: SYNAPSE-648
URL:
Make it Possible to Create a Proxy Service Solely as a FIX Initiator
Key: SYNAPSE-649
URL: https://issues.apache.org/jira/browse/SYNAPSE-649
Project: Synapse
Issue Type:
Make the Usage of CDATA Optional in the FIX SOAP Infoset
Key: SYNAPSE-650
URL: https://issues.apache.org/jira/browse/SYNAPSE-650
Project: Synapse
Issue Type: Improvement
17 matches
Mail list logo
