10 Replies Latest reply on Jul 3, 2014 9:24 AM by Paweł Maroszczyk

    exception during calling jBPM6 REST URL

    Jaykumar Pandya Novice

      Hi All,

       

      We have integrated jBPM6 REST Api from our JAVA Application using maven. Now when we are hitting the REST URL which internally calls REST API we are getting following exception. Can anybody please guide how to remove this conflicts?

       

      16:53:52,285 INFO  [com.cred.utils.LogUtility] (http-localhost/127.0.0.1:8080-1) Knowledge base session closed

      16:53:52,293 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/CredValidationTestService].[RestEasy]] (http-localhost/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet RestEasy threw exception: org.jboss.resteasy.spi.UnhandledException: java.lang.LinkageError: loader constraint violation: when resolving method "org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.<init>(Lorg/apache/http/client/HttpClient;Lorg/apache/http/protocol/HttpContext;)V" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/kie/services/client/api/command/RemoteConfiguration, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/jboss/resteasy/client/core/executors/ApacheHttpClient4Executor, have different Class objects for the type or used in the signature

        at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:365) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:233) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:209) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:557) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]

      Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.<init>(Lorg/apache/http/client/HttpClient;Lorg/apache/http/protocol/HttpContext;)V" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/kie/services/client/api/command/RemoteConfiguration, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/jboss/resteasy/client/core/executors/ApacheHttpClient4Executor, have different Class objects for the type or used in the signature

        at org.kie.services.client.api.command.RemoteConfiguration.createAuthenticatingRequestFactory(RemoteConfiguration.java:151) [kie-services-client-6.0.1.Final.jar:6.0.1.Final]

        at org.kie.services.client.api.command.RemoteConfiguration.<init>(RemoteConfiguration.java:106) [kie-services-client-6.0.1.Final.jar:6.0.1.Final]

        at org.kie.services.client.api.command.RemoteConfiguration.<init>(RemoteConfiguration.java:100) [kie-services-client-6.0.1.Final.jar:6.0.1.Final]

        at org.kie.services.client.api.RemoteRestRuntimeFactory.<init>(RemoteRestRuntimeFactory.java:13) [kie-services-client-6.0.1.Final.jar:6.0.1.Final]

        at com.cred.monitor.restclients.RestClientjBPM.jbpmProcessEvidenceNotFoundWorkItems(RestClientjBPM.java:39) [CReDValidate-0.0.1-SNAPSHOT.jar:]

        at com.cred.monitor.handlers.CredWorkItemHandler.createWIforLEEvidenceNotFoundFields(CredWorkItemHandler.java:61) [CReDValidate-0.0.1-SNAPSHOT.jar:]

        at com.cred.monitor.services.CredWorkItemService.createWIForLEEvidenceNotFoundFields(CredWorkItemService.java:86) [CReDValidate-0.0.1-SNAPSHOT.jar:]

        at com.cred.validate.service.ValidateLegalEntityService.validateLegalEntity(ValidateLegalEntityService.java:126) [classes:]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]

        at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]

        at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]

        ... 19 more

        • 1. Re: exception during calling jBPM6 REST URL
          Mauricio Salatino Master

          This sounds as a dependency issue or a clash, or something that was compiled with one version and is running with another.

          Can you please clarify when is this exception happening? what code are you executing?

          • 2. Re: exception during calling jBPM6 REST URL
            Jaykumar Pandya Novice

            Hi,

            we are working on DROOLS Project which is deployed on EAP 6.2.0 server as a part of workflow integration we placed a new file where we defined the integration to jBPM6 using REST API. All existing functionality are working fine but when we are calling service which internally calls these API as that times it is giving this exception.

            I tried to exclude HTTP Client JAR  file through maven but still it is getting download so it seems that clash is happening for HTTPClient and HTTPComtext with existing JAR file of JBOSS Server but still i am new to JBOSS so this is my assumption. please let me know if you need more details.

            • 3. Re: exception during calling jBPM6 REST URL
              Jaykumar Pandya Novice

              based on the internet search, i have updated my pom.xml with following content and it is working fine.

               

                    <plugin>

                      <artifactId>maven-war-plugin</artifactId>

                      <version>2.3</version>

                      <configuration>       

                   <archive>

                          <manifestEntries>

                             <Dependencies>org.jboss.resteasy.resteasy-jaxrs,org.apache.httpcomponents</Dependencies>

                          </manifestEntries>

                       </archive>

              • 5. Re: exception during calling jBPM6 REST URL
                Guy Rouillier Newbie

                I just got the exact same error running the sample from the JBPM 6 docs section 17.1.1. The REST Remote Java RuntimeEngine Factory.  I also ran into the following problems:

                 

                (1) I'm working with the Eclipse plugin.  For some odd reason, the JBPM runtime has some of the JARs in the runtime lib directory, but not all of them.  For example,  in Maven dependencies, I see kie-ci, kie-api and kie-internal, but not kie-services-client-6.0.1.Final.jar.  httpclient and httpcore are not in the dependencies list either.  I finally just created a User Library containing all the JARs from runtime/lib.  That solved all my class issues.

                 

                (2) ProcessMain.java which is automatically generated when I create a JBPM project contains this final statement:

                 

                manager.disposeRuntimeEngine(engine);

                 

                But with RemoteRestRuntimeFactory, we never get a manager, but instead get an engine directly.  How then do we dispose of the engine?

                 

                Thanks.

                • 6. Re: exception during calling jBPM6 REST URL
                  Mateusz Adamiak Newbie

                  I also encountered the problem, but for me the solution with extending pom.xml does not work.

                   

                  The log is following:

                  20:47:54,923 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "virtual-lab-server.ear" (runtime-name: "virtual-lab-server.ear")

                  20:47:57,053 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb-api.jar in /C:/Users/VIRTUAL7/Downloads/jboss-eap-6.1/bin/content/virtual-lab-server.ear/lib/jaxb-impl-2.2.5.jar  does not point to a valid jar for a Class-Path reference.

                  20:47:57,053 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry activation.jar in /C:/Users/VIRTUAL7/Downloads/jboss-eap-6.1/bin/content/virtual-lab-server.ear/lib/jaxb-impl-2.2.5.jar  does not point to a valid jar for a Class-Path reference.

                  20:47:57,053 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/Users/VIRTUAL7/Downloads/jboss-eap-6.1/bin/content/virtual-lab-server.ear/lib/jaxb-impl-2.2.5.jar  does not point to a valid jar for a Class-Path reference.

                  20:47:57,054 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/Users/VIRTUAL7/Downloads/jboss-eap-6.1/bin/content/virtual-lab-server.ear/lib/jaxb-impl-2.2.5.jar  does not point to a valid jar for a Class-Path reference.

                  20:47:57,054 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "virtual-lab-booking-1.0-SNAPSHOT.jar")

                  20:47:57,054 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "virtual-lab-workflow-manager-brms-1.0-SNAPSHOT.jar")

                  20:47:57,062 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'

                  20:47:57,065 INFO  [org.jboss.as.pojo] (MSC service thread 1-1) JBAS017000: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).

                  20:47:57,222 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment virtual-lab-server.ear

                  20:47:57,234 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment virtual-lab-booking-1.0-SNAPSHOT.jar

                  20:47:57,249 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named EquipmentStorageBean in deployment unit subdeployment "virtual-lab-booking-1.0-SNAPSHOT.jar" of deployment "virtual-lab-server.ear" are as follows:

                   

                      java:global/virtual-lab-server/virtual-lab-booking-1.0-SNAPSHOT/EquipmentStorageBean!pl.wroc.pwr.vl.core.booking.EquipmentStorage

                      java:app/virtual-lab-booking-1.0-SNAPSHOT/EquipmentStorageBean!pl.wroc.pwr.vl.core.booking.EquipmentStorage

                      java:module/EquipmentStorageBean!pl.wroc.pwr.vl.core.booking.EquipmentStorage

                      java:global/virtual-lab-server/virtual-lab-booking-1.0-SNAPSHOT/EquipmentStorageBean

                      java:app/virtual-lab-booking-1.0-SNAPSHOT/EquipmentStorageBean

                      java:module/EquipmentStorageBean

                   

                  20:47:57,251 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment virtual-lab-workflow-manager-brms-1.0-SNAPSHOT.jar

                  20:47:57,259 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named BrmsWorkflowManagerBean in deployment unit subdeployment "virtual-lab-workflow-manager-brms-1.0-SNAPSHOT.jar" of deployment "virtual-lab-server.ear" are as follows:

                   

                      java:global/virtual-lab-server/virtual-lab-workflow-manager-brms-1.0-SNAPSHOT/BrmsWorkflowManagerBean!pl.worc.pwr.student.vl.workflow.brms.BrmsWorkflowManagerBean

                      java:app/virtual-lab-workflow-manager-brms-1.0-SNAPSHOT/BrmsWorkflowManagerBean!pl.worc.pwr.student.vl.workflow.brms.BrmsWorkflowManagerBean

                      java:module/BrmsWorkflowManagerBean!pl.worc.pwr.student.vl.workflow.brms.BrmsWorkflowManagerBean

                      java:global/virtual-lab-server/virtual-lab-workflow-manager-brms-1.0-SNAPSHOT/BrmsWorkflowManagerBean

                      java:app/virtual-lab-workflow-manager-brms-1.0-SNAPSHOT/BrmsWorkflowManagerBean

                      java:module/BrmsWorkflowManagerBean

                   

                  20:47:57,263 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: virtual-lab-server.ear

                  20:47:57,301 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment virtual-lab-server.ear

                  20:48:01,606 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 123) MSC000001: Failed to start service jboss.deployment.subunit."virtual-lab-server.ear"."virtual-lab-workflow-manager-brms-1.0-SNAPSHOT.jar".component.BrmsWorkflowManagerBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."virtual-lab-server.ear"."virtual-lab-workflow-manager-brms-1.0-SNAPSHOT.jar".component.BrmsWorkflowManagerBean.START: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance

                      at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_45]

                      at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_45]

                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]

                      at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]

                      at org.jboss.threads.JBossThread.run(JBossThread.java:122)

                  Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance

                      at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126)

                      at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141)

                      at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      ... 6 more

                  Caused by: javax.ejb.EJBException: JBAS014580: Unexpected Error

                      at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:162)

                      at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:250)

                      at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344)

                      at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66)

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      ... 10 more

                  Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.<init>(Lorg/apache/http/client/HttpClient;Lorg/apache/http/protocol/HttpContext;)V" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/kie/services/client/api/command/RemoteConfiguration, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/jboss/resteasy/client/core/executors/ApacheHttpClient4Executor, have different Class objects for the type xecutors.ApacheHttpClient4Executor.<init>(Lorg/apache/http/client/HttpClient;Lorg/apache/http/protocol/HttpContext;)V used in the signature

                      at org.kie.services.client.api.command.RemoteConfiguration.createAuthenticatingRequestFactory(RemoteConfiguration.java:151)

                      at org.kie.services.client.api.command.RemoteConfiguration.<init>(RemoteConfiguration.java:106)

                      at org.kie.services.client.api.command.RemoteConfiguration.<init>(RemoteConfiguration.java:100)

                      at org.kie.services.client.api.RemoteRestRuntimeFactory.<init>(RemoteRestRuntimeFactory.java:13)

                      at pl.worc.pwr.student.vl.workflow.brms.BrmsWorkflowManagerBean.init(BrmsWorkflowManagerBean.java:22)

                      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]

                      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]

                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]

                      at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]

                      at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73)

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

                      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]

                      at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248)

                      ... 19 more

                   

                  20:48:01,929 ERROR [org.jboss.as.server] (HttpManagementService-threads - 23) JBAS015870: Deploy of deployment "virtual-lab-server.ear" was rolled back with the following failure message:

                  {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"virtual-lab-server.ear\".\"virtual-lab-workflow-manager-brms-1.0-SNAPSHOT.jar\".component.BrmsWorkflowManagerBean.START" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"virtual-lab-server.ear\".\"virtual-lab-workflow-manager-brms-1.0-SNAPSHOT.jar\".component.BrmsWorkflowManagerBean.START: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance

                      Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance

                      Caused by: javax.ejb.EJBException: JBAS014580: Unexpected Error

                      Caused by: java.lang.LinkageError: loader constraint violation: when resolving method \"org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.<init>(Lorg/apache/http/client/HttpClient;Lorg/apache/http/protocol/HttpContext;)V\" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/kie/services/client/api/command/RemoteConfiguration, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/jboss/resteasy/client/core/executors/ApacheHttpClient4Executor, have different Class objects for the type xecutors.ApacheHttpClient4Executor.<init>(Lorg/apache/http/client/HttpClient;Lorg/apache/http/protocol/HttpContext;)V used in the signature"}}

                  20:48:01,952 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016009: Stopping weld service for deployment virtual-lab-server.ear

                  20:48:01,969 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment null (runtime-name: virtual-lab-booking-1.0-SNAPSHOT.jar) in 31ms

                  20:48:01,969 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: virtual-lab-workflow-manager-brms-1.0-SNAPSHOT.jar) in 31ms

                  20:48:02,043 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment virtual-lab-server.ear (runtime-name: virtual-lab-server.ear) in 92ms

                   

                  My pom.xml is following:

                  <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

                      <modelVersion>4.0.0</modelVersion>

                      <parent>

                          <groupId>pl.wroc.pwr.student.vl</groupId>

                          <artifactId>virtual-lab</artifactId>

                          <version>1.0-SNAPSHOT</version>

                      </parent>

                      <artifactId>virtual-lab-workflow-manager-brms</artifactId>

                      <packaging>ejb</packaging>

                      <properties>

                          <jbpm.version>6.0.1.Final</jbpm.version>

                      </properties>

                      <build>

                          <plugins>

                              <plugin>

                                  <artifactId>maven-jar-plugin</artifactId>

                                  <configuration>

                                      <archive>

                                          <manifestEntries>

                                              <Dependencies>org.apache.httpcomponents</Dependencies>

                                          </manifestEntries>

                                      </archive>

                                  </configuration>

                              </plugin>

                          </plugins>

                      </build>

                      <dependencies>

                          <!-- Java EE dependencies -->

                          <dependency>

                              <groupId>org.jboss.spec.javax.ejb</groupId>

                              <artifactId>jboss-ejb-api_3.1_spec</artifactId>

                              <scope>provided</scope>

                          </dependency>

                          <dependency>

                              <groupId>org.hibernate.javax.persistence</groupId>

                              <artifactId>hibernate-jpa-2.0-api</artifactId>

                              <scope>provided</scope>

                          </dependency>

                          <dependency>

                              <groupId>javax.transaction</groupId>

                              <artifactId>jta</artifactId>

                              <version>1.1</version>

                              <scope>provided</scope>

                          </dependency>

                          <dependency>

                              <groupId>javax.servlet</groupId>

                              <artifactId>servlet-api</artifactId>

                              <version>2.5</version>

                              <scope>provided</scope>

                          </dependency>

                          <dependency>

                              <groupId>javax.servlet.jsp</groupId>

                              <artifactId>jsp-api</artifactId>

                              <version>2.1</version>

                              <scope>provided</scope>

                          </dependency>

                          <!-- jBPM 6 dependencies -->

                          <dependency>

                              <groupId>org.kie.remote</groupId>

                              <artifactId>kie-services-client</artifactId>

                              <version>${jbpm.version}</version>

                          </dependency>

                      </dependencies>

                  </project>

                   

                  Have you any ideas how to solve the problem? The only solution I found was with this maven-jar-plugin. Maybe you could point out what possibly I did wrong?

                  • 7. Re: exception during calling jBPM6 REST URL
                    Jaykumar Pandya Novice

                    Hi,

                     

                    It seems that there is a conflicts of JAR file so  i will suggest to put following entry in your pom.xml.

                     

                    <archive>

                                <manifestEntries>

                                   <Dependencies>org.jboss.resteasy.resteasy-jaxrs,org.apache.httpcomponents</Dependencies>

                                </manifestEntries>

                             </archive>

                     

                    Regards,

                    Jay

                    • 8. Re: exception during calling jBPM6 REST URL
                      Mateusz Adamiak Newbie

                      Hi Jay,

                      Thanks for the reply. Unfortunately, your tip did not work, I have just applied it, but the problem remains the same. Thank you for the try though

                       

                      So the problem is unsolved yet. Some other solutions?

                      • 9. Re: exception during calling jBPM6 REST URL
                        Jaykumar Pandya Novice

                        Can you try once with following dependency

                         

                        <dependency>

                          <groupId>org.kie.remote</groupId>

                          <artifactId>kie-services-client</artifactId>

                          <exclusions>

                          <exclusion>

                          <artifactId>netty</artifactId>

                          <groupId>org.jboss.netty</groupId>

                          </exclusion>

                          </exclusions>

                          </dependency>

                         

                        If this solution does not work for you and if you get any other solution, please let me know as i am curious now to see it resolved

                        • 10. Re: exception during calling jBPM6 REST URL
                          Paweł Maroszczyk Newbie

                          Hi,

                          For AS7 I tried this (with success):

                           

                                  <exclusions>

                                          <exclusion>

                                              <artifactId>httpclient</artifactId>

                                              <groupId>org.apache.httpcomponents</groupId>

                                          </exclusion>

                                      </exclusions>

                           

                                     <plugin>

                                          <artifactId>maven-jar-plugin</artifactId>

                                          <configuration>

                                              <archive>

                                                  <manifestEntries>

                                                      <Dependencies>org.apache.httpcomponents</Dependencies>

                                                  </manifestEntries>

                                              </archive>

                                          </configuration>

                                      </plugin>