Bug 1039453 - TimeoutException, not ExceptionTimeout, in Important note of 18.1. About Java Transaction API Transactions
Summary: TimeoutException, not ExceptionTimeout, in Important note of 18.1. About Java...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Documentation
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 6.2.0
Assignee: gsheldon
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-09 06:32 UTC by Osamu Nagano
Modified: 2018-12-03 20:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build: CSProcessor Builder Version 1.12 Build Name: 11621, Administration and Configuration Guide-6-1 Build Date: 06-08-2013 09:16:07 Topic ID: 5270-368130 [Specified]
Last Closed: 2013-12-09 23:51:37 UTC
Type: Bug


Attachments (Terms of Use)

Description Osamu Nagano 2013-12-09 06:32:16 UTC
Title: About Java Transaction API Transactions

Describe the issue:
" Important
 With JBoss Data Grid 6.0.x, it is recommended to disable transactions in Remote Client-Server Mode. However, if an error displays warning of an ExceptionTimeout where JBoss Data Grid is Unable to acquire lock after {time} on key {key} for requester {thread}, enable transactions. This occurs because non-transactional caches acquire locks on each node they write on. Using transactions prevents deadlocks because caches acquire locks on a single node.
This problem is resolved in JBoss Data Grid 6.1. "

"ExceptionTimeout" is mentioned in the important note, but it is "TimeoutException" actually.


Additional information:
Actual error log looks like this.
~~~
00:15:37,619 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-145,null) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [30 seconds] on key [ByteArrayKey{data=ByteArray{size=21, hashCode=35884b34, array=0x033e1267656e3230..}}] for requestor [Thread[OOB-145,null,5,Thread Pools]]! Lock held by [(another thread)]	
	at org.infinispan.util.concurrent.locks.LockManagerImpl.lock(LockManagerImpl.java:216)
	at org.infinispan.util.concurrent.locks.LockManagerImpl.acquireLockNoCheck(LockManagerImpl.java:199)
	at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockKey(AbstractLockingInterceptor.java:114)
	at org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor.visitReplaceCommand(NonTransactionalLockingInterceptor.java:110)
	at org.infinispan.commands.write.ReplaceCommand.acceptVisitor(ReplaceCommand.java:66)
	at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
	at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:130)
	at org.infinispan.commands.AbstractVisitor.visitReplaceCommand(AbstractVisitor.java:72)
	...
~~~

Comment 2 Osamu Nagano 2013-12-09 06:49:22 UTC
A customer hit bug ISPN-2552 with JDG 6.0.1 and found a related documentation change done in Bug 886969.  They complained that they could find the bug sooner if the documentaion were correct.  They also requested to add an extra sentecce something like "... TimeoutException doesn't always happen, however, if an error displays warning of an ...".

Comment 3 gsheldon 2013-12-09 23:51:37 UTC
This issue has been resolved in documentation for JBoss Data Grid 6.2, and ISPN-2552 is now resolved.

Closing this issue as Current Release.

Comment 4 Osamu Nagano 2013-12-10 06:50:18 UTC
Is it possible to fix the typo in 6 and 6.1 docs?

Comment 5 gsheldon 2013-12-10 23:25:27 UTC
Thank you for bringing it to our attention.

We will include the fix in any future updates to the 6 and 6.1 documentation. 

As a rule, we do not republish old books to correct a typo. If any other fixes are required however, we will include this correction.


Note You need to log in before you can comment on or make changes to this bug.