I am developing JMS based module which consume message from IBM MQ and persist the data. My app is running in TomEE 8.0.0-M2. While starting my application I notice that Auto-linking resource-ref 'openejb/Resource is happening against all my EJB beans. I have configured my IBM MQ related factory and queue and Topic in resources.xml . All IBM MQ related resources are trying to auto link with all my EJB beans which is consuming more startup time.
None of my EJB doesn't have #Resource configuration.
I have MDB beans which has #MessageDriven annotation.
Why TomEE is trying to auto link to all EJB beans ?
How to fix this auto liking ?
I am ready to do any one time configuration in web.xml or in resources.xml
Sample log against one EJB Bean ( SimpleService)
08-Mar-2019 13:33:07.558 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/ROOT/imq_ra' in bean SimpleService to Resource(id=imq_ra)
08-Mar-2019 13:33:07.559 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/imq_ra' in bean SimpleService to Resource(id=imq_ra)
08-Mar-2019 13:33:07.559 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/ROOT/ibm.mq.connfactory' in bean SimpleService to Resource(id=ibm.mq.connfactory)
08-Mar-2019 13:33:07.559 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/ibm.mq.connfactory' in bean SimpleService to Resource(id=ibm.mq.connfactory)
08-Mar-2019 13:33:07.561 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/ROOT/imq_container-javax.jms.QueueConnectionFactory' in bean SimpleService to Resource(id=imq_container-javax.jms.QueueConnectionFactory)
08-Mar-2019 13:33:07.562 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/imq_container-javax.jms.QueueConnectionFactory' in bean SimpleService to Resource(id=imq_container-javax.jms.QueueConnectionFactory)
08-Mar-2019 13:33:07.562 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/ROOT/imq_container-javax.jms.TopicConnectionFactory' in bean SimpleService to Resource(id=imq_container-javax.jms.TopicConnectionFactory)
08-Mar-2019 13:33:07.563 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/imq_container-javax.jms.TopicConnectionFactory' in bean SimpleService to Resource(id=imq_container-javax.jms.TopicConnectionFactory)
08-Mar-2019 13:33:07.566 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/ROOT/download.topic' in bean SimpleService to Resource(id=download.topic)
08-Mar-2019 13:33:07.571 INFO [localhost-startStop-1] org.apache.openejb.config.AutoConfig.processResourceRef Auto-linking resource-ref 'openejb/Resource/download.topic' in bean SimpleService to Resource(id=download.topic)
Related
When i try to deploy war file in jboss 7 AS server i got following error
23:23:07,111 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."testapp.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."testapp.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "testapp.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_95]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_95]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_95]
Caused by: java.lang.RuntimeException: Error getting reflective information for class fr.improve.struts.taglib.layout.LabelledTag with ClassLoader ModuleClassLoader for Module "deployment.testapp.war:main" from Service Module Loader
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:85)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:70)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: java.lang.NoClassDefFoundError: Lorg/apache/struts/util/MessageResources;
at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.7.0_95]
at java.lang.Class.privateGetDeclaredFields(Class.java:2509) [rt.jar:1.7.0_95]
at java.lang.Class.getDeclaredFields(Class.java:1819) [rt.jar:1.7.0_95]
at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:66) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 10 more
Caused by: java.lang.ClassNotFoundException: org.apache.struts.util.MessageResources from [Module "deployment.testapp.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
... 15 more
23:23:07,118 INFO [org.jboss.as.server] (HttpManagementService-threads - 7) JBAS015870: Deploy of deployment "testapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"testapp.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"testapp.war\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"testapp.war\""}}
23:23:07,206 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment testapp.war in 87ms
23:23:07,206 INFO [org.jboss.as.controller] (HttpManagementService-threads - 7) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."testapp.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."testapp.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "testapp.war"
This problem happens when you try to deploy an ear/war/jar deployment in jboss7/wildfly and you have not specified what dependencies need your application.
Jboss7/Wildfly has his own module class loader to isolate applications and dependencies running into the same java virtual machine.
All deployments in jboss/wildfly are loaded as modules (not only the content included in modules folder, the content of deployments folder are modules too).
If you don't have packaged "struts" jar into the application deployment file, you will need to deploy the required dependencies as modules and tell to jboss that your application depends on it.
So, you have at least five alternatives:
Build your application as an Uber-Jar including your dependencies
inside.
Deploy your application and dependencies in the deployments folder and add a manifest entry in your application to tell to jboss that
your application depends on it.
Deploy your application and application dependencies (jars) in the deployments folder and add a jboss deployment descriptor xml in your
application to tell to jboss that your application depends on it.
Deploy your application in the deployments folder and create modules for your dependencies (if do not exist) and add a manifest
entry in your application to tell to jboss that your application
depends on it.
Deploy your application in deployments folder and create modules for your dependencies (if do not exist) and use a jboss deployment
descriptor xml in your application to tell to jboss that your
application depends on it.
For more information visit:
jboss 7 classloader
jboss 7 deployment descriptors
I am having a problem with deploying my application on JBoss AS 7.1. Here is what happened, we have a project that has been build on JDK 1.4 currently running on JRun 4. We are migrating the project to JDK 1.7 and deploy on JBoss AS 7.1.1.
Made required changes to the project compile in eclipse using JDK 1.7 like "enum", changed implementation of Log4j, etc. However the current project heavily relies on jaxb ver 1.0 implementation (which we would make changes over a period of time to the latest jaxb version and convert the project to web services).
However when I try to deploy the same project in JBoss I get an error as below, any help to get this resolved would be really appreciated.
12:39:55,710 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "presto.war"
12:40:00,590 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/xerces-1.2.3.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,591 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/xalan-2.0.0.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,593 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/xalanj1compat.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,595 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/batik.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,596 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/jimi-1.0.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,598 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/logkit-1.0b4.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,599 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/avalon-framework-4.0.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,611 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jaxp.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,612 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry crimson.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,617 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry sax.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/xt.jar" does not point to a valid jar for a Class-Path reference.
12:40:01,495 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.deployment.unit."presto.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."presto.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "presto.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.RuntimeException: Error getting reflective information for class org.apache.taglibs.xtags.xslt.XalanStyleTag with ClassLoader ModuleClassLoader for Module "deployment.presto.war:main" from Service Module Loader
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:85)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:70)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: java.lang.NoClassDefFoundError: Lorg/apache/xalan/xslt/XSLTResultTarget;
at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.7.0_51]
at java.lang.Class.privateGetDeclaredFields(Class.java:2397) [rt.jar:1.7.0_51]
at java.lang.Class.getDeclaredFields(Class.java:1806) [rt.jar:1.7.0_51]
at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:66) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 10 more
Caused by: java.lang.ClassNotFoundException: org.apache.xalan.xslt.XSLTResultTarget from [Module "deployment.presto.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
... 15 more
From the error stack you can see that:
Caused by: java.lang.ClassNotFoundException: org.apache.xalan.xslt.XSLTResultTarget from [Module "deployment.presto.war:main" from Service Module Loader]
So the class jar file getting loaded is from default JBOSS Modules and clearly the xalan.jar that comes with the JBoss 7(jboss-as-7.1.1.Final\modules\org\apache\xalan\main) does not contain that that class:
You need to either start using the jar file that your application refers to by replacing it with this jar(which is not reccomended) or use jboss-deployment-structure.xml to do so. This link could help you to decide what works best for you
The following error occurs when I start worklight:
objc[732]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/jre/bin/java and /Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined.
Launching worklight (WebSphere Application Server 8.5.5.0/wlp-1.0.3.20130524-0951) on Java HotSpot(TM) 64-Bit Server VM, version 1.7.0_40-b43 (en_US)
[AUDIT ] CWWKE0001I: The server worklight has been launched.
[AUDIT ] CWWKZ0058I: Monitoring dropins for applications.
[AUDIT ] CWWKT0016I: Web application available (default_host): http://acab0a7a.ipt.aol.com:10080/_MobileBrowserSimulator/
[AUDIT ] CWWKZ0001I: Application _MobileBrowserSimulator started in 0.274 seconds.
[AUDIT ] CWWKT0016I: Web application available (default_host): http://acab0a7a.ipt.aol.com:10080/mobile/
[err] 22 WorklightPU WARN [Scheduled Executor-thread-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root URL [file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available.
[ERROR ] FWLST0003E: ========= Failed starting project /mobile [project mobile]
Error creating bean with name 'taskManager' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Cannot resolve reference to bean 'worklightAuthenticationService' while setting bean property 'authenticationService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'worklightAuthenticationService' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Cannot create inner bean 'com.worklight.core.auth.impl.LoginConfigurationServiceBean#eb508f3' of type [com.worklight.core.auth.impl.LoginConfigurationServiceBean] while setting bean property 'loginConfigurationService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.worklight.core.auth.impl.LoginConfigurationServiceBean#eb508f3' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Class 'com.customauthpackage.CustomLoginModule' defined in login module 'CustomLoginModule' in the authentication configuration file doesn't exist.
[ERROR ] SRVE0283E: Exception caught while initializing context: java.lang.RuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskManager' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Cannot resolve reference to bean 'worklightAuthenticationService' while setting bean property 'authenticationService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'worklightAuthenticationService' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Cannot create inner bean 'com.worklight.core.auth.impl.LoginConfigurationServiceBean#eb508f3' of type [com.worklight.core.auth.impl.LoginConfigurationServiceBean] while setting bean property 'loginConfigurationService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.worklight.core.auth.impl.LoginConfigurationServiceBean#eb508f3' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Class 'com.customauthpackage.CustomLoginModule' defined in login module 'CustomLoginModule' in the authentication configuration file doesn't exist.
Caused by (repeated) ... : org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskManager' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Cannot resolve reference to bean 'worklightAuthenticationService' while setting bean property 'authenticationService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'worklightAuthenticationService' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Cannot create inner bean 'com.worklight.core.auth.impl.LoginConfigurationServiceBean#eb508f3' of type [com.worklight.core.auth.impl.LoginConfigurationServiceBean] while setting bean property 'loginConfigurationService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.worklight.core.auth.impl.LoginConfigurationServiceBean#eb508f3' defined in URL [wsjar:file:/Users/thomas/Documents/workspace/Concert/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar!/conf/core.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Class 'com.customauthpackage.CustomLoginModule' defined in login module 'CustomLoginModule' in the authentication configuration file doesn't exist.
...
Caused by: java.lang.RuntimeException: Class 'com.customauthpackage.CustomLoginModule' defined in login module 'CustomLoginModule' in the authentication configuration file doesn't exist.
...
[AUDIT ] CWWKZ0001I: Application mobile started in 4.168 seconds.
[AUDIT ] CWWKF0011I: The server worklight is ready to run a smarter planet.
I'm running OS X (10.8.4), Eclipse Juno SR2 20130225-0426, worklight plugin version 6.0.0.20130724-1819, Eclipse is pointing to jdk1.7.0_40 ("MacOS X VM") running in 1.7 compiler compliance level. CustomLoginModule is on the server and in the Eclipse viewer its covered in odd errors such as "String cannot be resolved to a type". I had this same error in windows and I believe I fixed it when I switched the eclipse jdk, but that didn't help this time. I really think this is a jdk issue, but everything seems correct. Any ideas? Thanks
EDIT: I resolved the issue by right clicking my project > properties > Java Build Path > Libraries > editing that "JRE System Library [jre7] (unbound)" and selecting "Workspace default JRE (Home)" thanks for your help! I got another problem now, but this one looks familiar as well. –
Have you checked for updates to your installed Worklight plug-in? a fix for 6.0.0.0 was released a while ago. Please check.
Otherwise, and I am not entirely sure, you should perhaps do the following:
Right-click on the Worklight project >> Properties
Java Build Path >> Libraries >> Add Library >> Server Runtime
Choose "Worklight Development Server" >> OK
Clean >> Restart server
seems for me JSF 2.2 is not working at all on JBoss 7.1.1
with jboss's multi jsf I just dropped in replacement of the jsf api and jsf implementation modules with respective jars of jsf 2.2
when my application starts I see following error:
01:46:59,286 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-5) Initializing Mojarra 2.2.0 ( 20130502-2118 https://svn.java.net/svn/mojarra~svn/tags/2.2.0#11930) for context '/broker'
01:46:59,922 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-5) Critical error during deployment: : java.lang.NoClassDefFoundError: com/sun/faces/spi/InjectionProvider
at javax.faces.FactoryFinder$FactoryManager.copyInjectionProviderFromFacesContext(FactoryFinder.java:1051) [jboss-jsf-api_2.2_spec-2.2.0.jar:2.2.0]
at javax.faces.FactoryFinder$FactoryManager.<init>(FactoryFinder.java:1035) [jboss-jsf-api_2.2_spec-2.2.0.jar:2.2.0]
at javax.faces.FactoryFinder$FactoryManagerCache.getApplicationFactoryManager(FactoryFinder.java:856) [jboss-jsf-api_2.2_spec-2.2.0.jar:2.2.0]
at javax.faces.FactoryFinder$FactoryManagerCache.getApplicationFactoryManager(FactoryFinder.java:793) [jboss-jsf-api_2.2_spec-2.2.0.jar:2.2.0]
at javax.faces.FactoryFinder$FactoryManagerCache.access$100(FactoryFinder.java:768) [jboss-jsf-api_2.2_spec-2.2.0.jar:2.2.0]
at javax.faces.FactoryFinder.setFactory(FactoryFinder.java:409) [jboss-jsf-api_2.2_spec-2.2.0.jar:2.2.0]
at com.sun.faces.config.processor.FactoryConfigProcessor.setFactory(FactoryConfigProcessor.java:317) [jsf-impl-2.2.0.jar:2.2.0]
at com.sun.faces.config.processor.FactoryConfigProcessor.processFactories(FactoryConfigProcessor.java:259) [jsf-impl-2.2.0.jar:2.2.0]
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216) [jsf-impl-2.2.0.jar:2.2.0]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:435) [jsf-impl-2.2.0.jar:2.2.0]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:214) [jsf-impl-2.2.0.jar:2.2.0]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Caused by: java.lang.ClassNotFoundException: com.sun.faces.spi.InjectionProvider from [Module "javax.faces.api:main" from local module loader #70dc82be (roots: /Users/ilyadyoshin/develop/jboss-as-7.1.1.Final/modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
... 19 more
Even more: when I look through contents of the jsf-api.jar I see this class.
may be I'm late but for other peoples who fall into the same problem, I found a solution here : https://community.jboss.org/thread/203257?start=0&tstart=0
Add to the module.xml of your JSF API module a depency to the JSF IMPL module by adding this line :
<module name="com.sun.jsf-impl"/>
Some changes may be required when multiple JSF versions exists on the AS.
Tested with JBoss 7.1 and JSF 2.2.0m12
EDIT : I didn't saw "(final)" in your subject, with the final JSF 2.2 version I ran into another probleme with NoContextActiveException for FlowDefinition :(
You are right, JSF 2.2 seems only to be supported starting from Wildfly / AS 8. I found a thread at JBoss community with installation instructions, followed by the information that it makes no sense to install with AS 7.1.1.
The thread referenced in the other answer (https://community.jboss.org/thread/203257) has been updated. I've tried it on my AS 7.1.1 and it works
My question is more related to "Force Jboss logging to use of SLF4J" but couldn't find more details in it so i am posting it here again. How to make slf4j work, if one of my class calls for slf4j i get the below error. Since jboss 7.1.1 already have slf4j module, what else i need add to make it work.
20:20:31,565 ERROR [stderr] (MSC service thread 1-8) SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
20:20:31,572 ERROR [stderr] (MSC service thread 1-8) SLF4J: Defaulting to no-operation (NOP) logger implementation
20:20:31,578 ERROR [stderr] (MSC service thread 1-8) SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
There is no need to force anything. slf4j is a logging facade. JBoss AS provides a bridge between slf4j and the JBoss Log Manager. All you need to do to get it to work is
Make sure you don't include the slf4j API library in your deployment
Also make sure you don't include an slf4j bridge in your deployment
Other than those two things there souldn't be anything else to do.