Environment:
Jboss 7.2
Java 11
On loading JBoss 7.2 server I am getting an issue obtaining CDI 1.1 utilities. How could I to resolve this problem?
Server log SEVERE error on loading
...
08:24:15,561 SEVERE [javax.enterprise.resource.webcontainer.jsf.flow] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra
08:24:15,562 SEVERE [javax.enterprise.resource.webcontainer.jsf.application.view] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra
...
Related
[10/20/21 15:20:38:248 GMT] 0000006e view E Unable to obtain CDI 1.1 utilities for Mojarra
[10/20/21 15:20:38:254 GMT] 0000006e flow E Unable to obtain CDI 1.1 utilities for Mojarra
Caused by: java.lang.ClassNotFoundException: org.slf4j.Logger
at java.net.URLClassLoader.findClass(URLClassLoader.java:610)
at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:244)
at com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:129)
at java.lang.ClassLoader.loadClass(ClassLoader.java:872)
at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:62)
at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:58)
at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:607)
at java.lang.ClassLoader.loadClass(ClassLoader.java:872)
One problem here is that WebSphere 9 does not provide CDI integration with third-party JSF implementations like Mojarra. I'm not sure if this message Unable to obtain CDI 1.1 utilities for Mojarra error is caused by that lack of integration. IBM provides some docs for configuring third-party JSF implementations - for example putting the Mojarra lib in an isolated shared library is recommended.
Regardless CDI ViewScoped beans will not work correctly in this configuration. The WebSphere 9 runtime provides JSF MyFaces 2.2, which does have CDI integration. If you do need CDI+JSF integration, you should consider updating your app to use the JSF provided by WebSphere 9.
How could I make a common jar availabe in jboss 6.4 redhat ?
Is it possible to put it in JBOSS_HOME/standalone/lib ?
01:00:42,659 DEBUG [org.jboss.as.server.deployment] (MSC service thread 1-2) Adding dependency ModuleDependency [identifier=LogManager4JBoss-4.1.0rc2.jar:main, moduleLoader=local module loader #16f65612 (finder: local module finder #311d617d (roots: /opt/jboss6/modules,/opt/jboss6/modules/system/layers/base)), export=false, optional=false, importServices=false] to module deployment.tserver-5.0.0.jar:main
01:00:42,670 TRACE [org.jboss.modules] (MSC service thread 1-2) Locally loading module LogManager4JBoss-4.1.0rc2.jar:main from local module loader #16f65612 (finder: local module finder #311d617d (roots: /opt/jboss6/modules,/opt/jboss6/modules/system/layers/base))
01:00:42,671 TRACE [org.jboss.modules] (MSC service thread 1-2) Module LogManager4JBoss-4.1.0rc2.jar:main not found from local module loader #16f65612 (finder: local module finder #311d617d (roots: /opt/jboss6/modules,/opt/jboss6/modules/system/layers/base))
tserver-5.0.0.jar needs some common log stuff from LogManager4JBoss-4.1.0rc2.jar, all the documentation I read so far is confusing, I can't figure out where to put the common jar, this is working in a jboss 4.2.3, I need to use hibernate 3.5 for oracle db synonym support, from jboss 6
At the time of starting Jboss server I am getting below exception.
ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
Note: I am doing Jboss migration from 6.4 to 7.2
Please help.
I am trying to configure my ESB server as a client for JBoss EAP 7.1 integrated Active MQ Artemis which will connect using the RemoteConnectionFactory. However, I couldn't use the JBoss client jar as it conflicts with the internal JARs. Therefore, I added all the necessary JARs separately.
Now an exception is being thrown saying no provider found.
I have added both xnio-api and xnio-nio jars.
Below is the exception.
Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found
at org.xnio.Xnio.doGetInstance(Xnio.java:226)
at org.xnio.Xnio.getInstance(Xnio.java:192)
at org.jboss.naming.remote.client.EndpointCache.get(EndpointCache.java:47)
at org.jboss.naming.remote.client.InitialContextFactory.createEndpoint(InitialContextFactory.java:226)
at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateEndpoint(InitialContextFactory.java:207)
at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:170)
at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:146)
... 50 more
How do I resolve this error?
I am deploying a OSGI bundle in Jboss 7.1.1 by using Jboss as maven plugin and I am successfully deployed it into my jboss, my console shows following massege after deployment.
00:54:51,080 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "services-1.0-SNAPSHOT.jar"
00:54:51,110 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: testAapi:1.0.0.SNAPSHOT
00:54:51,190 INFO [org.jboss.as.server] (management-handler-thread - 7) JBAS018562: Redeployed "services-1.0-SNAPSHOT.jar"
But now I dont understand how can I start my osgi bundle automatically using the same maven plugin means jboss as maven plugin
Means I am deploying bundle using mvn jboss-as:deploy and it is deployed but it is not started.
See here: http://community.jboss.org/message/759637#759637