This week's book giveaways are in the Cloud and AI/ML forums.
We're giving away four copies each of Cloud Native Patterns and Natural Language Processing and have the authors on-line!
See this thread and this one for details.
Win a copy of Cloud Native PatternsE this week in the Cloud forum
or Natural Language Processing in the AI/ML forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

JBAS015893: Encountered invalid class name error while JBoss 6.1 eap server startup

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am having an issue with the warnings trace while JBoss server startup while deploying the application. After placing the war/dump files into jboss-eap-6.1\standalone\deployments folders on server startup getting below warning trace. There is no issue with this trace but looking awkward in server log.



[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
[org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for service type 'javax.ws.rs.ext.MessageBodyWriter'



Another type of warning...


JBAS015960: Class Path entry schema/weblogic-domain-binding.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path reference.

JBAS015960: Class Path entry schema/diagnostics-binding.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path reference.

JBAS015960: Class Path entry schema/diagnostics-image-binding.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid

JBAS015960: Class Path entry schema/kodo-conf-binding.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for

JBAS015960: Class Path entry wlcipher.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path re

JBAS015960: Class Path entry xmlx.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path refere

JBAS015960: Class Path entry jconn2.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path refe

JBAS015960: Class Path entry jConnect.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path re

JBAS015960: Class Path entry EccpressoAsn1.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Pa

JBAS015960: Class Path entry EccpressoCore.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Pa

JBAS015960: Class Path entry EccpressoJcae.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Pa

JBAS015960: Class Path entry mysql-connector-java-commercial-5.0.3-bin.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point t

JBAS015960: Class Path entry wlbase.jar in /D:/jboss-eap-6.1/standalone/deployments/pmtwsWar.war/WEB-INF/lib/wlfullclient.jar does not point to a valid jar for a Class-Path refe







Is there any setting to overcome this in server log. ?
 
Greenhorn
Posts: 1
Mac Netbeans IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can give you an advise for the second type of warning. Check out the MANIFEST file of the wlfullclient.jar. It should be pointing to the wrong class names for classes in your Classpath. As mentioned here http://stackoverflow.com/a/15694701/3254097 you could try to remove the Class-Path entry in the MANIFEST file of the wlfullclient.jar.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!