[jboss-jira] [JBoss JIRA] Commented: (JBAS-6466) Log as TRACE not being able to find cache entry trying to be removed
Galder Zamarreno (JIRA)
jira-events at lists.jboss.org
Thu Feb 5 04:28:44 EST 2009
[ https://jira.jboss.org/jira/browse/JBAS-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12451257#action_12451257 ]
Galder Zamarreno commented on JBAS-6466:
----------------------------------------
http://www.jboss.com/?module=bb&op=viewtopic&t=57173
> 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.Beta1, JBossAS-6.0.0.Alpha1
>
>
> 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
More information about the jboss-jira
mailing list