Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 18:02:15,666 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
- 18:02:16,020 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
- 18:02:16,029 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
- 18:02:16,124 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) starting
- 18:02:16,791 INFO [org.wildfly.security] (ServerService Thread Pool -- 29) ELY00001: WildFly Elytron version 1.10.4.Final
- 18:02:17,359 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.
- 18:02:17,379 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.
- 18:02:17,434 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
- 18:02:17,450 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.7.3.Final
- 18:02:17,457 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.7.3.Final
- 18:02:17,507 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0001: Activating Infinispan subsystem.
- 18:02:17,513 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 66) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
- 18:02:17,517 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 78) 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.
- 18:02:17,532 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 54) WFLYIIOP0001: Activating IIOP Subsystem
- 18:02:17,546 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 57) WFLYRS0016: RESTEasy version 3.9.1.Final
- 18:02:17,547 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 69) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
- 18:02:17,554 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 70) WFLYNAM0001: Activating Naming Subsystem
- 18:02:17,558 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 62) WFLYJSF0007: Activated the following JSF Implementations: [main]
- 18:02:17,559 INFO [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.17.Final)
- 18:02:17,573 INFO [org.jboss.as.security] (ServerService Thread Pool -- 76) WFLYSEC0002: Activating Security Subsystem
- 18:02:17,573 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 68) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
- 18:02:17,575 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 80) WFLYWS0002: Activating WebServices Extension
- 18:02:17,579 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 2.0.27.Final starting
- 18:02:17,588 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 67) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
- 18:02:17,597 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.3.Final
- 18:02:17,642 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 46) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
- 18:02:17,679 INFO [org.jboss.as.naming] (MSC service thread 1-7) WFLYNAM0003: Starting Naming Service
- 18:02:17,680 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
- 18:02:17,706 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
- 18:02:17,765 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 79) WFLYUT0014: Creating file handler for path 'C:\enterprise\wildfly-18.0.1.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
- 18:02:18,238 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 56) WFLYIO001: Worker 'default' has auto-configured to 24 core threads with 192 task threads based on your 12 available processors
- 18:02:18,244 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 48 (per class), which is derived from the number of CPUs on this host.
- 18:02:18,244 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 192 (per class), which is derived from thread worker pool sizing.
- 18:02:18,275 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 5.0.15.Final
- 18:02:18,282 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
- 18:02:18,284 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
- 18:02:18,321 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
- 18:02:18,338 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0493: EJB subsystem suspension complete
- 18:02:18,344 INFO [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
- 18:02:18,359 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.
- 18:02:18,362 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\enterprise\wildfly-18.0.1.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
- 18:02:18,366 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory C:\enterprise\wildfly-18.0.1.Final\standalone\deployments
- 18:02:18,405 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
- 18:02:18,433 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\enterprise\wildfly-18.0.1.Final\standalone\data\activemq\journal,bindingsDirectory=C:\enterprise\wildfly-18.0.1.Final\standalone\data\activemq\bindings,largeMessagesDirectory=C:\enterprise\wildfly-18.0.1.Final\standalone\data\activemq\largemessages,pagingDirectory=C:\enterprise\wildfly-18.0.1.Final\standalone\data\activemq\paging)
- 18:02:18,464 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221013: Using NIO Journal
- 18:02:18,532 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
- 18:02:18,533 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
- 18:02:18,533 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
- 18:02:18,534 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
- 18:02:18,550 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-2) WFLYIIOP0009: CORBA ORB Service started
- 18:02:18,597 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221034: Waiting indefinitely to obtain live lock
- 18:02:18,597 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221035: Live Server Obtained live lock
- 18:02:18,718 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
- 18:02:18,776 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.3)
- 18:02:19,039 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
- 18:02:19,039 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
- 18:02:19,039 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
- 18:02:19,039 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
- 18:02:19,195 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221007: Server is now live
- 18:02:19,195 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.10.1 [default, nodeID=52970618-4748-11ed-8936-8032532a2a56]
- 18:02:19,212 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 82) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
- 18:02:19,230 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
- 18:02:19,268 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA
- 18:02:19,309 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) AMQ151007: Resource adaptor started
- 18:02:19,310 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra
- 18:02:19,311 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
- 18:02:19,311 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
- 18:02:19,438 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
- 18:02:19,439 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
- 18:02:19,439 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
- 18:02:19,440 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) started in 4148ms - Started 367 of 630 services (397 services are lazy, passive or on-demand)
- 18:17:41,074 INFO [org.wildfly.naming] (default task-1) WildFly Naming version 1.0.11.Final
- 18:45:00,680 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found helloworld-mdb.war in deployment directory. To trigger deployment create a file called helloworld-mdb.war.dodeploy
- 18:45:00,726 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "helloworld-mdb.war" (runtime-name: "helloworld-mdb.war")
- 18:45:04,881 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment helloworld-mdb.war
- 18:45:06,620 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 6.0.18.Final
- 18:45:07,257 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/queue/HELLOWORLDMDBQueue
- 18:45:07,258 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/topic/HELLOWORLDMDBTopic
- 18:45:07,303 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 3.1.2 (Final)
- 18:45:07,304 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.16.Final
- 18:45:07,442 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0042: Started message driven bean 'HelloWorldQueueMDB' with 'activemq-ra.rar' resource adapter
- 18:45:07,443 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0042: Started message driven bean 'HelloWorldQTopicMDB' with 'activemq-ra.rar' resource adapter
- 18:45:07,773 INFO [io.smallrye.metrics] (MSC service thread 1-4) MicroProfile: Metrics activated
- 18:45:07,824 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 92) WFLYCLINF0002: Started client-mappings cache from ejb container
- 18:45:08,570 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 92) WFLYUT0021: Registered web context: '/helloworld-mdb' for server 'default-server'
- 18:45:08,647 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "helloworld-mdb.war" (runtime-name : "helloworld-mdb.war")
- 18:45:30,995 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-5 (ActiveMQ-client-global-threads)) Received Message from queue: This is message 3
- 18:45:30,995 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-7 (ActiveMQ-client-global-threads)) Received Message from queue: This is message 5
- 18:45:30,995 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-4 (ActiveMQ-client-global-threads)) Received Message from queue: This is message 2
- 18:45:30,995 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-3 (ActiveMQ-client-global-threads)) Received Message from queue: This is message 1
- 18:45:30,995 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-6 (ActiveMQ-client-global-threads)) Received Message from queue: This is message 4
- 18:45:59,898 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldTopicMDB] (Thread-3 (ActiveMQ-client-global-threads)) Received Message from topic: This is message 2
- 18:45:59,898 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldTopicMDB] (Thread-4 (ActiveMQ-client-global-threads)) Received Message from topic: This is message 1
- 18:45:59,901 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldTopicMDB] (Thread-5 (ActiveMQ-client-global-threads)) Received Message from topic: This is message 3
- 18:45:59,904 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldTopicMDB] (Thread-7 (ActiveMQ-client-global-threads)) Received Message from topic: This is message 4
- 18:45:59,907 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldTopicMDB] (Thread-6 (ActiveMQ-client-global-threads)) Received Message from topic: This is message 5
- 18:53:34,760 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 92) WFLYUT0022: Unregistered web context: '/helloworld-mdb' from server 'default-server'
- 18:53:34,832 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/queue/HELLOWORLDMDBQueue
- 18:53:34,832 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/topic/HELLOWORLDMDBTopic
- 18:53:34,873 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment helloworld-mdb.war (runtime-name: helloworld-mdb.war) in 125ms
- 18:53:34,913 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "helloworld-mdb.war" (runtime-name: "helloworld-mdb.war")
- 20:01:58,321 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\2d\43d30c7fec449dade79a3a744951382a365812\content
- 20:01:58,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "ec-ejb.jar" (runtime-name: "ec-ejb.jar")
- 20:01:58,644 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Read persistence.xml for primary
- 20:01:58,722 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment ec-ejb.jar
- 20:01:58,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SecuityGuard' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:app/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:module/SecuityGuard!ec.jpa.SecurityLocal
- ejb:/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:global/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- java:app/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- java:module/SecuityGuard!ec.jpa.SecuityGuard
- ejb:/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- 20:01:58,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'JMSStateless' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:app/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:module/JMSStateless!ec.mdb.JMSStateless
- ejb:/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:global/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- java:app/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- java:module/JMSStateless!ec.mdb.JMSStatelessLocal
- ejb:/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- 20:01:58,771 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBStateless' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:app/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:module/SBStateless!ec.lab.SBStatelessRemote
- java:jboss/exported/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- ejb:/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:global/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:app/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:module/SBStateless!ec.lab.SBStatelessLocal
- ejb:/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:global/ec-ejb/SBStateless!ec.lab.SBStateless
- java:app/ec-ejb/SBStateless!ec.lab.SBStateless
- java:module/SBStateless!ec.lab.SBStateless
- ejb:/ec-ejb/SBStateless!ec.lab.SBStateless
- 20:01:58,771 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'UserSB' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/UserSB!ec.jpa.UserSBRemote
- java:app/ec-ejb/UserSB!ec.jpa.UserSBRemote
- java:module/UserSB!ec.jpa.UserSBRemote
- java:jboss/exported/ec-ejb/UserSB!ec.jpa.UserSBRemote
- ejb:/ec-ejb/UserSB!ec.jpa.UserSBRemote?stateful
- java:global/ec-ejb/UserSB
- java:app/ec-ejb/UserSB
- java:module/UserSB
- 20:01:58,771 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBStateful' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- java:app/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- java:module/SBStateful!ec.lab.SBStatefulRemote
- java:jboss/exported/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- ejb:/ec-ejb/SBStateful!ec.lab.SBStatefulRemote?stateful
- java:global/ec-ejb/SBStateful!ec.lab.SBStatefulLocal
- java:app/ec-ejb/SBStateful!ec.lab.SBStatefulLocal
- java:module/SBStateful!ec.lab.SBStatefulLocal
- ejb:/ec-ejb/SBStateful!ec.lab.SBStatefulLocal?stateful
- 20:01:58,771 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBSingleton' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:module/SBSingleton!ec.lab.SBSingletonRemote
- java:jboss/exported/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:module/SBSingleton!ec.lab.SBSingleton
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- java:module/SBSingleton!ec.lab.SBSingletonLocal
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- 20:01:58,913 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean 'sub1' with 'activemq-ra.rar' resource adapter
- 20:01:58,913 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0042: Started message driven bean 'sub2' with 'activemq-ra.rar' resource adapter
- 20:01:58,917 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean 'testQueue' with 'activemq-ra.rar' resource adapter
- 20:01:58,938 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "ec-ejb.jar")]) - failure description: {
- "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.MySqlDS"],
- "WFLYCTL0180: Services with missing/unavailable dependencies" => [
- "jboss.persistenceunit.\"ec-ejb.jar#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.MySqlDS]",
- "jboss.persistenceunit.\"ec-ejb.jar#primary\" is missing [jboss.naming.context.java.MySqlDS]"
- ]
- }
- 20:01:58,938 ERROR [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0021: Deploy of deployment "ec-ejb.jar" was rolled back with the following failure message:
- {
- "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.MySqlDS"],
- "WFLYCTL0180: Services with missing/unavailable dependencies" => [
- "jboss.persistenceunit.\"ec-ejb.jar#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.MySqlDS]",
- "jboss.persistenceunit.\"ec-ejb.jar#primary\" is missing [jboss.naming.context.java.MySqlDS]"
- ]
- }
- 20:01:58,962 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment ec-ejb.jar (runtime-name: ec-ejb.jar) in 23ms
- 20:03:53,898 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\99\9517961513be0cbe3ca492c6d15cbf28a4e1ce\content
- 20:03:53,902 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "ec-ejb.jar" (runtime-name: "ec-ejb.jar")
- 20:03:54,171 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for primary
- 20:03:54,190 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment ec-ejb.jar
- 20:03:54,223 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SecuityGuard' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:app/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:module/SecuityGuard!ec.jpa.SecurityLocal
- ejb:/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:global/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- java:app/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- java:module/SecuityGuard!ec.jpa.SecuityGuard
- ejb:/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- 20:03:54,224 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'JMSStateless' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:app/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:module/JMSStateless!ec.mdb.JMSStateless
- ejb:/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:global/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- java:app/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- java:module/JMSStateless!ec.mdb.JMSStatelessLocal
- ejb:/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- 20:03:54,224 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBStateless' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:app/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:module/SBStateless!ec.lab.SBStatelessRemote
- java:jboss/exported/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- ejb:/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:global/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:app/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:module/SBStateless!ec.lab.SBStatelessLocal
- ejb:/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:global/ec-ejb/SBStateless!ec.lab.SBStateless
- java:app/ec-ejb/SBStateless!ec.lab.SBStateless
- java:module/SBStateless!ec.lab.SBStateless
- ejb:/ec-ejb/SBStateless!ec.lab.SBStateless
- 20:03:54,224 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'UserSB' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/UserSB!ec.jpa.UserSBRemote
- java:app/ec-ejb/UserSB!ec.jpa.UserSBRemote
- java:module/UserSB!ec.jpa.UserSBRemote
- java:jboss/exported/ec-ejb/UserSB!ec.jpa.UserSBRemote
- ejb:/ec-ejb/UserSB!ec.jpa.UserSBRemote?stateful
- java:global/ec-ejb/UserSB
- java:app/ec-ejb/UserSB
- java:module/UserSB
- 20:03:54,224 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBStateful' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- java:app/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- java:module/SBStateful!ec.lab.SBStatefulRemote
- java:jboss/exported/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- ejb:/ec-ejb/SBStateful!ec.lab.SBStatefulRemote?stateful
- java:global/ec-ejb/SBStateful!ec.lab.SBStatefulLocal
- java:app/ec-ejb/SBStateful!ec.lab.SBStatefulLocal
- java:module/SBStateful!ec.lab.SBStatefulLocal
- ejb:/ec-ejb/SBStateful!ec.lab.SBStatefulLocal?stateful
- 20:03:54,225 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBSingleton' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:module/SBSingleton!ec.lab.SBSingletonRemote
- java:jboss/exported/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:module/SBSingleton!ec.lab.SBSingleton
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- java:module/SBSingleton!ec.lab.SBSingletonLocal
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- 20:03:54,307 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0042: Started message driven bean 'sub1' with 'activemq-ra.rar' resource adapter
- 20:03:54,308 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean 'sub2' with 'activemq-ra.rar' resource adapter
- 20:03:54,308 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0042: Started message driven bean 'testQueue' with 'activemq-ra.rar' resource adapter
- 20:03:54,319 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "ec-ejb.jar")]) - failure description: {
- "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.MySqlDS"],
- "WFLYCTL0180: Services with missing/unavailable dependencies" => [
- "jboss.persistenceunit.\"ec-ejb.jar#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.MySqlDS]",
- "jboss.persistenceunit.\"ec-ejb.jar#primary\" is missing [jboss.naming.context.java.MySqlDS]"
- ]
- }
- 20:03:54,320 ERROR [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0021: Deploy of deployment "ec-ejb.jar" was rolled back with the following failure message:
- {
- "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.MySqlDS"],
- "WFLYCTL0180: Services with missing/unavailable dependencies" => [
- "jboss.persistenceunit.\"ec-ejb.jar#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.MySqlDS]",
- "jboss.persistenceunit.\"ec-ejb.jar#primary\" is missing [jboss.naming.context.java.MySqlDS]"
- ]
- }
- 20:03:54,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment ec-ejb.jar (runtime-name: ec-ejb.jar) in 13ms
- 20:05:33,233 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\b2\92ea8036ff719afd9d1e324f1c98beb9a10a57\content
- 20:05:33,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "ec-ejb.jar" (runtime-name: "ec-ejb.jar")
- 20:05:33,445 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Read persistence.xml for primary
- 20:05:33,462 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment ec-ejb.jar
- 20:05:33,493 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'SecuityGuard' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:app/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:module/SecuityGuard!ec.jpa.SecurityLocal
- ejb:/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:global/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- java:app/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- java:module/SecuityGuard!ec.jpa.SecuityGuard
- ejb:/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- 20:05:33,493 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'JMSStateless' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:app/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:module/JMSStateless!ec.mdb.JMSStateless
- ejb:/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:global/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- java:app/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- java:module/JMSStateless!ec.mdb.JMSStatelessLocal
- ejb:/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- 20:05:33,493 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'SBStateless' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:app/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:module/SBStateless!ec.lab.SBStatelessRemote
- java:jboss/exported/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- ejb:/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:global/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:app/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:module/SBStateless!ec.lab.SBStatelessLocal
- ejb:/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:global/ec-ejb/SBStateless!ec.lab.SBStateless
- java:app/ec-ejb/SBStateless!ec.lab.SBStateless
- java:module/SBStateless!ec.lab.SBStateless
- ejb:/ec-ejb/SBStateless!ec.lab.SBStateless
- 20:05:33,493 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'UserSB' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/UserSB!ec.jpa.UserSBRemote
- java:app/ec-ejb/UserSB!ec.jpa.UserSBRemote
- java:module/UserSB!ec.jpa.UserSBRemote
- java:jboss/exported/ec-ejb/UserSB!ec.jpa.UserSBRemote
- ejb:/ec-ejb/UserSB!ec.jpa.UserSBRemote?stateful
- java:global/ec-ejb/UserSB
- java:app/ec-ejb/UserSB
- java:module/UserSB
- 20:05:33,493 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'SBStateful' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- java:app/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- java:module/SBStateful!ec.lab.SBStatefulRemote
- java:jboss/exported/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- ejb:/ec-ejb/SBStateful!ec.lab.SBStatefulRemote?stateful
- java:global/ec-ejb/SBStateful!ec.lab.SBStatefulLocal
- java:app/ec-ejb/SBStateful!ec.lab.SBStatefulLocal
- java:module/SBStateful!ec.lab.SBStatefulLocal
- ejb:/ec-ejb/SBStateful!ec.lab.SBStatefulLocal?stateful
- 20:05:33,494 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'SBSingleton' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:module/SBSingleton!ec.lab.SBSingletonRemote
- java:jboss/exported/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:module/SBSingleton!ec.lab.SBSingleton
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- java:module/SBSingleton!ec.lab.SBSingletonLocal
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- 20:05:33,564 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0042: Started message driven bean 'testQueue' with 'activemq-ra.rar' resource adapter
- 20:05:33,565 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0042: Started message driven bean 'sub2' with 'activemq-ra.rar' resource adapter
- 20:05:33,566 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0042: Started message driven bean 'sub1' with 'activemq-ra.rar' resource adapter
- 20:05:33,579 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "ec-ejb.jar")]) - failure description: {
- "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.MySqlDS"],
- "WFLYCTL0180: Services with missing/unavailable dependencies" => [
- "jboss.persistenceunit.\"ec-ejb.jar#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.MySqlDS]",
- "jboss.persistenceunit.\"ec-ejb.jar#primary\" is missing [jboss.naming.context.java.MySqlDS]"
- ]
- }
- 20:05:33,579 ERROR [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0021: Deploy of deployment "ec-ejb.jar" was rolled back with the following failure message:
- {
- "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.MySqlDS"],
- "WFLYCTL0180: Services with missing/unavailable dependencies" => [
- "jboss.persistenceunit.\"ec-ejb.jar#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.MySqlDS]",
- "jboss.persistenceunit.\"ec-ejb.jar#primary\" is missing [jboss.naming.context.java.MySqlDS]"
- ]
- }
- 20:05:33,592 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment ec-ejb.jar (runtime-name: ec-ejb.jar) in 12ms
- 20:11:48,432 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 90) WFLYDR0009: Content C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\b2\92ea8036ff719afd9d1e324f1c98beb9a10a57 is obsolete and will be removed
- 20:11:48,435 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 90) WFLYDR0002: Content removed from location C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\b2\92ea8036ff719afd9d1e324f1c98beb9a10a57\content
- 20:11:48,435 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 90) WFLYDR0009: Content C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\99\9517961513be0cbe3ca492c6d15cbf28a4e1ce is obsolete and will be removed
- 20:11:48,437 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 90) WFLYDR0002: Content removed from location C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\99\9517961513be0cbe3ca492c6d15cbf28a4e1ce\content
- 20:11:48,437 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 90) WFLYDR0009: Content C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\2d\43d30c7fec449dade79a3a744951382a365812 is obsolete and will be removed
- 20:11:48,438 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 90) WFLYDR0002: Content removed from location C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\2d\43d30c7fec449dade79a3a744951382a365812\content
- 20:19:29,481 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\87\812d21ec1fae8e0adf542164fa3ac9c707d5e9\content
- 20:19:29,484 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ec-ejb.jar" (runtime-name: "ec-ejb.jar")
- 20:19:29,731 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Read persistence.xml for primary
- 20:19:29,751 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment ec-ejb.jar
- 20:19:29,783 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SecuityGuard' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:app/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:module/SecuityGuard!ec.jpa.SecurityLocal
- ejb:/ec-ejb/SecuityGuard!ec.jpa.SecurityLocal
- java:global/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- java:app/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- java:module/SecuityGuard!ec.jpa.SecuityGuard
- ejb:/ec-ejb/SecuityGuard!ec.jpa.SecuityGuard
- 20:19:29,783 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'JMSStateless' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:app/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:module/JMSStateless!ec.mdb.JMSStateless
- ejb:/ec-ejb/JMSStateless!ec.mdb.JMSStateless
- java:global/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- java:app/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- java:module/JMSStateless!ec.mdb.JMSStatelessLocal
- ejb:/ec-ejb/JMSStateless!ec.mdb.JMSStatelessLocal
- 20:19:29,783 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBStateless' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:app/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:module/SBStateless!ec.lab.SBStatelessRemote
- java:jboss/exported/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- ejb:/ec-ejb/SBStateless!ec.lab.SBStatelessRemote
- java:global/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:app/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:module/SBStateless!ec.lab.SBStatelessLocal
- ejb:/ec-ejb/SBStateless!ec.lab.SBStatelessLocal
- java:global/ec-ejb/SBStateless!ec.lab.SBStateless
- java:app/ec-ejb/SBStateless!ec.lab.SBStateless
- java:module/SBStateless!ec.lab.SBStateless
- ejb:/ec-ejb/SBStateless!ec.lab.SBStateless
- 20:19:29,783 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'UserSB' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/UserSB!ec.jpa.UserSBRemote
- java:app/ec-ejb/UserSB!ec.jpa.UserSBRemote
- java:module/UserSB!ec.jpa.UserSBRemote
- java:jboss/exported/ec-ejb/UserSB!ec.jpa.UserSBRemote
- ejb:/ec-ejb/UserSB!ec.jpa.UserSBRemote?stateful
- java:global/ec-ejb/UserSB
- java:app/ec-ejb/UserSB
- java:module/UserSB
- 20:19:29,783 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBStateful' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- java:app/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- java:module/SBStateful!ec.lab.SBStatefulRemote
- java:jboss/exported/ec-ejb/SBStateful!ec.lab.SBStatefulRemote
- ejb:/ec-ejb/SBStateful!ec.lab.SBStatefulRemote?stateful
- java:global/ec-ejb/SBStateful!ec.lab.SBStatefulLocal
- java:app/ec-ejb/SBStateful!ec.lab.SBStatefulLocal
- java:module/SBStateful!ec.lab.SBStatefulLocal
- ejb:/ec-ejb/SBStateful!ec.lab.SBStatefulLocal?stateful
- 20:19:29,783 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'SBSingleton' in deployment unit 'deployment "ec-ejb.jar"' are as follows:
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:module/SBSingleton!ec.lab.SBSingletonRemote
- java:jboss/exported/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingletonRemote
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:module/SBSingleton!ec.lab.SBSingleton
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingleton
- java:global/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- java:app/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- java:module/SBSingleton!ec.lab.SBSingletonLocal
- ejb:/ec-ejb/SBSingleton!ec.lab.SBSingletonLocal
- 20:19:29,855 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0042: Started message driven bean 'testQueue' with 'activemq-ra.rar' resource adapter
- 20:19:29,855 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0042: Started message driven bean 'sub2' with 'activemq-ra.rar' resource adapter
- 20:19:29,859 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0042: Started message driven bean 'sub1' with 'activemq-ra.rar' resource adapter
- 20:19:29,873 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "ec-ejb.jar")]) - failure description: {
- "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.MySqlDS"],
- "WFLYCTL0180: Services with missing/unavailable dependencies" => [
- "jboss.persistenceunit.\"ec-ejb.jar#primary\" is missing [jboss.naming.context.java.MySqlDS]",
- "jboss.persistenceunit.\"ec-ejb.jar#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.MySqlDS]"
- ]
- }
- 20:19:29,873 ERROR [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0021: Deploy of deployment "ec-ejb.jar" was rolled back with the following failure message:
- {
- "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.MySqlDS"],
- "WFLYCTL0180: Services with missing/unavailable dependencies" => [
- "jboss.persistenceunit.\"ec-ejb.jar#primary\" is missing [jboss.naming.context.java.MySqlDS]",
- "jboss.persistenceunit.\"ec-ejb.jar#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.MySqlDS]"
- ]
- }
- 20:19:29,890 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment ec-ejb.jar (runtime-name: ec-ejb.jar) in 16ms
- 20:26:48,479 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 90) WFLYDR0009: Content C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\87\812d21ec1fae8e0adf542164fa3ac9c707d5e9 is obsolete and will be removed
- 20:26:48,482 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 90) WFLYDR0002: Content removed from location C:\enterprise\wildfly-18.0.1.Final\standalone\data\content\87\812d21ec1fae8e0adf542164fa3ac9c707d5e9\content
Advertisement
Add Comment
Please, Sign In to add comment