Maven, Wildfly Swarm, JRebel-Setup not booting up

ZeroTurnaround Homepage Forums JRebel Support Maven, Wildfly Swarm, JRebel-Setup not booting up

This topic contains 2 replies, has 2 voices, and was last updated by  romanbaertl 4 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #66969

    romanbaertl
    Member

    Hello,

    I have aproblem using JRebel with my Swarm project. It is built with maven.
    I think the most helpful is to post my log out:

    2018-01-24 10:29:58 JRebel: Directory ‘D:\workspace\CRS\CrsLrsWhKanban\target\classes’ will be monitored for changes.
    2018-01-24 10:29:58 JRebel: Directory ‘D:\workspace\CRS\CrsLrsWhKanban\src\main\webapp’ will be monitored for changes.
    2018-01-24 10:29:58 JRebel: Directory ‘D:\workspace\CRS\CrsLrsWhKanban\target\generated-resources’ will be monitored for changes.
    2018-01-24 10:29:58 JRebel: Directory ‘D:\workspace\CRS\CrsLrsWhKanban\target\m2e-wtp\web-resources’ will be monitored for changes.
    2018-01-24 10:29:58 JRebel: Directory ‘D:\workspace\CRS\CrsBase\target\classes’ will be monitored for changes.
    2018-01-24 10:29:59 JRebel:
    2018-01-24 10:29:59 JRebel: #############################################################
    2018-01-24 10:29:59 JRebel:
    2018-01-24 10:29:59 JRebel: JRebel Agent 7.1.5 (201801171200)
    2018-01-24 10:29:59 JRebel: (c) Copyright ZeroTurnaround AS, Estonia, Tartu.
    2018-01-24 10:29:59 JRebel:
    2018-01-24 10:29:59 JRebel: Over the last 30 days JRebel prevented
    2018-01-24 10:29:59 JRebel: at least 0 redeploys/restarts saving you about 0 hours.
    2018-01-24 10:29:59 JRebel:
    2018-01-24 10:29:59 JRebel: Over the last 360 days JRebel prevented
    2018-01-24 10:29:59 JRebel: at least 5125 redeploys/restarts saving you about 35.6 hours.
    2018-01-24 10:29:59 JRebel:
    2018-01-24 10:29:59 JRebel: Licensed to ***
    2018-01-24 10:29:59 JRebel:
    2018-01-24 10:29:59 JRebel: License type: dedicated
    2018-01-24 10:29:59 JRebel: Valid from: October 27, 2017
    2018-01-24 10:29:59 JRebel: Valid until: October 30, 2018
    2018-01-24 10:29:59 JRebel:
    2018-01-24 10:29:59 JRebel:
    2018-01-24 10:29:59 JRebel: #############################################################
    2018-01-24 10:29:59 JRebel:
    Wed Jan 24 10:30:01 CET 2018 INFO [org.wildfly.swarm.bootstrap] (main) Dependencies not bundled; resolving from M2REPO.
    log4j:WARN No appenders could be found for logger (org.jboss.logging).
    log4j:WARN Please initialize the log4j system properly.
    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
    2018-01-24 10:30:17,760 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Logging – STABLE org.wildfly.swarm:logging:2018.1.0
    2018-01-24 10:30:17,764 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: JCA – STABLE org.wildfly.swarm:jca:2018.1.0
    2018-01-24 10:30:17,765 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Bean Validation – STABLE org.wildfly.swarm:bean-validation:2018.1.0
    2018-01-24 10:30:17,768 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: CDI Configuration – STABLE org.wildfly.swarm:cdi-config:2018.1.0
    2018-01-24 10:30:17,768 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Datasources – STABLE org.wildfly.swarm:datasources:2018.1.0
    2018-01-24 10:30:17,769 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Transactions – STABLE org.wildfly.swarm:transactions:2018.1.0
    2018-01-24 10:30:17,769 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Elytron – STABLE org.wildfly.swarm:elytron:2018.1.0
    2018-01-24 10:30:17,769 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: JPA – STABLE org.wildfly.swarm:jpa:2018.1.0
    2018-01-24 10:30:17,769 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: CDI – STABLE org.wildfly.swarm:cdi:2018.1.0
    2018-01-24 10:30:17,770 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Undertow – STABLE org.wildfly.swarm:undertow:2018.1.0
    2018-01-24 10:30:17,771 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: JSF – STABLE org.wildfly.swarm:jsf:2018.1.0

    … Starts as usual…

    2018-01-24 10:30:59,896 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment “deployment.f2bb1289-c37a-4f40-95d3-2e28d15c735d.war” is using a private module (“org.jboss.ironjacamar.jdbcadapters”) which may be changed or removed in future versions without notice.
    2018-01-24 10:30:59,898 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment “deployment.f2bb1289-c37a-4f40-95d3-2e28d15c735d.war” is using a private module (“org.jboss.jts”) which may be changed or removed in future versions without notice.
    2018-01-24 10:30:59,899 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment “deployment.f2bb1289-c37a-4f40-95d3-2e28d15c735d.war” is using a private module (“org.jboss.ironjacamar.jdbcadapters”) which may be changed or removed in future versions without notice.
    2018-01-24 10:30:59,900 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment “deployment.f2bb1289-c37a-4f40-95d3-2e28d15c735d.war” is using a private module (“org.jboss.jts”) which may be changed or removed in future versions without notice.
    2018-01-24 10:30:59,900 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment “deployment.f2bb1289-c37a-4f40-95d3-2e28d15c735d.war” is using a private module (“org.jboss.ironjacamar.jdbcadapters”) which may be changed or removed in future versions without notice.
    2018-01-24 10:30:59,900 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment “deployment.f2bb1289-c37a-4f40-95d3-2e28d15c735d.war” is using a private module (“org.jboss.jts”) which may be changed or removed in future versions without notice.
    2018-01-24 10:31:00,425 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment f2bb1289-c37a-4f40-95d3-2e28d15c735d.war
    2018-01-24 10:31:00,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit.”f2bb1289-c37a-4f40-95d3-2e28d15c735d.war”.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.”f2bb1289-c37a-4f40-95d3-2e28d15c735d.war”.POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment “f2bb1289-c37a-4f40-95d3-2e28d15c735d.war”
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
    Caused by: java.lang.LinkageError: loader constraint violation: when resolving method “org.zeroturnaround.jrebel.weld2.jboss.cbp.JbossBeanDeploymentArchiveUtil.processClasses(Lorg/jboss/weld/bootstrap/JbossJrDirScanner;Lorg/jboss/weld/bootstrap/spi/BeansXml;Lorg/jboss/weld/resources/spi/ResourceLoader;Ljava/util/Set;Ljava/util/Set;Z)Lorg/jboss/weld/bootstrap/spi/BeansXml;” the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/jboss/as/weld/deployment/BeanDeploymentArchiveImpl, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for the method’s defining class, org/zeroturnaround/jrebel/weld2/jboss/cbp/JbossBeanDeploymentArchiveUtil, have different Class objects for the type org/jboss/weld/bootstrap/JbossJrDirScanner used in the signature
    at org.jboss.as.weld.deployment.BeanDeploymentArchiveImpl._scan(BeanDeploymentArchiveImpl.java)
    at org.jboss.as.weld.deployment.BeanDeploymentArchiveImpl.jrRescan(BeanDeploymentArchiveImpl.java)
    at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.handleResourceRoot(BeanArchiveProcessor.java:237)
    at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.access$100(BeanArchiveProcessor.java:206)
    at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:113)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
    … 5 more

    2018-01-24 10:31:00,511 ERROR [org.jboss.as.controller.management-operation] (main) WFLYCTL0013: Operation (“add”) failed – address: ((“deployment” => “f2bb1289-c37a-4f40-95d3-2e28d15c735d.war”)) – failure description: {“WFLYCTL0080: Failed services” => {“jboss.deployment.unit.\”f2bb1289-c37a-4f40-95d3-2e28d15c735d.war\”.POST_MODULE” => “WFLYSRV0153: Failed to process phase POST_MODULE of deployment \”f2bb1289-c37a-4f40-95d3-2e28d15c735d.war\”
    Caused by: java.lang.LinkageError: loader constraint violation: when resolving method \”org.zeroturnaround.jrebel.weld2.jboss.cbp.JbossBeanDeploymentArchiveUtil.processClasses(Lorg/jboss/weld/bootstrap/JbossJrDirScanner;Lorg/jboss/weld/bootstrap/spi/BeansXml;Lorg/jboss/weld/resources/spi/ResourceLoader;Ljava/util/Set;Ljava/util/Set;Z)Lorg/jboss/weld/bootstrap/spi/BeansXml;\” the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/jboss/as/weld/deployment/BeanDeploymentArchiveImpl, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for the method’s defining class, org/zeroturnaround/jrebel/weld2/jboss/cbp/JbossBeanDeploymentArchiveUtil, have different Class objects for the type org/jboss/weld/bootstrap/JbossJrDirScanner used in the signature”}}
    2018-01-24 10:31:00,517 ERROR [org.jboss.as.server] (main) WFLYSRV0021: Deploy of deployment “f2bb1289-c37a-4f40-95d3-2e28d15c735d.war” was rolled back with the following failure message:
    {“WFLYCTL0080: Failed services” => {“jboss.deployment.unit.\”f2bb1289-c37a-4f40-95d3-2e28d15c735d.war\”.POST_MODULE” => “WFLYSRV0153: Failed to process phase POST_MODULE of deployment \”f2bb1289-c37a-4f40-95d3-2e28d15c735d.war\”
    Caused by: java.lang.LinkageError: loader constraint violation: when resolving method \”org.zeroturnaround.jrebel.weld2.jboss.cbp.JbossBeanDeploymentArchiveUtil.processClasses(Lorg/jboss/weld/bootstrap/JbossJrDirScanner;Lorg/jboss/weld/bootstrap/spi/BeansXml;Lorg/jboss/weld/resources/spi/ResourceLoader;Ljava/util/Set;Ljava/util/Set;Z)Lorg/jboss/weld/bootstrap/spi/BeansXml;\” the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/jboss/as/weld/deployment/BeanDeploymentArchiveImpl, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for the method’s defining class, org/zeroturnaround/jrebel/weld2/jboss/cbp/JbossBeanDeploymentArchiveUtil, have different Class objects for the type org/jboss/weld/bootstrap/JbossJrDirScanner used in the signature”}}
    2018-01-24 10:31:01,900 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment f2bb1289-c37a-4f40-95d3-2e28d15c735d.war (runtime-name: f2bb1289-c37a-4f40-95d3-2e28d15c735d.war) in 1378ms

    Can you help me? What is that java.lang.LinkageError: loader constraint violation exception containing jrebel classes?

    #66971

    Hannes Metssalu
    Rebel Staff

    Hi Roman,

    I tried reproducing a similar issue on my end but didn’t succeed in doing so. Could you help me out by starting the application with the additional VM argument -Drebel.log=trace and reproduce this issue once more. This will generate a jrebel.log to {user.home}/.jrebel/ which should give us enough information about why you’re seeing this exception.

    Please send this log to support@zeroturnaround.com. All the additional details are also appreciated, for example pom.xml files for both of your modules would potentially help.

    As soon as we can reproduce it on our end, we can figure out a solution.

    Best,
    Hannes

    #66973

    romanbaertl
    Member

    I’ve sent you a mail. Thanks for your support! :-)

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.