[
https://jira.jboss.org/jira/browse/JBAS-6466?page=com.atlassian.jira.plug...
]
Jason T. Greene updated JBAS-6466:
----------------------------------
Fix Version/s: JBossAS-5.1.0.CR1
(was: JBossAS-5.1.0.Beta1)
(was: JBossAS-6.0.0.Alpha1)
Rescheduling for CR1 for now. Please set it to the release you want to deliver this on.
Log as TRACE not being able to find cache entry trying to be removed
--------------------------------------------------------------------
Key: JBAS-6466
URL:
https://jira.jboss.org/jira/browse/JBAS-6466
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: CMP service
Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.GA
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Minor
Fix For: JBossAS-5.1.0.CR1
Make WARN messages like this TRACE:
2009-01-30 15:35:41,172 WARN [org.jboss.ejb.plugins.cmp.jdbc2.schema.EntityTable.XYZ]
removal of 40 rejected for TransactionImple < ac, BasicAction:
-3f57e8a7:507:49835914:7ce19 status: ActionStatus.COMMITTED >: the entry could not be
found
It's not an error at all. It's an expected situation for a shared cache accessed
concurrently w/o
transaction-long pessimistic locking, which is the point of this implementation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira