Petals BC SOAP

MessagingException: Cannot create or get an Axis service client from the pool

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.4.0
  • Fix Version/s: 4.4.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The following error occurs sometimes running load tests through a Roboconf installation:

    container-node 2015/10/29 15:31:48,882 GMT+0000 WARNING [Petals.Container.Components.petals-bc-soap.edpt-9dbb3290-7e51-11e5-a618-0242ac110036] : Exception on the WS invocation
javax.jbi.messaging.MessagingException: Cannot create or get an Axis service client from the pool
        at org.ow2.petals.binding.soap.SoapComponentContext.borrowServiceClient(SoapComponentContext.java:418)
        at org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:146)
        at org.ow2.petals.binding.soap.listener.outgoing.JBIListener.onJBIMessage(JBIListener.java:59)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.invokeJBIListener(MessageExchangeProcessor.java:475)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:414)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:276)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:200)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalStateException: Pool not open
        at org.apache.commons.pool.BaseObjectPool.assertOpen(BaseObjectPool.java:140)
        at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1079)
        at org.ow2.petals.binding.soap.SoapComponentContext.borrowServiceClient(SoapComponentContext.java:382)
        ... 9 more
    Show
    The following error occurs sometimes running load tests through a Roboconf installation: 
    container-node 2015/10/29 15:31:48,882 GMT+0000 WARNING [Petals.Container.Components.petals-bc-soap.edpt-9dbb3290-7e51-11e5-a618-0242ac110036] : Exception on the WS invocation
javax.jbi.messaging.MessagingException: Cannot create or get an Axis service client from the pool
        at org.ow2.petals.binding.soap.SoapComponentContext.borrowServiceClient(SoapComponentContext.java:418)
        at org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:146)
        at org.ow2.petals.binding.soap.listener.outgoing.JBIListener.onJBIMessage(JBIListener.java:59)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.invokeJBIListener(MessageExchangeProcessor.java:475)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:414)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:276)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:200)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalStateException: Pool not open
        at org.apache.commons.pool.BaseObjectPool.assertOpen(BaseObjectPool.java:140)
        at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1079)
        at org.ow2.petals.binding.soap.SoapComponentContext.borrowServiceClient(SoapComponentContext.java:382)
        ... 9 more
  • Environment:
    -

Issue Links

Depends

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 29 Oct 2015 - 17:16:30 +0100
Field Original Value New Value
Fix Version/s 4.4.1 [ 10587 ]
Priority Blocker [ 1 ]
Christophe DENEUX made changes - Thu, 29 Oct 2015 - 17:16:47 +0100
Link This issue blocks PETALSDISTRIB-181 [ PETALSDISTRIB-181 ]
Hide
Permalink
Victor NOËL added a comment - Thu, 29 Oct 2015 - 17:48:27 +0100 - edited

This is caused by PETALSCDK-150.

Edit: it is not, see next comments.

Show
Victor NOËL added a comment - Thu, 29 Oct 2015 - 17:48:27 +0100 - edited This is caused by PETALSCDK-150. Edit: it is not, see next comments.
Victor NOËL made changes - Thu, 29 Oct 2015 - 17:48:33 +0100
Link This issue depends on PETALSCDK-150 [ PETALSCDK-150 ]
Hide
Permalink
Christophe DENEUX added a comment - Thu, 29 Oct 2015 - 17:56:00 +0100

I'm not sure that this problem is due to PETALSCDK-150 because the pool is closed when the component is stop or when reloading the component properties file. When the pool is created, it is directly opened.

Show
Christophe DENEUX added a comment - Thu, 29 Oct 2015 - 17:56:00 +0100 I'm not sure that this problem is due to PETALSCDK-150 because the pool is closed when the component is stop or when reloading the component properties file. When the pool is created, it is directly opened.
Hide
Permalink
Victor NOËL added a comment - Thu, 29 Oct 2015 - 18:05:25 +0100

You mean when the SU is stopped? Not the component.

Anyway, yes, it's very strange, maybe it's not related to PETALSCDK-150… I don't really see how this can happen ^^

Show
Victor NOËL added a comment - Thu, 29 Oct 2015 - 18:05:25 +0100 You mean when the SU is stopped? Not the component. Anyway, yes, it's very strange, maybe it's not related to PETALSCDK-150… I don't really see how this can happen ^^
Hide
Permalink
Christophe DENEUX added a comment - Fri, 30 Oct 2015 - 09:30:15 +0100

The object pools are closed only into SoapComponentContext.deleteServiceClientPools that is invoked by SoapSUManager.doStop and SoapSUManager.onPlaceHolderValuesReloaded.

IMO, the problem may be a concurrency problem between SoapSUManager.onPlaceHolderValuesReloaded and requests processing. This could be also the cause of PETALSBCSOAP-168.

Show
Christophe DENEUX added a comment - Fri, 30 Oct 2015 - 09:30:15 +0100 The object pools are closed only into SoapComponentContext.deleteServiceClientPools that is invoked by SoapSUManager.doStop and SoapSUManager.onPlaceHolderValuesReloaded. IMO, the problem may be a concurrency problem between SoapSUManager.onPlaceHolderValuesReloaded and requests processing. This could be also the cause of PETALSBCSOAP-168.
Christophe DENEUX made changes - Fri, 30 Oct 2015 - 09:31:03 +0100
Link This issue depends on PETALSBCSOAP-168 [ PETALSBCSOAP-168 ]
Christophe DENEUX made changes - Fri, 30 Oct 2015 - 09:31:15 +0100
Link This issue depends on PETALSCDK-150 [ PETALSCDK-150 ]
Hide
Permalink
Victor NOËL added a comment - Fri, 30 Oct 2015 - 13:34:30 +0100 - edited

Yep, that's what I mean: it's when the SU is stopped and not the component

That makes sense, but I don't see how this can happen, there is synchronization, that's really strange… For PETALSBCSOAP-168 it could make sense because there is no synchronization between borrowing and returning an object from the pool.

Is onPlaceHolderValuesReloaded is called when this bug happens?

Show
Victor NOËL added a comment - Fri, 30 Oct 2015 - 13:34:30 +0100 - edited Yep, that's what I mean: it's when the SU is stopped and not the component That makes sense, but I don't see how this can happen, there is synchronization, that's really strange… For PETALSBCSOAP-168 it could make sense because there is no synchronization between borrowing and returning an object from the pool. Is onPlaceHolderValuesReloaded is called when this bug happens?
Christophe DENEUX made changes - Fri, 30 Oct 2015 - 15:06:42 +0100
Comment [ As mentioned in my 4th comment of PETALSBCSOAP-168, this error seems to be concomitant to the place holders reloading. ]
Victor NOËL made changes - Fri, 30 Oct 2015 - 17:40:28 +0100
Link This issue depends on PETALSBCSOAP-173 [ PETALSBCSOAP-173 ]
Hide
Permalink
Victor NOËL added a comment - Fri, 30 Oct 2015 - 17:41:52 +0100

Caused by PETALSBCSOAP-173.

Show
Victor NOËL added a comment - Fri, 30 Oct 2015 - 17:41:52 +0100 Caused by PETALSBCSOAP-173.
Victor NOËL made changes - Fri, 30 Oct 2015 - 17:41:52 +0100
Status New [ 10000 ] Open [ 10002 ]
Priority Blocker [ 1 ] Major [ 3 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Fri, 30 Oct 2015 - 17:42:04 +0100
Link This issue depends on PETALSBCSOAP-168 [ PETALSBCSOAP-168 ]
Victor NOËL made changes - Fri, 30 Oct 2015 - 17:42:53 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Victor NOËL added a comment - Mon, 2 Nov 2015 - 14:22:01 +0100

A fix has been committed, could you test again and tell me if it's good?

Show
Victor NOËL added a comment - Mon, 2 Nov 2015 - 14:22:01 +0100 A fix has been committed, could you test again and tell me if it's good?
Hide
Permalink
Victor NOËL added a comment - Thu, 5 Nov 2015 - 09:01:49 +0100

It seems ok now.

Show
Victor NOËL added a comment - Thu, 5 Nov 2015 - 09:01:49 +0100 It seems ok now.
Victor NOËL made changes - Thu, 5 Nov 2015 - 09:01:49 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
1d 25m
1
Victor NOËL
Fri, 30 Oct 2015 - 17:41:52 +0100
Open Open In Progress In Progress
1m 1s
1
Victor NOËL
Fri, 30 Oct 2015 - 17:42:53 +0100
In Progress In Progress Resolved Resolved
5d 15h 18m
1
Victor NOËL
Thu, 5 Nov 2015 - 09:01:49 +0100



People

Dates

  • Created:
    Thu, 29 Oct 2015 - 17:16:21 +0100
    Updated:
    Thu, 5 Nov 2015 - 09:01:49 +0100
    Resolved:
    Thu, 5 Nov 2015 - 09:01:48 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.