[
http://jira.jboss.com/jira/browse/JBAS-3513?page=comments#action_12341297 ]
Chris Nappin commented on JBAS-3513:
------------------------------------
Also raised as Customer Support Case 00010807. We would like to see the behaviour of
presious versions of JBoss reinstated, which is that it only warns the user.
adding <distributable> to webapp's web.xml causes ERROR on
startup in default server profile
--------------------------------------------------------------------------------------------
Key: JBAS-3513
URL:
http://jira.jboss.com/jira/browse/JBAS-3513
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.0.4.GA
Environment: Suse Linux Enterprise Desktop 10 on IBM Thinkpad T40p with JDK 1.5
Reporter: Hany Mesha
Assigned To: Brian Stansberry
Priority: Minor
To reproduce, add <distributable> to a webapp's web.xml and deploy to a default
server profile. You'll see the following exception thrown on the server console:
11:50:38,181 ERROR [JBossCacheManager] JBossCacheService to Tomcat clustering not found
java.lang.NoClassDefFoundError: org/jboss/cache/CacheException
[stacktrace]....
followed by ..
11:50:38,215 ERROR [TomcatDeployer] Failed to setup clustering, clustering disabled.
Exception:
org.jboss.web.tomcat.tc5.session.ClusteringNotSupportedException: JBossCacheService to
Tomcat clustering not found
[stacktrace]...
While the exception is true and the cluster is disabled at the end. It should only warn
the user and not throw the exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira