| Category: | Bug report |
Priority: | Urgent |
Status: | New |
| Project: | Severity: | Block |
Resolution: | Open |
|
| Component: | Reproducibility: | Always |
Assigned to: |
After I follow the installation procedure for the war file, the war file and the mysql-connector are in the deployments folder.
When I start the jboss server (7) standalone mode I get the error below.
I think it has to do with the deployment order of the jars.
----
17:48:47,049 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "jasperserver.war"
17:48:53,295 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry avalon-framework-4.2.0.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,303 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry batik-all-1.7.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,312 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry commons-io-1.3.1.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,320 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry serializer-2.7.0.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,329 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry servlet-2.2.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,338 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry xalan-2.7.0.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,347 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry xercesImpl-2.7.1.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,355 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry fop-hyph.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,363 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jai_codec.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,373 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jai_core.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,382 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jai_imageio.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,391 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jimi-1.0.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry xmlunit1.0.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,410 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jaxb-api.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/jaxb-impl-2.1.5.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,419 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry activation.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/jaxb-impl-2.1.5.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jsr173_1.0_api.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/jaxb-impl-2.1.5.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,443 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry jaxb1-impl.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/jaxb-impl-2.1.5.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,454 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry xml-apis.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/serializer-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry xercesImpl.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,475 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry xml-apis.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,484 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry serializer.jar in "/home/maarten/apps/jboss7/standalone/deployments/jasperserver.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
17:48:53,733 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'http\://java.sun.com/jaxp/xpath/dom: net.sf.saxon.xpath.XPathFactoryImpl' for service type 'javax.xml.xpath.XPathFactory'
17:48:53,751 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'http\://saxon.sf.net/jaxp/xpath/om: net.sf.saxon.xpath.XPathFactoryImpl' for service type 'javax.xml.xpath.XPathFactory'
17:48:53,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'moduleName=groovy-all' for service type 'org.codehaus.groovy.runtime.ExtensionModule'
17:48:53,784 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'moduleVersion=2.0.1' for service type 'org.codehaus.groovy.runtime.ExtensionModule'
17:48:53,795 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'extensionClasses=org.codehaus.groovy.jsr223.ScriptExtensions,org.codehaus.groovy.runtime.SqlGroovyMethods,org.codehaus.groovy.runtime.SwingGroovyMethods,org.codehaus.groovy.runtime.XmlGroovyMethods' for service type 'org.codehaus.groovy.runtime.ExtensionModule'
17:48:53,820 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'staticExtensionClasses=org.codehaus.groovy.jsr223.ScriptStaticExtensions' for service type 'org.codehaus.groovy.runtime.ExtensionModule'
17:48:53,839 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromStringEnum' for service type 'com.sun.jersey.spi.StringReaderProvider'
17:48:53,854 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeValueOf' for service type 'com.sun.jersey.spi.StringReaderProvider'
17:48:53,869 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromString' for service type 'com.sun.jersey.spi.StringReaderProvider'
17:48:53,884 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$StringConstructor' for service type 'com.sun.jersey.spi.StringReaderProvider'
17:48:53,898 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$DateProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'
17:48:53,915 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.JAXBStringReaderProviders$RootElementProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'
17:48:53,931 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.apache.hadoop.hdfs.DFSClient$Renewer' for service type 'org.apache.hadoop.security.token.TokenRenewer'
17:48:53,944 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.apache.hadoop.mapred.JobClient$Renewer' for service type 'org.apache.hadoop.security.token.TokenRenewer'
17:48:53,956 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.apache.hadoop.hdfs.security.token.block.BlockTokenIdentifier$Renewer' for service type 'org.apache.hadoop.security.token.TokenRenewer'
17:48:53,970 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.apache.hadoop.mapreduce.security.token.JobTokenIdentifier$Renewer' for service type 'org.apache.hadoop.security.token.TokenRenewer'
17:48:53,984 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.apache.hadoop.hdfs.HftpFileSystem$TokenManager' for service type 'org.apache.hadoop.security.token.TokenRenewer'
17:48:53,996 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.apache.hadoop.hdfs.web.WebHdfsFileSystem$DtRenewer' for service type 'org.apache.hadoop.security.token.TokenRenewer'
17:48:54,010 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,024 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,036 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,044 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,052 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,062 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,079 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,087 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,095 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,103 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,112 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,124 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,132 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,140 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,148 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,157 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,165 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,174 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,186 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,200 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,208 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,215 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,223 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,231 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,239 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,248 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,256 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,264 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,280 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,288 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,296 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,305 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,313 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,321 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
17:48:54,334 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,347 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,357 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,365 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,373 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,381 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,388 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,396 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,404 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,412 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
17:48:54,513 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."jasperserver.war".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jasperserver.war".CONFIGURE_MODULE: Failed to process phase CONFIGURE_MODULE of deployment "jasperserver.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:1110) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
Caused by: java.lang.NullPointerException
at org.jboss.vfs.VFSUtils.getRootURL(VFSUtils.java:571)
at org.jboss.as.server.deployment.module.VFSResourceLoader.<init>(VFSResourceLoader.java:86) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.module.ModuleSpecProcessor.addResourceRoot(ModuleSpecProcessor.java:253) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.module.ModuleSpecProcessor.createModuleService(ModuleSpecProcessor.java:165) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.module.ModuleSpecProcessor.deploy(ModuleSpecProcessor.java:105) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
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
8 Comments:
I'm running Jboss 7.1.1 (for clarity)
Same here. Noticed an odd issue though, I am deploying JS 5 on Oracle 11g however js.jdbc.properties file still has default properties pointing to default DB configuration for postgressSQL
please solved the problem?
After running ./js-install-ce.sh standalone directory/deployment file appears
jasperserver.war.failed
please solved the problem?
After running ./js-install-ce.sh standalone directory/deployment file appears
jasperserver.war.failed
we're facing same problem with JBossAS 7.1
is there anyone working on this?
There are two problems when running JS the first time in JBoss 7.1.x
Mysql-driver:
Workaround for this problem: use a fresh jboss 7.1.1 install. (This will not include the mysql-jdbc, which is why I think caused the problem.)
Loading time (is addressed in the documentation (installation manual A8.7.1): allow it to deploy for longer than one minute: it's an option somewhere in the standalone.xml)
A.8.7
JBoss Modifications
A.8.7.1
JBoss 7 Startup Error
JBoss7 has a default startup time period. If your JBoss 7 takes longer than 60 seconds to startup or deploy, you may receive the
following error:
"(DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout
period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the
deployment".
To fix this, you need to increase your deployment-timeout setting as follows:
1.
Change to the JBoss standalone configuration directory.
cd <jboss>/standalone/configuration
2. Open the standalone.xml file.
3. Look for the <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> element, for example:
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-
interval="5000"/>
</subsystem>
4.
Edit this to add or set the attribute deployment-timeout to the desired amount of time in seconds, for example:
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-
interval="5000" deployment-timeout="600"/>
</subsystem>
5.
Save the file.
On server restart, your system will have the specified amount of time to start up.
I have the same error.
The mysql driver is firing an error as well, If I deploy the mysql-***.jar through the administration console it works but in the deployments folder it fails. My installation is very very fresh.
the deployment stuff doesn't help at all.... I mean the timeout configuration
Kind regards,
Just I wanted to add if I remove jasper-pro.war folder the JDBC driver deploy properly or any other application in the moment jasper-pro.war is in the deployment folder none of the applications are deployed.
I didn't use the jasper-pro.war, but I did install jasperserver 5.5 on a clean JBoss 7 server without a hitch when following the installation instructions.
So my suggestion is to upgrade the jasperserver and I think it will run smoothly after that.