Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-170

Server VM crashes in org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs() with type2 driver with DB2-7.2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.RC6
    • None
    • System
    • None
    • DB2 7.2
      Type2 driver (db2java.zip)

      18:18:47,837 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
      #

      1. An unexpected error has been detected by HotSpot Virtual Machine:
        #
      2. SIGSEGV (0xb) at pc=0x88261325, pid=6619, tid=2355481520
        #
      3. Java VM: Java HotSpot(TM) Server VM (1.5.0_11-b03 mixed mode)
      4. Problematic frame:
      5. C [libdb2jdbc.so+0x6325] allocateSpace+0x55
        #
      6. An error report file with more information is saved as hs_err_pid6619.log
        #
      7. If you would like to submit a bug report, please visit:
      8. http://java.sun.com/webapps/bugreport/crash.jsp
        #
        ./run.sh: line 246: 6619 Aborted "$JAVA" $JAVA_OPTS -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" -classpath "$JBOSS_CLASSPATH" org.jboss.Main "$@"

      End of Server log:
      2007-05-09 18:18:48,597 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Starting jboss.mq:service=PersistenceManager
      2007-05-09 18:18:48,599 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Creating Schema
      2007-05-09 18:18:48,778 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Resolving uncommited TXS

            rrajasek@redhat.com Rajesh Rajasekaran
            rrajasek@redhat.com Rajesh Rajasekaran
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: