Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-9057

bin/client command does not work if a DefaultJDBCLock thread is hang

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jboss-fuse-6.3
    • Fix Version/s: fuse-6.x-GA
    • Component/s: Karaf
    • Labels:
      None
    • Steps to Reproduce:
      Hide
      • Set a breakpoint at org.apache.karaf.main.DefaultJDBCLock.aquireLock()
      • Start Fuse which has a "JDBC Lock System" setting
      • When the DefaultJDBCLock thread is paused by the debugger, run bin/client command
        -> client command works with R5 or R6. But not work with R7
      Show
      Set a breakpoint at org.apache.karaf.main.DefaultJDBCLock.aquireLock() Start Fuse which has a " JDBC Lock System " setting When the DefaultJDBCLock thread is paused by the debugger, run bin/client command -> client command works with R5 or R6. But not work with R7

      Description

      If a first sql query executed in org.apache.karaf.main.Main.doLock() is hang, bin/client command does not work.
      With 6.3 R5 and R6, bin/client command works even the thread is hang.

      Fix for ENTESB-7349(KARAF-3514) would be related for this issue.
      Although it's a jdbc driver's bug, there is a situation that "karaf.lock.jdbc.timeout" does not work in some environment.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  grgrzybek Grzegorz Grzybek
                  Reporter:
                  hisao.furuichi Hisao Furuichi
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: