I'm having a similar problem, but on linux (gentoo kernel 2.6.15). The Jboss install seems to have been fine. It starts up and runs without any errors. However after the 5 step compile and install of Lams2, without any error messages, Jboss starts, but with errors. Adding /lams onto the Jboss URL just generates a 404 error.
The errors during startup of Jboss after installing Lams are:
----------------
12:29:26,743 ERROR [MainDeployer] could not create deployment: file:/usr/share/jboss-4.0.2/server/default/deploy/local-service.xml
org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.cache.TreeCache; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.cache.TreeCache)
...
12:29:55,870 ERROR [ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'coreSessionFactory' defined in class path resource [org/lamsfoundation/lams/commonContext.xml]: Initialization of bean failed; nested exception is org.hibernate.cache.CacheException: Unable to locate TreeCache MBean under object name [jboss.cache:service=TreeCache]
org.hibernate.cache.CacheException: Unable to locate TreeCache MBean under object name [jboss.cache:service=TreeCache]
...
12:29:55,927 ERROR [[/lams/admin]] Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'coreSessionFactory' defined in class path resource [org/lamsfoundation/lams/commonContext.xml]: Initialization of bean failed; nested exception is org.hibernate.cache.CacheException: Unable to locate TreeCache MBean under object name [jboss.cache:service=TreeCache]
org.hibernate.cache.CacheException: Unable to locate TreeCache MBean under object name [jboss.cache:service=TreeCache]
...
12:29:56,016 ERROR [StandardContext] Error listenerStart
12:29:56,017 ERROR [StandardContext] Context [/lams/admin] startup failed due to previous errors
12:29:56,024 INFO [[/lams/admin]] Closing Spring root WebApplicationContext
12:29:56,032 ERROR [WebModule] Starting failed jboss.web.deployment:war=lams-admin.war,id=-2053588469
org.jboss.deployment.DeploymentException: URL file:/usr/share/jboss-4.0.2/server/default/tmp/deploy/tmp49202lams-admin.war/ deployment failed
....
12:29:56,073 ERROR [MainDeployer] could not start deployment: file:/usr/share/jboss-4.0.2/server/default/deploy/lams.ear/lams-admin.war
....
12:29:56,092 ERROR [MainDeployer] could not start deployment: file:/usr/share/jboss-4.0.2/server/default/deploy/lams.ear/
org.jboss.deployment.DeploymentException: URL file:/usr/share/jboss-4.0.2/server/default/tmp/deploy/tmp49202lams-admin.war/ deployment failed
12:29:56,113 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
...
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@4c758a4 { url=file:/usr/share/jboss-4.0.2/server/default/deploy/local-service.xml }
deployer: org.jboss.deployment.SARDeployer@16921fd
status: Deployment FAILED reason: No ClassLoaders found for: org.jboss.cache.TreeCache; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.cache.TreeCache)
state: FAILED
watch: file:/usr/share/jboss-4.0.2/server/default/deploy/local-service.xml
altDD: null
lastDeployed: 1158942566729
lastModified: 1158942566000
mbeans:
....
org.jboss.deployment.DeploymentInfo@acdb8b74 { url=file:/usr/share/jboss-4.0.2/server/default/deploy/lams.ear/ }
deployer: org.jboss.deployment.EARDeployer@19c7c21
status: Deployment FAILED reason: URL file:/usr/share/jboss-4.0.2/server/default/tmp/deploy/tmp49202lams-admin.war/ deployment failed
state: FAILED
watch: file:/usr/share/jboss-4.0.2/server/default/deploy/lams.ear/META-INF/application.xml
altDD: null
lastDeployed: 1158942586043
lastModified: 1158941018000
mbeans:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.web.deployment:war=lams-admin.war,id=-2053588469
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/usr/share/jboss-4.0.2/server/default/tmp/deploy/tmp49202lams-admin.war/ deployment failed
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.web.deployment:war=lams-admin.war,id=-2053588469
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/usr/share/jboss-4.0.2/server/default/tmp/deploy/tmp49202lams-admin.war/ deployment failed
------------------------------------
Starting Jboss using "run.sh -c all" produces no errors, but trying to start Lams still generates a 404
I'm on my third install from scratch, having tried multiple versions of Jboss, including the web install of 4.0.4g1, ending back with 4.0.2. lams.ear/ appears to have been created properly in jboss-4.0.2/server/default/deploy and lamsconf appears to be in order. The lams.xml seems correct, but can't say for sure. All the files jboss complains about when starting do exist where they should be in default/deploy/default/lams.ear. lams.xml looks like this:
-------------------
<Lams>
<ServerURL>http://localhost:8080/lams/</ServerURL>
<LamsHome>/var/opt/lams</LamsHome>
<TempDir>/var/opt/lams/temp</TempDir>
<DumpDir>/var/opt/lams/dump</DumpDir>
<EARDir>/usr/share/jboss-4.0.2/server/default/deploy/lams.ear</EARDir>
<SMTPServer>mail.utoronto.ca</SMTPServer>
<LamsSupportEmail>lams_support@melcoe.mq.edu.au</LamsSupportEmail>
<ContentRepositoryPath>/var/opt/lams/repository</ContentRepositoryPath>
<UploadFileMaxSize>1048576</UploadFileMaxSize>
<UploadLargeFileMaxSize>10485760</UploadLargeFileMaxSize>
<UploadFileMaxMemorySize>4096</UploadFileMaxMemorySize>
<ChatServerName></ChatServerName>
<ChatPortNumber>9800</ChatPortNumber>
<FileManagerDir>/usr/share/jboss-4.0.2/server/default/deploy/upload.war</FileManagerDir>
<ExecutableExtensions>.bat,.bin,.com,.cmd,.exe,.msi,.msp,.ocx,.pif,.scr,.sct,.sh,.shs,.vbs</ExecutableExtensions>
<TicketFile>/usr/share/jboss-4.0.2/server/default/conf/lams.tck</TicketFile>
<!-- UserInactiveTimeout in seconds. 86400 seconds is one day-->
<UserInactiveTimeout>86400</UserInactiveTimeout>
<!-- If a user is allowed to login with different clients at the same time-->
<!-- It should be always false except when running testHarness-->
<AllowMultipleLogin>false</AllowMultipleLogin>
<!-- Turn on the cache debugging listener. Set to false in production -->
<UseCacheDebugListener>false</UseCacheDebugListener>
<!-- Number of days after which preview session data may be deleted. Recommend 7 days -->
<CleanupPreviewOlderThanDays>7</CleanupPreviewOlderThanDays>
<!-- client updates -->
<AuthoringClientVersion>1.0.200609221204</AuthoringClientVersion>
<MonitorClientVersion>1.0.200609221204</MonitorClientVersion>
<LearnerClientVersion>1.0.200609221204</LearnerClientVersion>
<ServerVersionNumber>1.1</ServerVersionNumber>
<ServerLanguage>en_AU</ServerLanguage>
<DictionaryDates>
<Dictionary>
<language>en_AU</language>
<createDate>2006-01-02</createDate>
</Dictionary>
</DictionaryDates>
<XmppDomain>shaun.melcoe.mq.edu.au</XmppDomain>
<XmppConference>conference.shaun.melcoe.mq.edu.au</XmppConference>
<XmppAdmin>admin</XmppAdmin>
<XmppPassword>wildfire</XmppPassword>
</Lams>
-------------------------------
My Java Evironment looks like this
ANT_HOME=/usr/share/ant-core
CLASSPATH=.:/usr/share/servletapi-2.3/lib
JAVAC=/opt/jdk1.5.0_08/bin/javac
JAVA_HOME=/opt/jdk1.5.0_08
JBOSS_HOME=/usr/share/jboss-4.0.2
JDK_HOME=/opt/jdk1.5.0_08
I'm hoping the problem is something simple. Can anyone help?
greg
Posted by Greg Gay
