Server Crash from Db2 XA Connection Pool
We are running WLS 6.1 sp2 on Redhat Linux 7.2
and using a XA Connection pool with Type 2 DB2 XA Driver.
<JDBCConnectionPool
Name="TXBusobj" Targets="jeeva_adminServer"
InitialCapacity="0" CapacityIncrement="2" MaxCapacity="15" RefreshMinutes="5"
DriverName="COM.ibm.db2.jdbc.DB2XADataSource" Password="db2" URL="jdbc:db2/TEST_REP"
Properties="user=db2as;password=db2;DatabaseName=TEST_REP"
TestConnectionsOnReserve="false"
TestTableName="SYSIBM.SYSDUMMY1"/>
The application works fine with out the above XA Connection pool.
After adding the connection pool the server randomly crashes with Signal 11 from
JVM.
We are using 1.3.1_04 and also tried with 1.3.1_11
Following is the stack trace:
# Problematic Thread: prio=1 tid=0xabb6768 nid=0xa05 runnable
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x0
Function name=(N/A)
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at java.util.zip.ZipFile.getEntry(ZipFile.java:141)
at java.util.jar.JarFile.getEntry(JarFile.java:176)
at java.util.jar.JarFile.getJarEntry(JarFile.java:163)
at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:546)
at sun.misc.URLClassPath.getResource(URLClassPath.java:133)
at java.net.URLClassLoader$2.run(URLClassLoader.java:344)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:341)
at java.lang.ClassLoader.getResource(ClassLoader.java:766)
at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:927)
at java.util.ResourceBundle$1.run(ResourceBundle.java:931)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.ResourceBundle.loadBundle(ResourceBundle.java:927)
at java.util.ResourceBundle.findBundle(ResourceBundle.java:786)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:616)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:570)
at weblogic.i18ntools.L10nLookup.getLocalizer(L10nLookup.java:299)
at weblogic.logging.LogManager.log(LogManager.java:230)
at weblogic.logging.MessageLogger.log(MessageLogger.java:17)
at weblogic.jdbc.JDBCLogger.logSleepingInCreateResourceInfo(JDBCLogger.java:1060)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:69)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:511)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:400)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:390)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:164)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:118)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1152)
at weblogic.jdbc.jta.DataSource.getXAResource(DataSource.java:679)
at weblogic.jdbc.jta.DataSource.recover(DataSource.java:887)
at weblogic.transaction.internal.ServerResourceInfo.recover(ServerResourceInfo.java:786)
at weblogic.transaction.internal.ServerSCInfo.recover(ServerSCInfo.java:283)
at weblogic.transaction.internal.ResourceDescriptor.getXidsToBeRolledBack(ResourceDescriptor.java:1112)
at weblogic.transaction.internal.ResourceDescriptor.recover(ResourceDescriptor.java:1046)
at weblogic.transaction.internal.ResourceDescriptor.access$9(ResourceDescriptor.java:1029)
at weblogic.transaction.internal.ResourceDescriptor$1.execute(ResourceDescriptor.java:770)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
08048000-0804c000 r-xp 00000000 03:02 464716 /usr/java/jdk1.3.1_04/bin/i386/native_threads/java
0804c000-0804d000 rw-p 00003000 03:02 464716 /usr/java/jdk1.3.1_04/bin/i386/native_threads/java
40000000-40015000 r-xp 00000000 03:03 496100 /lib/ld-2.2.4.so
40015000-40016000 rw-p 00014000 03:03 496100 /lib/ld-2.2.4.so
40017000-40018000 r--p 00000000 03:02 288014 /usr/lib/locale/en_US/LC_IDENTIFICATION
40018000-40019000 r--p 00000000 03:02 544149 /usr/lib/locale/en_US/LC_MEASUREMENT
40019000-4001a000 r--p 00000000 03:02 48241 /usr/lib/locale/en_US/LC_TELEPHONE
4001a000-4001b000 r--p 00000000 03:02 48430 /usr/lib/locale/en_US/LC_ADDRESS
4001b000-4001c000 r--p 00000000 03:02 48429 /usr/lib/locale/en_US/LC_NAME
4001c000-4001d000 r--p 00000000 03:02 112040 /usr/lib/locale/en_US/LC_PAPER
4001d000-4002c000 r-xp 00000000 03:03 496046 /lib/libpthread-0.9.so
4002c000-40034000 rw-p 0000e000 03:03 496046 /lib/libpthread-0.9.so
40034000-4003d000 r-xp 00000000 03:02 144730 /usr/java/jdk1.3.1_04/jre/lib/i386/native_threads/libhpi.so
4003d000-4003e000 rw-p 00008000 03:02 144730 /usr/java/jdk1.3.1_04/jre/lib/i386/native_threads/libhpi.so
4003e000-40243000 r-xp 00000000 03:02 272604 /usr/java/jdk1.3.1_04/jre/lib/i386/client/libjvm.so
40243000-40344000 rw-p 00204000 03:02 272604 /usr/java/jdk1.3.1_04/jre/lib/i386/client/libjvm.so
4035b000-4035d000 r-xp 00000000 03:03 496014 /lib/libdl-2.2.4.so
4035d000-4035f000 rw-p 00001000 03:03 496014 /lib/libdl-2.2.4.so
40360000-4048c000 r-xp 00000000 03:03 496010 /lib/libc-2.2.4.so
4048c000-40492000 rw-p 0012b000 03:03 496010 /lib/libc-2.2.4.so
40496000-404a9000 r-xp 00000000 03:03 496019 /lib/libnsl-2.2.4.so
404a9000-404ab000 rw-p 00012000 03:03 496019 /lib/libnsl-2.2.4.so
404ad000-404ce000 r-xp 00000000 03:03 496016 /lib/libm-2.2.4.so
404ce000-404cf000 rw-p 00020000 03:03 496016 /lib/libm-2.2.4.so
404cf000-40503000 r-xp 00000000 03:02 64413 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
40503000-4050f000 rw-p 00033000 03:02 64413 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
40512000-40523000 r-xp 00000000 03:02 512622 /usr/java/jdk1.3.1_04/jre/lib/i386/libverify.so
40523000-40525000 rw-p 00010000 03:02 512622 /usr/java/jdk1.3.1_04/jre/lib/i386/libverify.so
40525000-40546000 r-xp 00000000 03:02 512614 /usr/java/jdk1.3.1_04/jre/lib/i386/libjava.so
40546000-40548000 rw-p 00020000 03:02 512614 /usr/java/jdk1.3.1_04/jre/lib/i386/libjava.so
40549000-4055d000 r-xp 00000000 03:02 512623 /usr/java/jdk1.3.1_04/jre/lib/i386/libzip.so
4055d000-40560000 rw-p 00013000 03:02 512623 /usr/java/jdk1.3.1_04/jre/lib/i386/libzip.so
40560000-41296000 r--s 00000000 03:02 384740 /usr/java/jdk1.3.1_04/jre/lib/rt.jar
412c3000-415ba000 r--s 00000000 03:02 384738 /usr/java/jdk1.3.1_04/jre/lib/i18n.jar
415ba000-415d0000 r--s 00000000 03:02 384745 /usr/java/jdk1.3.1_04/jre/lib/sunrsasign.jar
415d0000-415f4000 r--s 00000000 03:09 33023 /weblogic/wlserver6.1/config/blue2/lib/pja.jar
415f4000-41606000 r--s 00000000 03:02 160797 /usr/local/OptimizeitSuite55/lib/oibcp.jar
436ae000-436af000 r--p 00000000 03:02 384071 /usr/lib/locale/en_US/LC_MESSAGES/SYS_LC_MESSAGES
436af000-436b0000 r--p 00000000 03:02 544108 /usr/lib/locale/en_US/LC_MONETARY
4d740000-4d76b000 r--p 00000000 03:02 592102 /usr/lib/locale/en_US/LC_CTYPE
4d76b000-4d771000 r--p 00000000 03:02 464163 /usr/lib/locale/en_US/LC_COLLATE
4d771000-4d772000 r--p 00000000 03:02 288192 /usr/lib/locale/en_US/LC_TIME
4d772000-4d773000 r--p 00000000 03:02 592098 /usr/lib/locale/en_US/LC_NUMERIC
4d773000-4d775000 r--s 00000000 03:02 352729 /usr/java/jdk1.3.1_04/jre/lib/ext/jcert.jar
4d775000-4d776000 r--s 00000000 03:02 352731 /usr/java/jdk1.3.1_04/jre/lib/ext/jnet.jar
4d776000-4d778000 r--s 00000000 03:09 33018 /weblogic/wlserver6.1/config/blue2/lib/CR082443_61sp2.jar
4d778000-4d779000 r--s 00000000 03:09 33017 /weblogic/wlserver6.1/config/blue2/lib/db2jcc_license_cu.jar
4d779000-4d782000 r-xp 00000000 03:03 496035 /lib/libnss_files-2.2.4.so
4d782000-4d784000 rw-p 00008000 03:03 496035 /lib/libnss_files-2.2.4.so
4d784000-4d7b1000 r-xp 00000000 03:02 160810 /usr/local/OptimizeitSuite55/lib/libpri.so
4d7b1000-4d7b3000 rw-p 0002c000 03:02 160810 /usr/local/OptimizeitSuite55/lib/libpri.so
4d7b7000-4d829000 r--s 00000000 03:02 352730 /usr/java/jdk1.3.1_04/jre/lib/ext/jsse.jar
4d829000-4dd78000 r--s 00000000 03:09 33025 /weblogic/wlserver6.1/config/blue2/lib/CR061106_61sp2.jar
4dd78000-4dd7c000 r--s 00000000 03:09 33021 /weblogic/wlserver6.1/config/blue2/lib/CR067966_610sp2.jar
4dd7c000-4dd7f000 r--s 00000000 03:09 33024 /weblogic/wlserver6.1/config/blue2/lib/CR064117_61sp2.jar
4dd7f000-4dd82000 r--s 00000000 03:09 33028 /weblogic/wlserver6.1/config/blue2/lib/CR060018_610sp2.jar
4dd82000-4dd84000 r--s 00000000 03:09 33026 /weblogic/wlserver6.1/config/blue2/lib/CR058352_61sp2.jar
4dd84000-4dd89000 r--s 00000000 03:09 33019 /weblogic/wlserver6.1/config/blue2/lib/rdbmsRealm.jar
4dd89000-4dda8000 r--s 00000000 03:09 33022 /weblogic/wlserver6.1/config/blue2/lib/xmlParserAPIs.jar
4dda8000-4de81000 r--s 00000000 03:09 33027 /weblogic/wlserver6.1/config/blue2/lib/xercesImpl.jar
4de81000-4dff7000 r--s 00000000 03:09 33016 /weblogic/wlserver6.1/config/blue2/lib/db2java.zip
4dff7000-4e0d3000 r--s 00000000 03:09 33020 /weblogic/wlserver6.1/config/blue2/lib/db2jcc.jar
4e0d3000-4e553000 r--s 00000000 03:02 48466 /usr/java/jdk1.3.1_04/lib/tools.jar
4e553000-4fdcd000 r--s 00000000 03:09 229395 /weblogic/wlserver6.1/lib/weblogic.jar
4fe2d000-4ff04000 r--s 00000000 03:09 229399 /weblogic/wlserver6.1/lib/xmlx.jar
4ff04000-50265000 r--s 00000000 03:02 160793 /usr/local/OptimizeitSuite55/lib/optit.jar
502d1000-502da000 r-xp 00000000 03:02 512621 /usr/java/jdk1.3.1_04/jre/lib/i386/libnet.so
502da000-502db000 rw-p 00008000 03:02 512621 /usr/java/jdk1.3.1_04/jre/lib/i386/libnet.so
502db000-50316000 r-xp 00000000 03:02 240768 /usr/local/OptimizeitSuite55/lib/native/libauditjni.so
50316000-50317000 rw-p 0003a000 03:02 240768 /usr/local/OptimizeitSuite55/lib/native/libauditjni.so
5031f000-50323000 r--s 00000000 03:09 213324 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50094.war
50325000-5032f000 r-xp 00000000 03:03 496043 /lib/libnss_nisplus-2.2.4.so
5032f000-50330000 rw-p 00009000 03:03 496043 /lib/libnss_nisplus-2.2.4.so
50331000-50334000 r-xp 00000000 03:03 496032 /lib/libnss_dns-2.2.4.so
50334000-50336000 rw-p 00002000 03:03 496032 /lib/libnss_dns-2.2.4.so
50336000-5033a000 r--s 00000000 03:09 213324 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50094.war
5033a000-5033d000 r--s 00000000 03:09 98634 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_wl_management_internal2/cls50095.jar
5033d000-50340000 r--s 00000000 03:09 213327 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50098.war
50361000-50392000 r-xp 00000000 03:02 512620 /usr/java/jdk1.3.1_04/jre/lib/i386/libmlib_image.so
50392000-50394000 rw-p 00030000 03:02 512620 /usr/java/jdk1.3.1_04/jre/lib/i386/libmlib_image.so
50394000-50397000 r--s 00000000 03:09 213327 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50098.war
50397000-5039a000 r--s 00000000 03:09 49447 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_wl_management_internal1/cls50099.jar
5039a000-503a0000 r-xp 00000000 03:02 96189 /usr/X11R6/lib/libXp.so.6.2
503a0000-503a2000 rw-p 00005000 03:02 96189 /usr/X11R6/lib/libXp.so.6.2
503c3000-503d1000 r-xp 00000000 03:03 496048 /lib/libresolv-2.2.4.so
503d1000-503d2000 rw-p 0000d000 03:03 496048 /lib/libresolv-2.2.4.so
503d5000-503e3000 r--s 00000000 03:09 49459 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/messaging50109.jar
504a5000-504ed000 r-xp 00000000 03:02 96195 /usr/X11R6/lib/libXt.so.6.0
504ed000-504f1000 rw-p 00047000 03:02 96195 /usr/X11R6/lib/libXt.so.6.0
504f1000-504fd000 r-xp 00000000 03:02 96177 /usr/X11R6/lib/libXext.so.6.4
504fd000-504ff000 rw-p 0000b000 03:02 96177 /usr/X11R6/lib/libXext.so.6.4
50600000-50604000 r-xp 00000000 03:02 96197 /usr/X11R6/lib/libXtst.so.6.1
50604000-50606000 rw-p 00003000 03:02 96197 /usr/X11R6/lib/libXtst.so.6.1
50606000-5060d000 r-xp 00000000 03:02 96167 /usr/X11R6/lib/libSM.so.6.0
5060d000-5060f000 rw-p 00006000 03:02 96167 /usr/X11R6/lib/libSM.so.6.0
5060f000-50623000 r-xp 00000000 03:02 96163 /usr/X11R6/lib/libICE.so.6.3
50623000-50624000 rw-p 00013000 03:02 96163 /usr/X11R6/lib/libICE.so.6.3
506e9000-506fe000 r--s 00000000 03:09 49460 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/controller50110.jar
50800000-5081b000 r-xp 00000000 03:03 288205 /opt/IBM/db2/V8.1/lib/libdb2jdbc.so.1
5081b000-50820000 rw-p 0001a000 03:03 288205 /opt/IBM/db2/V8.1/lib/libdb2jdbc.so.1
50827000-50829000 r-xp 00000000 03:03 288166 /opt/IBM/db2/V8.1/lib/libdb2install.so.1
50829000-5082a000 rw-p 00001000 03:03 288166 /opt/IBM/db2/V8.1/lib/libdb2install.so.1
5082a000-50831000 r-xp 00000000 03:03 288177 /opt/IBM/db2/V8.1/lib/libdb2trcapi.so.1
50831000-50836000 rw-p 00006000 03:03 288177 /opt/IBM/db2/V8.1/lib/libdb2trcapi.so.1
50863000-508aa000 r--s 00000000 03:09 49458 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/utils50108.jar
508aa000-508b2000 r--s 00000000 03:09 49455 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/org50105.jar
508b2000-508ba000 r--s 00000000 03:09 49461 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/aspectjrt50111.jar
508ba000-508d0000 r--s 00000000 03:09 49454 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/security50104.jar
508d0000-508ef000 r--s 00000000 03:09 49453 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/persistence50103.jar
508ef000-508f8000 r--s 00000000 03:09 49457 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/caching50107.jar
50d02000-50d9d000 r--s 00000000 03:09 49463 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/iText50113.jar
50d9d000-50e33000 r--s 00000000 03:09 49466 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/jsTMP50116.jar
50e33000-50e8a000 r--s 00000000 03:09 49465 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/log4j50115.jar
50e8a000-50ee3000 r--s 00000000 03:09 49464 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/trove50114.jar
50f65000-50f96000 r-xp 00000000 03:03 288158 /opt/IBM/db2/V8.1/lib/libdb2g11n.so.1
50f96000-50fd6000 rw-p 00030000 03:03 288158 /opt/IBM/db2/V8.1/lib/libdb2g11n.so.1
510e7000-51136000 r-xp 00000000 03:03 288144 /opt/IBM/db2/V8.1/lib/libcxa.so.1
51136000-51155000 rw-p 0004e000 03:03 288144 /opt/IBM/db2/V8.1/lib/libcxa.so.1
51155000-5115a000 r-xp 00000000 03:03 496012 /lib/libcrypt-2.2.4.so
5115a000-5115b000 rw-p 00004000 03:03 496012 /lib/libcrypt-2.2.4.so
51182000-51193000 r-xp 00000000 03:03 288169 /opt/IBM/db2/V8.1/lib/libdb2locale.so.1
51193000-511a0000 rw-p 00010000 03:03 288169 /opt/IBM/db2/V8.1/lib/libdb2locale.so.1
511a0000-511da000 r-xp 00000000 03:03 288171 /opt/IBM/db2/V8.1/lib/libdb2osse.so.1
511da000-51221000 rw-p 00039000 03:03 288171 /opt/IBM/db2/V8.1/lib/libdb2osse.so.1
51234000-5125a000 r-xp 00000000 03:03 288160 /opt/IBM/db2/V8.1/lib/libdb2genreg.so.1
5125a000-51277000 rw-p 00025000 03:03 288160 /opt/IBM/db2/V8.1/lib/libdb2genreg.so.1
512ea000-516b8000 r-xp 00000000 03:02 512608 /usr/java/jdk1.3.1_04/jre/lib/i386/libawt.so
516b8000-516c8000 rw-p 003cd000 03:02 512608 /usr/java/jdk1.3.1_04/jre/lib/i386/libawt.so
516dd000-517ce000 r-xp 00000000 03:02 96169 /usr/X11R6/lib/libX11.so.6.2
517ce000-517d3000 rw-p 000f0000 03:02 96169 /usr/X11R6/lib/libX11.so.6.2
517d3000-517f1000 r--s 00000000 03:09 49456 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/adminfw50106.jar
52300000-526ea000 r--s 00000000 03:09 213328 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50100.war
526ea000-52ad4000 r--s 00000000 03:09 213328 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50100.war
52ad4000-52b2f000 r--s 00000000 03:09 49452 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/sysadmin50102.jar
52b2f000-52c0b000 r--s 00000000 03:09 49462 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/db2jcc50112.jar
53700000-53b80000 r--s 00000000 03:02 48466 /usr/java/jdk1.3.1_04/lib/tools.jar
54300000-54691000 r--s 00000000 03:09 213326 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50096.war
54a00000-54d91000 r--s 00000000 03:09 213326 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50096.war
58909000-590cc000 r-xp 00000000 03:03 288146 /opt/IBM/db2/V8.1/lib/libdb2.so.1
590cc000-5967e000 rw-p 007c2000 03:03 288146 /opt/IBM/db2/V8.1/lib/libdb2.so.1
Local Time = Wed May 26 16:44:53 2004
Elapsed Time = 387
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1_04-b02 mixed mode)
# An error report file has been saved as hs_err_pid2565.log.
# Please refer to the file for further information.
Attached the Profiler snapshot of the connection classes.
There seem to be large instances of weblogic.jdbc.Connection
Joe Weinstein <[email protected]> wrote:
>
>
Jeeva wrote:
We are running WLS 6.1 sp2 on Redhat Linux 7.2
and using a XA Connection pool with Type 2 DB2 XA Driver.The type-2 driver is killing the JVM process with a bug in it's
native code. It seems to be failing randomly at runtime while
your pool is trying to make jdbc connections. You may be able
to avoid this if you will define your pool to make all it's
connections at startup. Ie: init capacity = max capacity.
Java is so much safer. If you can use a type-4 driver it
can't kill the JVM...
Joe
<JDBCConnectionPool
Name="TXBusobj" Targets="jeeva_adminServer"
InitialCapacity="0" CapacityIncrement="2" MaxCapacity="15"RefreshMinutes="5"
DriverName="COM.ibm.db2.jdbc.DB2XADataSource" Password="db2"URL="jdbc:db2/TEST_REP"
Properties="user=db2as;password=db2;DatabaseName=TEST_REP"
TestConnectionsOnReserve="false"
TestTableName="SYSIBM.SYSDUMMY1"/>
The application works fine with out the above XA Connection pool.
After adding the connection pool the server randomly crashes with Signal11 from
JVM.
We are using 1.3.1_04 and also tried with 1.3.1_11
Following is the stack trace:
# Problematic Thread: prio=1 tid=0xabb6768 nid=0xa05 runnable
An unexpected exception has been detected in native code outside theVM.
Unexpected Signal : 11 occurred at PC=0x0
Function name=(N/A)
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at java.util.zip.ZipFile.getEntry(ZipFile.java:141)
at java.util.jar.JarFile.getEntry(JarFile.java:176)
at java.util.jar.JarFile.getJarEntry(JarFile.java:163)
at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:546)
at sun.misc.URLClassPath.getResource(URLClassPath.java:133)
at java.net.URLClassLoader$2.run(URLClassLoader.java:344)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:341)
at java.lang.ClassLoader.getResource(ClassLoader.java:766)
at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:927)
at java.util.ResourceBundle$1.run(ResourceBundle.java:931)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.ResourceBundle.loadBundle(ResourceBundle.java:927)
at java.util.ResourceBundle.findBundle(ResourceBundle.java:786)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:616)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:570)
at weblogic.i18ntools.L10nLookup.getLocalizer(L10nLookup.java:299)
at weblogic.logging.LogManager.log(LogManager.java:230)
at weblogic.logging.MessageLogger.log(MessageLogger.java:17)
at weblogic.jdbc.JDBCLogger.logSleepingInCreateResourceInfo(JDBCLogger.java:1060)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:69)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:511)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:400)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:390)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:164)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:118)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1152)
at weblogic.jdbc.jta.DataSource.getXAResource(DataSource.java:679)
at weblogic.jdbc.jta.DataSource.recover(DataSource.java:887)
at weblogic.transaction.internal.ServerResourceInfo.recover(ServerResourceInfo.java:786)
at weblogic.transaction.internal.ServerSCInfo.recover(ServerSCInfo.java:283)
at weblogic.transaction.internal.ResourceDescriptor.getXidsToBeRolledBack(ResourceDescriptor.java:1112)
at weblogic.transaction.internal.ResourceDescriptor.recover(ResourceDescriptor.java:1046)
at weblogic.transaction.internal.ResourceDescriptor.access$9(ResourceDescriptor.java:1029)
at weblogic.transaction.internal.ResourceDescriptor$1.execute(ResourceDescriptor.java:770)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
08048000-0804c000 r-xp 00000000 03:02 464716 /usr/java/jdk1.3.1_04/bin/i386/native_threads/java
0804c000-0804d000 rw-p 00003000 03:02 464716 /usr/java/jdk1.3.1_04/bin/i386/native_threads/java
40000000-40015000 r-xp 00000000 03:03 496100 /lib/ld-2.2.4.so
40015000-40016000 rw-p 00014000 03:03 496100 /lib/ld-2.2.4.so
40017000-40018000 r--p 00000000 03:02 288014 /usr/lib/locale/en_US/LC_IDENTIFICATION
40018000-40019000 r--p 00000000 03:02 544149 /usr/lib/locale/en_US/LC_MEASUREMENT
40019000-4001a000 r--p 00000000 03:02 48241 /usr/lib/locale/en_US/LC_TELEPHONE
4001a000-4001b000 r--p 00000000 03:02 48430 /usr/lib/locale/en_US/LC_ADDRESS
4001b000-4001c000 r--p 00000000 03:02 48429 /usr/lib/locale/en_US/LC_NAME
4001c000-4001d000 r--p 00000000 03:02 112040 /usr/lib/locale/en_US/LC_PAPER
4001d000-4002c000 r-xp 00000000 03:03 496046 /lib/libpthread-0.9.so
4002c000-40034000 rw-p 0000e000 03:03 496046 /lib/libpthread-0.9.so
40034000-4003d000 r-xp 00000000 03:02 144730 /usr/java/jdk1.3.1_04/jre/lib/i386/native_threads/libhpi.so
4003d000-4003e000 rw-p 00008000 03:02 144730 /usr/java/jdk1.3.1_04/jre/lib/i386/native_threads/libhpi.so
4003e000-40243000 r-xp 00000000 03:02 272604 /usr/java/jdk1.3.1_04/jre/lib/i386/client/libjvm.so
40243000-40344000 rw-p 00204000 03:02 272604 /usr/java/jdk1.3.1_04/jre/lib/i386/client/libjvm.so
4035b000-4035d000 r-xp 00000000 03:03 496014 /lib/libdl-2.2.4.so
4035d000-4035f000 rw-p 00001000 03:03 496014 /lib/libdl-2.2.4.so
40360000-4048c000 r-xp 00000000 03:03 496010 /lib/libc-2.2.4.so
4048c000-40492000 rw-p 0012b000 03:03 496010 /lib/libc-2.2.4.so
40496000-404a9000 r-xp 00000000 03:03 496019 /lib/libnsl-2.2.4.so
404a9000-404ab000 rw-p 00012000 03:03 496019 /lib/libnsl-2.2.4.so
404ad000-404ce000 r-xp 00000000 03:03 496016 /lib/libm-2.2.4.so
404ce000-404cf000 rw-p 00020000 03:03 496016 /lib/libm-2.2.4.so
404cf000-40503000 r-xp 00000000 03:02 64413 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
40503000-4050f000 rw-p 00033000 03:02 64413 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
40512000-40523000 r-xp 00000000 03:02 512622 /usr/java/jdk1.3.1_04/jre/lib/i386/libverify.so
40523000-40525000 rw-p 00010000 03:02 512622 /usr/java/jdk1.3.1_04/jre/lib/i386/libverify.so
40525000-40546000 r-xp 00000000 03:02 512614 /usr/java/jdk1.3.1_04/jre/lib/i386/libjava.so
40546000-40548000 rw-p 00020000 03:02 512614 /usr/java/jdk1.3.1_04/jre/lib/i386/libjava.so
40549000-4055d000 r-xp 00000000 03:02 512623 /usr/java/jdk1.3.1_04/jre/lib/i386/libzip.so
4055d000-40560000 rw-p 00013000 03:02 512623 /usr/java/jdk1.3.1_04/jre/lib/i386/libzip.so
40560000-41296000 r--s 00000000 03:02 384740 /usr/java/jdk1.3.1_04/jre/lib/rt.jar
412c3000-415ba000 r--s 00000000 03:02 384738 /usr/java/jdk1.3.1_04/jre/lib/i18n.jar
415ba000-415d0000 r--s 00000000 03:02 384745 /usr/java/jdk1.3.1_04/jre/lib/sunrsasign.jar
415d0000-415f4000 r--s 00000000 03:09 33023 /weblogic/wlserver6.1/config/blue2/lib/pja.jar
415f4000-41606000 r--s 00000000 03:02 160797 /usr/local/OptimizeitSuite55/lib/oibcp.jar
436ae000-436af000 r--p 00000000 03:02 384071 /usr/lib/locale/en_US/LC_MESSAGES/SYS_LC_MESSAGES
436af000-436b0000 r--p 00000000 03:02 544108 /usr/lib/locale/en_US/LC_MONETARY
4d740000-4d76b000 r--p 00000000 03:02 592102 /usr/lib/locale/en_US/LC_CTYPE
4d76b000-4d771000 r--p 00000000 03:02 464163 /usr/lib/locale/en_US/LC_COLLATE
4d771000-4d772000 r--p 00000000 03:02 288192 /usr/lib/locale/en_US/LC_TIME
4d772000-4d773000 r--p 00000000 03:02 592098 /usr/lib/locale/en_US/LC_NUMERIC
4d773000-4d775000 r--s 00000000 03:02 352729 /usr/java/jdk1.3.1_04/jre/lib/ext/jcert.jar
4d775000-4d776000 r--s 00000000 03:02 352731 /usr/java/jdk1.3.1_04/jre/lib/ext/jnet.jar
4d776000-4d778000 r--s 00000000 03:09 33018 /weblogic/wlserver6.1/config/blue2/lib/CR082443_61sp2.jar
4d778000-4d779000 r--s 00000000 03:09 33017 /weblogic/wlserver6.1/config/blue2/lib/db2jcc_license_cu.jar
4d779000-4d782000 r-xp 00000000 03:03 496035 /lib/libnss_files-2.2.4.so
4d782000-4d784000 rw-p 00008000 03:03 496035 /lib/libnss_files-2.2.4.so
4d784000-4d7b1000 r-xp 00000000 03:02 160810 /usr/local/OptimizeitSuite55/lib/libpri.so
4d7b1000-4d7b3000 rw-p 0002c000 03:02 160810 /usr/local/OptimizeitSuite55/lib/libpri.so
4d7b7000-4d829000 r--s 00000000 03:02 352730 /usr/java/jdk1.3.1_04/jre/lib/ext/jsse.jar
4d829000-4dd78000 r--s 00000000 03:09 33025 /weblogic/wlserver6.1/config/blue2/lib/CR061106_61sp2.jar
4dd78000-4dd7c000 r--s 00000000 03:09 33021 /weblogic/wlserver6.1/config/blue2/lib/CR067966_610sp2.jar
4dd7c000-4dd7f000 r--s 00000000 03:09 33024 /weblogic/wlserver6.1/config/blue2/lib/CR064117_61sp2.jar
4dd7f000-4dd82000 r--s 00000000 03:09 33028 /weblogic/wlserver6.1/config/blue2/lib/CR060018_610sp2.jar
4dd82000-4dd84000 r--s 00000000 03:09 33026 /weblogic/wlserver6.1/config/blue2/lib/CR058352_61sp2.jar
4dd84000-4dd89000 r--s 00000000 03:09 33019 /weblogic/wlserver6.1/config/blue2/lib/rdbmsRealm.jar
4dd89000-4dda8000 r--s 00000000 03:09 33022 /weblogic/wlserver6.1/config/blue2/lib/xmlParserAPIs.jar
4dda8000-4de81000 r--s 00000000 03:09 33027 /weblogic/wlserver6.1/config/blue2/lib/xercesImpl.jar
4de81000-4dff7000 r--s 00000000 03:09 33016 /weblogic/wlserver6.1/config/blue2/lib/db2java.zip
4dff7000-4e0d3000 r--s 00000000 03:09 33020 /weblogic/wlserver6.1/config/blue2/lib/db2jcc.jar
4e0d3000-4e553000 r--s 00000000 03:02 48466 /usr/java/jdk1.3.1_04/lib/tools.jar
4e553000-4fdcd000 r--s 00000000 03:09 229395 /weblogic/wlserver6.1/lib/weblogic.jar
4fe2d000-4ff04000 r--s 00000000 03:09 229399 /weblogic/wlserver6.1/lib/xmlx.jar
4ff04000-50265000 r--s 00000000 03:02 160793 /usr/local/OptimizeitSuite55/lib/optit.jar
502d1000-502da000 r-xp 00000000 03:02 512621 /usr/java/jdk1.3.1_04/jre/lib/i386/libnet.so
502da000-502db000 rw-p 00008000 03:02 512621 /usr/java/jdk1.3.1_04/jre/lib/i386/libnet.so
502db000-50316000 r-xp 00000000 03:02 240768 /usr/local/OptimizeitSuite55/lib/native/libauditjni.so
50316000-50317000 rw-p 0003a000 03:02 240768 /usr/local/OptimizeitSuite55/lib/native/libauditjni.so
5031f000-50323000 r--s 00000000 03:09 213324 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50094.war
50325000-5032f000 r-xp 00000000 03:03 496043 /lib/libnss_nisplus-2.2.4.so
5032f000-50330000 rw-p 00009000 03:03 496043 /lib/libnss_nisplus-2.2.4.so
50331000-50334000 r-xp 00000000 03:03 496032 /lib/libnss_dns-2.2.4.so
50334000-50336000 rw-p 00002000 03:03 496032 /lib/libnss_dns-2.2.4.so
50336000-5033a000 r--s 00000000 03:09 213324 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50094.war
5033a000-5033d000 r--s 00000000 03:09 98634 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_wl_management_internal2/cls50095.jar
5033d000-50340000 r--s 00000000 03:09 213327 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50098.war
50361000-50392000 r-xp 00000000 03:02 512620 /usr/java/jdk1.3.1_04/jre/lib/i386/libmlib_image.so
50392000-50394000 rw-p 00030000 03:02 512620 /usr/java/jdk1.3.1_04/jre/lib/i386/libmlib_image.so
50394000-50397000 r--s 00000000 03:09 213327 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50098.war
50397000-5039a000 r--s 00000000 03:09 49447 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_wl_management_internal1/cls50099.jar
5039a000-503a0000 r-xp 00000000 03:02 96189 /usr/X11R6/lib/libXp.so.6.2
503a0000-503a2000 rw-p 00005000 03:02 96189 /usr/X11R6/lib/libXp.so.6.2
503c3000-503d1000 r-xp 00000000 03:03 496048 /lib/libresolv-2.2.4.so
503d1000-503d2000 rw-p 0000d000 03:03 496048 /lib/libresolv-2.2.4.so
503d5000-503e3000 r--s 00000000 03:09 49459 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/messaging50109.jar
504a5000-504ed000 r-xp 00000000 03:02 96195 /usr/X11R6/lib/libXt.so.6.0
504ed000-504f1000 rw-p 00047000 03:02 96195 /usr/X11R6/lib/libXt.so.6.0
504f1000-504fd000 r-xp 00000000 03:02 96177 /usr/X11R6/lib/libXext.so.6.4
504fd000-504ff000 rw-p 0000b000 03:02 96177 /usr/X11R6/lib/libXext.so.6.4
50600000-50604000 r-xp 00000000 03:02 96197 /usr/X11R6/lib/libXtst.so.6.1
50604000-50606000 rw-p 00003000 03:02 96197 /usr/X11R6/lib/libXtst.so.6.1
50606000-5060d000 r-xp 00000000 03:02 96167 /usr/X11R6/lib/libSM.so.6.0
5060d000-5060f000 rw-p 00006000 03:02 96167 /usr/X11R6/lib/libSM.so.6.0
5060f000-50623000 r-xp 00000000 03:02 96163 /usr/X11R6/lib/libICE.so.6.3
50623000-50624000 rw-p 00013000 03:02 96163 /usr/X11R6/lib/libICE.so.6.3
506e9000-506fe000 r--s 00000000 03:09 49460 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/controller50110.jar
50800000-5081b000 r-xp 00000000 03:03 288205 /opt/IBM/db2/V8.1/lib/libdb2jdbc.so.1
5081b000-50820000 rw-p 0001a000 03:03 288205 /opt/IBM/db2/V8.1/lib/libdb2jdbc.so.1
50827000-50829000 r-xp 00000000 03:03 288166 /opt/IBM/db2/V8.1/lib/libdb2install.so.1
50829000-5082a000 rw-p 00001000 03:03 288166 /opt/IBM/db2/V8.1/lib/libdb2install.so.1
5082a000-50831000 r-xp 00000000 03:03 288177 /opt/IBM/db2/V8.1/lib/libdb2trcapi.so.1
50831000-50836000 rw-p 00006000 03:03 288177 /opt/IBM/db2/V8.1/lib/libdb2trcapi.so.1
50863000-508aa000 r--s 00000000 03:09 49458 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/utils50108.jar
508aa000-508b2000 r--s 00000000 03:09 49455 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/org50105.jar
508b2000-508ba000 r--s 00000000 03:09 49461 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/aspectjrt50111.jar
508ba000-508d0000 r--s 00000000 03:09 49454 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/security50104.jar
508d0000-508ef000 r--s 00000000 03:09 49453 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/persistence50103.jar
508ef000-508f8000 r--s 00000000 03:09 49457 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/caching50107.jar
50d02000-50d9d000 r--s 00000000 03:09 49463 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/iText50113.jar
50d9d000-50e33000 r--s 00000000 03:09 49466 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/jsTMP50116.jar
50e33000-50e8a000 r--s 00000000 03:09 49465 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/log4j50115.jar
50e8a000-50ee3000 r--s 00000000 03:09 49464 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/trove50114.jar
50f65000-50f96000 r-xp 00000000 03:03 288158 /opt/IBM/db2/V8.1/lib/libdb2g11n.so.1
50f96000-50fd6000 rw-p 00030000 03:03 288158 /opt/IBM/db2/V8.1/lib/libdb2g11n.so.1
510e7000-51136000 r-xp 00000000 03:03 288144 /opt/IBM/db2/V8.1/lib/libcxa.so.1
51136000-51155000 rw-p 0004e000 03:03 288144 /opt/IBM/db2/V8.1/lib/libcxa.so.1
51155000-5115a000 r-xp 00000000 03:03 496012 /lib/libcrypt-2.2.4.so
5115a000-5115b000 rw-p 00004000 03:03 496012 /lib/libcrypt-2.2.4.so
51182000-51193000 r-xp 00000000 03:03 288169 /opt/IBM/db2/V8.1/lib/libdb2locale.so.1
51193000-511a0000 rw-p 00010000 03:03 288169 /opt/IBM/db2/V8.1/lib/libdb2locale.so.1
511a0000-511da000 r-xp 00000000 03:03 288171 /opt/IBM/db2/V8.1/lib/libdb2osse.so.1
511da000-51221000 rw-p 00039000 03:03 288171 /opt/IBM/db2/V8.1/lib/libdb2osse.so.1
51234000-5125a000 r-xp 00000000 03:03 288160 /opt/IBM/db2/V8.1/lib/libdb2genreg.so.1
5125a000-51277000 rw-p 00025000 03:03 288160 /opt/IBM/db2/V8.1/lib/libdb2genreg.so.1
512ea000-516b8000 r-xp 00000000 03:02 512608 /usr/java/jdk1.3.1_04/jre/lib/i386/libawt.so
516b8000-516c8000 rw-p 003cd000 03:02 512608 /usr/java/jdk1.3.1_04/jre/lib/i386/libawt.so
516dd000-517ce000 r-xp 00000000 03:02 96169 /usr/X11R6/lib/libX11.so.6.2
517ce000-517d3000 rw-p 000f0000 03:02 96169 /usr/X11R6/lib/libX11.so.6.2
517d3000-517f1000 r--s 00000000 03:09 49456 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/adminfw50106.jar
52300000-526ea000 r--s 00000000 03:09 213328 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50100.war
526ea000-52ad4000 r--s 00000000 03:09 213328 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50100.war
52ad4000-52b2f000 r--s 00000000 03:09 49452 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/sysadmin50102.jar
52b2f000-52c0b000 r--s 00000000 03:09 49462 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/WEB-INF/_tmp_war_blue2Server_blue2Server_sysadmin/WEB-INF/lib/db2jcc50112.jar
53700000-53b80000 r--s 00000000 03:02 48466 /usr/java/jdk1.3.1_04/lib/tools.jar
54300000-54691000 r--s 00000000 03:09 213326 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50096.war
54a00000-54d91000 r--s 00000000 03:09 213326 /weblogic/wlserver6.1/config/blue2/applications/.wlnotdelete/wl_comp50096.war
58909000-590cc000 r-xp 00000000 03:03 288146 /opt/IBM/db2/V8.1/lib/libdb2.so.1
590cc000-5967e000 rw-p 007c2000 03:03 288146 /opt/IBM/db2/V8.1/lib/libdb2.so.1
Local Time = Wed May 26 16:44:53 2004
Elapsed Time = 387
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1_04-b02 mixed mode)
# An error report file has been saved as hs_err_pid2565.log.
# Please refer to the file for further information.
[connection_profile.doc]
Similar Messages
-
HELP - DB2 v9 & App Server PE 9.0 - PING Connection Pool Failure - HELP
I've been playing around with Studio Creator and DB2 v9 without any issues.
So I figured I would installed App Server PE 9 and use this as my production server that I would deploy to from studio creator.
However, in my efforts to set up db2/v9 I have been trying to ping a connection pool without any luck. I get the following message:
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: [sunm][DB2 JDBC Driver]Resource Limits Reached( ALLOCATE MEMORY FOR NEW SQLSTT FAILED ). Diagnostic Info: FUNCTION ID = 0049 , PROBE POINT = 0400 , TRACE POINT = 0030 , SUBCODE1 = 8B0F0000, SUBCODE2 = 78A68A98, SUBCODE3 = 00000000, ERROR MSG = Parser: Memory allocation error.
My datasource class name is com.sun.sql.jdbcx.db2.DB2DataSource.
And my resource type is javax.sql.datasource
I have copied smbase.jar, smdb2.jar and smutil.jar into c:\sun\appserver\lib
and I have all of the properties (serverName, portNumber, databaseName, user, password) created and set accordingly.
Any help would be greatly appreciated.Here is how I got the DB2 Express-C and Sun PE 9.0 to work. ( at least base connectivity wise )
1. ) You have to have at least the DB2 Client installed on the system that will be communicating to the DB2 instance.
2.) The following jars will be needed ( depending on the driver type used) . db2java.zip, db2jcc.jar, and db2jcc_license_cu.jar and use them in the App Server ->JVM settings -> Path Settings -> Classpath Suffix
3.) The next setup is dependent on the Type driver you use
I used the Type 4 and this is the resource setup I used.
Connection Pool:
Name: DB2TestPool
Datasource Classname: com.ibm.db2.jcc.DB2SimpleDataSource
Resource Type: javax.sql.ConnectionPoolDataSource
Properties:
user: xxxxxx
password: xxxxxx
databaseName: TEST
serverName: <hostname of machine>
portnumber: 50000
driverType: 4
URL: jdbc:db2://<hostname>:<port>/<database>
JDBC Resource:
JNDI Name: jdbc/TEST
Pool Name: DB2TestPool
With this configuration I was able to ping the database as well as connect to create an entity bean from a table. This should give you a starting point.
I have yet to deploy my application, but should be doing that sometime today to verify that a connection can be made and used from within the application. -
Weblogic server not starting due to connection pool error.
Hi all,
We have some issues with the network due to that, weblog server not able to create the connection pool or make physical connection with the database in the allocated time, we need to increase the timeout so that weblogic can wait and create a connection and then start the apps. How to achieve this?
Currently the server crashes and forcing to shutdown the error listed below
<Oct 10, 2012 5:08:47 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:09:48 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:10:49 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:10:50 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oltpDS' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:302)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:276)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1249)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1166)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:249)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1155)
Truncated. see log file for complete stacktrace
javax.naming.NameNotFoundException: Unable to resolve 'oltpDS'. Resolved ''; remaining name 'oltpDS'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.healthedge.j2ee.PooledConnectionHelper.addDataSource(PooledConnectionHelper.java:202)
at com.healthedge.j2ee.PooledConnectionHelper.getSTConnection(PooledConnectionHelper.java:281)
at com.healthedge.j2ee.PooledConnectionHelper.getConnectionIgnoreTxn(PooledConnectionHelper.java:268)
at com.healthedge.j2ee.PooledConnectionHelper.getConnection(PooledConnectionHelper.java:251)
at com.healthedge.query.execution.Query.prepareStatement(Query.java:504)
at com.healthedge.query.execution.Query.setValue(Query.java:716)
at com.healthedge.config.util.ReferenceResolutionHelper.setConstraintValues(ReferenceResolutionHelper.java:277)
at com.healthedge.config.util.ReferenceResolver.getTypeReference(ReferenceResolver.java:232)
at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:221)
at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:211)
at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:187)
at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:156)
at com.healthedge.config.eval.HicIdentifier.getReference(HicIdentifier.java:58)
at com.healthedge.startup.StartupService.startup(StartupService.java:56)
at com.healthedge.startup.wl.WLStartupService.main(WLStartupService.java:13)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:362)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:272)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:186)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppAdminState(ClassDeploymentManager.java:162)
at weblogic.management.deploy.classdeployment.StartupClassPrelistenService.start(StartupClassPrelistenService.java:13)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
NESTED TRACES DONE
>
<Oct 10, 2012 5:11:18 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Oct 10, 2012 5:11:18 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Oct 10, 2012 5:11:18 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>Hi,
It looks like your DB is down for now and that is reason why the server cannot initialize your App while startup.
Check which Data source you are using and make initial capacity as zero and try to restart the server again.
Note: you need to do this changes from JMS module under %Domain_Home% / config / jdbc/
Regards,
Kal -
Most efficient way to get a connection from a defined connection -pool [whole message]
Having recently load-tested the application we are developing I noticed that
one of the most expensive (time-wise) calls was my fetch of a db-connection
from the defined db-pool. At present I fetch my connections using :
private Connection getConnection() throws SQLException {
try {
Context jndiCntx = new InitialContext();
DataSource ds =
(DataSource)
jndiCntx.lookup("java:comp/env/jdbc/txDatasource");
return ds.getConnection();
} catch (NamingException ne) {
myLog.error(this.makeSQLInsertable("getConnection - could not
find connection"));
throw new EJBException(ne);
In other parts of the code, not developed by the same team, I've seen the
same task accomplished by :
private Connection getConnection() throws SQLException {
return DriverManager.getConnection("jdbc:weblogic:jts:FTPool");
From the performance-measurements I made the latter seems to be much more
efficient (time-wise). To give you some metrics:
The first version took a total of 75724ms for a total of 7224 calls which
gives ~ 11ms/call
The second version took a total of 8127ms for 11662 calls which gives
~0,7ms/call
I'm no JDBC guru som i'm probably missing something vital here. One
suspicion I have is that the second call first find the jdbc-pool and after
that makes the very same (DataSource)
jndiCntx.lookup("java:comp/env/jdbc/txDatasource") in order to fetch the
actual connection anyway. If that is true then my comparison is plain wrong
since one call is part of the second. If not, then the second version sure
seems a lot faster.
Apart from the obvious performance-differences in the two above approaches,
is there any other difference one should be aware of (transaction-context
for instance) between the two ? Basically I'm working in an EJB-environment
on weblogic 7.0 and looking for the most efficient way to get hold of a
db-connection in code. Comments anyone ?
//Linus Nikander - [email protected]Linus Nikander wrote:
Thank you for both your replies. As per your suggestions I've improved my
connectionhandling (I ended up implementing the Service Locator pattern as a
matter of fact).
One thing still puzzles me though. Which (and why) is the "proper" way to
fetch the actual dataSource. As I stated before in the code I've seen two
approaches within the code I've got.
1. myDs = myServiceLocator.getDataSource("jdbc:weblogic:jts:FTPool");
2. myDs = myServiceLocator.getDataSource("java:comp/env/jdbc/tgsDB");
where getDataSource does a dataSource = (DataSource)
initialContext.lookup(dataSourceName); dataSourceName being the input-string
obviously.
tgsDB is defined as
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/tgsDB</res-ref-name>
<jndi-name>tgs-dataSource</jndi-name>
</resource-description>
</reference-descriptor>
in weblogic-ejb-jar.xml
From what I can understand by your answer, you don't recommend using the
JNDI-lookup way of getting the connection at all ?Correct.
The service locator that
I implemented will still perform a JNDI lookup, but only once. Will the fact
that I'm talking to an RMI-object anyway significantly impact performance
(when compared to you non-jndi-method) ?In some cases, for earlier 7.0s, maybe yes. For the very latest, it shouldn't
hurt.
>
>
In my two examples above. If i use version 1. How will the server know
whether to give me a TX-bound connection and when not to ? In version 1
FTPool maps to a pool with both TX and non-TX datasources. In version 2.
tgsDB maps directly to a TX-dataSource.
I might be asking a lot of strange questions, probably because I'm just
getting the hang of all the resource-reference issues that EJBs are
associated with.Bear with me ;)
//Linus
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
Hi. As Jon said, the lookups are redundant. Because you showed that otherway,
I will infer that this code is always being run in serverside code. Good.I will give you
a third way which is much better than either of the ones you showed. Thefirst method
you showed has a problem for all but the latest sps, your jdbc objectswill all be
going through an unnecessary level of indirection because you are gettingan rmi jdbc
object which talks to the jts driver object.
The second, faster method you showed also has a serious problem! Oneshould
never call DriverManager methods in multithreaded JDBC programs becauseall
DriverManager calls are class-synchronized, including some small internalones like
DriverManager.println(), which all JDBC drivers and even the constructorfor
SQLException call, so one slow getConnection() call can inadvertantly haltall other
JDBC being done in the whole JVM! Also, for JVMs that have lots of jdbcdrivers
registered, DriverManager is inefficient because it simply sends your URLand
properties to every driver it has registered until it finds one thatdoesn't throw an
exception and returns a connection.
Here's the fastest way:
// do once and reuse driver object everywhere. Can be used by multiplethreads
Driver d =(Driver)Class.forName("weblogic.jdbc.jts.Driver").newInstance();
Then, whenever you want a connection:
public myJDBCMethod()
Connection c = null; // always a method level object
try {
c = d.connect("jdbc:weblogic:jts:FTPool", null);
... do all the jdbc for the method...
c.close();
c = null;
catch (Exception e) {
... do whatever, if needed...
finally {
// close connection regardless of failure or exit path
if (c != null) try {c.close();}catch (Exception ignore){}
Joe
Linus Nikander wrote:
Having recently load-tested the application we are developing I noticed
that
one of the most expensive (time-wise) calls was my fetch of adb-connection
from the defined db-pool. At present I fetch my connections using :
private Connection getConnection() throws SQLException {
try {
Context jndiCntx = new InitialContext();
DataSource ds =
(DataSource)
jndiCntx.lookup("java:comp/env/jdbc/txDatasource");
return ds.getConnection();
} catch (NamingException ne) {
myLog.error(this.makeSQLInsertable("getConnection - couldnot
find connection"));
throw new EJBException(ne);
In other parts of the code, not developed by the same team, I've seenthe
same task accomplished by :
private Connection getConnection() throws SQLException {
return DriverManager.getConnection("jdbc:weblogic:jts:FTPool");
From the performance-measurements I made the latter seems to be muchmore
efficient (time-wise). To give you some metrics:
The first version took a total of 75724ms for a total of 7224 callswhich
gives ~ 11ms/call
The second version took a total of 8127ms for 11662 calls which gives
~0,7ms/call
I'm no JDBC guru som i'm probably missing something vital here. One
suspicion I have is that the second call first find the jdbc-pool andafter
that makes the very same (DataSource)
jndiCntx.lookup("java:comp/env/jdbc/txDatasource") in order to fetch the
actual connection anyway. If that is true then my comparison is plainwrong
since one call is part of the second. If not, then the second versionsure
seems a lot faster.
Apart from the obvious performance-differences in the two aboveapproaches,
is there any other difference one should be aware of(transaction-context
for instance) between the two ? Basically I'm working in anEJB-environment
on weblogic 7.0 and looking for the most efficient way to get hold of a
db-connection in code. Comments anyone ?
//Linus Nikander - [email protected] -
How to access database from applet using connection pooling.
Hi,
I am using tomcat 4.1, JRE 1.4.2_10, MySQL 5.0, and IE 6.0. I can access the database using connection pooling from JSP without problems. But, if I try to acess from the applet, I get the following exception (related to JNDI.):
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.lookup(Unknown Source)
I know what this acception means, but I don't know how to fix it. I set up connection pooling in my Tomcat 4.1 that talks to MySQL 5.0. As I said, when I access from jsp, JNDI works. But, applet complains. Please help. In my applet, the following code accesses the database:
ArrayList toolTipData =
access.getToolTipData (projectName,interfac);This is the snipet of my Access class:
public ArrayList getToolTipData (String projectName, String interfac) {
System.out.println("In getToolTipData");
ArrayList toolTipData = new ArrayList();
try{
Context ctx = new InitialContext();
if(ctx == null )
throw new Exception("No Context");
DataSource ds = (DataSource)ctx.lookup("java:comp/env/jdbc/interfacesDB");
if (ds != null) {
Connection conn = ds.getConnection();
if(conn != null) {
Statement s = conn.createStatement();
//For some reason paramtized queries don't work, so I am forced
//to this in slighly less eficient way.
ResultSet rst = s.executeQuery("select * from interfaces");
while (rst.next()) {
if (rst.getString("Project_Name").equals(projectName) &&
rst.getString("Interface").equals(interfac)) {
System.out.println("getToolTipData: ITG #" + rst.getString("ITG"));
toolTipData.add("ITG #: " + rst.getString("ITG"));
toolTipData.add("SPNE Prime Name: " +
rst.getString("SPNE_Prime_Name"));
toolTipData.add("PD Prime Name: " +
rst.getString("PD_Prime_Name"));
toolTipData.add("IT Prime Name: " +
rst.getString("IT_Prime_Name"));
toolTipData.add("MLC Priority: " +
rst.getString("MLC_Priority"));
toolTipData.add("Gary's Prime: " + rst.getString("Garys_Prime"));
toolTipData.add("QA Prime: " + rst.getString("QA_Prime"));
toolTipData.add("Brief Description: " +
rst.getString("Brief_Description"));
toolTipData.add("Project_Status: " +
rst.getString("Project_Status"));
conn.close();
}catch(Exception e) {
e.printStackTrace();
return toolTipData;
....The jsp runs on the server, whereas the applet runs on the client so
you must package with your applet any jndi implementation specific classes
and
Properties props = new Properties();
props.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory" );
props.setProperty("java.naming.provider.url", "url:1099");
Context ctx = new InitialContext(props);
Object ref = ctx.lookup("..."); -
Maximum open cursors exceeded from Oracle XA Connection pool
I am on WLS 6.1 sp2.
When i leave the server up overnight unaccessed and come back and see in the morning,
I see the following stacktrace on the server console.
I dont think its causing any harm, but is there anyway to prevent this from occuring?
java.sql.SQLException: ORA-01000: maximum open cursors exceeded
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oopen.receive(Oopen.java:118)
at oracle.jdbc.ttc7.TTC7Protocol.open(TTC7Protocol.java:466)
at oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:413)
at oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:432)
at oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.java:182)
at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:102)
at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:86)
at oracle.jdbc.driver.OracleConnection.privatePrepareCall(OracleConnection.java:736)
at oracle.jdbc.driver.OracleConnection.prepareCall(OracleConnection.java:622)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:163)
at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
at weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.java:1032)
at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:975)
at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:937)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:465)
at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:376)
at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1103)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)Hi. I think this is an oracle driver problem, in all likelihood.
We test a connection with:
Statement stmt = c.createStatement();
stmt.execute(sql);
Where the string sql is "select count(*) from DUAL" if you named your test table as 'DUAL'.
We obtain no result set, so the driver shouldn't be accruing cursors...
Can you upgrade to the latest oracle driver?
Can you upgrade to the latest version of 6.1?
Jeeva wrote:
I am on WLS 6.1 sp2.
When i leave the server up overnight unaccessed and come back and see in the morning,
I see the following stacktrace on the server console.
I dont think its causing any harm, but is there anyway to prevent this from occuring?
java.sql.SQLException: ORA-01000: maximum open cursors exceeded
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oopen.receive(Oopen.java:118)
at oracle.jdbc.ttc7.TTC7Protocol.open(TTC7Protocol.java:466)
at oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:413)
at oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:432)
at oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.java:182)
at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:102)
at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:86)
at oracle.jdbc.driver.OracleConnection.privatePrepareCall(OracleConnection.java:736)
at oracle.jdbc.driver.OracleConnection.prepareCall(OracleConnection.java:622)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:163)
at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
at weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.java:1032)
at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:975)
at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:937)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:465)
at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:376)
at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1103)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) -
Go connect to server crashes finder without hitting connect
i didn't see this issue posted elsewhere, i apologize if it is.
every time i click on go > connect to server... in the finder, the finder crashes BEFORE i even enter in a server to connect to. the server connection dialog is only visible for a split second. i have already repaired permissions, restarted, and updating to 10.4.11 didn't resolve the issue.
any ideas would be appreciated.I really hate to bump this, but I'm still plagued with this problem. If any of you have any ideas that would be very helpful.
-
Replace Quotes, Connection Pooling, and Sun Web Server with MySQL, Oracle
This is code I use to insert data into my MySQL and Oracle databases.
I takes care of quotes and shows use of context, i.e. when you use Sun Web Server's
ConnectionPooling. This code works. Feel free to reply if you have questions on how to set up connection pooling using Sun Web Server 6.1SP - it took quite a long time to learn and I couldn't find much information throughout the web, so I hope this helps...
This is not a question and I am not looking for an answer, but please post comments or suggestions.
dailysun
This is in one class where I have a hashtable containing the
column name / value pairs that I want to enter into my table.
This class simply creates the SQL string from the values in the
hashtable. It then passes that hashtable including the database
name to a class which executes that sql statement (second code
portion).
/* Insert data into sf_parts. Create the column strings from
* the provided hash table. Be sure to parse out hash elements which
* are used for the createTemplate process
StringBuffer values = new StringBuffer();
StringBuffer fields = new StringBuffer();
Enumeration keys = fieldHash.keys();
while(keys.hasMoreElements()){
Object currentKey = keys.nextElement();
String fieldValue = (String) fieldHash.get(currentKey);
if(values.length() >0){
values.append(",");
values.append("'"+fieldValue.replaceAll("'","''")+"'"); // Takes care of quotes and various other special characters!
if(fields.length() >0){
fields.append(",");
fields.append(currentKey);
sql = "INSERT INTO myTable (" + fields.toString() + ") VALUES (" + values.toString() + ");";
String insertResult = caq.getInsertDelete(sql,"myDatabaseName"); // your database name is defined in web.xml and sun-web.xml when you use Sun Web Server's Connection Pooling.
returnValue += "<br><br><b>Rows inserted into table(myTable): </b>" + insertResult + "<br>\n";
And, like I describe above, this method executes the sql statement.
* Takes care of insert, update and delete requests.
* Must have set both dbName as well as the sql String.
* Will return number of rows affected as String.
* @return String Number of rows affected
* @exception SQLException
* @exception Exception
public String getInsertDelete() {
checkData(); // this simply checks if the variables dbName and sql are not empty ;-)
InitialContext initContext = null;
int rv = 0;
try{
// Get connection from configured pool
initContext = new InitialContext();
source = (DataSource) initContext.lookup("java:comp/env/jdbc/" + dbName); // I have this set up in web.xml and sun-web.xml (I use Sun Web Server 6.1SP which does connection pooling for me)
conn = source.getConnection();
if(conn != null){
stmt = conn.createStatement();
rv = stmt.executeUpdate(sql);
}catch (SQLException e){
// do something
}catch (Exception e){
// do something
}finally{
try{
stmt.close();
}catch(Exception e){
// do something
try{
conn.close();
}catch(Exception e){
// do something
try{
initContext.close();
}catch(Exception e){
// do something
return rv+"";
}This is code I use to insert data into my MySQL and
Oracle databases.
I takes care of quotes and shows use of context, i.e.
when you use Sun Web Server's
ConnectionPooling. This code works. Feel free to
reply if you have questions on how to set up
connection pooling using Sun Web Server 6.1SP - it
took quite a long time to learn and I couldn't find
much information throughout the web, so I hope this
helps...
This is not a question and I am not looking for an
answer, but please post comments or suggestions.Using prepared statements would mean that you wouldn't have to worry about quotes.
You should be closing the result set.
You are handling all fields as strings. That won't work with time fields and might not work for numeric fields.
Presumably most of your variables are member variables. They should be local variables because that is the scope of the usage.
You must do something with the exceptions.
Hashtables although convienent mean that problems with usage can only be resolved at run time rather than compile time. -
How to use Connection Pool in ADF ear file creaion from jDev 10.1.3
Hi,
We are developing big application in ADF with 10 different modules. We are creating ear file with data source setting.
How to use connection pool while creating ear file from jDev. Connection pool is alreday created in Application Server 10g.
What all the setting we need do to make use of connection pool while creating ear file jDev.
ThanksUser,
If you are using ADF Business Components, you can right-click each application module, select "configurations" and edit the configuration you are using. On the initial page of the configuration dialog, you can specify to use either a JDBC URL or a Datasource - you just need to choose Datasource and then provide the name by which to access it.
John -
How to Retrieve Server Name for creating connection pool during startup!
Hi All,
I am going thru the edocs documentation of weblogic for creating the connection pool and the datasource dynamically. The URL I referred to was as under
http://edocs.bea.com/wls/docs81/jdbc/programming.html
There is a sample given in the above-mentioned URL. The Server MBean is created by passing the server name.
The code below mentioned was have placed in my dblib.java
svrAdminMBean = (ServerMBean)adminMBeanHome.getAdminMBean("myserver", "Server");
I am creating the connection pool from the servlet by invoking the dblib.java
I cannot hard-code the server name in the dblib.java since the same code was shared across multiple servlets.
Each Servlet will create its own connection pool during application server startup.
Is there a way to retrieve the server name in which the dblib.java is invoked.
Any pointers to info source will be REALLY appreciated.
Many Thanks in Advance,
C R BaradwajYou can get it from the Java system property weblogic.Name, i.e. System.getProperty("weblogic.Name");
Cheers
Feargal -
Application Server and Driver Connection Pool
Hi,
What is the difference between Connection Pool implemented by the Driver and the Connection Pool implemented by the Application Server?
If i am using a JDBC3.0 compliant driver,i can use PooledDataSource to get a Conenction from the Connection pool. But, even otherwise, the application server (JBOSS) would implement a Connection Pooling mechanism. i.e even from a basic Datasource, i will get the Connection Pool.
1. Can i do away with PooledDataSource of Driver when using an application server?
2. If i have to use both, then what is the criterion for optimal usage?
Can someone answer this please...
If there is some reference available on this topic, please let me know.
Thanks in AdvanceConnection pooling is good that the connection object that have been created can be used later by other client.
Application server is better since server always have more resources( such as memory, processor speed) in order to perform the task.
And this may improve centralization, all connection object managed by a single centralized server.
Pls correct me if i am wrong. -
Setting up connection pool in MSSQL SERVER 2000
hi,
i m having too much trouble in setting up connection pool in TOMCAT 5.0.25 for MS SQL SERVER 2000...
......so plz guide me how to do that...
TIA
bhupsi m having too much trouble in setting up connection
pool in TOMCAT 5.0.25 for MS SQL SERVER 2000...Never done it for SQL Server, but setting up a connection pool in tomcat is basically the same no matter what DB you're using:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html
The two files you're interested in are server.xml and web.xml. You just need to look at the MYSQL and Oracle examples and "tweak" it ... -
REgarding problem in Connection pooling of weblogic server
Hi ,
I have installed weblogic server 9 and trying to connection pooling in datasource , i am getting error to unable to load driver class: oracle.jdbc.DataSource
see below error log
####<Oct 29, 2008 4:55:34 PM IST> <Error> <Console> <cdhulipati> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1225279534589> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:268)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:118)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:215)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.prepare(DeploymentReceiverCallbackDeliverer.java:40)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.callDeploymentReceivers(AwaitingContextUpdateCompletion.java:156)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.handleContextUpdateSuccess(AwaitingContextUpdateCompletion.java:66)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.contextUpdated(AwaitingContextUpdateCompletion.java:32)
at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.notifyContextUpdated(TargetDeploymentService.java:225)
at weblogic.deploy.service.internal.DeploymentService$1.run(DeploymentService.java:189)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: weblogic.common.resourcepool.ResourceSystemException: Cannot load driver class: oracle.jdbc.DataSource at weblogic.jdbc.common.internal.JDBCUtil.parseException(JDBCUtil.java:292)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvFactory.java:77)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFactory.java:133)
at weblogic.jdbc.common.internal.ConnectionPool.initPooledResourceFactory(ConnectionPool.java:687)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:192)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1177)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:184)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:177)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:370)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:243)
>
Please help me outchaitudnvr wrote:
Please help me outYou would probably get better help in a forum where your question was on-topic. This forum is about XML and Java and your question isn't about either of them. -
Proxy functionality in the database connection pool
Hi,
I am scouring the internet and forums looking for a way to connect to my database from the .rpd connection pool using proxy authetication. NOT Act-As proxy that is a BIEE feature, but RDBMS proxy authentication with BIEE acting as the middle-tier connecting on behalf of many users and authenticating to the RDBMS AS THE INDIVIDUAL USER. I haven't had any luck, and am hoping someone here has set up this same kind of access.
We have a requirement to use SSO with BIEE to integrate with our portal and discoverer apps. We also have a requirement to use EUS (Enterprise User Security). EUS allows you to login to the database using the userids/password from OID. Note that the database doesn't support the SSO token, but it uses the same userid/password stored in OID for authenticating to the database. You still must initiate a connection to the database, but the authentication goes to LDAP. Every connection to BIEE may be using a different userid - we will not have a shared login.
So the issue I see is:
- We configure SSO
- In the BI Server the :USER session variable is set (but NOT :PASSWORD, since BI Server didn't authenticate you it doesn't have the password)
- We create a connection pool - This is where we hit the issue - we need each connection to BI Server to connect down to the database as the SSO user. Since we aren't using a shared account we can't enter a userid/password in this connection. We also can't user :USER and :PASSWORD since SSO doesn't set the :PASSWORD session variable. What I would hope to find is a checkbox "Proxy Authentication" (around where "Shared Logon" checkbox is located) that would connect to the database as the proxy user and then switch to the SSO user.
This is what happens with BI Publisher. On the JDBC connection screen there is a "Proxy Authentication" checkbox.
So, has anyone already solved this problem? Thanks!Hello, is there anyone knows what this program does
and how this program is executed? There is nodatabase
mentioned.That's because it's expecting the URL (which contains
the database type, hostname, and so on) to be passed
in on the command line (argv[0]), as well as the
username and password (argv[1] and argv[2]).
Thank you very much for your help.
Regards,
Lucas -
Hello, I'm using MS Access (it's all I have 'Access' to) to test my EJB application and I can connect to it with the following code:
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
String url = "jdbc:odbc:DRIVER=Microsoft Access Driver (*.mdb);DBQ=C:/projs/p1/Users.mdb";
Connection c = DriverManager.getConnection(url);
But I must somehow create a DataSource to this database so my app server (SUN app server 7) can create a connection pool to it. PLS HELP!! I have tried for the past 2 days but couldn't get the right parameters to make a DataSource connection!
(there's a limitation with MS Access in that 1 computer can only have 10 open connections to Access at a time, which is why I need to implement a connection pool)try this code, assume that i have database on drive G: named "soal.mdb". You have to download the package "com.sun.jndi.fscontext.RefFSContextFactory" from this site ( http://java.sun.com ) on JNDI sections.... 100% works !!
import javax.naming.*;
import java.util.*;
import java.io.*;
import java.sql.*;
import javax.sql.*;
public class CobaJNDI2 {
static final String BIND = "pool4";
public static void main( String[] args ) throws SQLException {
sun.jdbc.odbc.ee.ConnectionPoolDataSource cpds = new sun.jdbc.odbc.ee.ConnectionPoolDataSource( BIND );
Hashtable env = new Hashtable( 11 );
env.put( Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.fscontext.RefFSContextFactory" );
env.put( Context.PROVIDER_URL,
"file:/" );
cpds.setMinPoolSize( "1" );
cpds.setInitialPoolSize( "1" );
cpds.setMaxPoolSize( "2" );
cpds.setMaxIdleTime( "1" );
cpds.setTimeoutFromPool( "1" );
cpds.setMaintenanceInterval( "1" );
cpds.setDatabaseName( "DRIVER=Microsoft Access Driver (*.mdb);DBQ=g:\\soal.mdb" );
//cpds.setDatabaseName( "hoho" );
try {
Context c = new InitialContext( env );
c.rebind( BIND, cpds );
c.close();
InitialContext ic = new InitialContext( env );
ConnectionPoolDataSource ds = ( ConnectionPoolDataSource )ic.lookup( BIND );
Connection conn = ds.getPooledConnection().getConnection();
Statement stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery( "select * from trsewa" );
while( rs.next() )
System.out.println( rs.getString( 1 ) );
//NamingEnumeration ne = ic.list( "" );
//while( ne.hasMore() ) {
// System.out.println( ne.next() );
while( true ) { }
//System.exit( 0 );
catch( NamingException ne ) {
ne.printStackTrace();
}
Maybe you are looking for
-
Create a new user in xMII version 11.5
I want to create a new user in xMII version 11.5 that has rights to view everything and create queries. So far the user is part of the EVERYONE role and can view most of the items that the Admin can see. My question what do I have to do in order to
-
Creation of quotation with custom fields
Hai, We have created two custom fields in VA21(Quotation creation), how can we handle these custom fields while executing BAPI of quotation creation, could anybody suggest the procedure.
-
The procedure of subcontract parts
we have some raw material need to be send out for sanding blast,if this is a manufactured part,then I can create a subcontract operation specially for it,but this is raw material,who knows how to deal it either from PP side or from PO side Thanks in
-
Does iMovie11 work on Snow Leopard 10.6.8?
I would like to buy Imovie, and I need to know if it will work with my current OS. On the app store in requirements it says 1.7.4 or later? Is that true??? I'm not looking to upgrade my OS as my iMac is too old, probably not eligible.
-
How can i show just today tasks on today pane? On my today pane is showing tomorrow tasks...
Hi everyone... I'm update my lightning to the latest version, and since than, my tomorrow tasks is showing on my today pane... how can i correct that? Thanks