Unable to access KIE-WB after successful deployment
shiv.narayan Nov 23, 2015 7:45 AMI am using Red Hat JBoss EAP 6.2.4.GA. Succesfully deployed 'kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war' file.
Verified the log,which says Succesfully deployed.
03:55:32,546 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war" (runtime-name: "kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war") 03:55:42,172 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jaxb-api.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jaxb-impl-2.2.5.jar does not point to a valid jar for a Class-Path reference. 03:55:42,172 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry activation.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jaxb-impl-2.2.5.jar does not point to a valid jar for a Class-Path reference. 03:55:42,172 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jsr173_1.0_api.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jaxb-impl-2.2.5.jar does not point to a valid jar for a Class-Path reference. 03:55:42,172 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jaxb1-impl.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jaxb-impl-2.2.5.jar does not point to a valid jar for a Class-Path reference. 03:55:42,173 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xml-apis-1.0.b2.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jbpmmigration-0.12.jar does not point to a valid jar for a Class-Path reference. 03:55:42,173 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry log4j-1.2.16.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jbpmmigration-0.12.jar does not point to a valid jar for a Class-Path reference. 03:55:42,234 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jaxb-api.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar does not point to a valid jar for a Class-Path reference. 03:55:42,234 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jaxb-impl.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar does not point to a valid jar for a Class-Path reference. 03:55:42,234 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jsr173_1.0_api.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar does not point to a valid jar for a Class-Path reference. 03:55:42,234 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry activation.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar does not point to a valid jar for a Class-Path reference. 03:55:42,252 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xml-apis.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference. 03:55:42,257 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xercesImpl.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 03:55:42,257 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xml-apis.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 03:55:42,257 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry serializer.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference. 03:55:42,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry avalon-framework-4.2.0.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry batik-all-1.7.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commons-io-1.3.1.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry commons-logging-1.0.4.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry serializer-2.7.0.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry servlet-2.2.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xalan-2.7.0.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xercesImpl-2.7.1.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xml-apis-1.3.04.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xml-apis-ext-1.3.04.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xmlgraphics-commons-1.3.1.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry fop-hyph.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jai_codec.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jai_core.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jai_imageio.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry jimi-1.0.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,272 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry xmlunit1.0.jar in /content/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 03:55:42,535 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory' 03:55:43,473 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war" is using a private module ("org.jboss.netty:main") which may be changed or removed in future versions without notice. 03:55:43,473 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war" is using a private module ("org.jboss.netty:main") which may be changed or removed in future versions without notice. 03:55:43,473 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice. 03:55:43,473 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice. 03:55:43,923 INFO [org.jboss.web] (ServerService Thread Pool -- 374) JBAS018210: Register web context: /kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0 03:55:43,946 INFO [solder-servlet] (ServerService Thread Pool -- 374) CDI BeanManager cannot be found. Not sending event org.jboss.solder.servlet.event.ImplicitServletObjectsHolder$InternalServletContextEvent@73f91ad5 with qualifiers [@org.jboss.solder.servlet.event.Initialized()] 03:55:43,946 INFO [solder-servlet] (ServerService Thread Pool -- 374) CDI BeanManager cannot be found. Not sending event org.jboss.solder.servlet.WebApplication@76d15d67 with qualifiers [@org.jboss.solder.servlet.event.Initialized()] 03:55:43,946 INFO [solder-servlet] (ServerService Thread Pool -- 374) CDI BeanManager cannot be found. Not sending event org.apache.catalina.core.ApplicationContextFacade@242b1b12 with qualifiers [@org.jboss.solder.servlet.event.Initialized()] 03:55:43,947 INFO [solder-servlet] (ServerService Thread Pool -- 374) Could not locate CDI BeanManager. Catch Integration for Servlets disabled 03:55:44,122 INFO [org.jboss.errai.common.metadata.MetaDataScanner] (Thread-732) added class scanning extensions: org.jboss.errai.common.metadata.JbossVFsTypeHandler 03:55:47,806 INFO [org.jboss.errai.reflections.Reflections] (Thread-732) Reflections took 3681 ms to scan 83 urls, producing 2581 keys and 16047 values [using 2 cores] 03:55:47,931 INFO [org.jboss.errai.bus.server.cluster.noop.NoopClusteringProvider] (ServerService Thread Pool -- 374) clustering support not configured. 03:55:47,935 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (ServerService Thread Pool -- 374) starting errai bus ... 03:55:47,935 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (ServerService Thread Pool -- 374) using dispatcher implementation: org.jboss.errai.bus.server.SimpleDispatcher 03:55:47,938 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (ServerService Thread Pool -- 374) using session provider implementation: org.jboss.errai.bus.server.HttpSessionProvider 03:55:47,946 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (ServerService Thread Pool -- 374) searching for errai extensions ... 03:55:47,980 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (ServerService Thread Pool -- 374) errai bus started. 03:55:48,022 INFO [solder-servlet] (ServerService Thread Pool -- 374) CDI BeanManager cannot be found. Not sending event org.jboss.solder.servlet.WebApplication@76d15d67 with qualifiers [@org.jboss.solder.servlet.event.Started()] 03:55:48,043 INFO [org.jboss.as.server] (HttpManagementService-threads - 54) JBAS018559: Deployed "kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war" (runtime-name : "kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0.war")
Trying to access application with URL http://<serverName>:18080/kie-drools-wb-distribution-wars-6.1.0.Final-jboss-as7.0, but it says 'The Webpage cannot be found'. Checked the log and does not find anything wrong there.
while accessing above mentioned URL, i can see EAP6 (logo) at the title bar, which prooves that my servername and port is correct. There must be something wrong with application name. I have not changed anything and trying to access default application name (i.e. name of deployed war).
entries in Standalone.xml is as follows
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.so cket.binding.port-offset:0}"> <socket-binding name="management-native" interface="management" port="${jboss.management.nat ive.port:9999}"/> <socket-binding name="management-http" interface="management" port="${jboss.management.http. port:9990}"/> <socket-binding name="management-https" interface="management" port="${jboss.management.http s.port:9443}"/> <socket-binding name="ajp" port="8009"/> <socket-binding name="http" port="8080"/> <socket-binding name="https" port="8443"/> <socket-binding name="remoting" port="4447"/> <socket-binding name="txn-recovery-environment" port="4712"/> <socket-binding name="txn-status-manager" port="4713"/> <outbound-socket-binding name="mail-smtp"> <remote-destination host="localhost" port="25"/> </outbound-socket-binding> </socket-binding-group> </server>
Message was edited by: Shiv Narayan