[JBoss JIRA] Created: (JBAS-3941) JBossCacheService fails in start if context path contains '/'
by Brian Stansberry (JIRA)
JBossCacheService fails in start if context path contains '/'
-------------------------------------------------------------
Key: JBAS-3941
URL: http://jira.jboss.com/jira/browse/JBAS-3941
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Web (Tomcat) service
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Minor
Fix For: JBossAS-4.2.0.CR1
If the session replication cache is configured to use region-based marshalling, and the context path of a webapp contains a intermediate slash (e.g. /a/b), the deployment of the webapp may fail in JBossCacheService.start. See the forum thread for details.
(Admittedly hacky) solution is for JBossCacheService to replace the slash in webAppPath_ with something like ';'.
--
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
19 years, 6 months
[JBoss JIRA] Created: (JBAS-3840) StackTrace appears on stderr when session.processSessionRepl() without tx
by Takayoshi Kimura (JIRA)
StackTrace appears on stderr when session.processSessionRepl() without tx
-------------------------------------------------------------------------
Key: JBAS-3840
URL: http://jira.jboss.com/jira/browse/JBAS-3840
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Reporter: Takayoshi Kimura
Priority: Minor
I'm using JBoss AS 4.0.5.GA and setting up Tomcat Cluster Service.
Under high load, org.jboss.cache.lock.TimeoutException occurred at session.processSessionRepl(). It's ok, but JBossCacheManager dumps stack trace into stderr if there is no tx.
1. The notSession is true and the doTx is false since i'm using SESSION granularity.
2. JBossCacheManager doesn't call tm.begin() but calls tm.setRollbackOnly() when TimeoutException occurred.
3. tm.setRollbackOnly() throws IllegalStateException since there is no tx.
4. JBossCacheManager dumps stack trace into stderr.
--
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
19 years, 6 months