ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aosmakoff <alex.osmak...@macquarie.com>
Subject RE: Ignite as L2 cache in JBoss6
Date Sun, 21 Jun 2015 23:46:42 GMT
Hi Yakov, That was  quick ☺
Thanks we will check it out.

From: yakov [via Apache Ignite Users] [mailto:ml-node+s70518n546h62@n6.nabble.com]
Sent: Saturday, 20 June 2015 4:37 AM
To: Alex Osmakoff
Subject: Re: Ignite as L2 cache in JBoss6

Alex, I have fixed this. You will be able to download the build on Mon-Tue. Thanks for the


2015-06-19 11:07 GMT+03:00 Yakov Zhdanov <[hidden email]</user/SendEmail.jtp?type=node&node=546&i=0>>:
Alex, I have filed the ticket - https://issues.apache.org/jira/browse/IGNITE-1035

Anyone from community picks it up?


2015-06-19 10:18 GMT+03:00 aosmakoff <[hidden email]</user/SendEmail.jtp?type=node&node=546&i=1>>:
Hi there.
We are trying to use Ignite/GridGain as L2 cache for our hibernate
application(s) running in JBoss 6.x that configured with JTA transaction
manager. The program fails to update the cache with a Timeout error.
We narrowed it down to the code in GridCacheJtaManager::checkJta() line

if (!jtaTx.enlistResource(rsrc))

where the Tx updates the resource parameters including the timeout. The
problems seems to be that JTA treats the timeout value in seconds than
Ignite/GridGain uses mSec, effectively reducing the specified (in the
container) value by 1000 times. (In Ignite the class is CacheJtaManager)

Please see the error below (we used the default JTA timeout = 300sec)

/class org.gridgain.grid.cache.GridCacheTxTimeoutException: Cache
transaction timed out: GridLocalTx [fut=null, super=GridCacheTxLocalAdapter
[completedBase=null, partLock=false, sndTransformedVals=false,
super=GridCacheTxAdapter [xidVer=GridCacheVersion [topVer=46169865,
nodeOrderDrId=1, globalTime=1434692163247, order=1434689857213],
writeVer=null, implicit=false, implicitSingle=false, loc=true, threadId=362,
startTime=1434692163238, nodeId=38301945-ced9-4707-abfe-1ad1de827423,
startVer=GridCacheVersion [topVer=46169865, nodeOrderDrId=1,
globalTime=1434692163247, order=1434689857213], endVer=null,
isolation=READ_COMMITTED, concurrency=PESSIMISTIC,* timeout=300*,
sysInvalidate=false, commitVer=null, finalizing=NONE, preparing=false,
state=MARKED_ROLLBACK, timedOut=true, topVer=-1, duration=564ms,
grpLock=false, onePhaseCommit=false], size=3]]

Is this a know issue and is there any workaround.

Many thanks,



View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-as-L2-cache-in-JBoss6-tp538.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

If you reply to this email, your message will be added to the discussion below:
To unsubscribe from Ignite as L2 cache in JBoss6, click here<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=538&code=YWxleC5vc21ha29mZkBtYWNxdWFyaWUuY29tfDUzOHwtODQ0MDAyMjc=>.

This email, including any attachments, is confidential. If you are not the intended recipient,
you must not disclose, distribute or use the information in this email in any way. If you
received this email in error, please notify the sender immediately by return email and delete
the message. Unless expressly stated otherwise, the information in this email should not be
regarded as an offer to sell or as a solicitation of an offer to buy any financial product
or service, an official confirmation of any transaction, or as an official statement of the
entity sending this message. Neither Macquarie Group Limited, nor any of its subsidiaries,
guarantee the integrity of any emails or attached files and are not responsible for any changes
made to them by any other person.

View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-as-L2-cache-in-JBoss6-tp538p548.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
View raw message