I am having problems with OSGI bundles on Wildfly (formerly known as JBoss) 8.0.0-beta1.
I installed OSGI without issues. Then, when I launch the application server, OSGI apparently starts correctly:
[org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.apache.felix.log:1.0.1
[org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: jboss-osgi-logging:1.0.0
[org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.apache.felix.configadmin:1.6.0
[org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: jbosgi-wildfly-configadmin:2.1.0
[org.jboss.osgi.framework] (MSC service thread 1-13) JBOSGI011011: Starting bundles for start level: 1
[org.jboss.osgi.framework] (MSC service thread 1-13) JBOSGI011002: Bundle started: jbosgi-wildfly-http:2.1.0
[org.jboss.osgi.framework] (MSC service thread 1-13) JBOSGI011002: Bundle started: jbosgi-wildfly-jpa:2.1.0
[org.jboss.osgi.framework] (MSC service thread 1-13) JBOSGI011002: Bundle started: org.apache.felix.log:1.0.1
[org.jboss.osgi.framework] (MSC service thread 1-13) JBOSGI011002: Bundle started: jboss-osgi-logging:1.0.0
[org.jboss.osgi.framework] (MSC service thread 1-13) JBOSGI011002: Bundle started: org.apache.felix.configadmin:1.6.0
[org.jboss.osgi.framework] (MSC service thread 1-13) JBOSGI011002: Bundle started: jbosgi-wildfly-configadmin:2.1.0
[org.jboss.osgi.framework] (MSC service thread 1-13) JBOSGI011000: OSGi Framework started
However, when I use the management console, some important information on the bundles is apparently missing (check attached screen shot).
This is data I have using /subsystem=osgi:
{
"activation" => "eager",
"startlevel" => 1,
"bundle" => {
"0" => undefined,
"1" => undefined,
"10" => undefined,
"11" => undefined,
"12" => undefined,
"13" => undefined,
"14" => undefined,
"2" => undefined,
"3" => undefined,
"4" => undefined,
"5" => undefined,
"6" => undefined,
"7" => undefined,
"8" => undefined,
"9" => undefined
},
"capability" => {
"javax.jws.api" => undefined,
"javax.persistence.api" => undefined,
"javax.servlet.api" => undefined,
"javax.transaction.api" => undefined,
"javax.ws.rs.api" => undefined,
"javax.xml.bind.api" => undefined,
"javax.xml.ws.api" => undefined,
"org.apache.felix.log" => undefined,
"org.jboss.osgi.logging" => undefined,
"org.apache.felix.configadmin" => undefined,
"org.jboss.as.osgi.configadmin" => undefined,
"org.jboss.as.osgi.http" => undefined,
"org.jboss.as.osgi.jpa" => undefined
},
"property" => {"org.osgi.framework.startlevel.beginning" => undefined}
}
Related
I am experiencing an unexpected automatic EAR restart from Wildfly 23.0.2.Final (also verified with 22.0.1.Final and 23.0.0.Final).
Basically, what happens is that the application is started, but when everything is up and running, I receive a message that reads WFLYSRV0212: Resuming server and the deploy process starts over again. This also seems to jeopardize JMS queues definition (defined from within the EJB module as #JMSResourceDestinations).
Below the snippet of the logs when this happens (just a bit anonymized):
13:16:12,228 INFO [org.jboss.as.server] (ServerService Thread Pool -- 48) WFLYSRV0010: Deployed "XXXX.ear" (runtime-name : "XXXX.ear")
13:16:12,250 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0019: Stopped Driver service with driver-name = XXXXX.ear_org.postgresql.Driver_42_2
13:16:12,251 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
13:16:12,260 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 9) WFLYUT0022: Unregistered web context: '/api' from server 'default-server'
13:16:12,269 INFO [io.undertow.servlet] (ServerService Thread Pool -- 9) Closing Spring root WebApplicationContext
13:16:12,303 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 25) AMQ222061: Client connection failed, clearing up resources for session 1610e737-d282-11eb-9d4b-0242e77fb65d
13:16:12,309 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 25) AMQ222107: Cleared up resources for session 1610e737-d282-11eb-9d4b-0242e77fb65d
13:16:12,313 WARN [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ152005: Failure in broker activation org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter#9f1bfbc destination=java:global/XXXX/jms/queue/queue1 destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): ActiveMQUnBlockedException[errorType=UNBLOCKED message=AMQ219016: Connection failure detected. Unblocking a blocking call that will never get a response]
at org.apache.activemq.artemis#2.16.0//org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:540)
at org.apache.activemq.artemis#2.16.0//org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:434)
at org.apache.activemq.artemis#2.16.0//org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:300)
at org.apache.activemq.artemis#2.16.0//org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:249)
at org.apache.activemq.artemis#2.16.0//org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1401)
at org.apache.activemq.artemis#2.16.0//org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:705)
at org.apache.activemq.artemis#2.16.0//org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:316)
at org.apache.activemq.artemis.ra#2.16.0//org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.createSession(ActiveMQResourceAdapter.java:1602)
at org.apache.activemq.artemis.ra#2.16.0//org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setupSession(ActiveMQActivation.java:491)
at org.apache.activemq.artemis.ra#2.16.0//org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setup(ActiveMQActivation.java:316)
at org.apache.activemq.artemis.ra#2.16.0//org.apache.activemq.artemis.ra.inflow.ActiveMQActivation$SetupActivation.run(ActiveMQActivation.java:764)
at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter$WorkWrapper.run(ActiveMQResourceAdapter.java:161)
at org.jboss.ironjacamar.impl#1.4.27.Final//org.jboss.jca.core.workmanager.WorkWrapper.runWork(WorkWrapper.java:445)
at org.jboss.as.connector#23.0.2.Final//org.jboss.as.connector.services.workmanager.WildflyWorkWrapper.runWork(WildflyWorkWrapper.java:69)
at org.jboss.ironjacamar.impl#1.4.27.Final//org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:29)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:789)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:44)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:809)
at java.base/java.lang.Thread.run(Thread.java:829)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
13:16:12,329 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:global/XXXX/jms/queue/queue1
The EAR was created with the specific Wildfly archetype. The configuration of the Wildfly instance is the standalone-full, as it comes out of the box.
Anyone who can help me understand what's happening?
UPDATE: Wildfly logs
Increasing the root log level and goinf through it, I've found the following:
2021-06-22 18:44:59,357 DEBUG [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) Deployment scan of [/home/xxxx/wildfly-23.0.2.Final/standalone/deployments] found update action [{
"operation" => "composite",
"address" => [],
"steps" => [
{
"operation" => "add",
"address" => [("deployment" => "togather-engine.ear")],
"content" => [{
"archive" => false,
"path" => "deployments/XXXX.ear",
"relative-to" => "jboss.server.base.dir"
}],
"persistent" => false,
"owner" => [
("subsystem" => "deployment-scanner"),
("scanner" => "default")
]
},
{
"operation" => "deploy",
"address" => [("deployment" => "XXXX.ear")],
"owner" => [
("subsystem" => "deployment-scanner"),
("scanner" => "default")
]
}
],
"operation-headers" => {"rollback-on-runtime-failure" => false}
}]
After a bit
2021-06-22 18:45:11,886 DEBUG [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) Deployment scan of [/home/xxxxx/wildfly-23.0.2.Final/standalone/deployments] found update action [{
"operation" => "redeploy",
"address" => [("deployment" => "XXXX.ear")],
"owner" => [
("subsystem" => "deployment-scanner"),
("scanner" => "default")
]
}]
It looks that it's actually that is going through the deployment twice.
I have created the maridb folder inside Wildfly/module.../mariadb/ and added the required module.xml file and appropriate jar file.
08:36:58,152 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "dgpa")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.jdbc-driver.mariadb-java-client-2_3_0_jar"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.driver-demander.java:jboss/datasources/Archive is missing [jboss.jdbc-driver.mariadb-java-client-2_3_0_jar]",
"org.wildfly.data-source.dbpa is missing [jboss.jdbc-driver.mariadb-java-client-2_3_0_jar]"
]
}
08:36:58,192 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "dbagpa")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => [
"jboss.jdbc-driver.mariadb-java-client-2_3_0_jar",
"jboss.jdbc-driver.mariadb-java-client-2_3_0_jar"
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.driver-demander.java:jboss/datasources/Archive is missing [jboss.jdbc-driver.mariadb-java-client-2_3_0_jar]",
"org.wildfly.data-source.dbpa is missing [jboss.jdbc-driver.mariadb-java-client-2_3_0_jar]",
"org.wildfly.data-source.dbpa is missing [jboss.jdbc-driver.mariadb-java-client-2_3_0_jar]"
I am posting answer to my question, I messed up with my standalone.xml and I followed the below-mentioned link and it worked.
https://issues.redhat.com/browse/JBEAP-2405
My jboss server starts without errors and deploys my ear but after some seconds it undeploys it:
16:03:34,762 DEBUG [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) Deployment scan of [U:\JBOSS_CFG\deployments] found update action
16:28:46,919 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "myear.ear" (runtime-name : "my-ear.ear")
[{
"operation" => "composite",
"address" => [],
"steps" => [
{
"operation" => "undeploy",
"address" => [("deployment" => "my-ear.ear")]
},
{
"operation" => "remove",
"address" => [("deployment" => "my-ear.ear")]
}
]
}]
16:28:51,014 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment null (runtime-name: my-ejb.jar) in 25ms
16:28:51,093 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment my-ear.ear (runtime-name: my-ear.ear) in 82ms
16:28:51,186 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "my-ear.ear" (runtime-name: "my-ear.ear")
Unable to deploy my ears into WildFly10.0.0 and same ear working fine in JBoss7.1.1 server. Here are the details of my project and error which i'm facing while adding my ear to server. Jar file used in ejbModule to prepare ear file attached as a screen shot. Giving an exception while adding it to server. same ear working fine in JBoss7.1.1 Final version.
**jboss-deployment-structure.xml**
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="com.hway.blz.fm" export="true"/>
<module name="com.hway.blz.common" export="true"/>
<module name="com.blazesoft" export="true"/>
<module name="com.thoughtworks" export="true"/>
<module name="org.jboss.ws.cxf.jbossws-cxf-client" services="true" export="true"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
fm-web.jar:
Jar having two classes to expose my object model as wsdl using RPC\soap binding
\fm-web\ejbModule\com\hway\blz\fm\Fmbean.java
[Error details provided in the attached screen shot][1] Pls. help me on this issue resolution.
Dismiss
Wed Apr 19 21:51:18 GMT-500 2017
Unable to assign fm-rules.ear.
Unexpected HTTP response: 500
Request
{
"operation" => "composite",
"address" => undefined,
"steps" => [{
"operation" => "add",
"address" => [
("server-group" => "main-server-group"),
("deployment" => "fm-rules.ear")
],
"runtime-name" => "fm-rules.ear",
"enabled" => true
}]
}
Response
Internal Server Error
{
"outcome" => "failed",
"result" => {"step-1" => {
"outcome" => "failed",
"rolled-back" => true
}},
"failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"main-server-group" => {"host" => {"master" => {
"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {
"jboss.module.service.\"deployment.fm-rules.ear\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.fm-rules.ear\".main: WFLYSRV0179: Failed to load module: deployment.fm-rules.ear:main
Caused by: org.jboss.modules.ModuleNotFoundException: com.hway.blz.fm:main",
"jboss.module.service.\"deployment.fm-rules.ear.fm-web.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.fm-rules.ear.fm-web.jar\".main: WFLYSRV0179: Failed to load module: deployment.fm-rules.ear.fm-web.jar:main
Caused by: org.jboss.modules.ModuleNotFoundException: com.hway.blz.fm:main"
}}}},
"server-two" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {
"jboss.module.service.\"deployment.fm-rules.ear.fm-web.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.fm-rules.ear.fm-web.jar\".main: WFLYSRV0179: Failed to load module: deployment.fm-rules.ear.fm-web.jar:main
Caused by: org.jboss.modules.ModuleNotFoundException: com.hway.blz.fm:main",
"jboss.module.service.\"deployment.fm-rules.ear\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.fm-rules.ear\".main: WFLYSRV0179: Failed to load module: deployment.fm-rules.ear:main
Caused by: org.jboss.modules.ModuleNotFoundException: com.hway.blz.fm:main"
}}}}
}}}}}}
[1]: https://i.stack.imgur.com/UEP0O.png
[1]: https://i.stack.imgur.com/W9WHi.png
It looks like you're missing a module Caused by: org.jboss.modules.ModuleNotFoundException: com.hway.blz.fm:main. You'll need to make sure that module is installed in the $JBOSS_HOME/modules directory.
Wildfly 10 on deploy
Can you help me with such error
11:25:36,039 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "console-dev.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => [
"jboss.naming.context.java.global.\"services-1.0.5\".\"api.ejb-1.1\".\"ActionsFacadeBean!by.common.api.IActionsService\""
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.naming.context.java.module.console-dev.console-dev.env.\"by.abank.admin.ui.factory.EJBFactory\".iActionsService is missing [jboss.naming.context.java.global.\"services-1.0.5\".\"api.ejb-1.1\".\"ActionsFacadeBean!by.common.api.IActionsService\"]",
]
}
I have service.ear with
#Stateless #Remote ActionsFacadeBean
And console-dev.war
#EJB(lookup = "java:global/services-1.0.5/api.ejb-1.1/ActionsFacadeBean!by.common.api.IActionsService")
protected IActionsService iActionsService;