1 Reply Latest reply on Sep 5, 2012 7:45 PM by Mircea Markus

    Error while trying to acquire write lock

    Túlio Gomes Barbosa Newbie

      Hi guys,

      i'm a brazilian oss analyst facing with the following problem:


      <Aug 28, 2012 10:15:22 AM BRT> <Notice> <Stdout> <BEA-000000> <AsyncClient: Response cannot be read!>

      <8-28-2012 10:15:22.261> <JVMDAgent|jamagent.c:1472> <Error receiving data from console>

      <Aug 28, 2012 10:15:32 AM BRT> <Notice> <Stdout> <BEA-000000> <<28-Aug-2012 10:15:32,483 BRT AM> <ERROR> <jboss.JBossOrderCacheManager> <ExecuteThread: '12'

      for queue: 'oms.automation'> <Caught exception adding value to cache fqn[/9976/root/0/Client_Details/1346158074198] value[null] nodeId[87386] nodeIndex[null]


      org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/9976/root/0/Client_Details/1346158074198, caller=GlobalTransaction:<null>:887, lock=write

      owner=GlobalTransaction:<null>:892 (org.jboss.cache.lock.LockStrategyReadCommitted@3fcbb918)


      Here's the situation:

      We're using an oracle application that manages service orders life cycle. So we have specifics flows based at telecom industry business rules that access all time the same fqn.

      In some flows we have integrations with others systems via webservices and jms queues who are responsible for allocating the equipment inventory. However, these integrations lasts 20 seconds on average.


      Looking at the jboss cache configuration we observed that some parameters are not following the recommended configuration by the jboss specialists (please look at attached file omscache-config.xml ).


      ps.: The parameter LockAcquisitionTimeout (30000 milliseconds) seems not to be sufficient.


      Anyone have some ideas for the problem related?


      ps2.: Sorry for the english