i am installatng the JBoss server and starting it as part of jbpm installation.
when i start the server with ant start.demo syntax, i am getting the below error in log file,
13:13:55,082 INFO [org.jboss.jaxr] (MSC service thread 1-2) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
13:13:55,082 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
13:13:55,565 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 48) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:13:57,250 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
13:13:58,014 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory D:\New folder\jbpm-6.0.0.Final-installer-full\jbpm-installer\jboss-as-7.1.1.Final\standalone\deployments
13:13:58,014 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment dashboard-builder.war
13:13:58,046 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment jbpm-console.war
13:14:03,256 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
13:14:03,287 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jbpm-console.war"
13:14:03,287 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "dashboard-builder.war"
13:14:35,610 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.lang:main") which may be changed or removed in future versions without notice.
13:14:35,610 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.lang:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.io:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.io:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.codec:main") which may be changed or removed in future versions without notice.
13:14:35,642 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.codec:main") which may be changed or removed in future versions without notice.
13:14:35,642 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.jboss.ironjacamar.jdbcadapters:main") which may be changed or removed in future versions without notice.
13:14:35,642 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.jboss.ironjacamar.jdbcadapters:main") which may be changed or removed in future versions without notice.
13:14:35,907 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment dashboard-builder.war
13:14:38,372 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: dashboard-builder.war
13:14:38,434 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
13:15:49,679 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry avalon-framework-4.2.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,679 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-all-1.7.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-io-1.3.1.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-logging-1.0.4.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry serializer-2.7.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry servlet-2.2.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xalan-2.7.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xercesImpl-2.7.1.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis-1.3.04.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis-ext-1.3.04.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xmlgraphics-commons-1.3.1.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry fop-hyph.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jai_codec.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,726 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jai_core.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,726 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jai_imageio.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jimi-1.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xmlunit1.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jaxb-api.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-impl-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry activation.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-impl-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jsr173_1.0_api.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-impl-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jaxb1-impl.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-impl-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jaxb-api.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jaxb-impl.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jsr173_1.0_api.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry activation.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,788 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis-1.0.b2.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jbpmmigration-0.11.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,788 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry log4j-1.2.16.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jbpmmigration-0.11.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,804 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/serializer-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,804 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xercesImpl.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,804 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,866 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry serializer.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,991 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.springframework.context.ApplicationContext,org.springframework.beans.BeansException,org.springframework.beans.factory.xml.NamespaceHandlerResolver' for service type 'org.apache.cxf.bus.factory'
13:15:50,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
13:15:50,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
13:15:50,194 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for org.jbpm.domain
13:15:52,815 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.jbpm-console.war" is using a private module ("org.jboss.netty:main") which may be changed or removed in future versions without notice.
13:15:52,815 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.jbpm-console.war" is using a private module ("org.jboss.netty:main") which may be changed or removed in future versions without notice.
13:15:52,924 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jbpm-console.war
13:15:52,986 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named RetryTrackerSingleton in deployment unit deployment "jbpm-console.war" are as follows:
java:global/jbpm-console/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:app/jbpm-console/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:module/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:global/jbpm-console/RetryTrackerSingleton
java:app/jbpm-console/RetryTrackerSingleton
java:module/RetryTrackerSingleton
13:15:53,901 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:15:53,901 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:15:53,911 WARN [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010402: Unable to instantiate driver class "org.h2.Driver": org.jboss.msc.service.DuplicateServiceException: Service jboss.jdbc-driver.jbpm-console_warorg_h2_Driver_1_3 is already registered
13:15:53,911 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jbpm-console.war
13:15:53,931 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015954: Admin console is not enabled
13:15:53,931 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 140455ms - Started 323 of 754 services (376 services failed or missing dependencies, 53 services are passive or on-demand)
13:15:54,131 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jbpm-console.war" was rolled back with no failure message
13:15:54,141 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "dashboard-builder.war" was rolled back with failure message JBAS014750: Operation handler failed to complete
13:15:55,746 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment dashboard-builder.war in 1596ms
13:15:59,537 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment jbpm-console.war in 5393ms
13:15:59,537 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.JmsXA (missing) dependents: [service jboss.naming.context.java.module.jbpm-console.jbpm-console.env."org.kie.services.remote.jms.RequestMessageBean".connectionFactory, service jboss.naming.context.java.module.jbpm-console.jbpm-console.env."org.kie.services.remote.jms.RequestMessageBean".factory]
service jboss.ra.hornetq-ra (missing) dependents: [service jboss.deployment.unit."jbpm-console.war".component.JMSAuditProcessor.CREATE, service jboss.deployment.unit."jbpm-console.war".component.TaskServiceRequesMessageBean.CREATE, service jboss.deployment.unit."jbpm-console.war".component.KieSessionRequesMessageBean.CREATE]
13:15:59,537 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "JBAS014750: Operation handler failed to complete"}}
13:15:59,552 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
Can any one of you help to get rid of this issue?
In order to deploy JBPM in jboss server we need run in standalone-full mode.
In jboss->standalone-->configuration standalone.xml and standalone-full.xml will be there. Normally jboss will configured with standalone.xml so we need to change as standalone-full.xml and run.
This error will be solved.
Can you try the new versions? 6.1 and 6.2.CRx ?
That kind of issue seems to be caused because the application server wasn't started with the full profile, but ant start.demo should that for you, unless you modify it in some way or provided another server installation.
Related
We are planning to migrate the application from Jboss EAP 6.4 to WILDFLY 19 and facing the below error while deploying the war file in it.
Manifest-Version: 1.0
Built-By: jenkins
Created-By: Apache Maven 3.3.9
Build-Jdk: 1.8.0_151
Platform : Wildfly 19
JDK version using in the server
openjdk version "1.8.0_282"
OpenJDK Runtime Environment (build 1.8.0_282-b08)
OpenJDK 64-Bit Server VM (build 25.282-b08, mixed mode)
Will this cause the compatibility issue ? Same war is deployed in JBOSS EAP 6.4 with JDK 1.8.0_151 installed in server . Could some one help me to understand the issue .Thanks in advance
2021-03-03 19:00:58,126 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
2021-03-03 19:00:58,180 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "testit-base.war" (runtime-name: "testit-base.war")
2021-03-03 19:00:58,184 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "externalapi.war" (runtime-name: "externalapi.war")
2021-03-03 19:00:58,185 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "wmq.jmsra.rar" (runtime-name: "wmq.jmsra.rar")
2021-03-03 19:00:58,234 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/server/deployments
2021-03-03 19:00:59,051 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0493: EJB subsystem suspension complete
2021-03-03 19:00:59,253 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
2021-03-03 19:00:59,875 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.4.1.Final (Apache CXF 3.3.5)
2021-03-03 19:01:00,359 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2021-03-03 19:01:01,132 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry connector.jar in /content/wmq.jmsra.rar/com.ibm.mq.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,180 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jta.jar in /content/wmq.jmsra.rar/com.ibm.mq.jmqi.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,183 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry ldap.jar in /content/wmq.jmsra.rar/com.ibm.mqjms.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,184 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jndi.jar in /content/wmq.jmsra.rar/com.ibm.mqjms.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,184 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry fscontext.jar in /content/wmq.jmsra.rar/com.ibm.mqjms.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,184 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry providerutil.jar in /content/wmq.jmsra.rar/com.ibm.mqjms.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,203 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jms.jar in /content/wmq.jmsra.rar/com.ibm.msg.client.jms.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,206 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry rmm.jar in /content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry CL3Export.jar in /content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:01,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry CL3Nonexport.jar in /content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:04,020 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-3) IJ020001: Required license terms for file:/opt/wildfly/server/tmp/vfs/temp/temp9866aa9ab5895a5a/content-7c3c685b4673a9c7/contents/
2021-03-03 19:01:04,953 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment externalapi.war
2021-03-03 19:01:05,350 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.18.Final
2021-03-03 19:01:05,628 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 6.0.18.Final
2021-03-03 19:01:05,859 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/snakeyaml-1.13.jar in /content/testit-base.war/WEB-INF/lib/liquibase-core-3.5.3.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:05,862 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry xercesImpl.jar in /content/testit-base.war/WEB-INF/lib/xalan-2.7.0.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:05,862 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry xml-apis.jar in /content/testit-base.war/WEB-INF/lib/xalan-2.7.0.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:05,863 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry serializer.jar in /content/testit-base.war/WEB-INF/lib/xalan-2.7.0.jar does not point to a valid jar for a Class-Path reference.
2021-03-03 19:01:06,129 ERROR [stderr] (MSC service thread 1-3) Could not initialize log file, java.nio.file.AccessDeniedException: mqjms.log.0.lck
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) March 3, 2021 7:01:06 PM CET[MSC service thread 1-3] ResourceAdapterImpl
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) WMQ messaging : '7.5.0.6-p750-006-160226'.
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3)
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) EXPLANATION:
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) null
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3)
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) ACTION:
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) null
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) --------------------------------------------------------------------
2021-03-03 19:01:06,433 WARN [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-3) IJ020017: Invalid archive: file:/opt/wildfly/server/tmp/vfs/temp/temp9866aa9ab5895a5a/content-7c3c685b4673a9c7/contents/
2021-03-03 19:01:06,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."testit-base.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."testit-base.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "testit-base.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:248)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:156)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:83)
at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:50)
at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:76)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
... 8 more
2021-03-03 19:01:07,346 WARN [org.jboss.as.jaxrs] (MSC service thread 1-4) WFLYRS0018: Explicit usage of Jackson annotation in a JAX-RS deployment; the system will disable JSON-B processing for the current deployment. Consider setting the 'resteasy.preferJacksonOverJsonB' property to 'false' to restore JSON-B.
2021-03-03 19:01:07,455 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.1.3 (Final)
2021-03-03 19:01:07,762 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 67) WFLYCLINF0002: Started client-mappings cache from ejb container
2021-03-03 19:01:09,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002225: Deploying javax.ws.rs.core.Application: class ExternalApiApplication
2021-03-03 19:01:09,808 WARN [org.jboss.as.weld] (ServerService Thread Pool -- 67) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi, org.jboss.weld.api]
2021-03-03 19:01:09,966 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0021: Registered web context: '/externalapi' for server 'default-server'
2021-03-03 19:01:09,978 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "testit-base.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"testit-base.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"testit-base.war\"
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
2021-03-03 19:01:09,996 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "wmq.jmsra.rar" (runtime-name : "wmq.jmsra.rar")
2021-03-03 19:01:09,996 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "externalapi.war" (runtime-name : "externalapi.war")
2021-03-03 19:01:09,996 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "testit-base.war" (runtime-name : "testit-base.war")
2021-03-03 19:01:09,998 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."testit-base.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "testit-base.war"
2021-03-03 19:01:10,146 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
2021-03-03 19:01:10,149 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2021-03-03 19:01:10,149 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2021-03-03 19:01:10,149 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 19.0.0.Final (WildFly Core 11.0.0.Final) started (with errors) in 28607ms - Started 487 of 679 services (1 services failed or missing dependencies, 338 services are lazy, passive or on-demand)
Resource adapters settings are as below,
<subsystem xmlns="urn:jboss:domain:resource-adapters:5.0">
<resource-adapters>
<resource-adapter id="wmq.jmsra.rar">
<archive>
wmq.jmsra.rar
</archive>
<transaction-support>NoTransaction</transaction-support>
<connection-definitions>
<connection-definition class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl" jndi-name="java:jboss/WMQConnectionFactory" pool-name="WMQConnectionFactory">
<config-property name="channel">
CL.SC1023AC.TIMS
</config-property>
<config-property name="hostName">
sc1023ac.domain.com
</config-property>
<config-property name="transportType">
Client
</config-property>
<config-property name="queueManager">
SC1023AC
</config-property>
<config-property name="port">
49400
</config-property>
</connection-definition>
</connection-definitions>
<admin-objects>
<admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/queue/PurchaseOrderExportQueue" pool-name="purchaseOrderExport">
<config-property name="baseQueueName">
RQ.SCCO4234
</config-property>
</admin-object>>
</admin-objects>
</resource-adapter>
</resource-adapters>
</subsystem>
<subsystem xmlns="urn:jboss:domain:ejb3:6.0">
<session-bean>
<stateless>
<bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
</stateless>
<stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/>
<singleton default-access-timeout="5000"/>
</session-bean>
<mdb>
<resource-adapter-ref resource-adapter-name="${ejb.resource-adapter-name:wmq.jmsra.rar}"/>
<!--resource-adapter-ref resource-adapter-name="wmq.jmsra.rar"/-->
<bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
</mdb>
You WMQ resource adapter is not working properly as stated in:
2021-03-03 19:01:06,129 ERROR [stderr] (MSC service thread 1-3) Could not initialize log file, java.nio.file.AccessDeniedException: mqjms.log.0.lck
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) March 3, 2021 7:01:06 PM CET[MSC service thread 1-3] ResourceAdapterImpl
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) WMQ messaging : '7.5.0.6-p750-006-160226'.
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3)
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) EXPLANATION:
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) null
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3)
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) ACTION:
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) null
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) --------------------------------------------------------------------
2021-03-03 19:01:06,433 WARN [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-3) IJ020017: Invalid archive: file:/opt/wildfly/server/tmp/vfs/temp/temp9866aa9ab5895a5a/content-7c3c685b4673a9c7/contents/
This makes the ejbs fail
Looks like you are trying to deploy your own JMS service rather than use Artemis, but that something is still trying to use the default, which presumably isn't there as I assume you are using the standalone not standalone-full profile
i am not so familiar with ejb. I had hard time to set up realm authorization at wildfly, (13) all the time i had same error:
20:33:55,037 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RaportGeneratorEE-0.0.1-SNAPSHOT.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.exampleApplicationDomain"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"RaportGeneratorEE-0.0.1-SNAPSHOT.war\".component.ProgrammaticScheduler.CREATE is missing [jboss.security.security-domain.exampleApplicationDomain]"]
}
After this i have removed #Singleton Annotation from "ProgrammaticScheduler" and with out it my realm authentication works well. But than my scheduler doesnt work at all. When i remove lane with
exampleApplicationDomain
Scheduler works, realm doesnt. Where is the point? This two componenst dont have any common classes.. (well.. i dont know about any). Any one have some ideas? I have seen many familiar problems here but almost all of them were about missing or wrong line in standalone.xml.
Ps. I had another class with #stateless annotation and this class was in error too, but i didnt need it and jsut removed it. Full error log, standalone, jboss-web.xml below. Hope some will find solution
standalone.xml
<security-domains>
<security-domain name="ApplicationDomain" default-realm="ApplicationRealm" permission-mapper="default-permission-mapper">
<realm name="ApplicationRealm" role-decoder="groups-to-roles"/>
<realm name="local"/>
</security-domain>
<security-domain name="ManagementDomain" default-realm="ManagementRealm" permission-mapper="default-permission-mapper">
<realm name="ManagementRealm" role-decoder="groups-to-roles"/>
<realm name="local" role-mapper="super-user-mapper"/>
</security-domain>
<security-domain name="jdbcdomain" default-realm="jdbcRealm">
<realm name="jdbcRealm"/>
</security-domain>
<security-domain name="exampleDbSD" default-realm="exampleDbRealm" permission-mapper="default-permission-mapper">
<realm name="exampleDbRealm" role-decoder="groups-to-roles"/>
</security-domain>
</security-domains>
ProgrammaticScheduler
#Singleton
public class ProgrammaticScheduler {
#Schedule(hour="20", minute="33")
public void removeExpiredSearches() throws IOException{
System.out.println("Kick off!");
}
#Timeout()
public void onTimeout(Timer timer){
}
}
Error log
20:33:34,908 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
20:33:36,349 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
20:33:36,373 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
20:33:36,662 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) starting
20:33:40,940 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
20:33:41,000 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 17) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
20:33:41,004 INFO [org.wildfly.security] (ServerService Thread Pool -- 7) ELY00001: WildFly Elytron version 1.3.3.Final
20:33:41,220 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found RaportGeneratorEE-0.0.1-SNAPSHOT.war in deployment directory. To trigger deployment create a file called RaportGeneratorEE-0.0.1-SNAPSHOT.war.dodeploy
20:33:41,324 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
20:33:41,409 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.6.3.Final
20:33:41,421 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.6.3.Final
20:33:41,674 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem
20:33:41,683 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension
20:33:41,666 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
20:33:41,677 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 47) WFLYRS0016: RESTEasy version 3.5.1.Final
20:33:41,682 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=5.0.2.Final
20:33:41,705 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
20:33:41,718 INFO [org.jboss.as.ee] (ServerService Thread Pool -- 41) WFLYEE0119: The system property 'ee8.preview.mode' is NOT set to 'true'. For provided EE 8 APIs where the EE 8 version of the API differs from what is supported in EE 7, the EE 7 variant of the API will be used. Support for this setting will be removed once all EE 8 APIs are provided and certified.
20:33:41,737 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 45) WFLYCLINF0001: Activating Infinispan subsystem.
20:33:41,743 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem
20:33:41,818 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.0.9.Final starting
20:33:41,863 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
20:33:41,885 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.9.Final)
20:33:41,932 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
20:33:42,046 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
20:33:42,056 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
20:33:42,419 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path 'C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
20:33:42,886 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 46) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
20:33:42,904 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
20:33:42,913 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
20:33:43,056 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.7.Final
20:33:43,060 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
20:33:43,101 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
20:33:43,112 INFO [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
20:33:43,226 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
20:33:43,236 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final\standalone\deployments
20:33:43,265 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "mysql" (runtime-name: "mysql-connector-java-5.1.44-bin.jar")
20:33:43,271 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "RaportGeneratorEE-0.0.1-SNAPSHOT.war" (runtime-name: "RaportGeneratorEE-0.0.1-SNAPSHOT.war")
20:33:43,301 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
20:33:43,345 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
20:33:44,142 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
20:33:44,619 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
20:33:44,801 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.1.Final (Apache CXF 3.2.4.jbossorg-1)
20:33:45,530 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:33:45,536 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
20:33:45,705 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
20:33:45,706 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.jdbc.Driver_5_1
20:33:45,736 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/MysqlXADS]
20:33:45,745 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/examplePostgresDS]
20:33:47,033 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Gaina' 9.2.4.Final
20:33:48,039 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
20:33:52,002 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry serializer.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:53,000 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment RaportGeneratorEE-0.0.1-SNAPSHOT.war
20:33:53,923 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.3.6.Final
20:33:54,036 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'ProgrammaticScheduler' in deployment unit 'deployment "RaportGeneratorEE-0.0.1-SNAPSHOT.war"' are as follows:
java:global/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:app/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:module/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
ejb:RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:global/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler
java:app/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler
java:module/ProgrammaticScheduler
20:33:54,485 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:33:54,490 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
20:33:54,500 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
20:33:54,539 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 3.0.4 (Final)
20:33:54,721 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
20:33:54,722 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.jdbc.Driver_5_1
20:33:54,724 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.cj.jdbc.Driver_8_0
20:33:55,037 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RaportGeneratorEE-0.0.1-SNAPSHOT.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.exampleApplicationDomain"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"RaportGeneratorEE-0.0.1-SNAPSHOT.war\".component.ProgrammaticScheduler.CREATE is missing [jboss.security.security-domain.exampleApplicationDomain]"]
}
20:33:55,057 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "mysql" (runtime-name : "mysql-connector-java-5.1.44-bin.jar")
20:33:55,058 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "RaportGeneratorEE-0.0.1-SNAPSHOT.war" (runtime-name : "RaportGeneratorEE-0.0.1-SNAPSHOT.war")
20:33:55,064 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.security.security-domain.exampleApplicationDomain (missing) dependents: [service jboss.deployment.unit."RaportGeneratorEE-0.0.1-SNAPSHOT.war".component.ProgrammaticScheduler.CREATE]
WFLYCTL0448: 225 additional services are down due to their dependencies being missing or failed
There is need to add aplication-security-domain (using security-domain) in ejb3 services:
subsystem=ejb3/application-security-domain=exampleApplicationDomain:add(security-domain=exampleDbSD)
I use wildfly Master-domain. When I deploy some application, in domain.xml is created sha for example:
dd234b0920c094b633ebb38c9432dee9ea96ecfc
and is too created content in
/opt/wildfly/domain/data/content/dd/234b0920c094b633ebb38c9432dee9ea96ecfc/
But when I undeploy application via management console, content from
/opt/wildfly/domain/data/content/
will disappear. When I need restart wildfly I get message:
[Host Controller] 15:34:01,768 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "APPLICATION.ear")]) - failure description: "WFLYDC0058: No deployment content with hash dd234b0920c094b633ebb38c9432dee9ea96ecfc is available in the deployment content repository for deployment 'APPLICATION.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart."[Host Controller] 15:34:01,815 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.[Host Controller] 15:34:01,817 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99
In domain.xml file exist sha1.
server log:
2018-03-15 10:30:21,518 DEBUG [org.wildfly.extension.batch] (MSC service thread 1-1) Removing batch environment; ModuleClassLoader for Module "deployment.APPLICATION-1.9.3.ear:main" from Service Module Loader
2018-03-15 10:30:21,527 DEBUG [org.hibernate.validator.internal.engine.ConfigurationImpl] (MSC service thread 1-4) Setting custom ConstraintValidatorFactory of type org.hibernate.validator.internal.cdi.InjectingConstraintValidatorFactory
2018-03-15 10:30:21,528 DEBUG [org.hibernate.validator.internal.engine.ConfigurationImpl] (MSC service thread 1-4) Setting custom MessageInterpolator of type org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator
2018-03-15 10:30:21,528 DEBUG [org.hibernate.validator.internal.engine.ConfigurationImpl] (MSC service thread 1-4) Setting custom TraversableResolver of type org.hibernate.validator.internal.engine.resolver.DefaultTraversableResolver
2018-03-15 10:30:21,528 DEBUG [org.hibernate.validator.internal.engine.ConfigurationImpl] (MSC service thread 1-4) Setting custom ParameterNameProvider of type org.hibernate.validator.internal.engine.DefaultParameterNameProvider
2018-03-15 10:30:21,532 DEBUG [org.wildfly.extension.batch] (MSC service thread 1-3) Removing batch environment; ModuleClassLoader for Module "deployment.APPLICATION-1.9.3.ear.APPLICATION-web-1.9.3.war:main" from Service Module Loader
2018-03-15 10:30:21,588 DEBUG [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) unRegistering EJB client context for classloader ModuleClassLoader for Module "deployment.APPLICATION-1.9.3.ear.APPLICATION-ejb-1.9.3.jar:main" from Service Module Loader
2018-03-15 10:30:21,591 DEBUG [org.wildfly.extension.batch] (MSC service thread 1-2) Removing batch environment; ModuleClassLoader for Module "deployment.APPLICATION-1.9.3.ear.APPLICATION-ejb-1.9.3.jar:main" from Service Module Loader
2018-03-15 10:30:21,599 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /APPLICATION
2018-03-15 10:30:21,630 FINE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 74) ConfigureListener.contextDestroyed(APPLICATION-web)
2018-03-15 10:30:21,651 DEBUG [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment APPLICATION-1.9.3.ear
2018-03-15 10:30:21,667 DEBUG [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) unRegistering EJB client context for classloader ModuleClassLoader for Module "deployment.APPLICATION-1.9.3.ear.APPLICATION-web-1.9.3.war:main" from Service Module Loader
2018-03-15 10:30:21,742 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0208: Stopped subdeployment (runtime-name: APPLICATION-web-1.9.3.war) in 270ms
2018-03-15 10:30:21,743 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: APPLICATION-ejb-1.9.3.jar) in 271ms
2018-03-15 10:30:21,744 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (DefaultQuartzScheduler_Worker-10) loom-devsync1-datasource: getConnection(null, WrappedConnectionRequestInfo#228b594d[userName=user]) [0/30]
2018-03-15 10:30:21,746 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (DefaultQuartzScheduler_Worker-10) loom-devsync1-datasource: returnConnection(29207e12, false) [0/30]
2018-03-15 10:30:21,762 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment APPLICATION-1.9.3.ear (runtime-name: APPLICATION-1.9.3.ear) in 291ms
2018-03-15 10:30:21,847 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (DefaultQuartzScheduler_Worker-1) loom-devsync1-datasource: getConnection(null, WrappedConnectionRequestInfo#228b594d[userName=user]) [0/30]
2018-03-15 10:30:21,848 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (DefaultQuartzScheduler_Worker-2) loom-devsync1-datasource: getConnection(null, WrappedConnectionRequestInfo#228b594d[userName=user]) [0/30]
2018-03-15 10:30:21,851 DEBUG [org.jboss.jca.core.connectionmanager.poouseel.strategy.OnePool] (DefaultQuartzScheduler_Worker-1) loom-devsync1-datasource: returnConnection(29207e12, false) [0/30]
2018-03-15 10:30:21,852 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (DefaultQuartzScheduler_Worker-2) loom-devsync1-datasource: returnConnection(2ffe1f48, false) [0/30]
2018-03-15 10:30:22,116 INFO [org.jboss.as.server] (ServerService Thread Pool -- 64) WFLYSRV0009: Undeployed "APPLICATION-1.9.3.ear" (runtime-name: "APPLICATION-1.9.3.ear")
2018-03-15 10:30:22,123 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 64) WFLYDR0002: Content removed from location /opt/wildfly/data/content/dd/234b0920c094b633ebb38c9432dee9ea96ecfc/content
and environment: Debian wheezy, wildlfy 10.1.0 FINAL Core version: 2.8.27.Final
I need to solve problem with deleting content from /opt/wildfly/domain/data/content/.
The content should by stay in this folder. Application can by again deploy.
I recommend to use the latest version which is WildFly 12
I am trying to create an Java Enterprise Application using Eclipse IDE with JBoss 7.0 Server. I already had experience developing such applications but using NetBeans IDE. The main problem for me are the differences between these two IDEs. Currently, Eclipse's giving me headaches about adding JPA to EAR.
I already configured Enterprise Application (EAR) that has two containers:
-- EJB
-- WAR
Those two are configured to work together (Java Build Paths, Manifest and Deployment assembly are set for those two) so when I run EAR on the server it all works properly.
Problem:
The next thing I would like to configure is JPA. I want to add JPA container to my EAR and so I did. I've created JPA 2.1 (with EclipseLink 2.5.x and MySQL), added to EAR, I've add the changes to EJB project (right click on project->properties->deployment assembly->add jpa project).
After this point when I try to run EAR again I got HTTP Status 404 - The requested resource (/eLearningJJ-war/) is not available and my stacktrace looks like as down bellow.
Punch line
I wonder do I have to configure something extra in order to avoid this error after adding JPA to my EAR project.
If you need more details about the project please let me know,
Thank you.
Console
18:51:41,833 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA
18:51:42,224 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA
18:51:42,280 INFO [org.jboss.as] JBoss AS 7.0.1.Final "Zap" starting
18:51:43,186 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.
18:51:43,202 INFO [org.jboss.as] creating http management service using network interface (management) port (9990)
18:51:43,202 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.
18:51:43,217 INFO [org.jboss.as.logging] Removing bootstrap log handlers
18:51:43,233 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
18:51:43,280 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
18:51:43,452 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
18:51:43,468 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
18:51:43,468 INFO [org.jboss.as.naming] (MSC service thread 1-6) Starting Naming Service
18:51:43,530 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
18:51:43,546 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
18:51:43,561 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
18:51:43,593 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
18:51:43,999 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.8.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\MinGW\bin;C:\msys\1.0\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;.
18:51:43,999 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
18:51:44,452 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /127.0.0.1:9999
18:51:44,585 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-6) Starting remote JMX connector
18:51:44,675 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
18:51:44,847 INFO [org.jboss.as.connector] (MSC service thread 1-6) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
18:51:44,907 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) Bound data source [java:jboss/datasources/ExampleDS]
18:51:44,927 INFO [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory C:\Users\Milan\jboss-as-7.0.1.Final\standalone\deployments
18:51:44,975 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 3626ms - Started 93 of 148 services (55 services are passive or on-demand)
18:51:45,022 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found eLearningJJ-ear.ear in deployment directory. To trigger deployment create a file called eLearningJJ-ear.ear.dodeploy
18:51:45,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "eLearningJJ-ear.ear"
18:51:45,334 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "eLearningJJ-war.war"
18:51:45,334 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "eLearningJJ-ejb.jar"
18:51:45,897 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry in "/C:/Users/Milan/jboss-as-7.0.1.Final/standalone/deployments/eLearningJJ-ear.ear/lib/testjpa.jar" does not point to a valid jar for a Class-Path reference.
18:51:46,101 INFO [org.jboss.jpa] (MSC service thread 1-3) read persistence.xml for testjpa
18:51:46,458 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-4) Encountered invalid class name "com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor" for service type "com.sun.faces.spi.injectionprovider"
18:51:46,459 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-4) Encountered invalid class name "com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection" for service type "com.sun.faces.spi.injectionprovider"
18:51:46,526 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-ear.ear
18:51:46,528 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added (default provider) org.hibernate dependency to application deployment (since 1 PU(s) didn't specify jboss.as.jpa.providerModule)
18:51:46,528 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added org.hibernate dependency to application deployment
18:51:46,533 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-ejb.jar
18:51:46,533 INFO [org.jboss.as.jpa] (MSC service thread 1-7) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-war.war
18:51:46,704 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named UserTest in deployment unit subdeployment "eLearningJJ-ejb.jar" of deployment "eLearningJJ-ear.ear" are as follows:
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserTest!com.test.UserTest
java:app/eLearningJJ-ejb/UserTest!com.test.UserTest
java:module/UserTest!com.test.UserTest
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserTest!com.test.UserTestLocal
java:app/eLearningJJ-ejb/UserTest!com.test.UserTestLocal
java:module/UserTest!com.test.UserTestLocal
18:51:46,704 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named UserStateless in deployment unit subdeployment "eLearningJJ-ejb.jar" of deployment "eLearningJJ-ear.ear" are as follows:
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:app/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:module/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStateless
java:app/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStateless
java:module/UserStateless!com.elearningjj.beans.UserStateless
18:51:48,392 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
18:51:48,399 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
18:51:48,712 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.0.4 (FCS b09-jbossorg-4) for context '/eLearningJJ-war'
18:51:53,821 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /eLearningJJ-war
18:51:54,055 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "eLearningJJ-ear.ear" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"eLearningJJ-ear.ear#testjpa\" missing [ jboss.data-source.java:/ ]"]}
18:51:54,180 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment eLearningJJ-ejb.jar in 131ms
18:51:54,195 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment eLearningJJ-war.war in 140ms
18:51:54,195 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment eLearningJJ-ear.ear in 144ms
18:51:54,195 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"eLearningJJ-ear.ear#testjpa\" missing [ jboss.data-source.java:/ ]"]}}}
Solution
The main problem was improperly configured JPA's persistance.xml file. In my case, concrete problem was related to the jta-data-source which wasn't properly configured.
The solution for this is checking the JBoss Administration Console for more details about Datasource Configurations, Registered Datasources, etc. Regarding to this source of information, my persistance.xml file looks like down bellow:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
<persistence-unit name="eLearningJJ-jpa">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>
<properties>
<property name="hibernate.dialect"
value="org.hibernate.dialect.HSQLDialect"/>
<property name="hibernate.hbm2ddl.auto" value="create-drop"/>
</properties>
</persistence-unit>
</persistence>
I want to get rid of the WARN messages in the following JBoss console output.
08:46:53,653 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "IodLogin.war"
08:46:53,670 INFO [org.jboss.as.remoting] (MSC service thread 1-12) JBAS017100: Listening on 127.0.0.1:9999
08:46:53,670 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447
08:46:54,124 WARN [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
08:46:54,124 WARN [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'
08:46:54,596 INFO [org.jboss.weld.deployer] (MSC service thread 1-15) JBAS016002: Processing weld deployment IodLogin.war
08:46:54,815 INFO [org.jboss.weld.deployer] (MSC service thread 1-10) JBAS016005: Starting Services for CDI deployment: IodLogin.war
08:46:54,858 INFO [org.jboss.weld.Version] (MSC service thread 1-10) WELD-000900 1.1.10 (redhat)
08:46:54,901 INFO [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011907: Register module: Module "deployment.IodLogin.war:main" from Service Module Loader
08:46:54,904 INFO [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016008: Starting weld service for deployment IodLogin.war
08:46:55,269 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-13) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
08:46:55,327 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-13) Initializing Mojarra 2.1.13-jbossorg-1 20121010-0442 for context '/IodLogin'
08:46:55,933 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-13) Hibernate Validator 4.2.0.Final-redhat-2
08:46:56,281 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-13) Monitoring jndi:/default-host/IodLogin/WEB-INF/faces-config.xml for modifications
This is "just" a warning message, and I doubt it has any direct negative effect, but I try to avoid warning messages that might distract me and others from a warning that shouldn't be ignored -- the "Boy who cried 'Wolf'" parable.
I'm not using Tomcat or Jetty, but it looks like some configuration file or code is referring to classes specific to those environments. I've verified that none of the XML files refer to them directly.
I'm running JBoss EAP 6.0.1.GA. So far, this JSF 2.0 application is pretty simple -- just one page and a few classes. I'm using Eclipse, without Maven. Elsewhere on SO, I found a reference to org.jboss.shrinkwrap, but I don't see how that applies to my situation.
Update: My question is along the line of "how do I make this symptom of a non-problem go away so it doesn't mask a real problem". I'm not looking for a mistake in my code, just an improvement in the configuration.
Any suggestions about where I should look?