No errors in console but can't access app?
Hi,
I'm using 7.0.2 in standalone mode and it seems like now everything is booting up correctly (see below info....), the one catch is that when I attempt to access my app at http://localhost/plu/ or localhost:8080/plu/ or https//localhost/plu/, the app does not display. No error is generated either. I just get the below page in firefox...
That page is not the standard 404 page I get if I enter a url for an app that doesn't exist. The first page doesn't access the db, as I mentioned earlier what makes it strange is that I don't get any error in the console except the browser page.
In my standalone.xml I have the following ports...
<socket-binding-group name="standard-sockets" default-interface="public">
<socket-binding name="http" port="8080"/>
<socket-binding name="https" port="8443"/>
<socket-binding name="jmx-connector-registry" port="1090" interface="management"/>
<socket-binding name="jmx-connector-server" port="1091" interface="management"/>
<socket-binding name="jndi" port="1099"/>
<socket-binding name="osgi-http" port="8090" interface="management"/>
<socket-binding name="remoting" port="4447"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
</socket-binding-group>
In my C:\jboss7\standalone\deployments folder, all the dodeploys are now marked as .deployed. It looks like everything is good to go, I must be missing something?
Here is what happens on bootup.....
13:12:48,722 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "ojdbc6.jar"
13:12:48,945 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api dependency to ojdbc6.jar
13:12:49,005 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
13:12:49,014 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) Bound data source [java:/PluDS]
13:12:49,047 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "ojdbc6.jar"
13:12:49,048 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) Service status report
Newly corrected services:
service jboss.jdbc-driver.ojdbc6_jar (now available)
13:12:59,097 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "mysql-connector-java-5.1.18-bin.jar"
13:12:59,160 INFO [org.jboss.as.jpa] (MSC service thread 1-5) added javax.persistence.api dependency to mysql-connector-java-5.1.18-bin.jar
13:12:59,168 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
13:12:59,171 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) Bound data source [java:/jdbc/ScormEngineDB]
13:12:59,200 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "mysql-connector-java-5.1.18-bin.jar"
13:12:59,200 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) Service status report
Newly corrected services:
service jboss.jdbc-driver.mysql-connector-java-5_1_18-bin_jar (now available)
13:13:09,269 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "ScormEngineInterface.war"
13:13:10,837 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry iText-toolbox.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,837 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry iText-toolbox-2.1.3.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,837 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry bcmail-jdk14-138.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,838 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry bcprov-jdk14-138.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,839 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry iText.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,839 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry iText-2.1.3.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,839 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry dom4j-1.6.1.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,839 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry bcmail-jdk14-138.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,839 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry bcprov-jdk14-138.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,839 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry pdf-renderer.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,840 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xml-apis.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/serializer.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,840 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-beanutils.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/struts.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,840 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-collections.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/struts.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,841 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-digester.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/struts.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,841 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-logging.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/struts.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,841 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-validator.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/struts.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,842 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jakarta-oro.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/struts.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,842 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry struts-legacy.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/struts.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,842 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xercesImpl.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,842 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xml-apis.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,842 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry serializer.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
13:13:10,843 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry relaxngDatatype.jar in "/C:/jboss7/standalone/deployments/ScormEngineInterface.war/WEB-INF/lib/xsdlib.jar" does not point to a valid jar for a Class-Path reference.
13:13:11,020 INFO [org.jboss.as.jpa] (MSC service thread 1-2) added javax.persistence.api dependency to ScormEngineInterface.war
13:13:12,152 INFO [org.jboss.web] (MSC service thread 1-7) registering web context: /ScormEngineInterface
13:13:12,164 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployed "ScormEngineInterface.war"
13:13:31,461 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "plu.war"
13:13:34,313 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry gdata-client-1.0.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/gdata-blogger-2.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,314 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry gdata-media-1.0.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/gdata-blogger-2.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,314 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry gdata-blogger-meta-2.0.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/gdata-blogger-2.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,315 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry gdata-core-1.0.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/gdata-client-1.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,315 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry gdata-client-meta-1.0.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/gdata-client-1.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,315 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry gdata-client-1.0.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/gdata-media-1.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,315 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry iText-toolbox.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,315 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry iText-toolbox-2.1.3.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,315 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry bcmail-jdk14-138.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,315 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry bcprov-jdk14-138.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry iText.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry iText-2.1.3.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry dom4j-1.6.1.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry bcmail-jdk14-138.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry bcprov-jdk14-138.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry pdf-renderer.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/iText-rups-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb-api.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxb-impl-2.1.7.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry activation.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxb-impl-2.1.7.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,316 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jsr173_1.0_api.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxb-impl-2.1.7.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb1-impl.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxb-impl-2.1.7.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb-api.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxb-xjc-2.1.7.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb-impl.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxb-xjc-2.1.7.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jsr173_1.0_api.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxb-xjc-2.1.7.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry activation.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxb-xjc-2.1.7.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxws-rt.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxws-tools-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb-xjc.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxws-tools-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry relaxngDatatype.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jaxws-tools-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry bcel.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jibx-bind-1.2.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jibx-run.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jibx-bind-1.2.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xpp3.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jibx-bind-1.2.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry stax-api.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jibx-bind-1.2.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry wstx-asl.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jibx-bind-1.2.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xpp3.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jibx-run-1.2.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry stax-api.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jibx-run-1.2.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry wstx-asl.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/jibx-run-1.2.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry activation.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/mail-1.4.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxen-1.1.1.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/pmd-4.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry asm-3.1.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/pmd-4.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xercesImpl.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/xalan-2.7.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xml-apis.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/xalan-2.7.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry serializer.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/xalan-2.7.0.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,320 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xercesImpl.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,320 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xml-apis.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,320 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry relaxngDatatype.jar in "/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/xsdlib.jar" does not point to a valid jar for a Class-Path reference.
13:13:34,405 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api dependency to plu.war
13:13:34,939 INFO [stdout] (MSC service thread 1-6) log4j: Parsing for [root] with value=[INFO, stdout, importLogger, errorLogger, messageLogger, dbLogger].
13:13:34,939 INFO [stdout] (MSC service thread 1-6) log4j: Level token is [INFO].
13:13:34,939 INFO [stdout] (MSC service thread 1-6) log4j: Category root set to INFO
13:13:34,939 INFO [stdout] (MSC service thread 1-6) log4j: Parsing appender named "stdout".
13:13:34,946 INFO [stdout] (MSC service thread 1-6) log4j: Parsing layout options for "stdout".
13:13:34,952 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [conversionPattern] to [%d{ISO8601} %5p %c{1}: %m%n].
13:13:34,953 INFO [stdout] (MSC service thread 1-6) log4j: End of parsing for "stdout".
13:13:34,954 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [target] to [System.out].
13:13:34,955 INFO [stdout] (MSC service thread 1-6) log4j: Parsed "stdout" options.
13:13:34,955 INFO [stdout] (MSC service thread 1-6) log4j: Parsing appender named "importLogger".
13:13:34,955 ERROR [stderr] (MSC service thread 1-6) log4j:ERROR Could not find value for key log4j.appender.importLogger
13:13:34,956 ERROR [stderr] (MSC service thread 1-6) log4j:ERROR Could not instantiate appender named "importLogger".
13:13:34,956 INFO [stdout] (MSC service thread 1-6) log4j: Parsing appender named "errorLogger".
13:13:34,956 ERROR [stderr] (MSC service thread 1-6) log4j:ERROR Could not find value for key log4j.appender.errorLogger
13:13:34,956 ERROR [stderr] (MSC service thread 1-6) log4j:ERROR Could not instantiate appender named "errorLogger".
13:13:34,956 INFO [stdout] (MSC service thread 1-6) log4j: Parsing appender named "messageLogger".
13:13:34,956 ERROR [stderr] (MSC service thread 1-6) log4j:ERROR Could not find value for key log4j.appender.messageLogger
13:13:34,956 ERROR [stderr] (MSC service thread 1-6) log4j:ERROR Could not instantiate appender named "messageLogger".
13:13:34,956 INFO [stdout] (MSC service thread 1-6) log4j: Parsing appender named "dbLogger".
13:13:34,956 ERROR [stderr] (MSC service thread 1-6) log4j:ERROR Could not find value for key log4j.appender.dbLogger
13:13:34,957 ERROR [stderr] (MSC service thread 1-6) log4j:ERROR Could not instantiate appender named "dbLogger".
13:13:34,957 INFO [stdout] (MSC service thread 1-6) log4j: Parsing for [importLogger] with value=[INFO, import_logger].
13:13:34,957 INFO [stdout] (MSC service thread 1-6) log4j: Level token is [INFO].
13:13:34,957 INFO [stdout] (MSC service thread 1-6) log4j: Category importLogger set to INFO
13:13:34,957 INFO [stdout] (MSC service thread 1-6) log4j: Parsing appender named "import_logger".
13:13:34,959 INFO [stdout] (MSC service thread 1-6) log4j: Parsing layout options for "import_logger".
13:13:34,959 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [conversionPattern] to [%d{ISO8601} [%t] %-5p %x: %m%n].
13:13:34,959 INFO [stdout] (MSC service thread 1-6) log4j: End of parsing for "import_logger".
13:13:34,960 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [file] to [C:\jboss7\standalone\log/plu-import.log].
13:13:34,961 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [append] to [true].
13:13:34,961 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [datePattern] to ['.'yyyyMMdd].
13:13:34,961 INFO [stdout] (MSC service thread 1-6) log4j: setFile called: C:\jboss7\standalone\log/plu-import.log, true
13:13:34,961 INFO [stdout] (MSC service thread 1-6) log4j: setFile ended
13:13:34,962 INFO [stdout] (MSC service thread 1-6) log4j: Appender [import_logger] to be rolled at midnight.
13:13:34,962 INFO [stdout] (MSC service thread 1-6) log4j: Parsed "import_logger" options.
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Handling log4j.additivity.importLogger=[null]
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Parsing for [messageLogger] with value=[INFO].
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Level token is [INFO].
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Category messageLogger set to INFO
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Handling log4j.additivity.messageLogger=[null]
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Parsing for [dbLogger] with value=[DEBUG].
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Level token is [DEBUG].
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Category dbLogger set to DEBUG
13:13:34,963 INFO [stdout] (MSC service thread 1-6) log4j: Handling log4j.additivity.dbLogger=[null]
13:13:34,964 INFO [stdout] (MSC service thread 1-6) log4j: Parsing for [noTrainingCleanerLog] with value=[INFO, no_training_logger].
13:13:34,964 INFO [stdout] (MSC service thread 1-6) log4j: Level token is [INFO].
13:13:34,964 INFO [stdout] (MSC service thread 1-6) log4j: Category noTrainingCleanerLog set to INFO
13:13:34,964 INFO [stdout] (MSC service thread 1-6) log4j: Parsing appender named "no_training_logger".
13:13:34,964 INFO [stdout] (MSC service thread 1-6) log4j: Parsing layout options for "no_training_logger".
13:13:34,964 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [conversionPattern] to [%d{ISO8601} [%t] %-5p %x: %m%n].
13:13:34,964 INFO [stdout] (MSC service thread 1-6) log4j: End of parsing for "no_training_logger".
13:13:34,965 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [append] to [true].
13:13:34,965 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [file] to [C:\jboss7\standalone\log/plu-notraining.log].
13:13:34,965 INFO [stdout] (MSC service thread 1-6) log4j: Setting property [datePattern] to ['.'yyyyMMdd].
13:13:34,965 INFO [stdout] (MSC service thread 1-6) log4j: setFile called: C:\jboss7\standalone\log/plu-notraining.log, true
13:13:34,965 INFO [stdout] (MSC service thread 1-6) log4j: setFile ended
13:13:34,966 INFO [stdout] (MSC service thread 1-6) log4j: Appender [no_training_logger] to be rolled at midnight.
13:13:34,966 INFO [stdout] (MSC service thread 1-6) log4j: Parsed "no_training_logger" options.
13:13:34,966 INFO [stdout] (MSC service thread 1-6) log4j: Handling log4j.additivity.noTrainingCleanerLog=[null]
13:13:34,966 INFO [stdout] (MSC service thread 1-6) log4j: Finished configuring.
13:13:34,967 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:34,967 INFO ResponseOverrideFilter: Filter initialized. Response buffering is enabled
13:13:34,988 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:34,988 INFO SimpleThreadPool: Job execution threads will use class loader of thread: MSC service thread 1-6
13:13:34,999 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:34,999 INFO QuartzScheduler: Quartz Scheduler v.1.6.0 created.
13:13:35,000 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,000 INFO RAMJobStore: RAMJobStore initialized.
13:13:35,000 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,000 INFO StdSchedulerFactory: Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
13:13:35,000 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,000 INFO StdSchedulerFactory: Quartz scheduler version: 1.6.0
13:13:35,007 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,007 INFO QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:13:35,009 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,009 INFO QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:13:35,011 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,011 INFO QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:13:35,012 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,012 INFO QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:13:35,014 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,014 INFO QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:13:35,016 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,016 INFO QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:13:35,018 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,018 INFO QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:13:35,020 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,020 INFO QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:13:35,021 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/plu]] (MSC service thread 1-6) No Configuration for this context. Initializing.
13:13:35,021 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/plu]] (MSC service thread 1-6) configuring cewolf app..
13:13:35,022 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/plu]] (MSC service thread 1-6) using storage class de.laures.cewolf.storage.TransientSessionStorage
13:13:35,022 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/plu]] (MSC service thread 1-6) using overlibURL overlib.js
13:13:35,022 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/plu]] (MSC service thread 1-6) debugging is turned off
13:13:35,023 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/plu]] (MSC service thread 1-6) ...done.
13:13:35,148 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,148 INFO ActionServlet: Loading chain catalog from vfs:/C:/jboss7/standalone/deployments/plu.war/WEB-INF/lib/struts-core-1.3.10.jar/org/apache/struts/chain/chain-config.xml
13:13:35,339 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,339 WARN ModuleConfigImpl: Overriding ActionConfig of path /adminAction
13:13:35,449 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,449 INFO TilesPlugin: Tiles definition factory loaded for module ''.
13:13:35,451 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,451 INFO ValidatorPlugIn: Loading validation rules file from '/WEB-INF/validator-rules.xml'
13:13:35,452 INFO [stdout] (MSC service thread 1-6) 2011-12-30 13:13:35,452 INFO ValidatorPlugIn: Loading validation rules file from '/WEB-INF/validation.xml'
13:13:35,518 INFO [org.jboss.web] (MSC service thread 1-6) registering web context: /plu
13:13:35,533 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployed "plu.war"
This app is functional on jboss 4.2, trying to move to 7. http://localhost:8080/ takes me to the jboss admin page correctly which states "
Your JBoss Application Server 7 is running."
The only change I've made to my app code is in the jboss-web.xml I temporarly commented out the following line...
<security-domain>java:/jaas/jmx-console</security-domain>
Because that was creating an error. Any ideas on how I can access my app? Thanks.