Petals BC REST

Few times, the error "No such servlet" is fired deploying a SU consume

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Blocker Blocker
  • Resolution: Unresolved
  • Affects Version/s: 1.3.0-BC
  • Fix Version/s: 1.4.0-BC, 2.5.0-BC
  • Component/s: Consumer mode
  • Security Level: Public
  • Description:
    Hide

    Few times, the error "No such servlet" is fired deploying a SU consume:

    petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] : Rest resource:
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :        - HTTP method: PATCH
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :        - HTTP path: /{reference}/planFinancement/recette/lignes/MGS_LIGNE_FICTIVE
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :        - No incoming payload generator
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :        - On JBI response:
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No conditional transformation for JBI 'OUT' message
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - default 'OUT' message transformation:
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                        - No extra transformation.
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                        - HTTP response:
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                                - HTTP code: 200
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                                - No specific header to set
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No conditional transformation for JBI fault
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No default transformation for JBI fault
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No conditional transformation for JBI error
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No default transformation for JBI error
petals-03 2019/09/30 15:40:28,173 GMT+0200 FINE [Petals.Container.Components.petals-bc-rest.jetty.org.eclipse.jetty.util.component.ContainerLifeCycle] : org.eclipse.jetty.servlet.ServletHandler@768a3f32 added {org.ow2.petals.binding.rest.exchange.incoming.RESTServlet-7c102606@ddc18248==org.ow2.petals.binding.rest.exchange.incoming.RESTServlet,jsp=null,order=-1,inst=true,UNMANAGED}
petals-03 2019/09/30 15:40:28,173 GMT+0200 FINE [Petals.Container.Components.petals-bc-rest.jetty.org.eclipse.jetty.util.component.ContainerLifeCycle] : org.eclipse.jetty.servlet.ServletHandler@768a3f32 added {[/services/ProgosCallback/*]=>org.ow2.petals.binding.rest.exchange.incoming.RESTServlet-7c102606,POJO}
petals-03 2019/09/30 15:40:28,173 GMT+0200 SEVERE [Petals.Container.Components.petals-bc-rest] : Failed to deploy Service Unit 'su-rest-notifier-subvention-consume-1.1.1', reverting and calling undeploy
java.lang.IllegalStateException: No such servlet: org.ow2.petals.binding.rest.exchange.incoming.RESTServlet-16e139e7
        at org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1405)
        at org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1567)
        at org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:907)
        at org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:462)
        at org.ow2.petals.binding.rest.exchange.incoming.RESTServer.addRESTServlet(RESTServer.java:228)
        at org.ow2.petals.binding.rest.exchange.incoming.RESTServer.addRESTService(RESTServer.java:123)
        at org.ow2.petals.binding.rest.RESTComponent.addRESTService(RESTComponent.java:102)
        at org.ow2.petals.binding.rest.RESTSUManager.doDeploy(RESTSUManager.java:76)
        at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:144)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:121)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75)
        at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:165)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:128)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:89)
        at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
        at org.ow2.petals.microkernel.jbi.management.recovery.task.RecoverSaTask.recoverSA(RecoverSaTask.java:178)
        at org.ow2.petals.microkernel.jbi.management.recovery.task.RecoverSaTask.recoverServiceAssembly(RecoverSaTask.java:127)
        at org.ow2.petals.microkernel.jbi.management.recovery.task.RecoverSaTask.call(RecoverSaTask.java:72)
        at org.ow2.petals.microkernel.jbi.management.recovery.task.RecoverSaTask.call(RecoverSaTask.java:49)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
    Show
    Few times, the error "No such servlet" is fired deploying a SU consume: 
    petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] : Rest resource:
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :        - HTTP method: PATCH
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :        - HTTP path: /{reference}/planFinancement/recette/lignes/MGS_LIGNE_FICTIVE
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :        - No incoming payload generator
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :        - On JBI response:
petals-03 2019/09/30 15:40:28,171 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No conditional transformation for JBI 'OUT' message
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - default 'OUT' message transformation:
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                        - No extra transformation.
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                        - HTTP response:
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                                - HTTP code: 200
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                                - No specific header to set
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No conditional transformation for JBI fault
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No default transformation for JBI fault
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No conditional transformation for JBI error
petals-03 2019/09/30 15:40:28,172 GMT+0200 CONFIG [Petals.Container.Components.petals-bc-rest] :                - No default transformation for JBI error
petals-03 2019/09/30 15:40:28,173 GMT+0200 FINE [Petals.Container.Components.petals-bc-rest.jetty.org.eclipse.jetty.util.component.ContainerLifeCycle] : org.eclipse.jetty.servlet.ServletHandler@768a3f32 added {org.ow2.petals.binding.rest.exchange.incoming.RESTServlet-7c102606@ddc18248==org.ow2.petals.binding.rest.exchange.incoming.RESTServlet,jsp=null,order=-1,inst=true,UNMANAGED}
petals-03 2019/09/30 15:40:28,173 GMT+0200 FINE [Petals.Container.Components.petals-bc-rest.jetty.org.eclipse.jetty.util.component.ContainerLifeCycle] : org.eclipse.jetty.servlet.ServletHandler@768a3f32 added {[/services/ProgosCallback/*]=>org.ow2.petals.binding.rest.exchange.incoming.RESTServlet-7c102606,POJO}
petals-03 2019/09/30 15:40:28,173 GMT+0200 SEVERE [Petals.Container.Components.petals-bc-rest] : Failed to deploy Service Unit 'su-rest-notifier-subvention-consume-1.1.1', reverting and calling undeploy
java.lang.IllegalStateException: No such servlet: org.ow2.petals.binding.rest.exchange.incoming.RESTServlet-16e139e7
        at org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1405)
        at org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1567)
        at org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:907)
        at org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:462)
        at org.ow2.petals.binding.rest.exchange.incoming.RESTServer.addRESTServlet(RESTServer.java:228)
        at org.ow2.petals.binding.rest.exchange.incoming.RESTServer.addRESTService(RESTServer.java:123)
        at org.ow2.petals.binding.rest.RESTComponent.addRESTService(RESTComponent.java:102)
        at org.ow2.petals.binding.rest.RESTSUManager.doDeploy(RESTSUManager.java:76)
        at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:144)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:121)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75)
        at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:165)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:128)
        at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:89)
        at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
        at org.ow2.petals.microkernel.jbi.management.recovery.task.RecoverSaTask.recoverSA(RecoverSaTask.java:178)
        at org.ow2.petals.microkernel.jbi.management.recovery.task.RecoverSaTask.recoverServiceAssembly(RecoverSaTask.java:127)
        at org.ow2.petals.microkernel.jbi.management.recovery.task.RecoverSaTask.call(RecoverSaTask.java:72)
        at org.ow2.petals.microkernel.jbi.management.recovery.task.RecoverSaTask.call(RecoverSaTask.java:49)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
  • Environment:
    -

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Christophe DENEUX added a comment - Tue, 11 Apr 2023 - 11:36:42 +0200

Postponed to version 2.5.0 on main dev line

Show
Christophe DENEUX added a comment - Tue, 11 Apr 2023 - 11:36:42 +0200 Postponed to version 2.5.0 on main dev line
Hide
Permalink
Christophe DENEUX added a comment - Fri, 4 Oct 2019 - 14:55:55 +0200 - edited

Log traces merged in trunk

Show
Christophe DENEUX added a comment - Fri, 4 Oct 2019 - 14:55:55 +0200 - edited Log traces merged in trunk
Hide
Permalink
Christophe DENEUX added a comment - Fri, 4 Oct 2019 - 14:39:06 +0200 - edited

Log traces added in branch petals-bc-rest-1.3.x for version 1.4.0

Show
Christophe DENEUX added a comment - Fri, 4 Oct 2019 - 14:39:06 +0200 - edited Log traces added in branch petals-bc-rest-1.3.x for version 1.4.0
Hide
Permalink
Christophe DENEUX added a comment - Fri, 4 Oct 2019 - 11:27:59 +0200

The issue is due to a RuntimeException that is not catched explicitely registering the servlet.
Few log traces have been added to get more information on the servlet that is not found.

Show
Christophe DENEUX added a comment - Fri, 4 Oct 2019 - 11:27:59 +0200 The issue is due to a RuntimeException that is not catched explicitely registering the servlet. Few log traces have been added to get more information on the servlet that is not found.
Hide
Permalink
Christophe DENEUX added a comment - Fri, 4 Oct 2019 - 11:25:16 +0200

This issue is random:

  • once it occurs, the problem occurs on each Petals restart,
  • the problem can disappear redeploying Petal artifacts,
  • if running on a VM, taking a snapshot of the VM, the problem disappears restarting the image on another VM.
Show
Christophe DENEUX added a comment - Fri, 4 Oct 2019 - 11:25:16 +0200 This issue is random:
  • once it occurs, the problem occurs on each Petals restart,
  • the problem can disappear redeploying Petal artifacts,
  • if running on a VM, taking a snapshot of the VM, the problem disappears restarting the image on another VM.

People

Dates

  • Created:
    Fri, 4 Oct 2019 - 11:21:44 +0200
    Updated:
    Tue, 11 Apr 2023 - 11:36:42 +0200
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.