-
1. Re: Issue with jboss EAP 6.3
rafachies Feb 21, 2015 8:50 AM (in response to sharad7879)It seems yor WAR file has any client in order to connect to an EJB or JMS through JNDI name, but in EAP 6 the jndi cliente api has changed.
Find out the String "org.jnp.interfaces.NamingContextFactory" in your project code, and tell us for what it's there. With that in mind we can help you to solve this.
-
2. Re: Issue with jboss EAP 6.3
akraydvhall Mar 4, 2015 4:25 AM (in response to rafachies)Dear Rafael
i too suffering the deployment problem in j boss eap 6.3....
i do have a doubt that " if we deployed a war ,,,,,Actually we have 2 server groups.....on which server group can we assign this [./war]..?
After deploying the war i got this errors :
------------------------------------------------------------------------------------------------
Errors due to libraries:
Caused by:
java.lang.RuntimeException: JBAS018757: Error getting reflective information for class org.apache.struts.taglib.html.JavascriptValidatorTag with ClassLoader ModuleClassLoader for Module \"deployment.XXXXXXXXXX.war:main\" from Service Module Loader
Caused by:
java.lang.NoClassDefFoundError: org/apache/commons/validator/ValidatorResources
Caused by:
java.lang.ClassNotFoundException: org.apache.commons.validator.ValidatorResources from [Module \"deployment.XXXXXXXXXX.war:main\" from Service Module Loader]"}}
12:12:49,240
WARN [org.jboss.as.server.deployment] (MSC service thread 1-1)
JBAS015960: Class Path entry common-l10n.jar in /D:/jboss-eap-6.3/content/XXXXXXXXXX.war/WEB-INF/lib/common-util.jar does not point to a valid jar for a Class-Path reference.
===================================================================
Error due to services:
12:36:47,934 INFO [org.apache.catalina.core] (MSC service thread 1-3) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
12:36:48,092 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010409: Unbound data source [java:jboss/datasources/MY DATASOURCES]
12:36:48,092 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
12:36:48,107 INFO [org.jboss.jaxr] (MSC service thread 1-2) JBAS014002: UnBinding JAXR ConnectionFactory: java:jboss/jaxr/ConnectionFactory
12:36:48,170 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 70) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/ExpiryQueue
12:36:48,981 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) JBWEB003075: Coyote HTTP/1.1 pausing on: http-127.0.0.1/127.0.0.1:8230
12:36:48,981 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) JBWEB003077: Coyote HTTP/1.1 stopping on : http-127.0.0.1/127.0.0.1:8230
12:36:49,932 INFO [org.hornetq.ra] (ServerService Thread Pool -- 71) HQ151003: HornetQ resource adaptor stopped
12:36:50,603 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 71) HQ221002: HornetQ Server version 2.3.20.Final (2.3.20, 123) [3f963b26-b8bc-11e4-85cc-4df15aebebc9] stopped
12:36:51,102 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015950: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) stopped in 4038ms
please guide me,,
Thank u
-
3. Re: Issue with jboss EAP 6.3
sharad7879 Mar 4, 2015 4:55 AM (in response to sharad7879)My issue got solved after changing initial context to org.jboss.as.naming.InitialContextFactory.