dev@synapse.apache.org Archives

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #92

2009-12-06T06:06:42Z

See 

------------------------------------------
[...truncated 463 lines...]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-20] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-20] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
[IsolatedClassLoader@15cda3f] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:167) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@15cda3f] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:287) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
ERROR [HttpServerWorker-7] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-7] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-7] HttpCoreNIOSender IO Error sending response message to : 127.0.0.1
org.apache.axis2.AxisFault: Bad file number
	at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
	at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83)
	at org.apache.synapse.transport.nhttp.HttpCoreNIOSender.writeTo_aroundBody0(HttpCoreNIOSender.java:446)
	at org.apache.synapse.transport.nhttp.HttpCoreNIOSender$AjcClosure1.run(HttpCoreNIOSender.java:1)
	at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:173)
	at org.apache.axis2.transport.testkit.axis2.LogAspect.aroundWriteTo(LogAspect.java:54)
	at org.apache.synapse.transport.nhttp.HttpCoreNIOSender.sendAsyncResponse(HttpCoreNIOSender.java:446)
	at org.apache.synapse.transport.nhttp.HttpCoreNIOSender.invoke(HttpCoreNIOSender.java:262)
	at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:518)
	at org.apache.synapse.transport.nhttp.ServerWorker.handleException(ServerWorker.java:644)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:356)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Caused by: com.ctc.wstx.exc.WstxIOException: Bad file number
	at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313)
	at org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:168)
	at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:487)
	at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79)
	... 14 more
Caused by: java.io.IOException: Bad file number
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at org.apache.commons.io.output.TeeOutputStream.write(TeeOutputStream.java:63)
	at com.ctc.wstx.sw.EncodingXmlWriter.flushBuffer(EncodingXmlWriter.java:527)
	at com.ctc.wstx.sw.EncodingXmlWriter.flush(EncodingXmlWriter.java:157)
	at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:311)
	... 17 more
ERROR [HttpServerWorker-7] ServerHandler Unexpected HTTP protocol error : Transfer-encoding
header already present
org.apache.http.ProtocolException: Transfer-encoding header already present
	at org.apache.http.protocol.ResponseContent.process(ResponseContent.java:63)
	at org.apache.http.protocol.BasicHttpProcessor.process(BasicHttpProcessor.java:211)
	at org.apache.synapse.transport.nhttp.ServerHandler.commitResponseHideExceptions(ServerHandler.java:276)
	at org.apache.synapse.transport.nhttp.ServerWorker.handleException(ServerWorker.java:649)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:356)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-7] NativeWorkerPool Uncaught exception
java.lang.IllegalStateException: Buffer already closed for writing
	at org.apache.http.nio.util.SharedOutputBuffer.write(SharedOutputBuffer.java:142)
	at org.apache.http.nio.entity.ContentOutputStream.write(ContentOutputStream.java:71)
	at org.apache.synapse.transport.nhttp.ServerWorker.handleException(ServerWorker.java:652)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:356)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-d0a215f2-de3b-4de4-b4cc-69969dbc1764
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
log4j:ERROR Failed to flush writer,
java.io.InterruptedIOException
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
	at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:57)
	at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:315)
	at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
	at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
	at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
	at org.apache.log4j.Category.callAppenders(Category.java:203)
	at org.apache.log4j.Category.forcedLog(Category.java:388)
	at org.apache.log4j.Category.log(Category.java:853)
	at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
	at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:659)
Tests run: 77, Failures: 1, Errors: 9, Skipped: 0, Time elapsed: 72.415 sec <<< FAILURE!

Results :

Failed tests: 
  0034:test=AsyncXML,data=ASCII,messageType=SOAP11,forceHTTP10=true,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests in error: 
  0056:test=AsyncTextPlain,data=ASCII,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0057:test=AsyncTextPlain,data=UTF8,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0058:test=AsyncTextPlain,data=Latin1,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0059:test=AsyncTextPlain,data=ASCII,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0060:test=AsyncTextPlain,data=UTF8,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0061:test=AsyncTextPlain,data=Latin1,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0072:test=AsyncBinary,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0073:test=AsyncBinary,forceHTTP10=false,client=axis,endpoint=jetty(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0077:test=MinConcurrency(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests run: 77, Failures: 1, Errors: 9, Skipped: 0

[ERROR] There are test failures.
[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [assembly:attached {execution: attach-testkit-logs}]
[INFO] Reading assembly descriptor: src/main/assembly/testkit-logs.xml
[INFO] Building zip: 
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-06_06-02-07/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-06_06-02-07/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-06_06-02-07/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-06_06-02-07/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 10 seconds
[INFO] Finished at: Sun Dec 06 06:06:29 UTC 2009
[INFO] Final Memory: 40M/183M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data
Sending e-mails to: dev@synapse.apache.org
Sending e-mails to: dev@synapse.apache.org
channel stopped


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Build_failed_in_Hudson:_Synapse_-_1.3_-_SNA?= =?UTF-8?Q?PSHOT_=C2=BB_Apache_Synapse_-_PIPE_Transport_#92?=

2009-12-06T06:06:39Z

See 

------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-06_06-02-07/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 10 seconds
[INFO] Finished at: Sun Dec 06 06:06:29 UTC 2009
[INFO] Final Memory: 40M/183M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Hudson_build_is_still_unstable:_Synapse_-_1.3_-_SNAPSH?= =?UTF-8?Q?OT_=C2=BB_Apache_Synapse_-_Non-blocking_HTTP/s_Transport_#92?=

2009-12-06T06:06:36Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #91

2009-12-06T00:15:04Z

See 

------------------------------------------
[...truncated 55 lines...]
[INFO] snapshot org.apache.sandesha2:sandesha2-parent:SNAPSHOT: checking for updates from
apache.snapshots
11K downloaded
[INFO] snapshot org.apache.axis2:addressing:SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:addressing:SNAPSHOT: checking for updates from wso2-m2
[INFO] snapshot org.apache.axis2:addressing:SNAPSHOT: checking for updates from apache.snapshots
[INFO] snapshot org.apache.axis2:axis2-parent:SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-parent:SNAPSHOT: checking for updates from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-parent:SNAPSHOT: checking for updates from apache.snapshots
Downloading: http://repository.apache.org/snapshots/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://dist.wso2.org/maven2//java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://people.apache.org/~asankha/repository/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://repo1.maven.org/maven2/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://repository.apache.org/snapshots/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://dist.wso2.org/maven2//JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://people.apache.org/~asankha/repository/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://repo1.maven.org/maven2/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
365K downloaded
[INFO] [compiler:compile]
Compiling 77 source files to 
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 1 source file to 
[INFO] [surefire:test]
[INFO] Surefire report directory: 

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.synapse.util.TemporaryDataTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.055 sec

Results :

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0

[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-commons/builds/2009-12-06_00-10-10/archive/org.apache.synapse/synapse-commons/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-commons/builds/2009-12-06_00-10-10/archive/org.apache.synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - Transports
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-transports/1.3.0-SNAPSHOT/synapse-transports-1.3.0-SNAPSHOT.pom
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-transports/builds/2009-12-06_00-10-10/archive/org.apache.synapse/synapse-transports/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - Non-blocking HTTP/s Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
apache.snapshots
6K downloaded
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from apache.snapshots
15K downloaded
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from apache.snapshots
8K downloaded
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
wso2-m2
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
apache.snapshots
100K downloaded
[INFO] [compiler:compile]
Compiling 29 source files to 
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: org.aspectj:aspectjweaver:?:jar
[INFO] Copying aspectjweaver-1.6.1.jar to 
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
192K downloaded
[INFO] [compiler:testCompile]
Compiling 2 source files to 
[INFO] [surefire:test]
[INFO] Surefire report directory: 
[IsolatedClassLoader@15cda3f] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.HttpCoreNIOSender'
(HttpCoreNIOSender.java:446) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@15cda3f] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.HttpCoreNIOSender'
(HttpCoreNIOSender.java:652) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest
Dec 6, 2009 12:14:14 AM org.apache.axis2.deployment.util.TempFileManager 
INFO: TempFileManager::unable to delete /var/tmp/axis2-tmp-25688.tmp
[IsolatedClassLoader@15cda3f] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:167) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@15cda3f] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:287) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
log4j:ERROR Failed to flush writer,
java.io.InterruptedIOException
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
	at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:57)
	at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:315)
	at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
	at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
	at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
	at org.apache.log4j.Category.callAppenders(Category.java:203)
	at org.apache.log4j.Category.forcedLog(Category.java:388)
	at org.apache.log4j.Category.log(Category.java:853)
	at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
	at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:659)
ERROR [HttpServerWorker-1] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-2] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-3] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-4] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Tests run: 77, Failures: 2, Errors: 6, Skipped: 0, Time elapsed: 143.984 sec <<<
FAILURE!

Results :

Failed tests: 
  0034:test=AsyncXML,data=ASCII,messageType=SOAP11,forceHTTP10=true,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0074:test=AsyncBinary,forceHTTP10=true,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests in error: 
  0056:test=AsyncTextPlain,data=ASCII,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0057:test=AsyncTextPlain,data=UTF8,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0059:test=AsyncTextPlain,data=ASCII,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0060:test=AsyncTextPlain,data=UTF8,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0061:test=AsyncTextPlain,data=Latin1,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0076:test=REST,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests run: 77, Failures: 2, Errors: 6, Skipped: 0

[ERROR] There are test failures.
[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [assembly:attached {execution: attach-testkit-logs}]
[INFO] Reading assembly descriptor: src/main/assembly/testkit-logs.xml
[INFO] Building zip: 
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-06_00-10-10/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-06_00-10-10/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-06_00-10-10/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-06_00-10-10/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 38 seconds
[INFO] Finished at: Sun Dec 06 00:14:56 UTC 2009
[INFO] Final Memory: 40M/194M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data
Sending e-mails to: dev@synapse.apache.org
Sending e-mails to: dev@synapse.apache.org
channel stopped


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Build_failed_in_Hudson:_Synapse_-_1.3_-_SNA?= =?UTF-8?Q?PSHOT_=C2=BB_Apache_Synapse_-_PIPE_Transport_#91?=

2009-12-06T00:15:02Z

See 

------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-06_00-10-10/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 38 seconds
[INFO] Finished at: Sun Dec 06 00:14:56 UTC 2009
[INFO] Final Memory: 40M/194M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Hudson_build_is_still_unstable:_Synapse_-_1.3_-_SNAPSH?= =?UTF-8?Q?OT_=C2=BB_Apache_Synapse_-_Non-blocking_HTTP/s_Transport_#91?=

2009-12-06T00:15:01Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Re: Advice on choosing http core NIO version for Synapse 1.2

2009-12-06T00:14:06Z

Oleg,

I think this will be very useful in general for synapse. Is this logging
behaviour on the synapse trunk??

Thanks,
Ruwan

On Sat, Dec 5, 2009 at 8:28 PM, Oleg Kalnichevski  wrote:

> Hubert, Eric wrote:
>
>> Hi all,
>>
>> we are currently using Synapse 1.2 with http-core-nio 4.0 beta2. From time
>> to time and unfortunately not reproducible we encounter IOReactor shutdowns
>> in our production environment. I would like to track down the actual cause
>> of these shutdowns, but the logs reveal no detail.
>> I quickly went through the release notes of http core 4.0-beta3, 4.0 and
>> 4.0.1. HTTPCORE-169 looked quite interesting. I remember that some time back
>> we tried out 4.0 but stumbled across an issue related to chunked encoding.
>> Unfortunately my memory has flashed. It could be that it was related to
>> HTTPCORE-175.
>>
>> Would it be advisable to check out updating to 4.0.1? Is there any chance
>> to get some information about the actual cause in case of IOReactor
>> terminations?
>>
>>
>> Thanks,
>>   Eric
>>
>
>
> Hi Eric
>
> I cannot think of any good reason to continue using HttpCore older than
> 4.0.1. Upgrade would be quite recommended.
>
> The process of an I/O reactor shutdown is quite complex and therefore lots
> of things can go sideways if a particular I/O worker terminates abnormally
> due to a runtime or a fatal I/O error. To help deal with postmortem analysis
> I/O reactors maintain so called exception log that contains all exceptions
> thrown in the process of reactor shutdown including the one that triggered
> it.
>
> http://hc.apache.org/httpcomponents-core/tutorial/html/nio.html#d0e1287
>
> Whenever an I/O reactor terminates it is advisable to examine the audit log
> and if it contains any entries print them out to the application log.
>
> Hope this helps
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

Re: JMX notifications for Endpoint state changes

2009-12-05T18:35:09Z

I suggested the common configuration mainly due a requirement for
implementing some ideas I had many time earlier. It is in archive [1] and it
contains a PDF attachment describing the basic idea. Actually, a university
student did a successful POC of the idea. Furthermore, In the synapse code
base, I have created a package �aspects� for this and added
�AspectConfiguration�. I also used a separate interface
�StatisticsConfigurable� for the statistics and expected to provide
interfaces for others such as tracing. However, I had no time those days, so
I added some temporary code just to preserve the backward compatibility of
the statistics collecting.

My preferences for a proper implementation

Defining configuration

A language construct that may be similar to what I have suggested in an
earlier post � aspect configuration.  Statistics, monitoring, etc are
configured though a policy whose syntax is written in a unique way (at least
like a spring bean).  The global aspect configuration is named as �system�.
It is the default one for any one. This can be overridden by defining inline
aspects configurations within endpoint, sequence, etc� In addition, if it is
needed to share a same configuration by many, then the configuration is
defined as a named aspect configuration and each component (sequence,
etc...) required it refers using an attribute �aspectRef�.

Implementation

EDA model � That can be used by any other places such as passive logging,
passive persistence, etc�,. This model should support required extensibility
to support SEDA model.  Concepts of patterns such as Command, Event Channel,
Pipe and Filters, Reactor, etc definitely help for a proper implementation.
I have a little bit personal experience of the use of this kind of model.

Thanks
Indika

[1] http://markmail.org/message/rrpalubz2dj2ff3g

Please Note :

These are just my preferences

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #90

2009-12-05T18:10:49Z

See 

Changes:

[ruwan] Applying the patch from Eric on https://issues.apache.org/jira/browse/SYNAPSE-594

------------------------------------------
[...truncated 49 lines...]
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.sandesha2:sandesha2-core:SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.sandesha2:sandesha2-core:SNAPSHOT: checking for updates from wso2-m2
2K downloaded
[INFO] snapshot org.apache.sandesha2:sandesha2-parent:SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.sandesha2:sandesha2-parent:SNAPSHOT: checking for updates from
wso2-m2
11K downloaded
[INFO] snapshot org.apache.axis2:addressing:SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:addressing:SNAPSHOT: checking for updates from wso2-m2
Downloading: http://repository.apache.org/snapshots/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://dist.wso2.org/maven2//java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://people.apache.org/~asankha/repository/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://repo1.maven.org/maven2/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://repository.apache.org/snapshots/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://dist.wso2.org/maven2//JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://people.apache.org/~asankha/repository/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://repo1.maven.org/maven2/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
365K downloaded
[INFO] [compiler:compile]
Compiling 77 source files to 
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 1 source file to 
[INFO] [surefire:test]
[INFO] Surefire report directory: 

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.synapse.util.TemporaryDataTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.148 sec

Results :

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0

[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-commons/builds/2009-12-05_18-02-02/archive/org.apache.synapse/synapse-commons/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-commons/builds/2009-12-05_18-02-02/archive/org.apache.synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - Transports
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-transports/1.3.0-SNAPSHOT/synapse-transports-1.3.0-SNAPSHOT.pom
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-transports/builds/2009-12-05_18-02-02/archive/org.apache.synapse/synapse-transports/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - Non-blocking HTTP/s Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
wso2-m2
6K downloaded
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from wso2-m2
15K downloaded
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from wso2-m2
8K downloaded
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
wso2-m2
100K downloaded
[INFO] [compiler:compile]
Compiling 29 source files to 
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: org.aspectj:aspectjweaver:?:jar
[INFO] Copying aspectjweaver-1.6.1.jar to 
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
192K downloaded
[INFO] [compiler:testCompile]
Compiling 2 source files to 
[INFO] [surefire:test]
[INFO] Surefire report directory: 
[IsolatedClassLoader@11c8a71] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.HttpCoreNIOSender'
(HttpCoreNIOSender.java:446) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@11c8a71] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.HttpCoreNIOSender'
(HttpCoreNIOSender.java:652) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest
Dec 5, 2009 6:08:48 PM org.apache.axis2.deployment.util.TempFileManager 
INFO: TempFileManager::unable to delete /var/tmp/axis2-tmp-25688.tmp
Dec 5, 2009 6:08:48 PM org.apache.axis2.deployment.util.TempFileManager 
INFO: TempFileManager::unable to delete /var/tmp/axis2-tmp-41996.tmp
[IsolatedClassLoader@11c8a71] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:167) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@11c8a71] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:287) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
ERROR [HttpServerWorker-2] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-3] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-4] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-5] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Tests run: 77, Failures: 12, Errors: 14, Skipped: 0, Time elapsed: 251.48 sec <<<
FAILURE!

Results :

Failed tests: 
  0012:test=AsyncXML,data=ASCII,messageType=SOAP11,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0013:test=AsyncXML,data=ASCII,messageType=SOAP12,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0014:test=AsyncXML,data=ASCII,messageType=POX,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0015:test=AsyncXML,data=UTF8,messageType=SOAP11,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0016:test=AsyncXML,data=UTF8,messageType=SOAP12,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0017:test=AsyncXML,data=UTF8,messageType=POX,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0018:test=AsyncXML,data=Latin1,messageType=SOAP11,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0019:test=AsyncXML,data=Latin1,messageType=SOAP12,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0020:test=AsyncXML,data=Latin1,messageType=POX,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0021:test=AsyncSwA,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0022:test=AsyncSOAPLarge,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0065:test=AsyncTextPlain,data=ASCII,forceHTTP10=true,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests in error: 
  0001:test=AsyncXML,data=ASCII,messageType=SOAP11,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0002:test=AsyncXML,data=ASCII,messageType=SOAP12,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0003:test=AsyncXML,data=ASCII,messageType=POX,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0004:test=AsyncXML,data=UTF8,messageType=SOAP11,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0005:test=AsyncXML,data=UTF8,messageType=SOAP12,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0006:test=AsyncXML,data=UTF8,messageType=POX,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0007:test=AsyncXML,data=Latin1,messageType=SOAP11,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0008:test=AsyncXML,data=Latin1,messageType=SOAP12,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0009:test=AsyncXML,data=Latin1,messageType=POX,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0010:test=AsyncSwA,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0011:test=AsyncSOAPLarge,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0056:test=AsyncTextPlain,data=ASCII,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0057:test=AsyncTextPlain,data=UTF8,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0071:test=AsyncBinary,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests run: 77, Failures: 12, Errors: 14, Skipped: 0

[ERROR] There are test failures.
[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [assembly:attached {execution: attach-testkit-logs}]
[INFO] Reading assembly descriptor: src/main/assembly/testkit-logs.xml
[INFO] Building zip: 
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_18-02-02/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_18-02-02/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_18-02-02/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-05_18-02-02/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 minutes 24 seconds
[INFO] Finished at: Sat Dec 05 18:10:43 UTC 2009
[INFO] Final Memory: 39M/195M
[INFO] ------------------------------------------------------------------------
Sending e-mails to: dev@synapse.apache.org
Sending e-mails to: dev@synapse.apache.org
channel stopped


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Build_failed_in_Hudson:_Synapse_-_1.3_-_SNA?= =?UTF-8?Q?PSHOT_=C2=BB_Apache_Synapse_-_PIPE_Transport_#90?=

2009-12-05T18:10:47Z

See 

------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-05_18-02-02/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 minutes 24 seconds
[INFO] Finished at: Sat Dec 05 18:10:43 UTC 2009
[INFO] Final Memory: 39M/195M
[INFO] ------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Hudson_build_is_unstable:_Synapse_-_1.3_-_SNAPSHOT_?= =?UTF-8?Q?=C2=BB_Apache_Synapse_-_Non-blocking_HTTP/s_Transport_#90?=

2009-12-05T18:10:46Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Re: Advice on choosing http core NIO version for Synapse 1.2

2009-12-05T14:58:09Z

Hubert, Eric wrote:
> Hi all,
> 
> we are currently using Synapse 1.2 with http-core-nio 4.0 beta2. From time to time and
unfortunately not reproducible we encounter IOReactor shutdowns in our production environment.
I would like to track down the actual cause of these shutdowns, but the logs reveal no detail.

> 
> I quickly went through the release notes of http core 4.0-beta3, 4.0 and 4.0.1. HTTPCORE-169
looked quite interesting. I remember that some time back we tried out 4.0 but stumbled across
an issue related to chunked encoding. Unfortunately my memory has flashed. It could be that
it was related to HTTPCORE-175.
> 
> Would it be advisable to check out updating to 4.0.1? Is there any chance to get some
information about the actual cause in case of IOReactor terminations?
> 
> 
> Thanks,
>    Eric

Hi Eric

I cannot think of any good reason to continue using HttpCore older than 
4.0.1. Upgrade would be quite recommended.

The process of an I/O reactor shutdown is quite complex and therefore 
lots of things can go sideways if a particular I/O worker terminates 
abnormally due to a runtime or a fatal I/O error. To help deal with 
postmortem analysis I/O reactors maintain so called exception log that 
contains all exceptions thrown in the process of reactor shutdown 
including the one that triggered it.

http://hc.apache.org/httpcomponents-core/tutorial/html/nio.html#d0e1287

Whenever an I/O reactor terminates it is advisable to examine the audit 
log and if it contains any entries print them out to the application log.

Hope this helps

Oleg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Advice on choosing http core NIO version for Synapse 1.2

2009-12-05T14:21:34Z

Hi all,

we are currently using Synapse 1.2 with http-core-nio 4.0 beta2. From time to time and unfortunately
not reproducible we encounter IOReactor shutdowns in our production environment. I would like
to track down the actual cause of these shutdowns, but the logs reveal no detail. 

I quickly went through the release notes of http core 4.0-beta3, 4.0 and 4.0.1. HTTPCORE-169
looked quite interesting. I remember that some time back we tried out 4.0 but stumbled across
an issue related to chunked encoding. Unfortunately my memory has flashed. It could be that
it was related to HTTPCORE-175.

Would it be advisable to check out updating to 4.0.1? Is there any chance to get some information
about the actual cause in case of IOReactor terminations?


Thanks,
   Eric

[jira] Resolved: (SYNAPSE-594) AbstractDBMediatorFactory should not create/lookup data sources

2009-12-05T12:16:20Z


     [ https://issues.apache.org/jira/browse/SYNAPSE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ruwan Linton resolved SYNAPSE-594.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3

Applied the patch from Eirc and commited to 1.3 branch as well as to the trunk.

> AbstractDBMediatorFactory should not create/lookup data sources
> ---------------------------------------------------------------
>
>                 Key: SYNAPSE-594
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-594
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: NIGHTLY
>            Reporter: Eric Hubert
>            Assignee: Ruwan Linton
>             Fix For: 1.3
>
>         Attachments: DataSourceInit.patch
>
>
> The process of building the in-memory object representation of the Synapse configuration
should be separated from the initialisation of mediators.
> The attached patch moves the creation/lookup of data sources to the AbstractDBMediator.
The factory only reads the XML confguration and transforms it to an object model.
> This allows to create a Synapse Configuration including data sources from an XML file
without having to have a fully initialized Synapse Environment available.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

[jira] Commented: (SYNAPSE-594) AbstractDBMediatorFactory should not create/lookup data sources

2009-12-05T12:14:20Z


    [ https://issues.apache.org/jira/browse/SYNAPSE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786376#action_12786376
] 

Ruwan Linton commented on SYNAPSE-594:
--------------------------------------

Eric, 

Thanks for the patch, this further cleans up the synapse startup.

Thanks,
Ruwan

> AbstractDBMediatorFactory should not create/lookup data sources
> ---------------------------------------------------------------
>
>                 Key: SYNAPSE-594
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-594
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: NIGHTLY
>            Reporter: Eric Hubert
>            Assignee: Ruwan Linton
>         Attachments: DataSourceInit.patch
>
>
> The process of building the in-memory object representation of the Synapse configuration
should be separated from the initialisation of mediators.
> The attached patch moves the creation/lookup of data sources to the AbstractDBMediator.
The factory only reads the XML confguration and transforms it to an object model.
> This allows to create a Synapse Configuration including data sources from an XML file
without having to have a fully initialized Synapse Environment available.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

[jira] Assigned: (SYNAPSE-594) AbstractDBMediatorFactory should not create/lookup data sources

2009-12-05T12:12:20Z


     [ https://issues.apache.org/jira/browse/SYNAPSE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ruwan Linton reassigned SYNAPSE-594:
------------------------------------

    Assignee: Ruwan Linton

> AbstractDBMediatorFactory should not create/lookup data sources
> ---------------------------------------------------------------
>
>                 Key: SYNAPSE-594
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-594
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: NIGHTLY
>            Reporter: Eric Hubert
>            Assignee: Ruwan Linton
>         Attachments: DataSourceInit.patch
>
>
> The process of building the in-memory object representation of the Synapse configuration
should be separated from the initialisation of mediators.
> The attached patch moves the creation/lookup of data sources to the AbstractDBMediator.
The factory only reads the XML confguration and transforms it to an object model.
> This allows to create a Synapse Configuration including data sources from an XML file
without having to have a fully initialized Synapse Environment available.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #88

2009-12-05T06:06:12Z

See 

------------------------------------------
[...truncated 331 lines...]
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-17] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-17] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-18] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-18] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-2] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-2] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
[IsolatedClassLoader@b82368] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:167) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@b82368] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:287) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
ERROR [HttpServerWorker-5] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-5] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
log4j:ERROR Failed to flush writer,
java.io.InterruptedIOException
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
	at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:57)
	at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:315)
	at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
	at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
	at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
	at org.apache.log4j.Category.callAppenders(Category.java:203)
	at org.apache.log4j.Category.forcedLog(Category.java:388)
	at org.apache.log4j.Category.log(Category.java:853)
	at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
	at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:659)
ERROR [HttpServerWorker-1] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-347c1d21-9d7a-4f24-ab77-7de9d9b64c62
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Tests run: 77, Failures: 1, Errors: 6, Skipped: 0, Time elapsed: 69.347 sec <<< FAILURE!

Results :

Failed tests: 
  0074:test=AsyncBinary,forceHTTP10=true,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests in error: 
  0056:test=AsyncTextPlain,data=ASCII,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0057:test=AsyncTextPlain,data=UTF8,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0059:test=AsyncTextPlain,data=ASCII,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0060:test=AsyncTextPlain,data=UTF8,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0061:test=AsyncTextPlain,data=Latin1,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0077:test=MinConcurrency(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests run: 77, Failures: 1, Errors: 6, Skipped: 0

[ERROR] There are test failures.
[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [assembly:attached {execution: attach-testkit-logs}]
[INFO] Reading assembly descriptor: src/main/assembly/testkit-logs.xml
[INFO] Building zip: 
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_06-01-52/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_06-01-52/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_06-01-52/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-05_06-01-52/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 51 seconds
[INFO] Finished at: Sat Dec 05 06:06:03 UTC 2009
[INFO] Final Memory: 39M/152M
[INFO] ------------------------------------------------------------------------
Sending e-mails to: dev@synapse.apache.org
Sending e-mails to: dev@synapse.apache.org
channel stopped


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Build_failed_in_Hudson:_Synapse_-_1.3_-_SNA?= =?UTF-8?Q?PSHOT_=C2=BB_Apache_Synapse_-_PIPE_Transport_#88?=

2009-12-05T06:06:10Z

See 

------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-05_06-01-52/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 51 seconds
[INFO] Finished at: Sat Dec 05 06:06:03 UTC 2009
[INFO] Final Memory: 39M/152M
[INFO] ------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Hudson_build_is_still_unstable:_Synapse_-_1.3_-_SNAPSH?= =?UTF-8?Q?OT_=C2=BB_Apache_Synapse_-_Non-blocking_HTTP/s_Transport_#88?=

2009-12-05T06:06:07Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Re: JMX notifications for Endpoint state changes

2009-12-05T02:43:41Z

Hhhmmm, not sure whether it is good to keep a one global aspect
configuration which configures all the child nodes even when you need to
turn on statistics (for example) for a given sequence, that will make the
configuration readability harder. I would think of the implementation when
deciding the configuration design, so that it is not affecting the
performance as well.

I would like to keep a global configuration of aspects, yes as Supun
explined that can define whether all services, all endpoints or
sequences.... but not a named entity. The default behaviour will be at
global level all these will be turned off for all types of entities.

Then at each and every element level you can define there aspects using the
same configuraiton.

Alternately, we could let the aspect configurations to be refered from from
all the elements, inorder to make this work we need to be able to define a
named set of aspects and from services and sequences they can refer to its
aspect. It will enable us to reuse the aspect configuraitons of the same
type within different elements without redefining.

Being said all that I would like to do the initial implementation of this,
considering the amount of change that this idea is going to take us.

Thanks,
Ruwan

On Sat, Dec 5, 2009 at 2:04 AM, Supun Kamburugamuva wrote:

> Hi,
>
> If we can define the statistics enabled endpoints or mediators at the top
> level aspect configuration we can leave the aspect configuration element
> only to the top level. This reduce the clutter from the specific component
> configurations. Specific component configurations can focus only on what
> they are mean to do. Things like statistics collection can be separated from
> the mediator configurations.
>
> Thanks,
> Supun..
>
>
> On Sat, Dec 5, 2009 at 1:56 AM, Hubert, Eric wrote:
>
>>  I would vote for both, on global and on those child elements where it is
>> applicable with the simple rule, that at runtime the most specific one wins.
>>
>>
>>
>> This would allow for the following scenarios.
>>
>>
>>
>> Turn it off for all (globally)
>>
>> Turn it off globally, but only activate it on demand for specific
>> endpoints, services etc.
>>
>> Turn it on globally
>>
>> Turn it on globally, but disable it for some specific services, endpoints
>> (exclusions)
>>
>>
>>
>> Of cause you could also add a configuration right in the middle on the
>> level of the services or endpoints etc., if someone also wants to turn an
>> aspect only on for ALL services, but not for all endpoints, but just some of
>> them.
>>
>>
>>
>> Regards,
>>
>>   Eric
>>
>>
>>
>>
>>
>>
>>   ------------------------------
>>
>> *From:* Supun Kamburugamuva [mailto:supun06@gmail.com]
>> *Sent:* Friday, December 04, 2009 8:15 PM
>>
>> *To:* dev@synapse.apache.org
>> *Subject:* Re: JMX notifications for Endpoint state changes
>>
>>
>>
>> +1 from me as well to the new aspect configuration. This solves the
>> problem more cleanly.
>>
>> I'm not clear about one thing. Shall we make this aspect configuration to
>> be a child of other elements like mediators and endpoints or is it a top
>> level configuration only?
>>
>> Thanks,
>> Supun..
>>
>> On Fri, Dec 4, 2009 at 2:23 PM, Ruwan Linton 
>> wrote:
>>
>> +1, we should go for this, and I think it will be very useful in a
>> production set up; if anything goes wrong and the admin wants to enable
>> tracing for the full synapse config he do not have to go onto each and every
>> config bit. OTOH, if he knows where the issue is he can just enable tracing
>> of that proxy only.
>>
>> Thnaks,
>> Ruwan
>>
>>
>>
>> On Fri, Dec 4, 2009 at 2:14 PM, Hubert, Eric 
>> wrote:
>>
>> Well, actually I thought in the same direction as Ruwan. If introducing a
>> global configuration option it should be consistent with the other
>> configurations like tracing and statistics. This was one point against
>> adding this only for any newly introduced feature like JMX notifications. If
>> we would like to use such a configuration option, than we should
>> consistently support this also for statistics and tracing.
>>
>>
>>   ------------------------------
>>
>> Hi Ruwan,
>>
>> I think if we do this the correct way, the way you've suggested is the
>> correct way. I was bit reluctant to do that because it is kind of like a
>> big change. At least at the conceptual level.
>>
>> I like your idea and I'll come up with an implementation.
>>
>> Eric, What do you think?
>>
>>
>>
>>    --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://ruwansblog.blogspot.com
>>
>>
>>
>>
>> --
>> Software Engineer, WSO2 Inc
>> http://wso2.org
>> supunk.blogspot.com
>>
>>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>
>


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #87

2009-12-05T00:30:38Z

See 

------------------------------------------
[...truncated 71 lines...]
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
365K downloaded
[INFO] [compiler:compile]
Compiling 77 source files to 
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 1 source file to 
[INFO] [surefire:test]
[INFO] Surefire report directory: 

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.synapse.util.TemporaryDataTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.712 sec

Results :

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0

[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-commons/builds/2009-12-05_00-25-30/archive/org.apache.synapse/synapse-commons/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-commons/builds/2009-12-05_00-25-30/archive/org.apache.synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - Transports
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-transports/1.3.0-SNAPSHOT/synapse-transports-1.3.0-SNAPSHOT.pom
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-transports/builds/2009-12-05_00-25-30/archive/org.apache.synapse/synapse-transports/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - Non-blocking HTTP/s Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
apache.snapshots
6K downloaded
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from apache.snapshots
15K downloaded
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from wso2-m2
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from apache.snapshots
8K downloaded
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
wso2-m2
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
asankha
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
apache.snapshots
100K downloaded
[INFO] [compiler:compile]
Compiling 29 source files to 
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: org.aspectj:aspectjweaver:?:jar
[INFO] Copying aspectjweaver-1.6.1.jar to 
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
192K downloaded
[INFO] [compiler:testCompile]
Compiling 2 source files to 
[INFO] [surefire:test]
[INFO] Surefire report directory: 
[IsolatedClassLoader@b82368] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.HttpCoreNIOSender'
(HttpCoreNIOSender.java:446) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@b82368] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.HttpCoreNIOSender'
(HttpCoreNIOSender.java:652) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest
Dec 5, 2009 12:29:44 AM org.apache.axis2.deployment.util.TempFileManager 
INFO: TempFileManager::unable to delete /var/tmp/axis2-tmp-25688.tmp
[IsolatedClassLoader@b82368] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:167) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@b82368] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:287) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
log4j:ERROR Failed to flush writer,
java.io.InterruptedIOException
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
	at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:57)
	at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:315)
	at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
	at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
	at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
	at org.apache.log4j.Category.callAppenders(Category.java:203)
	at org.apache.log4j.Category.forcedLog(Category.java:388)
	at org.apache.log4j.Category.log(Category.java:853)
	at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
	at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:659)
log4j:ERROR Failed to flush writer,
java.io.InterruptedIOException
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
	at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:57)
	at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:315)
	at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
	at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
	at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
	at org.apache.log4j.Category.callAppenders(Category.java:203)
	at org.apache.log4j.Category.forcedLog(Category.java:388)
	at org.apache.log4j.Category.log(Category.java:853)
	at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
	at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:659)
ERROR [HttpServerWorker-2] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-3] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-4] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-5] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Tests run: 77, Failures: 1, Errors: 4, Skipped: 0, Time elapsed: 151.933 sec <<<
FAILURE!

Results :

Failed tests: 
  0034:test=AsyncXML,data=ASCII,messageType=SOAP11,forceHTTP10=true,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests in error: 
  0056:test=AsyncTextPlain,data=ASCII,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0059:test=AsyncTextPlain,data=ASCII,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0060:test=AsyncTextPlain,data=UTF8,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0061:test=AsyncTextPlain,data=Latin1,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests run: 77, Failures: 1, Errors: 4, Skipped: 0

[ERROR] There are test failures.
[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [assembly:attached {execution: attach-testkit-logs}]
[INFO] Reading assembly descriptor: src/main/assembly/testkit-logs.xml
[INFO] Building zip: 
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_00-25-30/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_00-25-30/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-05_00-25-30/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-05_00-25-30/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 54 seconds
[INFO] Finished at: Sat Dec 05 00:30:34 UTC 2009
[INFO] Final Memory: 40M/194M
[INFO] ------------------------------------------------------------------------
Sending e-mails to: dev@synapse.apache.org
Sending e-mails to: dev@synapse.apache.org
channel stopped


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Build_failed_in_Hudson:_Synapse_-_1.3_-_SNA?= =?UTF-8?Q?PSHOT_=C2=BB_Apache_Synapse_-_PIPE_Transport_#87?=

2009-12-05T00:30:36Z

See 

------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-05_00-25-30/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 54 seconds
[INFO] Finished at: Sat Dec 05 00:30:34 UTC 2009
[INFO] Final Memory: 40M/194M
[INFO] ------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Hudson_build_is_still_unstable:_Synapse_-_1.3_-_SNAPSH?= =?UTF-8?Q?OT_=C2=BB_Apache_Synapse_-_Non-blocking_HTTP/s_Transport_#87?=

2009-12-05T00:30:35Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Re: JMX notifications for Endpoint state changes

2009-12-04T20:34:16Z

Hi,

If we can define the statistics enabled endpoints or mediators at the top
level aspect configuration we can leave the aspect configuration element
only to the top level. This reduce the clutter from the specific component
configurations. Specific component configurations can focus only on what
they are mean to do. Things like statistics collection can be separated from
the mediator configurations.

Thanks,
Supun..

On Sat, Dec 5, 2009 at 1:56 AM, Hubert, Eric wrote:

>  I would vote for both, on global and on those child elements where it is
> applicable with the simple rule, that at runtime the most specific one wins.
>
>
>
> This would allow for the following scenarios.
>
>
>
> Turn it off for all (globally)
>
> Turn it off globally, but only activate it on demand for specific
> endpoints, services etc.
>
> Turn it on globally
>
> Turn it on globally, but disable it for some specific services, endpoints
> (exclusions)
>
>
>
> Of cause you could also add a configuration right in the middle on the
> level of the services or endpoints etc., if someone also wants to turn an
> aspect only on for ALL services, but not for all endpoints, but just some of
> them.
>
>
>
> Regards,
>
>   Eric
>
>
>
>
>
>
>   ------------------------------
>
> *From:* Supun Kamburugamuva [mailto:supun06@gmail.com]
> *Sent:* Friday, December 04, 2009 8:15 PM
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: JMX notifications for Endpoint state changes
>
>
>
> +1 from me as well to the new aspect configuration. This solves the problem
> more cleanly.
>
> I'm not clear about one thing. Shall we make this aspect configuration to
> be a child of other elements like mediators and endpoints or is it a top
> level configuration only?
>
> Thanks,
> Supun..
>
> On Fri, Dec 4, 2009 at 2:23 PM, Ruwan Linton 
> wrote:
>
> +1, we should go for this, and I think it will be very useful in a
> production set up; if anything goes wrong and the admin wants to enable
> tracing for the full synapse config he do not have to go onto each and every
> config bit. OTOH, if he knows where the issue is he can just enable tracing
> of that proxy only.
>
> Thnaks,
> Ruwan
>
>
>
> On Fri, Dec 4, 2009 at 2:14 PM, Hubert, Eric 
> wrote:
>
> Well, actually I thought in the same direction as Ruwan. If introducing a
> global configuration option it should be consistent with the other
> configurations like tracing and statistics. This was one point against
> adding this only for any newly introduced feature like JMX notifications. If
> we would like to use such a configuration option, than we should
> consistently support this also for statistics and tracing.
>
>
>   ------------------------------
>
> Hi Ruwan,
>
> I think if we do this the correct way, the way you've suggested is the
> correct way. I was bit reluctant to do that because it is kind of like a
> big change. At least at the conceptual level.
>
> I like your idea and I'll come up with an implementation.
>
> Eric, What do you think?
>
>
>
>    --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>


-- 
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com

RE: JMX notifications for Endpoint state changes

2009-12-04T20:26:36Z

I would vote for both, on global and on those child elements where it is applicable with the
simple rule, that at runtime the most specific one wins.

This would allow for the following scenarios.

Turn it off for all (globally)
Turn it off globally, but only activate it on demand for specific endpoints, services etc.
Turn it on globally
Turn it on globally, but disable it for some specific services, endpoints (exclusions)

Of cause you could also add a configuration right in the middle on the level of the services
or endpoints etc., if someone also wants to turn an aspect only on for ALL services, but not
for all endpoints, but just some of them.

Regards,
  Eric



________________________________
From: Supun Kamburugamuva [mailto:supun06@gmail.com]
Sent: Friday, December 04, 2009 8:15 PM
To: dev@synapse.apache.org
Subject: Re: JMX notifications for Endpoint state changes

+1 from me as well to the new aspect configuration. This solves the problem more cleanly.

I'm not clear about one thing. Shall we make this aspect configuration to be a child of other
elements like mediators and endpoints or is it a top level configuration only?

Thanks,
Supun..
On Fri, Dec 4, 2009 at 2:23 PM, Ruwan Linton >
wrote:
+1, we should go for this, and I think it will be very useful in a production set up; if anything
goes wrong and the admin wants to enable tracing for the full synapse config he do not have
to go onto each and every config bit. OTOH, if he knows where the issue is he can just enable
tracing of that proxy only.

Thnaks,
Ruwan

On Fri, Dec 4, 2009 at 2:14 PM, Hubert, Eric >
wrote:
Well, actually I thought in the same direction as Ruwan. If introducing a global configuration
option it should be consistent with the other configurations like tracing and statistics.
This was one point against adding this only for any newly introduced feature like JMX notifications.
If we would like to use such a configuration option, than we should consistently support this
also for statistics and tracing.

________________________________
Hi Ruwan,

I think if we do this the correct way, the way you've suggested is the correct way. I was
bit reluctant to do that because it is kind of like a big change. At least at the conceptual
level.

I like your idea and I'll come up with an implementation.

Eric, What do you think?


--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com



--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com

Re: JMX notifications for Endpoint state changes

2009-12-04T20:08:26Z

How about having following policies

ALL : no matter what is the configuration at the mediator or endpoint level
this aspect will be enabled for all the components, to further configure we
can define what is mean by all, for example all the endpoints but not
mediators or we can have a named list containing the names of the items we
need to turn this on.

NONE : no matter what is the configuration at the mediator or endpoint
level, this aspect will be disabled for all the component. as in ALL case we
can define what is meant by NONE

DEFAULT : default means the configurations at the endpoint or mediator level
will take effect

These are my initial thoughts.

Thanks,
Supun..

On Sat, Dec 5, 2009 at 12:44 AM, Supun Kamburugamuva wrote:

> +1 from me as well to the new aspect configuration. This solves the problem
> more cleanly.
>
> I'm not clear about one thing. Shall we make this aspect configuration to
> be a child of other elements like mediators and endpoints or is it a top
> level configuration only?
>
> Thanks,
> Supun..
>
>
> On Fri, Dec 4, 2009 at 2:23 PM, Ruwan Linton wrote:
>
>> +1, we should go for this, and I think it will be very useful in a
>> production set up; if anything goes wrong and the admin wants to enable
>> tracing for the full synapse config he do not have to go onto each and every
>> config bit. OTOH, if he knows where the issue is he can just enable tracing
>> of that proxy only.
>>
>> Thnaks,
>> Ruwan
>>
>>
>> On Fri, Dec 4, 2009 at 2:14 PM, Hubert, Eric wrote:
>>
>>>  Well, actually I thought in the same direction as Ruwan. If introducing
>>> a global configuration option it should be consistent with the other
>>> configurations like tracing and statistics. This was one point against
>>> adding this only for any newly introduced feature like JMX notifications. If
>>> we would like to use such a configuration option, than we should
>>> consistently support this also for statistics and tracing.
>>>
>>>
>>>   ------------------------------
>>>
>>> Hi Ruwan,
>>>
>>> I think if we do this the correct way, the way you've suggested is the
>>> correct way. I was bit reluctant to do that because it is kind of like a
>>> big change. At least at the conceptual level.
>>>
>>> I like your idea and I'll come up with an implementation.
>>>
>>> Eric, What do you think?
>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://ruwansblog.blogspot.com
>>
>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>
>


-- 
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com

Re: JMX notifications for Endpoint state changes

2009-12-04T19:14:40Z

+1 from me as well to the new aspect configuration. This solves the problem
more cleanly.

I'm not clear about one thing. Shall we make this aspect configuration to be
a child of other elements like mediators and endpoints or is it a top level
configuration only?

Thanks,
Supun..

On Fri, Dec 4, 2009 at 2:23 PM, Ruwan Linton  wrote:

> +1, we should go for this, and I think it will be very useful in a
> production set up; if anything goes wrong and the admin wants to enable
> tracing for the full synapse config he do not have to go onto each and every
> config bit. OTOH, if he knows where the issue is he can just enable tracing
> of that proxy only.
>
> Thnaks,
> Ruwan
>
>
> On Fri, Dec 4, 2009 at 2:14 PM, Hubert, Eric wrote:
>
>>  Well, actually I thought in the same direction as Ruwan. If introducing
>> a global configuration option it should be consistent with the other
>> configurations like tracing and statistics. This was one point against
>> adding this only for any newly introduced feature like JMX notifications. If
>> we would like to use such a configuration option, than we should
>> consistently support this also for statistics and tracing.
>>
>>
>>   ------------------------------
>>
>> Hi Ruwan,
>>
>> I think if we do this the correct way, the way you've suggested is the
>> correct way. I was bit reluctant to do that because it is kind of like a
>> big change. At least at the conceptual level.
>>
>> I like your idea and I'll come up with an implementation.
>>
>> Eric, What do you think?
>>
>>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>



-- 
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #86

2009-12-04T18:05:03Z

See 

------------------------------------------
[...truncated 384 lines...]
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-2] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-2] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
[IsolatedClassLoader@b82368] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:167) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@b82368] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:287) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
ERROR [HttpServerWorker-14] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-14] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] AxisEngine The service cannot be found for the endpoint reference
(EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-1] ServerWorker Error processing POST request 
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /services/TestService-637a9a2f-70be-4651-b637-332a4ed7b194
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
log4j:ERROR Failed to flush writer,
java.io.InterruptedIOException
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
	at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
	at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:57)
	at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:315)
	at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
	at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
	at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
	at org.apache.log4j.Category.callAppenders(Category.java:203)
	at org.apache.log4j.Category.forcedLog(Category.java:388)
	at org.apache.log4j.Category.log(Category.java:853)
	at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
	at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:659)
ERROR [HttpServerWorker-1] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-2] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-3] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-4] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Tests run: 77, Failures: 1, Errors: 7, Skipped: 0, Time elapsed: 56.397 sec <<< FAILURE!

Results :

Failed tests: 
  0034:test=AsyncXML,data=ASCII,messageType=SOAP11,forceHTTP10=true,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests in error: 
  0056:test=AsyncTextPlain,data=ASCII,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0057:test=AsyncTextPlain,data=UTF8,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0058:test=AsyncTextPlain,data=Latin1,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0059:test=AsyncTextPlain,data=ASCII,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0060:test=AsyncTextPlain,data=UTF8,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0061:test=AsyncTextPlain,data=Latin1,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0076:test=REST,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests run: 77, Failures: 1, Errors: 7, Skipped: 0

[ERROR] There are test failures.
[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [assembly:attached {execution: attach-testkit-logs}]
[INFO] Reading assembly descriptor: src/main/assembly/testkit-logs.xml
[INFO] Building zip: 
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-04_18-01-43/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-04_18-01-43/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-04_18-01-43/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-04_18-01-43/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 8 seconds
[INFO] Finished at: Fri Dec 04 18:04:59 UTC 2009
[INFO] Final Memory: 39M/194M
[INFO] ------------------------------------------------------------------------
Sending e-mails to: dev@synapse.apache.org
Sending e-mails to: dev@synapse.apache.org
channel stopped


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Build_failed_in_Hudson:_Synapse_-_1.3_-_SNA?= =?UTF-8?Q?PSHOT_=C2=BB_Apache_Synapse_-_PIPE_Transport_#86?=

2009-12-04T18:05:02Z

See 

------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-04_18-01-43/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 8 seconds
[INFO] Finished at: Fri Dec 04 18:04:59 UTC 2009
[INFO] Final Memory: 39M/194M
[INFO] ------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Hudson_build_is_still_unstable:_Synapse_-_1.3_-_SNAPSH?= =?UTF-8?Q?OT_=C2=BB_Apache_Synapse_-_Non-blocking_HTTP/s_Transport_#86?=

2009-12-04T18:05:01Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #85

2009-12-04T12:15:09Z

See 

------------------------------------------
[...truncated 54 lines...]
[INFO] snapshot org.apache.sandesha2:sandesha2-parent:SNAPSHOT: checking for updates from
wso2-m2
11K downloaded
[INFO] snapshot org.apache.axis2:addressing:SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:addressing:SNAPSHOT: checking for updates from wso2-m2
Downloading: http://repository.apache.org/snapshots/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://dist.wso2.org/maven2//java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://people.apache.org/~asankha/repository/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://repo1.maven.org/maven2/java-cup/java-cup/0.0/java-cup-0.0.pom
Downloading: http://repository.apache.org/snapshots/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://dist.wso2.org/maven2//JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://people.apache.org/~asankha/repository/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://repo1.maven.org/maven2/JLex/JLex/0.0/JLex-0.0.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon/8.9/saxon-8.9.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon-dom/8.9/saxon-dom-8.9.pom
Downloading: http://repository.apache.org/snapshots/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://dist.wso2.org/maven2//net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://people.apache.org/~asankha/repository/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
Downloading: http://repo1.maven.org/maven2/net/sf/saxon/saxon-xqj/8.9/saxon-xqj-8.9.pom
365K downloaded
[INFO] [compiler:compile]
Compiling 77 source files to 
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 1 source file to 
[INFO] [surefire:test]
[INFO] Surefire report directory: 

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.synapse.util.TemporaryDataTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.434 sec

Results :

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0

[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-commons/builds/2009-12-04_12-02-31/archive/org.apache.synapse/synapse-commons/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-commons/builds/2009-12-04_12-02-31/archive/org.apache.synapse/synapse-commons/1.3.0-SNAPSHOT/synapse-commons-1.3.0-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - Transports
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-transports/1.3.0-SNAPSHOT/synapse-transports-1.3.0-SNAPSHOT.pom
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-transports/builds/2009-12-04_12-02-31/archive/org.apache.synapse/synapse-transports/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - Non-blocking HTTP/s Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-base:1.0-SNAPSHOT: checking for updates from
wso2-m2
6K downloaded
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport:1.0-SNAPSHOT: checking for updates from wso2-m2
15K downloaded
[WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from apache-snapshots
[INFO] snapshot org.apache.axis2:axis2-transport-testkit:1.0-SNAPSHOT: checking for updates
from wso2-m2
8K downloaded
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
apache-snapshots
[INFO] snapshot org.apache.synapse:synapse-commons:1.3.0-SNAPSHOT: checking for updates from
wso2-m2
100K downloaded
[INFO] [compiler:compile]
Compiling 29 source files to 
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: org.aspectj:aspectjweaver:?:jar
[INFO] Copying aspectjweaver-1.6.1.jar to 
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
192K downloaded
[INFO] [compiler:testCompile]
Compiling 2 source files to 
[INFO] [surefire:test]
[INFO] Surefire report directory: 
[IsolatedClassLoader@ab853b] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.HttpCoreNIOSender'
(HttpCoreNIOSender.java:446) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@ab853b] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.HttpCoreNIOSender'
(HttpCoreNIOSender.java:652) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest
Dec 4, 2009 12:12:28 PM org.apache.axis2.deployment.util.TempFileManager 
INFO: TempFileManager::unable to delete /var/tmp/axis2-tmp-25688.tmp
Dec 4, 2009 12:12:28 PM org.apache.axis2.deployment.util.TempFileManager 
INFO: TempFileManager::unable to delete /var/tmp/axis2-tmp-31455.tmp
[IsolatedClassLoader@ab853b] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:167) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
[IsolatedClassLoader@ab853b] weaveinfo Join point 'method-call(void org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in Type 'org.apache.synapse.transport.nhttp.Axis2HttpRequest'
(Axis2HttpRequest.java:287) advised by around advice from 'org.apache.axis2.transport.testkit.axis2.LogAspect'
(LogAspect.java)
ERROR [HttpServerWorker-2] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-3] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-4] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
ERROR [HttpServerWorker-5] NativeWorkerPool Uncaught exception
java.lang.IllegalMonitorStateException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at org.apache.axis2.transport.testkit.tests.misc.MinConcurrencyTest$1.receive(MinConcurrencyTest.java:91)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
	at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:349)
	at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:241)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Tests run: 77, Failures: 12, Errors: 20, Skipped: 0, Time elapsed: 495.978 sec <<<
FAILURE!

Results :

Failed tests: 
  0012:test=AsyncXML,data=ASCII,messageType=SOAP11,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0013:test=AsyncXML,data=ASCII,messageType=SOAP12,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0014:test=AsyncXML,data=ASCII,messageType=POX,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0015:test=AsyncXML,data=UTF8,messageType=SOAP11,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0016:test=AsyncXML,data=UTF8,messageType=SOAP12,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0017:test=AsyncXML,data=UTF8,messageType=POX,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0018:test=AsyncXML,data=Latin1,messageType=SOAP11,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0019:test=AsyncXML,data=Latin1,messageType=SOAP12,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0020:test=AsyncXML,data=Latin1,messageType=POX,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0021:test=AsyncSwA,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0022:test=AsyncSOAPLarge,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0065:test=AsyncTextPlain,data=ASCII,forceHTTP10=true,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests in error: 
  0001:test=AsyncXML,data=ASCII,messageType=SOAP11,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0002:test=AsyncXML,data=ASCII,messageType=SOAP12,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0003:test=AsyncXML,data=ASCII,messageType=POX,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0004:test=AsyncXML,data=UTF8,messageType=SOAP11,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0005:test=AsyncXML,data=UTF8,messageType=SOAP12,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0006:test=AsyncXML,data=UTF8,messageType=POX,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0007:test=AsyncXML,data=Latin1,messageType=SOAP11,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0008:test=AsyncXML,data=Latin1,messageType=SOAP12,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0009:test=AsyncXML,data=Latin1,messageType=POX,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0010:test=AsyncSwA,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0011:test=AsyncSOAPLarge,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0056:test=AsyncTextPlain,data=ASCII,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0057:test=AsyncTextPlain,data=UTF8,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0058:test=AsyncTextPlain,data=Latin1,client=java.net,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0059:test=AsyncTextPlain,data=ASCII,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0060:test=AsyncTextPlain,data=UTF8,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0061:test=AsyncTextPlain,data=Latin1,forceHTTP10=false,client=axis,endpoint=axis(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0062:test=AsyncTextPlain,data=ASCII,forceHTTP10=false,client=axis,endpoint=jetty(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0063:test=AsyncTextPlain,data=UTF8,forceHTTP10=false,client=axis,endpoint=jetty(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)
  0064:test=AsyncTextPlain,data=Latin1,forceHTTP10=false,client=axis,endpoint=jetty(org.apache.synapse.transport.nhttp.HttpCoreNIOListenerTest)

Tests run: 77, Failures: 12, Errors: 20, Skipped: 0

[ERROR] There are test failures.
[HUDSON] Recording test results
[INFO] [bundle:bundle]
[INFO] [assembly:attached {execution: attach-testkit-logs}]
[INFO] Reading assembly descriptor: src/main/assembly/testkit-logs.xml
[INFO] Building zip: 
[INFO] [install:install]
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Installing 
to /export/home/hudson/.m2/repository/org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] [bundle:install]
[INFO] Parsing file:/export/home/hudson/.m2/repository/repository.xml
[INFO] Installing org/apache/synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-04_12-02-31/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/pom.xml
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-04_12-02-31/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT.jar
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-nhttp-transport/builds/2009-12-04_12-02-31/archive/org.apache.synapse/synapse-nhttp-transport/1.3.0-SNAPSHOT/synapse-nhttp-transport-1.3.0-SNAPSHOT-testkit-logs.zip
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-04_12-02-31/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12 minutes 3 seconds
[INFO] Finished at: Fri Dec 04 12:14:50 UTC 2009
[INFO] Final Memory: 40M/191M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data
Sending e-mails to: dev@synapse.apache.org
Sending e-mails to: dev@synapse.apache.org
channel stopped


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Build_failed_in_Hudson:_Synapse_-_1.3_-_SNA?= =?UTF-8?Q?PSHOT_=C2=BB_Apache_Synapse_-_PIPE_Transport_#85?=

2009-12-04T12:15:05Z

See 

------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Synapse - PIPE Transport
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory 
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to 
[HUDSON] Archiving 
to /export/home/hudson/hudson/jobs/Synapse - 1.3 - SNAPSHOT/modules/org.apache.synapse$synapse-pipe-transport/builds/2009-12-04_12-02-31/archive/org.apache.synapse/synapse-pipe-transport/1.3.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

:[107,28]
receive(java.net.SocketAddress,org.apache.axis2.transport.base.datagram.DatagramEndpoint,byte[],int)
in org.apache.axis2.transport.base.datagram.DatagramDispatcherCallback cannot be applied to
(org.apache.synapse.transport.pipe.PipeEndpoint,byte[],int)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12 minutes 3 seconds
[INFO] Finished at: Fri Dec 04 12:14:50 UTC 2009
[INFO] Final Memory: 40M/191M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Hudson_build_is_still_unstable:_Synapse_-_1.3_-_SNAPSH?= =?UTF-8?Q?OT_=C2=BB_Apache_Synapse_-_Non-blocking_HTTP/s_Transport_#85?=

2009-12-04T12:15:00Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Re: JMX notifications for Endpoint state changes

2009-12-04T08:53:33Z

+1, we should go for this, and I think it will be very useful in a
production set up; if anything goes wrong and the admin wants to enable
tracing for the full synapse config he do not have to go onto each and every
config bit. OTOH, if he knows where the issue is he can just enable tracing
of that proxy only.

Thnaks,
Ruwan

On Fri, Dec 4, 2009 at 2:14 PM, Hubert, Eric wrote:

>  Well, actually I thought in the same direction as Ruwan. If introducing a
> global configuration option it should be consistent with the other
> configurations like tracing and statistics. This was one point against
> adding this only for any newly introduced feature like JMX notifications. If
> we would like to use such a configuration option, than we should
> consistently support this also for statistics and tracing.
>
>
>   ------------------------------
>
> Hi Ruwan,
>
> I think if we do this the correct way, the way you've suggested is the
> correct way. I was bit reluctant to do that because it is kind of like a
> big change. At least at the conceptual level.
>
> I like your idea and I'll come up with an implementation.
>
> Eric, What do you think?
>
>


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

RE: JMX notifications for Endpoint state changes

2009-12-04T08:52:31Z


> From: indika kumara [mailto:indika.kuma@gmail.com]
> Sent: Friday, December 04, 2009 9:37 AM

> 
>     statistics policy 
>     trace policy 
>     monitoring policy 
>     reporting policy 
>    ……
> 

To me a grouping makes absolutely sense. This would also be beneficial to have at the global
level below definitions. I don't think that adding more and more "aspects" directly on the
top level would be a good option. So yes, I like this idea...

Regards,
  Eric

RE: JMX notifications for Endpoint state changes

2009-12-04T08:44:59Z

Well, actually I thought in the same direction as Ruwan. If introducing a global configuration
option it should be consistent with the other configurations like tracing and statistics.
This was one point against adding this only for any newly introduced feature like JMX notifications.
If we would like to use such a configuration option, than we should consistently support this
also for statistics and tracing.

________________________________
Hi Ruwan,

I think if we do this the correct way, the way you've suggested is the correct way. I was
bit reluctant to do that because it is kind of like a big change. At least at the conceptual
level.

I like your idea and I'll come up with an implementation.

Eric, What do you think?

Re: JMX notifications for Endpoint state changes

2009-12-04T08:37:05Z

What about if we add some configuration section (as a child node in
the configuration) that can be used by any mediator, endpoint, proxy
service, etc.


    statistics policy 
    trace policy 
    monitoring policy 
    reporting policy 
   ��


This might be useful in long-term if someone is going to develop tools
for monitoring, deluging, reporting etc.  for synapse .

Thanks
Indika

On Fri, Dec 4, 2009 at 12:47 PM, Supun Kamburugamuva  wrote:
> I was not thinking about the implementation. But since this is introducing a
> new configuration, I was bit concerned.
>
> Supun..
>
> On Thu, Dec 3, 2009 at 10:07 PM, Ruwan Linton 
> wrote:
>>
>> Supun, It is not going to be a that big change, you just need to change
>> the implementation of isStatisticsEnabled and isTracingEnabled method to
>> look for the global flag if it is not set at the respective component.
>>
>> and you need to modify the synapse configuration builder to look at the
>> definitions tag and set the global values of these.
>>
>> Thanks,
>> Ruwan
>>
>> On Fri, Dec 4, 2009 at 9:42 AM, Supun Kamburugamuva 
>> wrote:
>>>
>>> Hi Ruwan,
>>>
>>> I think if we do this the correct way, the way you've suggested is the
>>> correct way. I was bit reluctant to do that because it is kind of like a big
>>> change. At least at the conceptual level.
>>>
>>> I like your idea and I'll come up with an implementation.
>>>
>>> Eric, What do you think?
>>>
>>> Thanks,
>>> Supun..
>>>
>>> On Thu, Dec 3, 2009 at 6:21 PM, Ruwan Linton 
>>> wrote:
>>>>
>>>> Supun,
>>>>
>>>> I see a real value of Eric's suggestion. We could introduce three
>>>> attributes called "statistics", "trace", and "notifications" in to the
>>>> definitions tag level, so those are the global values and you may override
>>>> the global value at any configurable node, like on a sequence or endpoint
or
>>>> even on a proxy.
>>>>
>>>> It is not clean if we bring this into the properties file, the XML model
>>>> that we use as the main configuration language allows you to nicely
>>>> implement that. So this effects statistics collection and tracing as well,
>>>> which can be turned on and off at a global level instead for the
>>>> notifications.
>>>>
>>>> Thanks,
>>>> Ruwan
>>>>
>>>> On Fri, Dec 4, 2009 at 4:54 AM, Supun Kamburugamuva 
>>>> wrote:
>>>>>
>>>>> +1 for a global property and we can include it to the
>>>>> synapse.properties file easily. But I'm also not sure about introducing
an
>>>>> attribute to the endpoint configuration.
>>>>>
>>>>> Thanks,
>>>>> Supun..
>>>>>
>>>>> On Fri, Dec 4, 2009 at 2:30 AM, Hubert, Eric
>>>>>  wrote:
>>>>>>
>>>>>> Agreed, coupling statistics and notification would not be a good
idea
>>>>>> as we are talking about two non-related things.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regarding useful configurations options I would also need to think
a
>>>>>> bit more about it�
>>>>>>
>>>>>> Introducing an optional attribute on the endpoint level to turn the
>>>>>> feature selectively on/off might (depending on the default) force
the user
>>>>>> having to set it on a large number of configuration items.
>>>>>>
>>>>>> Having a global switch (either on or off) plus the ability to override
>>>>>> the global option on the endpoint level may save configuration overhead
and
>>>>>> turn out to be more flexible, but could also make the configuration
harder
>>>>>> to read/understand.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> �� Eric
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> From: Supun Kamburugamuva [mailto:supun06@gmail.com]
>>>>>> Sent: Thursday, December 03, 2009 9:17 PM
>>>>>> To: dev@synapse.apache.org
>>>>>> Sub
>>>>>> ject: Re: JMX notifications for Endpoint state changes
>>>>>>
>>>>>>
>>>>>>
>>>>>> HI Eric,
>>>>>>
>>>>>> I can understand your suggestion about turning notifications on/off
>>>>>> selectively. One thing is if the statistics are enabled for a endpoint
then
>>>>>> enable the notifications. But statistics and notifications are two
different
>>>>>> things. So that may be not good. Any ideas from the community how
to do
>>>>>> this? May be we can introduce an attribute to the endpoint configuration?
>>>>>>
>>>>>> Thanks,
>>>>>> Supun..
>>>>>>
>>>>>> On Fri, Dec 4, 2009 at 1:33 AM, Hubert, Eric
>>>>>>  wrote:
>>>>>>
>>>>>> Hi Supun,
>>>>>>
>>>>>>
>>>>>>
>>>>>> You are welcome! Regarding my second point I think you are still
able
>>>>>> to deliver some details, if you really like. If I remember correctly
there
>>>>>> are actually three attributes type, message and userData, type and
message
>>>>>> being String and type being Object. So you can still use userData
to add
>>>>>> more detail which should not go into the message. The only thing
is that the
>>>>>> type of the user data should be some standard Object and not some
custom
>>>>>> type. It has been a while since I last looked into this, but you
may at
>>>>>> least want to check this�
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regarding my first point I assumed you would already have some user
>>>>>> requirements in mind as most of the time this is the starting point�
I�m not
>>>>>> quite sure if all users really do need this capability at all, although
I
>>>>>> really see its value. So at least I would expect a switch to turn
this
>>>>>> feature completely on and off (also as part of an initial implementation).
>>>>>> The decision about activating the feature by default, or having the
user to
>>>>>> activate it on demand � is of cause something different. What do
others
>>>>>> think about this?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Any �more advanced� configuration could also follow later on � I
>>>>>> agree. My idea was just a more practical one. Depending on how Synapse
is
>>>>>> operated it might be the case that some of the endpoints are somehow
>>>>>> �expected� to be suspended from time to time whereas others are expected
to
>>>>>> be 100% stable. Normally monitoring configuration is handled in one
central
>>>>>> place. The configuration knows about what events shall generate an
alert and
>>>>>> which ones have to be ignored to don�t flood the operational guys
with
>>>>>> �false positives�. This could be realized by proper filtering. On
the other
>>>>>> hand generating lots of events useless events will impose some overhead
>>>>>> which might be avoidable, if events are already fired selectively.
This of
>>>>>> cause only makes sense if the configuration is managed centrally
along with
>>>>>> the monitoring configurations. If this is done manually, most users
will
>>>>>> probably prefer to filter on the client (monitoring) side. Just my
personal
>>>>>> 0.2 cents from both a users and a developer�s perspective.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> �� Eric
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> From: Supun Kamburugamuva [mailto:supun06@gmail.com]
>>>>>> Sent: Thursday, December 03, 2009 7:08 PM
>>>>>> To: dev@synapse.apache.org
>>>>>> Subject: Re: JMX notifications for Endpoint state changes
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>> Thanks for the suggestions.
>>>>>>
>>>>>> I like your second idea. In Endpoint case I think we can avoid using
a
>>>>>> User defined notification. We simply send a notification of type
>>>>>> synapse.endpoint.state.change. We don't need to say what is the current
>>>>>> state using a user defined notification. User can query the MBean
and figure
>>>>>> out what is the current state.
>>>>>>
>>>>>> My personal opinion about your first idea is we should consider it
>>>>>> after the initial implementation depending on the user requirements.
This
>>>>>> gives us time to think about the correct way to have the configurations.
>>>>>> Still I don't have a clear understanding about how to configure this.
So my
>>>>>> initial plan was to enable it for all the endpoints as in the normal
JMX
>>>>>> case.
>>>>>>
>>>>>> If we can come up with a correct sensible way to introduce this to
the
>>>>>> configuration, I'm +1 for implementing it.
>>>>>>
>>>>>> Thanks,
>>>>>> Supun..
>>>>>>
>>>>>> On Thu, Dec 3, 2009 at 1:32 PM, Hubert, Eric
>>>>>>  wrote:
>>>>>>
>>>>>> Hi Supun,
>>>>>>
>>>>>>
>>>>>>
>>>>>> I�m +1 on the idea in general. There are at least two things which
>>>>>> come immediately into my mind we probably should consider when (before)
>>>>>> implementing this feature:
>>>>>>
>>>>>> 1) Configuration concept for event creation
>>>>>>
>>>>>> 2) Notification Object Type to use
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 1)
>>>>>>
>>>>>> Here we should consider how configurable we want to keep the event
>>>>>> creation. So I�m thinking on some decisions like this:
>>>>>>
>>>>>> -��������� only turn on/off event creation per type (e.g. type
>>>>>> endpoint marked as suspended)
>>>>>>
>>>>>> -��������� or configurable per data object itself (e.g. on endpoint
>>>>>> level) as part of the configuration language
>>>>>>
>>>>>>
>>>>>>
>>>>>> Here I also see a trade off. On the one hand the user will likely
only
>>>>>> be interested to keep his monitoring configuration in one central
place.
>>>>>> Definitely he may not be interested in all kind of events. Of course
there
>>>>>> is always the chance of using a NotificationFilter.
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2)
>>>>>>
>>>>>> Depending on what information we want to distribute as part of an
>>>>>> event object we should keep in mind that the client needs to have
the
>>>>>> Notification Object in his class path. So if using a non-standard
object
>>>>>> (e.g. a custom subclass of javax.management.Notification or non standard
>>>>>> objects stored inside the notification or one of its standard subclasses)
we
>>>>>> should always keep this in mind and think about its implications
and at
>>>>>> least consider this in the artefact structure (created deployment
units).
>>>>>> Personally when working with JMX I always try to avoid non-standard
objects
>>>>>> and restrict myself to standard types if possible.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> �� Eric
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> From: Supun Kamburugamuva [mailto:supun06@gmail.com]
>>>>>> Sent: Wednesday, December 02, 2009 10:47 PM
>>>>>> To: dev@synapse.apache.org
>>>>>> Subject: JMX notifications for Endpoint state changes
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> At the moment Synapse exposes endpoint statistics through JMX. In
case
>>>>>> of Endpoint state changes (i.e. marked as SUSPENDED) we can provide
JMX
>>>>>> notifications. This allows users to take actions promptly without
waiting
>>>>>> for pulling the endpoint status data. I would like to know the opinion
of
>>>>>> the community. The implementation is simple and if you agree on this
I can
>>>>>> provide a patch.
>>>>>>
>>>>>> Thanks,
>>>>>> Supun..
>>>>>>
>>>>>> --
>>>>>> Software Engineer, WSO2 Inc
>>>>>> http://wso2.org
>>>>>> supunk.blogspot.com
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Software Engineer, WSO2 Inc
>>>>>> http://wso2.org
>>>>>> supunk.blogspot.com
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Software Engineer, WSO2 Inc
>>>>>> http://wso2.org
>>>>>> supunk.blogspot.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Software Engineer, WSO2 Inc
>>>>> http://wso2.org
>>>>> supunk.blogspot.com
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ruwan Linton
>>>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>>>> WSO2 Inc.; http://wso2.org
>>>> email: ruwan@wso2.com; cell: +94 77 341 3097
>>>> blog: http://ruwansblog.blogspot.com
>>>
>>>
>>>
>>> --
>>> Software Engineer, WSO2 Inc
>>> http://wso2.org
>>> supunk.blogspot.com
>>>
>>>
>>
>>
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://ruwansblog.blogspot.com
>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

Re: JMX notifications for Endpoint state changes

2009-12-04T06:47:12Z

I was not thinking about the implementation. But since this is introducing a
new configuration, I was bit concerned.

Supun..

On Thu, Dec 3, 2009 at 10:07 PM, Ruwan Linton wrote:

> Supun, It is not going to be a that big change, you just need to change the
> implementation of isStatisticsEnabled and isTracingEnabled method to look
> for the global flag if it is not set at the respective component.
>
> and you need to modify the synapse configuration builder to look at the
> definitions tag and set the global values of these.
>
> Thanks,
> Ruwan
>
>
> On Fri, Dec 4, 2009 at 9:42 AM, Supun Kamburugamuva wrote:
>
>> Hi Ruwan,
>>
>> I think if we do this the correct way, the way you've suggested is the
>> correct way. I was bit reluctant to do that because it is kind of like a big
>> change. At least at the conceptual level.
>>
>> I like your idea and I'll come up with an implementation.
>>
>> Eric, What do you think?
>>
>> Thanks,
>> Supun..
>>
>>
>> On Thu, Dec 3, 2009 at 6:21 PM, Ruwan Linton wrote:
>>
>>> Supun,
>>>
>>> I see a real value of Eric's suggestion. We could introduce three
>>> attributes called "statistics", "trace", and "notifications" in to the
>>> definitions tag level, so those are the global values and you may override
>>> the global value at any configurable node, like on a sequence or endpoint or
>>> even on a proxy.
>>>
>>> It is not clean if we bring this into the properties file, the XML model
>>> that we use as the main configuration language allows you to nicely
>>> implement that. So this effects statistics collection and tracing as well,
>>> which can be turned on and off at a global level instead for the
>>> notifications.
>>>
>>> Thanks,
>>> Ruwan
>>>
>>>
>>> On Fri, Dec 4, 2009 at 4:54 AM, Supun Kamburugamuva wrote:
>>>
>>>> +1 for a global property and we can include it to the synapse.properties
>>>> file easily. But I'm also not sure about introducing an attribute to the
>>>> endpoint configuration.
>>>>
>>>> Thanks,
>>>> Supun..
>>>>
>>>>
>>>> On Fri, Dec 4, 2009 at 2:30 AM, Hubert, Eric >>> > wrote:
>>>>
>>>>>  Agreed, coupling statistics and notification would not be a good idea
>>>>> as we are talking about two non-related things.
>>>>>
>>>>>
>>>>>
>>>>> Regarding useful configurations options I would also need to think a
>>>>> bit more about it�
>>>>>
>>>>> Introducing an optional attribute on the endpoint level to turn the
>>>>> feature selectively on/off might (depending on the default) force the
user
>>>>> having to set it on a large number of configuration items.
>>>>>
>>>>> Having a global switch (either on or off) plus the ability to override
>>>>> the global option on the endpoint level may save configuration overhead
and
>>>>> turn out to be more flexible, but could also make the configuration harder
>>>>> to read/understand.
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>>    Eric
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   ------------------------------
>>>>>
>>>>> *From:* Supun Kamburugamuva [mailto:supun06@gmail.com]
>>>>> *Sent:* Thursday, December 03, 2009 9:17 PM
>>>>>
>>>>> *To:* dev@synapse.apache.org
>>>>> *Sub*
>>>>> *ject:* Re: JMX notifications for Endpoint state changes
>>>>>
>>>>>
>>>>>
>>>>> HI Eric,
>>>>>
>>>>> I can understand your suggestion about turning notifications on/off
>>>>> selectively. One thing is if the statistics are enabled for a endpoint
then
>>>>> enable the notifications. But statistics and notifications are two different
>>>>> things. So that may be not good. Any ideas from the community how to
do
>>>>> this? May be we can introduce an attribute to the endpoint configuration?
>>>>>
>>>>> Thanks,
>>>>> Supun..
>>>>>
>>>>> On Fri, Dec 4, 2009 at 1:33 AM, Hubert, Eric <
>>>>> Eric.Hubert@foxmobile.com> wrote:
>>>>>
>>>>> Hi Supun,
>>>>>
>>>>>
>>>>>
>>>>> You are welcome! Regarding my second point I think you are still able
>>>>> to deliver some details, if you really like. If I remember correctly
there
>>>>> are actually three attributes type, message and userData, type and message
>>>>> being String and type being Object. So you can still use userData to
add
>>>>> more detail which should not go into the message. The only thing is that
the
>>>>> type of the user data should be some standard Object and not some custom
>>>>> type. It has been a while since I last looked into this, but you may
at
>>>>> least want to check this�
>>>>>
>>>>>
>>>>>
>>>>> Regarding my first point I assumed you would already have some user
>>>>> requirements in mind as most of the time this is the starting point�
I�m not
>>>>> quite sure if all users really do need this capability at all, although
I
>>>>> really see its value. So at least I would expect a switch to turn this
>>>>> feature completely on and off (also as part of an initial implementation).
>>>>> The decision about activating the feature by default, or having the user
to
>>>>> activate it on demand � is of cause something different. What do others
>>>>> think about this?
>>>>>
>>>>>
>>>>>
>>>>> Any �more advanced� configuration could also follow later on � I agree.
>>>>> My idea was just a more practical one. Depending on how Synapse is operated
>>>>> it might be the case that some of the endpoints are somehow �expected�
to be
>>>>> suspended from time to time whereas others are expected to be 100% stable.
>>>>> Normally monitoring configuration is handled in one central place. The
>>>>> configuration knows about what events shall generate an alert and which
ones
>>>>> have to be ignored to don�t flood the operational guys with �false
>>>>> positives�. This could be realized by proper filtering. On the other
hand
>>>>> generating lots of events useless events will impose some overhead which
>>>>> might be avoidable, if events are already fired selectively. This of
cause
>>>>> only makes sense if the configuration is managed centrally along with
the
>>>>> monitoring configurations. If this is done manually, most users will
>>>>> probably prefer to filter on the client (monitoring) side. Just my personal
>>>>> 0.2 cents from both a users and a developer�s perspective.
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>>    Eric
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   ------------------------------
>>>>>
>>>>> *From:* Supun Kamburugamuva [mailto:supun06@gmail.com]
>>>>> *Sent:* Thursday, December 03, 2009 7:08 PM
>>>>> *To:* dev@synapse.apache.org
>>>>> *Subject:* Re: JMX notifications for Endpoint state changes
>>>>>
>>>>>
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>> Thanks for the suggestions.
>>>>>
>>>>> I like your second idea. In Endpoint case I think we can avoid using
a
>>>>> User defined notification. We simply send a notification of type
>>>>> synapse.endpoint.state.change. We don't need to say what is the current
>>>>> state using a user defined notification. User can query the MBean and
figure
>>>>> out what is the current state.
>>>>>
>>>>> My personal opinion about your first idea is we should consider it
>>>>> after the initial implementation depending on the user requirements.
This
>>>>> gives us time to think about the correct way to have the configurations.
>>>>> Still I don't have a clear understanding about how to configure this.
So my
>>>>> initial plan was to enable it for all the endpoints as in the normal
JMX
>>>>> case.
>>>>>
>>>>> If we can come up with a correct sensible way to introduce this to the
>>>>> configuration, I'm +1 for implementing it.
>>>>>
>>>>> Thanks,
>>>>> Supun..
>>>>>
>>>>> On Thu, Dec 3, 2009 at 1:32 PM, Hubert, Eric <
>>>>> Eric.Hubert@foxmobile.com> wrote:
>>>>>
>>>>> Hi Supun,
>>>>>
>>>>>
>>>>>
>>>>> I�m +1 on the idea in general. There are at least two things which come
>>>>> immediately into my mind we probably should consider when (before)
>>>>> implementing this feature:
>>>>>
>>>>> 1) Configuration concept for event creation
>>>>>
>>>>> 2) Notification Object Type to use
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 1)
>>>>>
>>>>> Here we should consider how configurable we want to keep the event
>>>>> creation. So I�m thinking on some decisions like this:
>>>>>
>>>>> -          only turn on/off event creation per type (e.g. type
>>>>> endpoint marked as suspended)
>>>>>
>>>>> -          or configurable per data object itself (e.g. on endpoint
>>>>> level) as part of the configuration language
>>>>>
>>>>>
>>>>>
>>>>> Here I also see a trade off. On the one hand the user will likely only
>>>>> be interested to keep his monitoring configuration in one central place.
>>>>> Definitely he may not be interested in all kind of events. Of course
there
>>>>> is always the chance of using a NotificationFilter.
>>>>>
>>>>>
>>>>>
>>>>> 2)
>>>>>
>>>>> Depending on what information we want to distribute as part of an event
>>>>> object we should keep in mind that the client needs to have the Notification
>>>>> Object in his class path. So if using a non-standard object (e.g. a custom
>>>>> subclass of javax.management.Notification or non standard objects stored
>>>>> inside the notification or one of its standard subclasses) we should
always
>>>>> keep this in mind and think about its implications and at least consider
>>>>> this in the artefact structure (created deployment units). Personally
when
>>>>> working with JMX I always try to avoid non-standard objects and restrict
>>>>> myself to standard types if possible.
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>>    Eric
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   ------------------------------
>>>>>
>>>>> *From:* Supun Kamburugamuva [mailto:supun06@gmail.com]
>>>>> *Sent:* Wednesday, December 02, 2009 10:47 PM
>>>>> *To:* dev@synapse.apache.org
>>>>> *Subject:* JMX notifications for Endpoint state changes
>>>>>
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> At the moment Synapse exposes endpoint statistics through JMX. In case
>>>>> of Endpoint state changes (i.e. marked as SUSPENDED) we can provide JMX
>>>>> notifications. This allows users to take actions promptly without waiting
>>>>> for pulling the endpoint status data. I would like to know the opinion
of
>>>>> the community. The implementation is simple and if you agree on this
I can
>>>>> provide a patch.
>>>>>
>>>>> Thanks,
>>>>> Supun..
>>>>>
>>>>> --
>>>>> Software Engineer, WSO2 Inc
>>>>> http://wso2.org
>>>>> supunk.blogspot.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Software Engineer, WSO2 Inc
>>>>> http://wso2.org
>>>>> supunk.blogspot.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Software Engineer, WSO2 Inc
>>>>> http://wso2.org
>>>>> supunk.blogspot.com
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Software Engineer, WSO2 Inc
>>>> http://wso2.org
>>>> supunk.blogspot.com
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Ruwan Linton
>>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>>> WSO2 Inc.; http://wso2.org
>>> email: ruwan@wso2.com; cell: +94 77 341 3097
>>> blog: http://ruwansblog.blogspot.com
>>>
>>
>>
>>
>> --
>> Software Engineer, WSO2 Inc
>> http://wso2.org
>> supunk.blogspot.com
>>
>>
>>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>



-- 
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com

Hudson build is still unstable: Synapse - 1.3 - SNAPSHOT #84

2009-12-04T06:17:22Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org

=?UTF-8?Q?Hudson_build_is_still_unstable:_Synapse_-_1.3_-_SNAPSH?= =?UTF-8?Q?OT_=C2=BB_Apache_Synapse_-_Non-blocking_HTTP/s_Transport_#84?=

2009-12-04T06:17:04Z

See 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org