Details
-
Type:
Bug
-
Status:
New
-
Priority:
Blocker
-
Resolution: Unresolved
-
Affects Version/s: 5.0.0-M1
-
Fix Version/s: 5.0.0-RC-1, 5.4.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
|||||||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | replicated-container.log [ 10783 ] |
| Summary | A timeout occurs on each call after to have attached a replicated container | Timeout occurs when attaching a replicated container conncurrently to service invocation |
| Priority | Blocker [ 1 ] | |
| Description |
I'm using Roboconf to deploy a proxy SOAP where:
* a first container runs the service consumer part, * a second container runs the service provider part, * external web-service is running into a sample webapp deployed on Tomcat * my webservice client is a load test run with SoapUI * my second container is configured to be replicated when more than 5 requests are processed concurrently by the BC SOAP Sometimes, when replicated containers are deployed, time out occurs during the startup of the replicated container, and this container is no more able to process request. I get always time-out. |
I'm using Roboconf to deploy a proxy SOAP where:
* a first container runs the service consumer part, * a second container runs the service provider part, * external web-service is running into a sample webapp deployed on Tomcat * my webservice client is a load test run with SoapUI * my second container is configured to be replicated when more than 5 requests are processed concurrently by the BC SOAP Sometimes, when replicated containers are deployed, time out occurs during the startup of the replicated container, and this container seems to be no more able to process request during a given duration. |
| Link |
This issue depends on |
| Link | This issue depends on PETALSBCSOAP-167 [ PETALSBCSOAP-167 ] |
| Link |
This issue depends on |
| Attachment | replicated-container.log [ 10783 ] |
| Attachment | replicated-container.log [ 10784 ] |
| Link |
This issue depends on |
| Link |
This issue depends on |
| Link |
This issue depends on |
| Comment |
[ What we would need is a log of the failure happening after the container has been replicated.
To understand where the problem is happening. ] |
| Comment | [ The problem is that we have no failure in log :/ except the ones I mentioned in previous comment. Perhaps is it linked ? ] |
| Comment |
[ On the web-service client side we have also few errors:
{code} org.apache.axis2.AxisFault: Error in the JBI exchange at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.processJBIResponse(PetalsReceiver.java:376) at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.sendJBIMessage(PetalsReceiver.java:512) at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.process(PetalsReceiver.java:242) at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.invokeBusinessLogic(PetalsReceiver.java:114) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146) at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:197) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:499) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.apache.commons.httpclient.HttpMethodBase.shouldCloseConnection(HttpMethodBase.java:990) at org.apache.commons.httpclient.HttpMethodBase.responseBodyConsumed(HttpMethodBase.java:2401) at org.apache.commons.httpclient.HttpMethodBase$1.responseConsumed(HttpMethodBase.java:1892) at org.apache.commons.httpclient.AutoCloseInputStream.notifyWatcher(AutoCloseInputStream.java:198) at org.apache.commons.httpclient.AutoCloseInputStream.close(AutoCloseInputStream.java:158) at org.apache.commons.httpclient.HttpMethodBase.releaseConnection(HttpMethodBase.java:1181) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.cleanup(CommonsHTTPTransportSender.java:89) at org.apache.axis2.client.ServiceClient.cleanupTransport(ServiceClient.java:862) at org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:220) at org.ow2.petals.binding.soap.listener.outgoing.JBIListener.onJBIMessage(JBIListener.java:59) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.invokeJBIListener(MessageExchangeProcessor.java:469) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:408) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:275) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:199) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ... 1 more {code} ] |
| Link | This issue depends on PETALSBCSOAP-167 [ PETALSBCSOAP-167 ] |
| Link | This issue depends on PETALSESBCONT-354 [ PETALSESBCONT-354 ] |
| Summary | Timeout occurs when attaching a replicated container conncurrently to service invocation | Problems running load test about Petals ESB in the cloud with Roboconf |
| Description |
I'm using Roboconf to deploy a proxy SOAP where:
* a first container runs the service consumer part, * a second container runs the service provider part, * external web-service is running into a sample webapp deployed on Tomcat * my webservice client is a load test run with SoapUI * my second container is configured to be replicated when more than 5 requests are processed concurrently by the BC SOAP Sometimes, when replicated containers are deployed, time out occurs during the startup of the replicated container, and this container seems to be no more able to process request during a given duration. |
I'm using Roboconf to deploy a proxy SOAP where:
* a first container runs the service consumer part, * a second container runs the service provider part, * external web-service is running into a sample webapp deployed on Tomcat * my webservice client is a load test run with SoapUI * my second container is configured to be replicated when more than 5 requests are processed concurrently by the BC SOAP Sometimes, when replicated containers are deployed, time out occurs during the startup of the replicated container, and this container seems to be no more able to process request during a given duration. I get few {{NullPointerException}} at BC Soap level. And the NIO transporter seems to establish too many connections. |
| Summary | Problems running load test about Petals ESB in the cloud with Roboconf | Problems running load tests about Petals ESB in the cloud with Roboconf |
| Fix Version/s | 5.0.0 [ 10574 ] |
| Link |
This issue depends on |
| Link |
This issue depends on |
| Description |
I'm using Roboconf to deploy a proxy SOAP where:
* a first container runs the service consumer part, * a second container runs the service provider part, * external web-service is running into a sample webapp deployed on Tomcat * my webservice client is a load test run with SoapUI * my second container is configured to be replicated when more than 5 requests are processed concurrently by the BC SOAP Sometimes, when replicated containers are deployed, time out occurs during the startup of the replicated container, and this container seems to be no more able to process request during a given duration. I get few {{NullPointerException}} at BC Soap level. And the NIO transporter seems to establish too many connections. |
I'm using Roboconf to deploy a proxy SOAP where:
* a first container runs the service consumer part, * a second container runs the service provider part, * external web-service is running into a sample webapp deployed on Tomcat * my webservice client is a load test run with SoapUI * my second container is configured to be replicated when more than 5 requests are processed concurrently by the BC SOAP Several problems occurs: * timeouts occur during the startup of the replicated container, and this container seems to be no more able to process request during a given duration, * I get few {{NullPointerException}} at BC Soap level, * and the NIO transporter seems to establish too many connections, * ... |
| Link |
This issue depends on |
| Link |
This issue depends on |
| Fix Version/s | 5.0.0 [ 10631 ] |
| Link | This issue depends on PETALSESBCONT-437 [ PETALSESBCONT-437 ] |
| Fix Version/s | 5.0.1 [ 10699 ] | |
| Fix Version/s | 5.0.0 [ 10631 ] |
| Fix Version/s | 5.2.0 [ 10837 ] | |
| Fix Version/s | 5.1.0 [ 10699 ] |
| Fix Version/s | 5.2.1 [ 10908 ] | |
| Fix Version/s | 5.2.0 [ 10837 ] |
| Fix Version/s | 5.4.0 [ 10950 ] | |
| Fix Version/s | 5.3.0 [ 10908 ] |
In log of the replicated container, we can see that a transporter NIO connection is established just after the SU deployment:
container-node_0 2015/10/28 11:12:18,881 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Deploy Service Unit 'su-SOAP-notifyVacationService-provide' container-node_0 2015/10/28 11:12:24,951 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : New Service Endpoint deployed : {http://petals.ow2.org/samples/se-bpmn/notifyVacationService}notifyV acationService ->edpt-c22ed980-7d64-11e5-bdb0-0242ac11001f (INTERNAL):roboconf-demo-1/container-node_0/petals-bc-soap container-node_0 2015/10/28 11:12:24,982 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Service Unit 'su-SOAP-notifyVacationService-provide' deployed container-node_0 2015/10/28 11:12:24,989 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42063,localport=7800] container-node_0 2015/10/28 11:12:25,000 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42064,localport=7800] container-node_0 2015/10/28 11:12:25,001 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42065,localport=7800] container-node_0 2015/10/28 11:12:25,005 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42067,localport=7800] container-node_0 2015/10/28 11:12:25,008 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42068,localport=7800] container-node_0 2015/10/28 11:12:25,062 GMT+0000 INFO [Petals.JBI-Management.DeploymentService] : Service Assembly 'sa-su-SOAP-notifyVacationService-provide' deployed container-node_0 2015/10/28 11:12:25,232 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Placeholders reloading. container-node_0 2015/10/28 11:12:25,233 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Placeholders reloaded. container-node_0 2015/10/28 11:12:25,255 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Init Service Unit 'su-SOAP-notifyVacationService-provide' container-node_0 2015/10/28 11:12:25,255 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Start Service Unit 'su-SOAP-notifyVacationService-provide'and it seems that no more message acceptor is available after few times:
These errors should be solved by
PETALSCDK-123.container-node_0 2015/10/28 11:12:18,881 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Deploy Service Unit 'su-SOAP-notifyVacationService-provide' container-node_0 2015/10/28 11:12:24,951 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : New Service Endpoint deployed : {http://petals.ow2.org/samples/se-bpmn/notifyVacationService}notifyV acationService ->edpt-c22ed980-7d64-11e5-bdb0-0242ac11001f (INTERNAL):roboconf-demo-1/container-node_0/petals-bc-soap container-node_0 2015/10/28 11:12:24,982 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Service Unit 'su-SOAP-notifyVacationService-provide' deployed container-node_0 2015/10/28 11:12:24,989 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42063,localport=7800] container-node_0 2015/10/28 11:12:25,000 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42064,localport=7800] container-node_0 2015/10/28 11:12:25,001 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42065,localport=7800] container-node_0 2015/10/28 11:12:25,005 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42067,localport=7800] container-node_0 2015/10/28 11:12:25,008 GMT+0000 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : A connection is accepted: Socket[addr=/172.17.0.15,port=42068,localport=7800] container-node_0 2015/10/28 11:12:25,062 GMT+0000 INFO [Petals.JBI-Management.DeploymentService] : Service Assembly 'sa-su-SOAP-notifyVacationService-provide' deployed container-node_0 2015/10/28 11:12:25,232 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Placeholders reloading. container-node_0 2015/10/28 11:12:25,233 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Placeholders reloaded. container-node_0 2015/10/28 11:12:25,255 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Init Service Unit 'su-SOAP-notifyVacationService-provide' container-node_0 2015/10/28 11:12:25,255 GMT+0000 INFO [Petals.Container.Components.petals-bc-soap] : Start Service Unit 'su-SOAP-notifyVacationService-provide'PETALSCDK-123.