JBoss EAP 6.4 server log not getting updated deploying Spring Boot war

We recently deployed a new Spring Boot war on Jboss EAP 6.4 on our dev server. After which Server.log file stopped getting updated. Later we realized the problem because of our application configuration. We have added jboss-deployment-structure.xml in our Spring Boot application.

JBoss Exception: Failed to register driver for: com.mysql.jdbc.Driver

Join us on Facebook 

I was getting "Failed to register driver for: com.mysql.jdbc.Driver" while trying to get a DB connection in my web app with MySQL 5.5.11 deployed on  JBoss 5.1.0.GA.

Stack Trace:

10:31:23,279 WARN  [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: com.mysql.jdbc.Driver; - nested throwable: (java.lang.ClassNotFoundException: com.mysql.jdbc.Driver))
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:633)
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:267)
    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:622)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
    at Util.DBConnection.openConnection(DBConnection.java:56)

Solution:
mysql-connector-java-5.0.7-bin.jar was missing in JBOSS lib

-K Himaanshu Shukla...

Copyright © 2014 - ScrutinyByKHimaanshu

How to solve 'XML error parsing context.xml' issue in JBOSS-5?

Join us on Facebook 

I got below exception while I was trying to deploy my application on 'jboss-5.1.0.GA' :

Stack Trace:

10:07:21,163 INFO  [TomcatDeployment] deploy, ctxPath=/TESTSSO
10:07:21,247 ERROR [JBossContextConfig] XML error parsing: context.xml
org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser
    at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100)
    at org.jboss.web.tomcat.service.deployers.JBossContextConfig.processContextConfig(JBossContextConfig.java:549)
    at org.jboss.web.tomcat.service.deployers.JBossContextConfig.init(JBossContextConfig.java:536)
    at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:279)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
    at org.apache.catalina.core.StandardContext.init(StandardContext.java:5436)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4148)
    at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
    at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
    at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
    at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
    at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
    at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)

Cause:
 I checked and found xerces related jar(s) (eg: xercesImpl.jar) is present in my application application.  also found JBoss AS ships the xerces related jar in its JBOSS_HOME/lib/endorsed/ folder.

As my application packages this jar, that's why while deploying it leads to a classlaoder issue whicg ultimately resulting in the ClassCastException

Workaround:
Best solution is to remove the xerces related jar file(s) from your application packaging.

-K Himaanshu Shukla...

Copyright © 2014 - ScrutinyByKHimaanshu