PKCS11Exception: CKR_ENCRYPTED_DATA_LEN_RANGE on Solaris JDK 1.6u14
Hi,
JDK 1.6 update 14 on Sun Solaris throws the following exception when trying to decrypt content from a PDF document. Strangely, the same works fine on a Windows environment.
Caused by: javax.crypto.IllegalBlockSizeException: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_ENCRYPTED_DATA_LEN_RANGE
at sun.security.pkcs11.P11Cipher.handleException(P11Cipher.java:807)
at sun.security.pkcs11.P11Cipher.implDoFinal(P11Cipher.java:710)
at sun.security.pkcs11.P11Cipher.engineDoFinal(P11Cipher.java:479)
at sun.security.pkcs11.P11Cipher.engineDoFinal(P11Cipher.java:462)
at javax.crypto.Cipher.doFinal(DashoA13*..)
Could you please let me know if this is a bug?
Thanks in advance!!
I specialise in mind-reading but I can't read your code. Any chance you can publish it with more mind-power or maybe just take the low-tech approach and post it here. Both the encryption and decryption code are needed.
Similar Messages
-
Hi,
How to check the JDK version on a solaris machine for SAP CE 7.2 systemHi,
you can use on os level <path_to_your_sapjvm_installation>/java -version
or you can view the jvm version in the systeminformation -> http://hostname:50<xx>00 -> Systeminformation -> Tab Systeminformation -> Select your Instance
Kind Regards
Franz -
WebLogic 5.1.0 crashes under Solaris
Hi,
I am using weblogic 5.1.0 under Solaris 8. Database is Oracle 8i Enterprise Edition Release 8.1.6.0.0.
WebLogic crashes with following dump. I will be very thankful if someone can help me out.
Thanks,
Viresh
Dump is as follows :
SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x14]
stackpointer=E9CAEA68
"Thread-69" (TID:0x4873e90, sys_thread_t:0x4873dc8, state:CW, thread_t: t@138, threadID:0xe9c81d78, stack_bottom:0xe9c82000, stack_size:0x20000) prio=5
[1] java.lang.Thread.sleep(Native Method)
[2] com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:173)
"Thread-8" (TID:0x41c5a48, sys_thread_t:0x41c5980, state:R, thread_t: t@47, threadID:0xe9cb1d78, stack_bottom:0xe9cb2000, stack_size:0x20000) prio=5 current thread
[1] weblogic.db.oci.OciCursor.exec(Native Method)
[2] weblogic.db.oci.OciCursor.oci_exec(OciCursor.java:1816)
[3] weblogic.jdbcbase.oci.Statement.executeUpdate(Statement.java:823)
[4] weblogic.jdbcbase.oci.Statement.execute(Statement.java:1351)
[5] weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:33)
[6] com.zaplet.schema.GetNextDeliveriesSP.execute(GetNextDeliveriesSP.java:142)
[7] com.zaplet.core.DigestThread.getNextBatch(DigestThread.java:194)
[8] com.zaplet.core.DigestThread.deliverDigests(DigestThread.java:131)
[9] com.zaplet.core.DigestThread.run(DigestThread.java:109)
"Thread-1" (TID:0x3f292e0, sys_thread_t:0x3f29218, state:CW, thread_t: t@37, threadID:0xe9ce1d78, stack_bottom:0xe9ce2000, stack_size:0x20000) prio=5
[1] java.lang.Thread.sleep(Native Method)
[2] com.zaplet.util.WorkerThread.run(WorkerThread.java:32)
"SSLListenThread" (TID:0x3d05d08, sys_thread_t:0x3d05c40, state:R, thread_t: t@36, threadID:0xe9d41d78, stack_bottom:0xe9d42000, stack_size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
[4] java.net.ServerSocket.accept(ServerSocket.java:224)
[5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
[6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
[7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
"ListenThread" (TID:0x742500, sys_thread_t:0x742438, state:R, thread_t: t@35, threadID:0xe9f01d78, stack_bottom:0xe9f02000, stack_size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
[4] java.net.ServerSocket.accept(ServerSocket.java:223)
[5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
"NBExecuteThread-1" (TID:0x8ee3d0, sys_thread_t:0x8ee308, state:CW, thread_t: t@31, threadID:0xe9f31d78, stack_bottom:0xe9f32000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"NBExecuteThread-0" (TID:0x8d8cc8, sys_thread_t:0x8d8c00, state:CW, thread_t: t@30, threadID:0xe9f81d78, stack_bottom:0xe9f82000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-19" (TID:0x8ec930, sys_thread_t:0x8ec868, state:MW, thread_t: t@29, threadID:0xe9fb1d78, stack_bottom:0xe9fb2000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-18" (TID:0x8d94c8, sys_thread_t:0x8d9400, state:R, thread_t: t@28, threadID:0xea001d78, stack_bottom:0xea002000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
[2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-17" (TID:0x8f5100, sys_thread_t:0x8f5038, state:MW, thread_t: t@27, threadID:0xea031d78, stack_bottom:0xea032000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-16" (TID:0x8a1508, sys_thread_t:0x8a1440, state:CW, thread_t: t@26, threadID:0xea081d78, stack_bottom:0xea082000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-15" (TID:0x8d8738, sys_thread_t:0x8d8670, state:MW, thread_t: t@25, threadID:0xea0b1d78, stack_bottom:0xea0b2000, stack_size:0x20000) prio=5
[1] java.sql.DriverManager.getConnection(DriverManager.java:104)
[2] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
[3] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
[4] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
[5] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
[6] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
[7] jsp._layout3._snippets._author._defaultEndWire._jspService(_defaultEndWire.java:69)
[8] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[9] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[10] weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:200)
[11] weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:172)
[12] weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:105)
[13] jsp._sending._sentokay._jspService(_sentokay.java:69)
[14] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[15] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[16] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[17] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[18] com.zaplet.StoreCreateServlet.sendMessage(StoreCreateServlet.java:510)
[19] com.zaplet.StoreCreateServlet.handleSend(StoreCreateServlet.java:272)
[20] com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:163)
[21] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:78)
[22] javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
[23] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[24] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[25] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
[26] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[27] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
[28] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
[29] javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
[30] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
[31] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
... remainder of stack truncated ...
"ExecuteThread-14" (TID:0x8e40d0, sys_thread_t:0x8e4008, state:CW, thread_t: t@24, threadID:0xea101d78, stack_bottom:0xea102000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-13" (TID:0x8facd8, sys_thread_t:0x8fac10, state:CW, thread_t: t@23, threadID:0xea131d78, stack_bottom:0xea132000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-12" (TID:0x8e0cf8, sys_thread_t:0x8e0c30, state:CW, thread_t: t@22, threadID:0xea181d78, stack_bottom:0xea182000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-11" (TID:0x938018, sys_thread_t:0x937f50, state:CW, thread_t: t@21, threadID:0xea1b1d78, stack_bottom:0xea1b2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-10" (TID:0x936e40, sys_thread_t:0x936d78, state:MW, thread_t: t@20, threadID:0xea201d78, stack_bottom:0xea202000, stack_size:0x20000) prio=5
[1] java.sql.DriverManager.getConnection(DriverManager.java:104)
[2] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
[3] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
[4] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
[5] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
[6] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
[7] jsp._errors._index._jspService(_index.java:69)
[8] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[9] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[10] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[11] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[12] com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:160)
[13] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:41)
[14] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[15] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[16] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[17] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[18] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[19] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
[20] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
[21] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[22] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[23] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[25] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[26] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:102)
[27] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[28] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[29] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-9" (TID:0x8a2ce8, sys_thread_t:0x8a2c20, state:CW, thread_t: t@19, threadID:0xea231d78, stack_bottom:0xea232000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-8" (TID:0x934cb0, sys_thread_t:0x934be8, state:CW, thread_t: t@18, threadID:0xea281d78, stack_bottom:0xea282000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-7" (TID:0x885108, sys_thread_t:0x885040, state:CW, thread_t: t@17, threadID:0xea2b1d78, stack_bottom:0xea2b2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-6" (TID:0x8a6cf8, sys_thread_t:0x8a6c30, state:CW, thread_t: t@16, threadID:0xea2f1d78, stack_bottom:0xea2f2000, stack_size:0x20000) prio=5
[1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
[2] weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:561)
[3] weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:555)
[4] weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:544)
[5] weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:162)
[6] weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:145)
[7] weblogic.jdbcbase.pool.Driver.connect(Driver.java:65)
[8] java.sql.DriverManager.getConnection(DriverManager.java:433)
[9] java.sql.DriverManager.getConnection(DriverManager.java:104)
[10] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
[11] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
[12] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
[13] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
[14] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
[15] jsp._authorpages._contacts._jspService(_contacts.java:96)
[16] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[17] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[18] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[19] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[20] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:102)
[21] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[22] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[23] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-5" (TID:0x92be00, sys_thread_t:0x92bd38, state:CW, thread_t: t@15, threadID:0xeadb1d78, stack_bottom:0xeadb2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-4" (TID:0x897cf8, sys_thread_t:0x897c30, state:MW, thread_t: t@14, threadID:0xeadf1d78, stack_bottom:0xeadf2000, stack_size:0x20000) prio=5
[1] java.sql.DriverManager.println(DriverManager.java:364)
[2] weblogic.jdbcbase.oci.Statement.private_parse(Statement.java:687)
[3] weblogic.jdbc.oci.Connection.prepareCall(Connection.java:52)
[4] weblogic.jdbc.pool.Connection.prepareCall(Connection.java:71)
[5] com.zaplet.schema.UserSP.execute1(UserSP.java:185)
[6] com.zaplet.schema.UserSP.execute(UserSP.java:159)
[7] com.zaplet.UserUtils.checkAndAddUser(UserUtils.java:51)
[8] com.zaplet.Zaplet.createMessageObject(Zaplet.java:1588)
[9] com.zaplet.Zaplet.storeZaplet(Zaplet.java:1083)
[10] com.zaplet.StoreCreateServlet.handleStoreCreate(StoreCreateServlet.java:246)
[11] com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:158)
[12] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:41)
[13] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[14] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[15] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[16] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[17] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[18] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
[19] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
[20] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[21] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:102)
[26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-3" (TID:0x8980f8, sys_thread_t:0x898030, state:CW, thread_t: t@13, threadID:0xeafd1d78, stack_bottom:0xeafd2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-2" (TID:0x8b94f8, sys_thread_t:0x8b9430, state:CW, thread_t: t@12, threadID:0xeb3b1d78, stack_bottom:0xeb3b2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-1" (TID:0x92f978, sys_thread_t:0x92f8b0, state:CW, thread_t: t@11, threadID:0xeb3e1d78, stack_bottom:0xeb3e2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-0" (TID:0x921968, sys_thread_t:0x9218a0, state:CW, thread_t: t@10, threadID:0xebea1d78, stack_bottom:0xebea2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"TimeEventGenerator" (TID:0x8d9aa8, sys_thread_t:0x8d99e0, state:CW, thread_t: t@9, threadID:0xebed1d78, stack_bottom:0xebed2000, stack_size:0x20000) prio=5
[1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
[2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
[3] java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" (TID:0x8a7500, sys_thread_t:0x8a7438, state:CW, thread_t: t@8, threadID:0xed041d78, stack_bottom:0xed042000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:102)
[3] weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:116)
Exiting Thread (sys_thread_t:0xff30e2e8) : no stack
"Finalizer" (TID:0x2cfa80, sys_thread_t:0x2cf9b8, state:CW, thread_t: t@6, threadID:0xfe3e1d78, stack_bottom:0xfe3e2000, stack_size:0x20000) prio=8
[1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
[3] java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:124)
"Reference Handler" (TID:0x2cd2a0, sys_thread_t:0x2cd1d8, state:CW, thread_t: t@5, threadID:0xfec41d78, stack_bottom:0xfec42000, stack_size:0x20000) prio=10
[1] java.lang.Object.wait(Object.java:424)
[2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
"Signal dispatcher" (TID:0x2aa5f0, sys_thread_t:0x2aa528, state:MW, thread_t: t@4, threadID:0xfed41d78, stack_bottom:0xfed42000, stack_size:0x20000) prio=10
"main" (TID:0x38280, sys_thread_t:0x381b8, state:CW, thread_t: t@1, threadID:0x25118, stack_bottom:0xffbf0000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1787)
[3] java.lang.reflect.Method.invoke(Native Method)
[4] weblogic.Server.startServerDynamically(Server.java:107)
[5] weblogic.Server.main(Server.java:65)
[6] weblogic.Server.main(Server.java:55)
Yup, try toggling between Solaris JDK 1.2.2 and 1.3. We've also experienced
seg fault problems with a certain JDK + JDBC driver combo.
Gene
"sumanth" <[email protected]> wrote in message
news:[email protected]...
> seg fault errors according to weblogic can be caused by the following 3
> reasons
> 1) native muxer
> 2) jdbc 2 drivers
> 3) jvm
>
> I dont know what the first one means. We had faced one similar problem
but
> when we upgraded our jdk to 1.3 things were back to normal. (weblogic
> supports 1.2)
>
> -Sumanth
>
> "Viresh Jain" <[email protected]> wrote in message
> news:[email protected]...
> >
> > Hi,
> > I am using weblogic 5.1.0 under Solaris 8. Database is Oracle 8i
> Enterprise Edition Release 8.1.6.0.0.
> >
> > WebLogic crashes with following dump. I will be very thankful if someone
> can help me out.
> >
> > Thanks,
> > Viresh
> >
> > Dump is as follows :
> >
> > SIGSEGV 11 segmentation violation
> > si_signo [11]: SEGV
> > si_errno [0]:
> > si_code [1]: SEGV_MAPERR [addr: 0x14]
> >
> > stackpointer=E9CAEA68
> > "Thread-69" (TID:0x4873e90, sys_thread_t:0x4873dc8, state:CW, thread_t:
> t@138, threadID:0xe9c81d78, stack_bottom:0xe9c82000, stack_size:0x20000)
> prio=5
> >
> > [1] java.lang.Thread.sleep(Native Method)
> > [2] com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:173)
> > -------------------
> > "Thread-8" (TID:0x41c5a48, sys_thread_t:0x41c5980, state:R, thread_t:
> t@47, threadID:0xe9cb1d78, stack_bottom:0xe9cb2000, stack_size:0x20000)
> prio=5 current thread
> >
> > [1] weblogic.db.oci.OciCursor.exec(Native Method)
> > [2] weblogic.db.oci.OciCursor.oci_exec(OciCursor.java:1816)
> > [3] weblogic.jdbcbase.oci.Statement.executeUpdate(Statement.java:823)
> > [4] weblogic.jdbcbase.oci.Statement.execute(Statement.java:1351)
> > [5]
> weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:33)
> > [6]
>
com.zaplet.schema.GetNextDeliveriesSP.execute(GetNextDeliveriesSP.java:142)
> > [7] com.zaplet.core.DigestThread.getNextBatch(DigestThread.java:194)
> > [8] com.zaplet.core.DigestThread.deliverDigests(DigestThread.java:131)
> > [9] com.zaplet.core.DigestThread.run(DigestThread.java:109)
> > -------------------
> > "Thread-1" (TID:0x3f292e0, sys_thread_t:0x3f29218, state:CW, thread_t:
> t@37, threadID:0xe9ce1d78, stack_bottom:0xe9ce2000, stack_size:0x20000)
> prio=5
> >
> > [1] java.lang.Thread.sleep(Native Method)
> > [2] com.zaplet.util.WorkerThread.run(WorkerThread.java:32)
> > -------------------
> > "SSLListenThread" (TID:0x3d05d08, sys_thread_t:0x3d05c40, state:R,
> thread_t: t@36, threadID:0xe9d41d78, stack_bottom:0xe9d42000,
> stack_size:0x20000) prio=5
> >
> > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> > [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
> > [4] java.net.ServerSocket.accept(ServerSocket.java:224)
> > [5]
>
weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
> :121)
> > [6]
weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
> > [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> > -------------------
> > "ListenThread" (TID:0x742500, sys_thread_t:0x742438, state:R, thread_t:
> t@35, threadID:0xe9f01d78, stack_bottom:0xe9f02000, stack_size:0x20000)
> prio=5
> >
> > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> > [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
> > [4] java.net.ServerSocket.accept(ServerSocket.java:223)
> > [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> > -------------------
> > "NBExecuteThread-1" (TID:0x8ee3d0, sys_thread_t:0x8ee308, state:CW,
> thread_t: t@31, threadID:0xe9f31d78, stack_bottom:0xe9f32000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "NBExecuteThread-0" (TID:0x8d8cc8, sys_thread_t:0x8d8c00, state:CW,
> thread_t: t@30, threadID:0xe9f81d78, stack_bottom:0xe9f82000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-19" (TID:0x8ec930, sys_thread_t:0x8ec868, state:MW,
> thread_t: t@29, threadID:0xe9fb1d78, stack_bottom:0xe9fb2000,
> stack_size:0x20000) prio=5
> >
> > [1]
> weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> > [2]
> weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-18" (TID:0x8d94c8, sys_thread_t:0x8d9400, state:R,
> thread_t: t@28, threadID:0xea001d78, stack_bottom:0xea002000,
> stack_size:0x20000) prio=5
> >
> > [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
> > [2]
> weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> > [3]
> weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> > [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-17" (TID:0x8f5100, sys_thread_t:0x8f5038, state:MW,
> thread_t: t@27, threadID:0xea031d78, stack_bottom:0xea032000,
> stack_size:0x20000) prio=5
> >
> > [1]
> weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> > [2]
> weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-16" (TID:0x8a1508, sys_thread_t:0x8a1440, state:CW,
> thread_t: t@26, threadID:0xea081d78, stack_bottom:0xea082000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-15" (TID:0x8d8738, sys_thread_t:0x8d8670, state:MW,
> thread_t: t@25, threadID:0xea0b1d78, stack_bottom:0xea0b2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.sql.DriverManager.getConnection(DriverManager.java:104)
> > [2] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
> > [3] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
> > [4] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
> > [5] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
> > [6] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
> > [7]
>
jsp._layout3._snippets._author._defaultEndWire._jspService(_defaultEndWire.j
> ava:69)
> > [8] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > [9]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [10]
>
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
> l.java:200)
> > [11]
>
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
> l.java:172)
> > [12]
> weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:105)
> > [13] jsp._sending._sentokay._jspService(_sentokay.java:69)
> > [14] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > [15]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [16]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:96)
> > [17] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [18]
> com.zaplet.StoreCreateServlet.sendMessage(StoreCreateServlet.java:510)
> > [19]
com.zaplet.StoreCreateServlet.handleSend(StoreCreateServlet.java:272)
> > [20]
>
com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:163)
> > [21] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:78)
> > [22] javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
> > [23] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [24]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [25]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:154)
> > [26] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [27] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
> > [28] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
> > [29] javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
> > [30] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> > [31]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > ... remainder of stack truncated ...
> > -------------------
> > "ExecuteThread-14" (TID:0x8e40d0, sys_thread_t:0x8e4008, state:CW,
> thread_t: t@24, threadID:0xea101d78, stack_bottom:0xea102000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-13" (TID:0x8facd8, sys_thread_t:0x8fac10, state:CW,
> thread_t: t@23, threadID:0xea131d78, stack_bottom:0xea132000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-12" (TID:0x8e0cf8, sys_thread_t:0x8e0c30, state:CW,
> thread_t: t@22, threadID:0xea181d78, stack_bottom:0xea182000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-11" (TID:0x938018, sys_thread_t:0x937f50, state:CW,
> thread_t: t@21, threadID:0xea1b1d78, stack_bottom:0xea1b2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-10" (TID:0x936e40, sys_thread_t:0x936d78, state:MW,
> thread_t: t@20, threadID:0xea201d78, stack_bottom:0xea202000,
> stack_size:0x20000) prio=5
> >
> > [1] java.sql.DriverManager.getConnection(DriverManager.java:104)
> > [2] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
> > [3] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
> > [4] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
> > [5] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
> > [6] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
> > [7] jsp._errors._index._jspService(_index.java:69)
> > [8] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > [9]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [10]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:96)
> > [11] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [12]
>
com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:160)
> > [13] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:41)
> > [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> > [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [16]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [17]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:96)
> > [18] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [19] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
> > [20] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
> > [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> > [22] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [23]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [24]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:723)
> > [25]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:707)
> > [26]
>
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
> Manager.java:102)
> > [27]
>
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
> > [28]
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
> > [29] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-9" (TID:0x8a2ce8, sys_thread_t:0x8a2c20, state:CW,
> thread_t: t@19, threadID:0xea231d78, stack_bottom:0xea232000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-8" (TID:0x934cb0, sys_thread_t:0x934be8, state:CW,
> thread_t: t@18, threadID:0xea281d78, stack_bottom:0xea282000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-7" (TID:0x885108, sys_thread_t:0x885040, state:CW,
> thread_t: t@17, threadID:0xea2b1d78, stack_bottom:0xea2b2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-6" (TID:0x8a6cf8, sys_thread_t:0x8a6c30, state:CW,
> thread_t: t@16, threadID:0xea2f1d78, stack_bottom:0xea2f2000,
> stack_size:0x20000) prio=5
> >
> > [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
> > [2]
>
weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:56
> 1)
> > [3]
>
weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:55
> 5)
> > [4]
>
weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator
> .java:544)
> > [5]
>
weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:162
> )
> > [6]
>
weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.
> java:145)
> > [7] weblogic.jdbcbase.pool.Driver.connect(Driver.java:65)
> > [8] java.sql.DriverManager.getConnection(DriverManager.java:433)
> > [9] java.sql.DriverManager.getConnection(DriverManager.java:104)
> > [10] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
> > [11] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
> > [12] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
> > [13] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
> > [14] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
> > [15] jsp._authorpages._contacts._jspService(_contacts.java:96)
> > [16] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > [17]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [18]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:723)
> > [19]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:707)
> > [20]
>
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
> Manager.java:102)
> > [21]
>
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
> > [22]
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
> > [23] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-5" (TID:0x92be00, sys_thread_t:0x92bd38, state:CW,
> thread_t: t@15, threadID:0xeadb1d78, stack_bottom:0xeadb2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-4" (TID:0x897cf8, sys_thread_t:0x897c30, state:MW,
> thread_t: t@14, threadID:0xeadf1d78, stack_bottom:0xeadf2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.sql.DriverManager.println(DriverManager.java:364)
> > [2] weblogic.jdbcbase.oci.Statement.private_parse(Statement.java:687)
> > [3] weblogic.jdbc.oci.Connection.prepareCall(Connection.java:52)
> > [4] weblogic.jdbc.pool.Connection.prepareCall(Connection.java:71)
> > [5] com.zaplet.schema.UserSP.execute1(UserSP.java:185)
> > [6] com.zaplet.schema.UserSP.execute(UserSP.java:159)
> > [7] com.zaplet.UserUtils.checkAndAddUser(UserUtils.java:51)
> > [8] com.zaplet.Zaplet.createMessageObject(Zaplet.java:1588)
> > [9] com.zaplet.Zaplet.storeZaplet(Zaplet.java:1083)
> > [10]
>
com.zaplet.StoreCreateServlet.handleStoreCreate(StoreCreateServlet.java:246)
> > [11]
>
com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:158)
> > [12] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:41)
> > [13] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> > [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [15]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [16]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:96)
> > [17] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [18] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
> > [19] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
> > [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> > [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [22]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [23]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:723)
> > [24]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:707)
> > [25]
>
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
> Manager.java:102)
> > [26]
>
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
> > [27]
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
> > [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-3" (TID:0x8980f8, sys_thread_t:0x898030, state:CW,
> thread_t: t@13, threadID:0xeafd1d78, stack_bottom:0xeafd2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-2" (TID:0x8b94f8, sys_thread_t:0x8b9430, state:CW,
> thread_t: t@12, threadID:0xeb3b1d78, stack_bottom:0xeb3b2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-1" (TID:0x92f978, sys_thread_t:0x92f8b0, state:CW,
> thread_t: t@11, threadID:0xeb3e1d78, stack_bottom:0xeb3e2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-0" (TID:0x921968, sys_thread_t:0x9218a0, state:CW,
> thread_t: t@10, threadID:0xebea1d78, stack_bottom:0xebea2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "TimeEventGenerator" (TID:0x8d9aa8, sys_thread_t:0x8d99e0, state:CW,
> thread_t: t@9, threadID:0xebed1d78, stack_bottom:0xebed2000,
> stack_size:0x20000) prio=5
> >
> > [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
> > [2]
>
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
> :131)
> > [3] java.lang.Thread.run(Thread.java:479)
> > -------------------
> > "SpinnerRandomSource" (TID:0x8a7500, sys_thread_t:0x8a7438, state:CW,
> thread_t: t@8, threadID:0xed041d78, stack_bottom:0xed042000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2]
>
weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:10
> 2)
> > [3]
weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:116)
> > -------------------
> >
> > Exiting Thread (sys_thread_t:0xff30e2e8) : no stack
> > "Finalizer" (TID:0x2cfa80, sys_thread_t:0x2cf9b8, state:CW, thread_t:
t@6,
> threadID:0xfe3e1d78, stack_bottom:0xfe3e2000, stack_size:0x20000) prio=8
> >
> > [1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
> > [2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
> > [3]
>
java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:1
> 24)
> > -------------------
> > "Reference Handler" (TID:0x2cd2a0, sys_thread_t:0x2cd1d8, state:CW,
> thread_t: t@5, threadID:0xfec41d78, stack_bottom:0xfec42000,
> stack_size:0x20000) prio=10
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
> > -------------------
> > "Signal dispatcher" (TID:0x2aa5f0, sys_thread_t:0x2aa528, state:MW,
> thread_t: t@4, threadID:0xfed41d78, stack_bottom:0xfed42000,
> stack_size:0x20000) prio=10
> >
> > -------------------
> > "main" (TID:0x38280, sys_thread_t:0x381b8, state:CW, thread_t: t@1,
> threadID:0x25118, stack_bottom:0xffbf0000, stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1787)
> > [3] java.lang.reflect.Method.invoke(Native Method)
> > [4] weblogic.Server.startServerDynamically(Server.java:107)
> > [5] weblogic.Server.main(Server.java:65)
> > [6] weblogic.Server.main(Server.java:55)
> > -------------------
> >
> >
>
-
VM related parameters on Solaris
The WL documentation for Solaris specifies some parameters to be set for
the JDK1.2.2_05a:
-Xgenconfig:64m,64m,semispaces:64m,512m,markcompact
We are currently using the -Xms and -Xmx options
How all these options relate to each other ? For example if you set N
meg of memeory for the heap size, what value should I put for the
genconfig options ?
Thanks for any info (the javasoft site is not helpful at all)
Olivier
[olivier.vcf]The impact of garbage collection is one of those things that seems to be very
dependent on the application and the (hardware/software) environment. On some
applications, I have seen that tuning the GC has made a significant difference
while others I have seen almost no noticable improvement no matter what we did...
Presumably, if you are creating a large number of temporary objects as a normal
part of processing a request, then increasing the size of the new heap could
potentially improve performance.
Olivier Brand wrote:
Thanks Robert,
That helps a lot, since I don't like to set those kind of parameters without
understanding the outcomes. Now I feel (a little bit) better.
have you seen some major improvments or better garbage collections taking place
Olivier
Robert Patrick wrote:
Although I am no expert on exactly what each of these parameters do, in
general they control the genrational garbage collector in the Solaris JDK
1.2.x JVM. The first two numbers (i.e., 64m,64m) control the minimum and
maximum size of the "young heap" (the place where all new objects initially
go); the last two numbers (i.e., 64m,512m) control the size of the "old
heap" where objects are eventually moved if they continue to be used for
some amount of time.
I was told by a SUN guy working at their performance center that you must
keep these numbers and -Xms and -Xms in sync so that the numbers specified
for the generational garbage collector are less than or equal to the
corresponding number specified in -Xms and -Xmx. For example, 64m max young
heap size + 512m max old heap size means that -Xmx must be greater than or
equal to 576m.
Hope this helps,
Robert
Olivier Brand wrote:
The WL documentation for Solaris specifies some parameters to be set for
the JDK1.2.2_05a:
-Xgenconfig:64m,64m,semispaces:64m,512m,markcompact
We are currently using the -Xms and -Xmx options
How all these options relate to each other ? For example if you set N
meg of memeory for the heap size, what value should I put for the
genconfig options ?
Thanks for any info (the javasoft site is not helpful at all)
Olivier -
Launch RCU utility on Solaris in CLI mode
Hi ,
We have a scenario to launch RCU utility to create MDS schema from Solaris machine.
The RCU utility can be launched only on Linux and Windows.
We have tried the following workaround to launch on Solaris and this seems to be going well.
Copied the executable (/bin/rcu) shell script as "/bin/rcu_solaris"
User Solaris JDK on the executable shell script (bin/rcu_solaris’) i.e.JRE_DIR="/sparcv9/packages/jdk/jdk1.6.0_33" in place default Linux JDK.
Can someone suggest whether it's only the JDK dependency which is stopping RCU to be launched on other platforms(Solaris) and any gaps with the above approach?
Thanks,
RajeshHi Erik,
As part of our automation framework, we are trying to automate this end to end application installation setup process(including MDS schema creation using RCU ) and we are in the process of certifying the automation process on other platforms like Solaris.
If this has to be launched only on Windows or Linux then it has to be manual process. therefore, we have tried this workaround of pointing to a Solaris JDK and launched it successfully.
We use this tool only to create MDS schema as a pre-installation step. Also, we believe from FMW 12c onwards this is part of Weblogic and should be able to launch on other platforms as well.
Just for the MDS schema creation with PS5 release, should we go with the mentioned approach of launching it on Solaris ? Considering that We will not disturb the original (/bin/rcu) executable shell script. We always take a copy(say /bin/rcu_solaris ) with Solaris JDK added for running it.
Appreciate your inputs on this.
Thanks,
Rajesh -
Linux crash (XtWindowOfObject), 1.3.1
Hello
I am seeing jvm crashes when running applications on linux, with java2 SE, 1.3.1. These crashes do not happen on the solaris jdk. It is actually a jvm crash, not an Error or Exception.
This only happens after I call JPopupMenu.setDefaultLightWeightPopupEnabled(false), (which is required as I have java3d components in the application and I would like the menus to appear in front of the java3d components) and while the user is manipulating menus.
The crash is not dependent on using java3d. I have attached the smallest program that can reproduce the crash, and it's pretty small. Javadoc comments in the code explain how to reproduce this. I have also attached one of the hs_err_pid<n> files that is produced by the crash.
I have searched through java.sun.com for all sorts of combinations of keywords, but haven't found anything that resembles this, although that doesn't mean it's not there.
Has anyone else seen this? Is there a solution or workaround (besides using lightweight menus)? Or perhaps it's a known bug that I didn't find in my searching...
Thanks
Russell
import javax.swing.JFrame;
import javax.swing.JMenu;
import javax.swing.JMenuBar;
import javax.swing.JMenuItem;
import javax.swing.JPopupMenu;
/** A class to demonstrate jvm crashes that occur sometime after
JPopupMenu.setDefaultLightWeightPopupEnabled(false) is called, on the
linux platform with Sun jdk 1.3.1, and blackdown jdk 1.3.1.
<p>To demonstrate the crash, compile and run this class. Drop down Menu
1, do not release the mouse button, and then move the mouse over both
Menus and the Menu items continuously. The jvm crash should occur within
a few seconds, although it can sometimes take up to a minute. And
occasionally (about one time in 10) the app will not crash.
<p>According to the dump, the jvm catches an unexpected Signal 11 inside
/usr/X11R6/lib/libXt.so.6, in function XtWindowOfObject (sometimes it
reports _XtWindowedAncestor.)
<p>This crash has been demonstrated on several different machines:
<ul>
<li>Debian woody, with XFree86 4.1.0, and mga_drv.o from the DRI
project.</li>
<li>Redhat 7.1 with XFree86 4.0.3.</li>
<li>Redhat 7.1 with Xaccel from Xi Graphics</li>
<li>Redhat 7.1 with XFree86 4.0.3, using a Sun Ultra 10 with Solaris 7 as
X display.</li>
</ul>
<p>This crash has not been seen on the solaris jdk.
public class CrashTest1
public CrashTest1()
// This is the guilty line. Remove this line, and the app doesn't crash.
JPopupMenu.setDefaultLightWeightPopupEnabled(false);
JFrame jframe = new JFrame("CrashTest1!!!");
JMenuBar jmenubar = new JMenuBar();
JMenu jmenu1 = new JMenu("Menu 1");
jmenu1.add(new JMenuItem("Item 1"));
jmenubar.add(jmenu1);
JMenu jmenu2 = new JMenu("Menu 2");
jmenu2.add(new JMenuItem("Item 2"));
jmenubar.add(jmenu2);
jframe.setJMenuBar(jmenubar);
jframe.setSize(new java.awt.Dimension(400,300));
jframe.setVisible(true);
public static void main(String[] args) {
CrashTest1 crash = new CrashTest1();
}Here is one of the hs_err_pid* files:
4001a000-4001b000 r--p 00000000 09:02 430291 /usr/lib/locale/en_AU/LC_TELEPHONE
4001b000-4001c000 r--p 00000000 09:02 159413 /usr/lib/locale/en_AU/LC_ADDRESS
4001c000-4001d000 r--p 00000000 09:02 159418 /usr/lib/locale/en_AU/LC_NAME
4001d000-4001e000 r--p 00000000 09:02 31935 /usr/lib/locale/en_AU/LC_PAPER
4001e000-4001f000 r--p 00000000 09:02 47861 /usr/lib/locale/en_AU/LC_MESSAGES/SYS_LC_MESSAGES
4001f000-40020000 r--p 00000000 09:02 430290 /usr/lib/locale/en_AU/LC_MONETARY
40020000-40021000 r--p 00000000 09:02 111582 /usr/lib/locale/en_AU/LC_TIME
40021000-4002e000 r-xp 00000000 09:01 108422 /lib/i686/libpthread-0.9.so
4002e000-40036000 rw-p 0000c000 09:01 108422 /lib/i686/libpthread-0.9.so
40036000-4003f000 r-xp 00000000 09:02 256346 /usr/java/jdk1.3.1/jre/lib/i386/native_threads/libhpi.so
4003f000-40040000 rw-p 00008000 09:02 256346 /usr/java/jdk1.3.1/jre/lib/i386/native_threads/libhpi.so
40040000-402a7000 r-xp 00000000 09:02 17335 /usr/java/jdk1.3.1/jre/lib/i386/client/libjvm.so
402a7000-4040d000 rw-p 00266000 09:02 17335 /usr/java/jdk1.3.1/jre/lib/i386/client/libjvm.so
40424000-40427000 r-xp 00000000 09:01 216849 /lib/libdl-2.2.2.so
40427000-40428000 rw-p 00002000 09:01 216849 /lib/libdl-2.2.2.so
40428000-4054e000 r-xp 00000000 09:01 108418 /lib/i686/libc-2.2.2.so
4054e000-40554000 rw-p 00125000 09:01 108418 /lib/i686/libc-2.2.2.so
40558000-4056b000 r-xp 00000000 09:01 216854 /lib/libnsl-2.2.2.so
4056b000-4056d000 rw-p 00012000 09:01 216854 /lib/libnsl-2.2.2.so
4056f000-40592000 r-xp 00000000 09:01 108420 /lib/i686/libm-2.2.2.so
40592000-40593000 rw-p 00022000 09:01 108420 /lib/i686/libm-2.2.2.so
40594000-405c8000 r-xp 00000000 09:02 414473 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
405c8000-405d4000 rw-p 00033000 09:02 414473 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
405d6000-405e7000 r-xp 00000000 09:02 463560 /usr/java/jdk1.3.1/jre/lib/i386/libverify.so
405e7000-405e9000 rw-p 00010000 09:02 463560 /usr/java/jdk1.3.1/jre/lib/i386/libverify.so
405e9000-4060a000 r-xp 00000000 09:02 463551 /usr/java/jdk1.3.1/jre/lib/i386/libjava.so
4060a000-4060c000 rw-p 00020000 09:02 463551 /usr/java/jdk1.3.1/jre/lib/i386/libjava.so
4060d000-40621000 r-xp 00000000 09:02 463561 /usr/java/jdk1.3.1/jre/lib/i386/libzip.so
40621000-40624000 rw-p 00013000 09:02 463561 /usr/java/jdk1.3.1/jre/lib/i386/libzip.so
40624000-4133d000 r--s 00000000 09:02 304193 /usr/java/jdk1.3.1/jre/lib/rt.jar
4136a000-4160f000 r--s 00000000 09:02 304186 /usr/java/jdk1.3.1/jre/lib/i18n.jar
4160f000-41625000 r--s 00000000 09:02 304194 /usr/java/jdk1.3.1/jre/lib/sunrsasign.jar
436cd000-436ce000 r--p 00000000 09:02 430316 /usr/lib/locale/en_AU/LC_NUMERIC
49d2f000-49d4a000 r--p 00000000 09:02 462196 /usr/lib/locale/en_AU/LC_CTYPE
49d4a000-49d50000 r--p 00000000 09:02 95665 /usr/lib/locale/en_AU/LC_COLLATE
49d50000-49d57000 r--s 00000000 09:07 275595 /home/russells/java/15-jaxp.jar
49d59000-49d63000 r-xp 00000000 09:01 216870 /lib/libnss_files-2.2.2.so
49d63000-49d64000 rw-p 00009000 09:01 216870 /lib/libnss_files-2.2.2.so
4a5d0000-4a5ed000 r--s 00000000 09:02 336024 /usr/java/jdk1.3.1/jre/lib/ext/j3daudio.jar
4a5ed000-4a5f3000 r-xp 00000000 09:02 32185 /usr/X11R6/lib/libXp.so.6.2
4a5f3000-4a5f5000 rw-p 00005000 09:02 32185 /usr/X11R6/lib/libXp.so.6.2
4a5f5000-4a5f9000 r-xp 00000000 09:02 32193 /usr/X11R6/lib/libXtst.so.6.1
4a5f9000-4a5fa000 rw-p 00003000 09:02 32193 /usr/X11R6/lib/libXtst.so.6.1
4a5fa000-4a5fd000 r--s 00000000 09:07 275606 /home/russells/java/93-ftp.jar
4a5fd000-4a5ff000 r-xp 00000000 09:02 32110 /usr/lib/gconv/ISO8859-1.so
4a5ff000-4a600000 rw-p 00001000 09:02 32110 /usr/lib/gconv/ISO8859-1.so
4a700000-4a744000 r--s 00000000 09:02 336022 /usr/java/jdk1.3.1/jre/lib/ext/vecmath.jar
4a744000-4a93b000 r--s 00000000 09:02 336023 /usr/java/jdk1.3.1/jre/lib/ext/j3dcore.jar
4a93b000-4a9ec000 r--s 00000000 09:02 336025 /usr/java/jdk1.3.1/jre/lib/ext/j3dutils.jar
4a9ec000-4adb9000 r-xp 00000000 09:02 463545 /usr/java/jdk1.3.1/jre/lib/i386/libawt.so
4adb9000-4adc9000 rw-p 003cc000 09:02 463545 /usr/java/jdk1.3.1/jre/lib/i386/libawt.so
4adde000-4ae0f000 r-xp 00000000 09:02 463557 /usr/java/jdk1.3.1/jre/lib/i386/libmlib_image.so
4ae0f000-4ae11000 rw-p 00030000 09:02 463557 /usr/java/jdk1.3.1/jre/lib/i386/libmlib_image.so
4ae11000-4ae56000 r-xp 00000000 09:02 32191 /usr/X11R6/lib/libXt.so.6.0
4ae56000-4ae5a000 rw-p 00044000 09:02 32191 /usr/X11R6/lib/libXt.so.6.0
4ae5b000-4ae67000 r-xp 00000000 09:02 32175 /usr/X11R6/lib/libXext.so.6.4
4ae67000-4ae69000 rw-p 0000b000 09:02 32175 /usr/X11R6/lib/libXext.so.6.4
4ae69000-4af3c000 r-xp 00000000 09:02 32167 /usr/X11R6/lib/libX11.so.6.2
4af3c000-4af41000 rw-p 000d2000 09:02 32167 /usr/X11R6/lib/libX11.so.6.2
4af41000-4af48000 r-xp 00000000 09:02 32165 /usr/X11R6/lib/libSM.so.6.0
4af48000-4af4a000 rw-p 00006000 09:02 32165 /usr/X11R6/lib/libSM.so.6.0
4af4a000-4af5d000 r-xp 00000000 09:02 32161 /usr/X11R6/lib/libICE.so.6.3
4af5d000-4af5e000 rw-p 00012000 09:02 32161 /usr/X11R6/lib/libICE.so.6.3
4af60000-4b11a000 r--s 00000000 09:07 275591 /home/russells/java/11-xerces-1.4.3.jar
4b11a000-4b148000 r--s 00000000 09:07 275592 /home/russells/java/12-crimson.jar
4b148000-4b162000 r--s 00000000 09:07 275593 /home/russells/java/13-jdom-b7.jar
4b162000-4b226000 r--s 00000000 09:07 275594 /home/russells/java/14-xalan.jar
4b226000-4b232000 r--s 00000000 09:07 275608 /home/russells/java/31-visad_mods.jar
4b232000-4b687000 r--s 00000000 09:07 275597 /home/russells/java/32-visad.jar
4b687000-4b805000 r--s 00000000 09:07 275598 /home/russells/java/51-classes12_01.zip
4b805000-4b813000 r--s 00000000 09:07 275599 /home/russells/java/52-jdev-rt.zip
4b813000-4b879000 r--s 00000000 09:07 275600 /home/russells/java/61-ant.jar
4b879000-4b8ba000 r--s 00000000 09:07 275601 /home/russells/java/62-optional.jar
4b8ba000-4b923000 r--s 00000000 09:07 275602 /home/russells/java/73-mapdata.jar
4b923000-4b942000 r--s 00000000 09:07 275603 /home/russells/java/74-jlfgr-1_0.jar
4b942000-4b95c000 r--s 00000000 09:07 275604 /home/russells/java/75-aifs2.jar
4b95c000-4b977000 r--s 00000000 09:07 275605 /home/russells/java/91-bom-util-prefs.jar
4b977000-4b9cc000 r--s 00000000 09:07 275607 /home/russells/java/94-jh.jar
4b9cc000-4be4b000 r--s 00000000 09:02 97002 /usr/java/jdk1.3.1/lib/tools.jar
4be4b000-4bed5000 r-xp 00000000 09:02 463548 /usr/java/jdk1.3.1/jre/lib/i386/libfontmanager.so
4bed5000-4bee5000 rw-p 00089000 09:02 463548 /usr/java/jdk1.3.1/jre/lib/i386/libfontmanager.so
Local Time = Wed Oct 31 17:15:41 2001
Elapsed Time = 64
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode)My original post had a truncated hs_err_pid file. Here's a complete one.
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x4ae2fbe7
Function name=XtWindowOfObject
Library=/usr/X11R6/lib/libXt.so.6
Current Java thread:
at sun.awt.motif.MComponentPeer.setCursor(Native Method)
at sun.awt.motif.MComponentPeer.initialize(MComponentPeer.java:123)
at sun.awt.motif.MComponentPeer.init(MComponentPeer.java:175)
at sun.awt.motif.MComponentPeer.<init>(MComponentPeer.java:179)
at sun.awt.motif.MCanvasPeer.<init>(MCanvasPeer.java:25)
at sun.awt.motif.MPanelPeer.<init>(MPanelPeer.java:22)
at sun.awt.motif.MToolkit.createPanel(MToolkit.java:150)
at java.awt.Panel.addNotify(Panel.java:73)
at java.awt.Container.addImpl(Container.java:374)
at javax.swing.JLayeredPane.addImpl(JLayeredPane.java:201)
at java.awt.Container.add(Container.java:284)
at javax.swing.DefaultPopupFactory$PanelPopup.show(DefaultPopupFactory.java:1111)
at javax.swing.JPopupMenu.setVisible(JPopupMenu.java:612)
at javax.swing.JPopupMenu.show(JPopupMenu.java:737)
at javax.swing.JMenu.setPopupMenuVisible(JMenu.java:311)
at javax.swing.JPopupMenu.menuSelectionChanged(JPopupMenu.java:1084)
at javax.swing.MenuSelectionManager.setSelectedPath(MenuSelectionManager.java:84)
at javax.swing.plaf.basic.BasicMenuUI$MenuDragMouseHandler.menuDragMouseDragged(BasicMenuUI.java:776)
at javax.swing.JMenuItem.fireMenuDragMouseDragged(JMenuItem.java:529)
at javax.swing.JMenuItem.processMenuDragMouseEvent(JMenuItem.java:450)
at javax.swing.JMenuItem.processMouseEvent(JMenuItem.java:400)
at javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:264)
at javax.swing.plaf.basic.BasicMenuUI$MouseInputHandler.mouseDragged(BasicMenuUI.java:364)
at java.awt.AWTEventMulticaster.mouseDragged(AWTEventMulticaster.java:260)
at java.awt.Component.processMouseMotionEvent(Component.java:3759)
at javax.swing.JComponent.processMouseMotionEvent(JComponent.java:2299)
at java.awt.Component.processEvent(Component.java:3548)
at java.awt.Container.processEvent(Container.java:1164)
at java.awt.Component.dispatchEventImpl(Component.java:2593)
at java.awt.Container.dispatchEventImpl(Container.java:1213)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2451)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:2205)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2125)
at java.awt.Container.dispatchEventImpl(Container.java:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:339)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
Dynamic libraries:
08048000-0804c000 r-xp 00000000 09:02 304134 /usr/java/jdk1.3.1/bin/i386/native_threads/java
0804c000-0804d000 rw-p 00003000 09:02 304134 /usr/java/jdk1.3.1/bin/i386/native_threads/java
40000000-40016000 r-xp 00000000 09:01 216836 /lib/ld-2.2.2.so
40016000-40017000 rw-p 00015000 09:01 216836 /lib/ld-2.2.2.so
40018000-40019000 r--p 00000000 09:02 430289 /usr/lib/locale/en_AU/LC_IDENTIFICATION
40019000-4001a000 r--p 00000000 09:02 31931 /usr/lib/locale/en_AU/LC_MEASUREMENT
4001a000-4001b000 r--p 00000000 09:02 430291 /usr/lib/locale/en_AU/LC_TELEPHONE
4001b000-4001c000 r--p 00000000 09:02 159413 /usr/lib/locale/en_AU/LC_ADDRESS
4001c000-4001d000 r--p 00000000 09:02 159418 /usr/lib/locale/en_AU/LC_NAME
4001d000-4001e000 r--p 00000000 09:02 31935 /usr/lib/locale/en_AU/LC_PAPER
4001e000-4001f000 r--p 00000000 09:02 47861 /usr/lib/locale/en_AU/LC_MESSAGES/SYS_LC_MESSAGES
4001f000-40020000 r--p 00000000 09:02 430290 /usr/lib/locale/en_AU/LC_MONETARY
40020000-40021000 r--p 00000000 09:02 111582 /usr/lib/locale/en_AU/LC_TIME
40021000-4002e000 r-xp 00000000 09:01 108422 /lib/i686/libpthread-0.9.so
4002e000-40036000 rw-p 0000c000 09:01 108422 /lib/i686/libpthread-0.9.so
40036000-4003f000 r-xp 00000000 09:02 256346 /usr/java/jdk1.3.1/jre/lib/i386/native_threads/libhpi.so
4003f000-40040000 rw-p 00008000 09:02 256346 /usr/java/jdk1.3.1/jre/lib/i386/native_threads/libhpi.so
40040000-402a7000 r-xp 00000000 09:02 17335 /usr/java/jdk1.3.1/jre/lib/i386/client/libjvm.so
402a7000-4040d000 rw-p 00266000 09:02 17335 /usr/java/jdk1.3.1/jre/lib/i386/client/libjvm.so
40424000-40427000 r-xp 00000000 09:01 216849 /lib/libdl-2.2.2.so
40427000-40428000 rw-p 00002000 09:01 216849 /lib/libdl-2.2.2.so
40428000-4054e000 r-xp 00000000 09:01 108418 /lib/i686/libc-2.2.2.so
4054e000-40554000 rw-p 00125000 09:01 108418 /lib/i686/libc-2.2.2.so
40558000-4056b000 r-xp 00000000 09:01 216854 /lib/libnsl-2.2.2.so
4056b000-4056d000 rw-p 00012000 09:01 216854 /lib/libnsl-2.2.2.so
4056f000-40592000 r-xp 00000000 09:01 108420 /lib/i686/libm-2.2.2.so
40592000-40593000 rw-p 00022000 09:01 108420 /lib/i686/libm-2.2.2.so
40594000-405c8000 r-xp 00000000 09:02 414473 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
405c8000-405d4000 rw-p 00033000 09:02 414473 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
405d6000-405e7000 r-xp 00000000 09:02 463560 /usr/java/jdk1.3.1/jre/lib/i386/libverify.so
405e7000-405e9000 rw-p 00010000 09:02 463560 /usr/java/jdk1.3.1/jre/lib/i386/libverify.so
405e9000-4060a000 r-xp 00000000 09:02 463551 /usr/java/jdk1.3.1/jre/lib/i386/libjava.so
4060a000-4060c000 rw-p 00020000 09:02 463551 /usr/java/jdk1.3.1/jre/lib/i386/libjava.so
4060d000-40621000 r-xp 00000000 09:02 463561 /usr/java/jdk1.3.1/jre/lib/i386/libzip.so
40621000-40624000 rw-p 00013000 09:02 463561 /usr/java/jdk1.3.1/jre/lib/i386/libzip.so
40624000-4133d000 r--s 00000000 09:02 304193 /usr/java/jdk1.3.1/jre/lib/rt.jar
4136a000-4160f000 r--s 00000000 09:02 304186 /usr/java/jdk1.3.1/jre/lib/i18n.jar
4160f000-41625000 r--s 00000000 09:02 304194 /usr/java/jdk1.3.1/jre/lib/sunrsasign.jar
436cd000-436ce000 r--p 00000000 09:02 430316 /usr/lib/locale/en_AU/LC_NUMERIC
49d2f000-49d4a000 r--p 00000000 09:02 462196 /usr/lib/locale/en_AU/LC_CTYPE
49d4a000-49d50000 r--p 00000000 09:02 95665 /usr/lib/locale/en_AU/LC_COLLATE
49d50000-49d57000 r--s 00000000 09:07 275595 /home/russells/java/15-jaxp.jar
49d59000-49d63000 r-xp 00000000 09:01 216870 /lib/libnss_files-2.2.2.so
49d63000-49d64000 rw-p 00009000 09:01 216870 /lib/libnss_files-2.2.2.so
4a5d0000-4a5ed000 r--s 00000000 09:02 336024 /usr/java/jdk1.3.1/jre/lib/ext/j3daudio.jar
4a5ed000-4a5f3000 r-xp 00000000 09:02 32185 /usr/X11R6/lib/libXp.so.6.2
4a5f3000-4a5f5000 rw-p 00005000 09:02 32185 /usr/X11R6/lib/libXp.so.6.2
4a5f5000-4a5f9000 r-xp 00000000 09:02 32193 /usr/X11R6/lib/libXtst.so.6.1
4a5f9000-4a5fa000 rw-p 00003000 09:02 32193 /usr/X11R6/lib/libXtst.so.6.1
4a5fa000-4a5fd000 r--s 00000000 09:07 275606 /home/russells/java/93-ftp.jar
4a5fd000-4a5ff000 r-xp 00000000 09:02 32110 /usr/lib/gconv/ISO8859-1.so
4a5ff000-4a600000 rw-p 00001000 09:02 32110 /usr/lib/gconv/ISO8859-1.so
4a700000-4a744000 r--s 00000000 09:02 336022 /usr/java/jdk1.3.1/jre/lib/ext/vecmath.jar
4a744000-4a93b000 r--s 00000000 09:02 336023 /usr/java/jdk1.3.1/jre/lib/ext/j3dcore.jar
4a93b000-4a9ec000 r--s 00000000 09:02 336025 /usr/java/jdk1.3.1/jre/lib/ext/j3dutils.jar
4a9ec000-4adb9000 r-xp 00000000 09:02 463545 /usr/java/jdk1.3.1/jre/lib/i386/libawt.so
4adb9000-4adc9000 rw-p 003cc000 09:02 463545 /usr/java/jdk1.3.1/jre/lib/i386/libawt.so
4adde000-4ae0f000 r-xp 00000000 09:02 463557 /usr/java/jdk1.3.1/jre/lib/i386/libmlib_image.so
4ae0f000-4ae11000 rw-p 00030000 09:02 463557 /usr/java/jdk1.3.1/jre/lib/i386/libmlib_image.so
4ae11000-4ae56000 r-xp 00000000 09:02 32191 /usr/X11R6/lib/libXt.so.6.0
4ae56000-4ae5a000 rw-p 00044000 09:02 32191 /usr/X11R6/lib/libXt.so.6.0
4ae5b000-4ae67000 r-xp 00000000 09:02 32175 /usr/X11R6/lib/libXext.so.6.4
4ae67000-4ae69000 rw-p 0000b000 09:02 32175 /usr/X11R6/lib/libXext.so.6.4
4ae69000-4af3c000 r-xp 00000000 09:02 32167 /usr/X11R6/lib/libX11.so.6.2
4af3c000-4af41000 rw-p 000d2000 09:02 32167 /usr/X11R6/lib/libX11.so.6.2
4af41000-4af48000 r-xp 00000000 09:02 32165 /usr/X11R6/lib/libSM.so.6.0
4af48000-4af4a000 rw-p 00006000 09:02 32165 /usr/X11R6/lib/libSM.so.6.0
4af4a000-4af5d000 r-xp 00000000 09:02 32161 /usr/X11R6/lib/libICE.so.6.3
4af5d000-4af5e000 rw-p 00012000 09:02 32161 /usr/X11R6/lib/libICE.so.6.3
4af60000-4b11a000 r--s 00000000 09:07 275591 /home/russells/java/11-xerces-1.4.3.jar
4b11a000-4b148000 r--s 00000000 09:07 275592 /home/russells/java/12-crimson.jar
4b148000-4b162000 r--s 00000000 09:07 275593 /home/russells/java/13-jdom-b7.jar
4b162000-4b226000 r--s 00000000 09:07 275594 /home/russells/java/14-xalan.jar
4b226000-4b232000 r--s 00000000 09:07 275608 /home/russells/java/31-visad_mods.jar
4b232000-4b687000 r--s 00000000 09:07 275597 /home/russells/java/32-visad.jar
4b687000-4b805000 r--s 00000000 09:07 275598 /home/russells/java/51-classes12_01.zip
4b805000-4b813000 r--s 00000000 09:07 275599 /home/russells/java/52-jdev-rt.zip
4b813000-4b879000 r--s 00000000 09:07 275600 /home/russells/java/61-ant.jar
4b879000-4b8ba000 r--s 00000000 09:07 275601 /home/russells/java/62-optional.jar
4b8ba000-4b923000 r--s 00000000 09:07 275602 /home/russells/java/73-mapdata.jar
4b923000-4b942000 r--s 00000000 09:07 275603 /home/russells/java/74-jlfgr-1_0.jar
4b942000-4b95c000 r--s 00000000 09:07 275604 /home/russells/java/75-aifs2.jar
4b95c000-4b977000 r--s 00000000 09:07 275605 /home/russells/java/91-bom-util-prefs.jar
4b977000-4b9cc000 r--s 00000000 09:07 275607 /home/russells/java/94-jh.jar
4b9cc000-4be4b000 r--s 00000000 09:02 97002 /usr/java/jdk1.3.1/lib/tools.jar
4be4b000-4bed5000 r-xp 00000000 09:02 463548 /usr/java/jdk1.3.1/jre/lib/i386/libfontmanager.so
4bed5000-4bee5000 rw-p 00089000 09:02 463548 /usr/java/jdk1.3.1/jre/lib/i386/libfontmanager.so
Local Time = Wed Oct 31 17:15:41 2001
Elapsed Time = 64
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode) -
Heap Memory Issue in weblogic 9.2 for a JSF 1.1 web application
Hi,
We are running a JSF application (Myfaces, facelets, tomahawk, richfaces & iBATIS) in weblogic 9.2 server on Solaris 10. This application is deployed in production and works fine under normal circumstances. But when there is a heavy user load we are facing a memory issue. The memory usage is gradually increasing and when it reaches to max, Full GC kicks in again & again which choks up all requests. We don't save anything in session scope. All our backing beans are saved in request scope hence they should be garbage collected after each request done, but this is not happening.
We took the heap dump from production after this issue and analyzed it. After my analysis, I found all objects which are set in request object not being garbage collected and the root referers of all these objects is weblogic.servlet.internal.MuxableSocketHTTP.
I reproduced the similar behaviour in one of our development environment using JMeter. I ran 100 concurrent users in JMeter for almost 1 hour and saw the similar behaviour. Below is the result of all weblogic objects which are still hanging in heap after test was over (I also ran manual Garbage Collector from admin server).
1) weblogic.servlet.internal.MuxableSocketHTTP - 1774 objects - retained heap (1 GB)
2) weblogic.servlet.internal.ServletRequestImpl - 1774 objects - retained heap (1 GB)
My understanding is that every request made to weblogic server goes through the MuxableSocketHTTP object which creates the ServletRequestImpl to serve it. Once the request is served these objects are suppose to be removed. As a result of that whatever is saved in your request will still be hanging.
I am not able to understand why these objects are hanging after request is done. Could anybody answer to my question. I appreciate your help in advance.
The GC setting for weblogic server while startup is:
-XX:MaxTenuringThreshold=15 -XX:+PrintTenuringDistribution -XX:+AggressiveHeap -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:PermSize=128m -XX:MaxPermSize=128m -Xms3g -Xmx3g -XX:NewSize=512m -XX:MaxNewSize=1024m
Thanks MaKKWhat happened with this issue? We are seeing something similar on WebLogic 9.2 MP1 in Solaris (Jdk 1.5. patch 10. 32 bit). Out of Memory's with thousands if instances of weblogic.socket.MuxableSocket hanging around.
Our thinking was initally the Java heap, then we thought that maybe the sockets weren't being closed properly, possible in WebLogic or in LiveCycle.
Any info would be greatly appreciated.
Snippet of our stack trace:
<16-Feb-2010 04:30:13 o'clock GMT> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space
>
javax.ejb.EJBException: EJB encountered System Exception: : java.lang.OutOfMemoryError: Java heap space
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwEJBException(EJBRuntimeUtils.java:145)
at weblogic.ejb.container.internal.BaseLocalObject.postInvokeCleanup(BaseLocalObject.java:550)
at weblogic.ejb.container.internal.BaseLocalObject.postInvokeCleanup(BaseLocalObject.java:496)
at com.adobe.idp.um.businesslogic.directoryservices.DirectorySynchronizationManagerBean_f5g74_ELOImpl.synchronizeProviders(DirectorySynchronizationManagerBean_f5g74_ELOImpl.java:267)
Joel -
TransformerConfigurationException with Xalan 2.1, WL 6.0 sp2
On Solaris, jdk 1.3:
I'm using:
public void transform( AdviewsXMLDocument xmlDoc, PrintWriter outWriter )
throws CorporateException {
String media= null , title = null, charset = null;
try{
TransformerFactory tFactory = TransformerFactory.newInstance();
StringReader xmlReader = new StringReader( xmlDoc.toString() );
StreamSource streamSource = new StreamSource( xmlReader ) ;
Source stylesheet = tFactory.getAssociatedStylesheet( streamSource,
media, title, charset);
Transformer transformer = tFactory.newTransformer(stylesheet);
StreamResult streamResult = new StreamResult( outWriter ) ;
transformer.transform( streamSource , streamResult ) ;
} catch (Exception ex ) {
throw new CorporateException(
"XSLT transform exception: " + ex.toString(),
CorporateException.ERROR );
but getting:
XSLT transform exception:
javax.xml.transform.TransformerConfigurationException:
getAssociatedStylesheets failed
The startup script does set the Transformer property:
.. -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Trans
formerFactoryImpl ...
The xml document ( inherited from the ecs XMLDocument ) passed has:
<?xml-stylesheet href="style/portal.xsl" type="text/xsl"?>
and it parses successfully when used against the command line of Xalan.
( The "style" directory is directly under the application's root directory
within the war within the ear ).
Apparently the org.apache.xalan.processor.TransformerFactoryImpl is throwing
a org.xml.sax.SAXException, which then produces the
"getAssociatedStylesheets failed", but why?
Any ideas?
Charlie Crook
Nielsen Media ResearchOn Solaris, jdk 1.3:
I'm using:
public void transform( AdviewsXMLDocument xmlDoc, PrintWriter outWriter )
throws CorporateException {
String media= null , title = null, charset = null;
try{
TransformerFactory tFactory = TransformerFactory.newInstance();
StringReader xmlReader = new StringReader( xmlDoc.toString() );
StreamSource streamSource = new StreamSource( xmlReader ) ;
Source stylesheet = tFactory.getAssociatedStylesheet( streamSource,
media, title, charset);
Transformer transformer = tFactory.newTransformer(stylesheet);
StreamResult streamResult = new StreamResult( outWriter ) ;
transformer.transform( streamSource , streamResult ) ;
} catch (Exception ex ) {
throw new CorporateException(
"XSLT transform exception: " + ex.toString(),
CorporateException.ERROR );
but getting:
XSLT transform exception:
javax.xml.transform.TransformerConfigurationException:
getAssociatedStylesheets failed
The startup script does set the Transformer property:
.. -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Trans
formerFactoryImpl ...
The xml document ( inherited from the ecs XMLDocument ) passed has:
<?xml-stylesheet href="style/portal.xsl" type="text/xsl"?>
and it parses successfully when used against the command line of Xalan.
( The "style" directory is directly under the application's root directory
within the war within the ear ).
Apparently the org.apache.xalan.processor.TransformerFactoryImpl is throwing
a org.xml.sax.SAXException, which then produces the
"getAssociatedStylesheets failed", but why?
Any ideas?
Charlie Crook
Nielsen Media Research -
Hi,
We are converting German and English DATA to XML. And
German data (UTF-8) is running through the system fine if I logged
and tested. But strangely its giving ?? chars when I run as a
different user. (Sun Solaris / JDK 1.4)
When I looks at the properties.
for me:
file.encoding = ISO8859-1
for the other user its
file.encoding=ISO646-US
Where is this property being set, and how can I change it. This is
killing me.. I could not find any thing on my system that enforces the
char set. I am not using any special writers or readers..
Thanks in advance
- RaviI do not think that the Latin-1 Supplement characters
\u00c4\u00e4\u00df\u00dc\u00fc\u00d6\u00f6
(used in German)
which are encoded in UTF-8 can be displayed correctly with other encoding than UTF-8, to my knowledge.
I suppose your browser automatically sets encoding to UTF-8 when reading those data while other users' browsers do not. -
WLS51 sp6 shutdown - java.lang.ThreadDeath?
Hi,
I'm trying to install WLS 5.1.0 sp6 on Solaris. I'm using Sun's
Solaris JDK 1.2.1_04, and yes I disabled aggressive JIT inlining.
The server starts up fine, but shut down seems to have a problem
Should I be worried about the following log messages?
Thanks for any reassurance/help,
and apologies if this stuff is normal -
Serge Monkewitz
log snippet
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Disable Server Logins
requested by system
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server Logins are now
disabled
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server shutdown by
system
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server shutdown
commencing NOW
Tue Nov 07 22:59:08 PST 2000:<A> <ListenThread> ListenThread.run()
failed:
java.lang.ThreadDeath
Tue Nov 07 22:59:08 PST 2000:<!> <ListenThread> **** The WebLogic Server
is no longer listening for connections.
Tue Nov 07 22:59:08 PST 2000:<!> <ListenThread> **** You should probably
restart it.
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server shutdown by
system
Tue Nov 07 22:59:08 PST 2000:<A> <SSLListenThread> ListenThread.run()
failed:
java.lang.ThreadDeath
Tue Nov 07 22:59:08 PST 2000:<!> <SSLListenThread> **** The WebLogic
Server is no longer listening for connections.
Tue Nov 07 22:59:08 PST 2000:<!> <SSLListenThread> **** You should
probably restart it.
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server shutdown by
system
Tue Nov 07 22:59:08 PST 2000:<I> <CliCon-#|myserver|2.973666172756>
Connection to client for ClientContext - id:
'#|myserver|2.973666172756', bound: 'true', dead: 'false' has been
unexpectedly lost because weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException].
Initiating hard disconnect.
Tue Nov 07 22:59:08 PST 2000:<I> <CliCon-#|myserver|2.973666172756>
Removing ClientContext - id: '#|myserver|2.973666172756', bound:
'false', dead: 'false' because of hard disconnect timeout
Tue Nov 07 22:59:09 PST 2000:<I> <HTTP> Destroying servlets in default
servlet context.
Tue Nov 07 22:59:09 PST 2000:<I> <WebLogicServer> Requesting thread
shutdown
Tue Nov 07 22:59:09 PST 2000:<I> <WebLogicServer> Waiting: '20' seconds
for threads to complete shutdown
Tue Nov 07 22:59:09 PST 2000:<I> <ListenThread> Shutting down
Thread[ListenThread,5,]
Tue Nov 07 22:59:09 PST 2000:<I> <SSLListenThread> Shutting down
Thread[SSLListenThread,5,]
Tue Nov 07 22:59:29 PST 2000:<I> <WebLogicServer> Invoking garbage
collection
Tue Nov 07 22:59:29 PST 2000:<I> <GC> GC: Before
free/total=62565008/67108864 (93%)
Tue Nov 07 22:59:29 PST 2000:<I> <GC> GC: After
free/total=63867744/67108864 (95%)
Tue Nov 07 22:59:29 PST 2000:<I> <WebLogicServer> Invoking garbage
collection
Tue Nov 07 22:59:29 PST 2000:<I> <GC> GC: Before
free/total=63856472/67108864 (95%)
Tue Nov 07 22:59:29 PST 2000:<I> <GC> GC: After
free/total=63877536/67108864 (95%)
Tue Nov 07 22:59:29 PST 2000:<I> <WebLogicServer> Shutting down execute
threads
Tue Nov 07 22:59:29 PST 2000:<I> <WebLogicServer> Shutdown completed<I> means informative & <A> means alert.
WLS shutdown has been commenced and Administrators are being alerted on
this.
YOu don't have to worry about the following messages.
Kumar
Serge Monkewitz wrote:
Hi,
I'm trying to install WLS 5.1.0 sp6 on Solaris. I'm using Sun's
Solaris JDK 1.2.1_04, and yes I disabled aggressive JIT inlining.
The server starts up fine, but shut down seems to have a problem
Should I be worried about the following log messages?
Thanks for any reassurance/help,
and apologies if this stuff is normal -
Serge Monkewitz
log snippet
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Disable Server Logins
requested by system
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server Logins are now
disabled
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server shutdown by
system
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server shutdown
commencing NOW
Tue Nov 07 22:59:08 PST 2000:<A> <ListenThread> ListenThread.run()
failed:
java.lang.ThreadDeath
Tue Nov 07 22:59:08 PST 2000:<!> <ListenThread> **** The WebLogic Server
is no longer listening for connections.
Tue Nov 07 22:59:08 PST 2000:<!> <ListenThread> **** You should probably
restart it.
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server shutdown by
system
Tue Nov 07 22:59:08 PST 2000:<A> <SSLListenThread> ListenThread.run()
failed:
java.lang.ThreadDeath
Tue Nov 07 22:59:08 PST 2000:<!> <SSLListenThread> **** The WebLogic
Server is no longer listening for connections.
Tue Nov 07 22:59:08 PST 2000:<!> <SSLListenThread> **** You should
probably restart it.
Tue Nov 07 22:59:08 PST 2000:<I> <WebLogicServer> Server shutdown by
system
Tue Nov 07 22:59:08 PST 2000:<I> <CliCon-#|myserver|2.973666172756>
Connection to client for ClientContext - id:
'#|myserver|2.973666172756', bound: 'true', dead: 'false' has been
unexpectedly lost because weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException].
Initiating hard disconnect.
Tue Nov 07 22:59:08 PST 2000:<I> <CliCon-#|myserver|2.973666172756>
Removing ClientContext - id: '#|myserver|2.973666172756', bound:
'false', dead: 'false' because of hard disconnect timeout
Tue Nov 07 22:59:09 PST 2000:<I> <HTTP> Destroying servlets in default
servlet context.
Tue Nov 07 22:59:09 PST 2000:<I> <WebLogicServer> Requesting thread
shutdown
Tue Nov 07 22:59:09 PST 2000:<I> <WebLogicServer> Waiting: '20' seconds
for threads to complete shutdown
Tue Nov 07 22:59:09 PST 2000:<I> <ListenThread> Shutting down
Thread[ListenThread,5,]
Tue Nov 07 22:59:09 PST 2000:<I> <SSLListenThread> Shutting down
Thread[SSLListenThread,5,]
Tue Nov 07 22:59:29 PST 2000:<I> <WebLogicServer> Invoking garbage
collection
Tue Nov 07 22:59:29 PST 2000:<I> <GC> GC: Before
free/total=62565008/67108864 (93%)
Tue Nov 07 22:59:29 PST 2000:<I> <GC> GC: After
free/total=63867744/67108864 (95%)
Tue Nov 07 22:59:29 PST 2000:<I> <WebLogicServer> Invoking garbage
collection
Tue Nov 07 22:59:29 PST 2000:<I> <GC> GC: Before
free/total=63856472/67108864 (95%)
Tue Nov 07 22:59:29 PST 2000:<I> <GC> GC: After
free/total=63877536/67108864 (95%)
Tue Nov 07 22:59:29 PST 2000:<I> <WebLogicServer> Shutting down execute
threads
Tue Nov 07 22:59:29 PST 2000:<I> <WebLogicServer> Shutdown completed -
Hello,
I am working with weblogic 4.5.1 sp 11 running on solaris 2.7.
We have a cluster of 8 servers on one box each with:
weblogic.system.executeThreadCount=80
weblogic.system.percentSocketReads=25
The clients are connecting with the following property in the java
startup.
-Dweblogic.system.executeThreadCount=16
-Dweblogic.system.percentSocketReaders=50
We specify the IP address of all the servers in the cluster on startup.
When we start 6 clients trying to connect at the same time the first
client connects to the first server at say 7:44:13.
The last client will connect to the last server at 7:47:10.
Three minutes from the first connection to the last seems a long time.
What can I do to decrease this.
Thanks,
Kirk Fritsche
No, the only version of the solaris JDK that does not crash is the 1.2.2_06
reference implementation.
I don't think native sockets are supported.
Kirk
Wei Guan wrote:
> Did you use performance pack?
>
> --
> Cheers - Wei
>
> Kirk Fritsche <[email protected]> wrote in message
> news:[email protected]..
> > Hello,
> >
> > I am working with weblogic 4.5.1 sp 11 running on solaris 2.7.
> > We have a cluster of 8 servers on one box each with:
> > weblogic.system.executeThreadCount=80
> > weblogic.system.percentSocketReads=25
> >
> > The clients are connecting with the following property in the java
> > startup.
> > -Dweblogic.system.executeThreadCount=16
> > -Dweblogic.system.percentSocketReaders=50
> >
> > We specify the IP address of all the servers in the cluster on startup.
> > When we start 6 clients trying to connect at the same time the first
> > client connects to the first server at say 7:44:13.
> > The last client will connect to the last server at 7:47:10.
> >
> > Three minutes from the first connection to the last seems a long time.
> > What can I do to decrease this.
> >
> > Thanks,
> >
> > Kirk Fritsche
> >
-
Flooding the Stomp interface - any ideas?
Does anyone have any experience of overloading the new Stomp interface using the OpenMQ 4.4 beta running under Windows? I've found that if messages are sent in too fast, exceptions occur. This happens with a Producer tool (for example Michael Justin's free download) and a different demo program based on the Delphi TStompClient component from the Codehaus site. I suspect it will happen with any program that writes, say, several hundred messages to a topic or queue in rapid succession.
A workaround which I have just tried this morning is to put in a Sleep(0) after each send in order to cede a bit of processor time to the JMS - early signs are that this seems to work. However I would like to know if anyone else has experience of this issue and what the best way forward is. Is it a JMS bug?
The exception generated is below - you can see that the JMS is having trouble interpreting a Stomp message with missing characters at the start of the message. (Different fragments will displayed in different occurrences of the exception).
04-Jun-2009 18:56:23
SEVERE: Parse incomming data failed: Unknown STOMP command: tination:/topic/Torus2ClientTopic
com.sun.messaging.bridge.service.stomp.FrameParseException: Unknown STOMP command: tination:/topic/Torus2ClientTopic
at com.sun.messaging.bridge.service.stomp.StompFrameMessage.parseCommand(StompFrameMessage.java:549)
at com.sun.messaging.bridge.service.stomp.StompProtocolParser.hasNextMessage(StompProtocolParser.java:179)
at com.sun.grizzly.filter.ParserProtocolFilter.execute(ParserProtocolFilter.java:139)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:136)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Thanks for any ideas...I've tried a few different platforms and mostly JRE 1.6u13. Yesterday I started using the JDK (1.6u13 - for compatibility with Open build 8/9). I have used Windows 2003 & Windows Vista. To be sure that everything is the latest, I've re-installed this afternoon as follows:
- Processor: Intel 2 Core Duo 2GHz.
- OS: Windows 32-bit Vista SP1
- Install JDK 1.6u14
- Install OpenMQ 4.4 build 9 and set up for Stomp
- Start imqbrokerd from a command window
- Create a topic with default parameters with the imqadmin tool
- Download "Habari OpenMQ Client - Delphi demo download" from: http://www55.pair.com/betasoft/habari.html#item_1197
- Unzip and run: ...\HabariOpenMQ-demo\demo\delphigui\GUIDemo.exe
- Ignoring the row of big buttons on top (no reason, that's just what I did) look at the left hand half of the screen and the different sections separated by parallel lines:
- In the Connection section click the Connect button
- In the Session section click the Create button;
- Click OK in the dialog that appears, accepting Automatic Acknowledgement
- In the Destinations section type the name of your test topic in the empty text box just above the New button and click New
- Subscribe to this topic by highlighting it in the Destinations list box and clicking the Subscribe button
- Click the Send button to send the default message and check that it is received in the Log Window (Received test message:....)
- Change the repeat count to 10000 and click Send again.
This configuration (with JDK 1.6u14 instead of u13) seems to be more robust than previous configurations I have tried. I could not get the problem to occur when sending only 1000 messages, so I increased the count to 10000. Then dozens of errors occurred.
I suspect the problem is not at the client side because it is also seen with a different client - using code based on the Delphi TStompClient class downloaded from the Codehaus site. (The TStompClient even uses a different TCP socket from the Habari component so it has different code at all levels of the program).
Banner at the top of a startup log is:
Open Message Queue 4.4
Sun Microsystems, Inc.
Version: 4.4 (Build 9-d)
Compile: Fri 06/05/2009
Copyright (c) 2009 Sun Microsystems, Inc. All rights reserved. Use is
subject to license terms.
================================================================================
Java Runtime: 1.6.0_14 Sun Microsystems Inc. C:\Program Files\Java\jdk1.6.0_14\jre
[12/Jun/2009:13:11:39 BST] IMQ_HOME=C:\Program Files\Sun\MessageQueue\mq
[12/Jun/2009:13:11:39 BST] IMQ_VARHOME=C:\Program Files\Sun\MessageQueue\var\mq
[12/Jun/2009:13:11:39 BST] Windows Vista 6.0 x86 JonStewart.apdcomms.co.uk (2 cpu) jon.stewart
[12/Jun/2009:13:11:40 BST] Java Heap Size: max=189376k, current=18176k
[12/Jun/2009:13:11:40 BST] Arguments:
[12/Jun/2009:13:11:40 BST] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
[12/Jun/2009:13:11:40 BST] [B1060]: Loading persistent data...
[12/Jun/2009:13:11:40 BST] Using built-in file-based persistent store: C:\Program Files\Sun\MessageQueue\var\mq\instances\imqbroker\
[12/Jun/2009:13:11:40 BST] [B1318]: Initialize bridge service manager
[12/Jun/2009:13:11:40 BST] BridgeManager: Loading bridge stomp
[12/Jun/2009:13:11:40 BST] BridgeManager: Loaded bridge stomp
[P.S. the different name for this post is 'cos I was having trouble accessing my original Sun account] -
Not able to see GC information in the logs even if verbose:gc is set
Hi,
We have IAS 6.0 SP4.
My iasenv.ksh script is set to :
if [ "$script" = "kjs" ]
then
## Set all User Level JVM flags for KJS here.
SPACE=" "
# set this variable to YES to run SmartHeap enabled kjs
MEMOPT_KJS=YES
## Desired JVM flags. A grab bag of interesting JVM Tuning options:
## -Xoptimize -verbose:gc -Xss512k -Xms128m -Xmx256m -Xgenconfig:32m,32m,se
mispaces:64m,512m,markcompact
## Read the Solaris JDK 1.2.2 FAQ for more information.
JAVA_ARGS="-Xgenconfig:64m,64m,semispaces:64m,128m,markcompact -Xss512k -ve
rbose:gc -Xms128m -Xmx196m"
I tried to change the position of the verbose:gc to different places - still I don't see any GC information logged to KJS.
Am I missing some thing?
Thanks in advance
SangeetaSangeeta,
Just try with <b>"-verbose"</b> option in JAVA_ARGS (no :gc).
Should you require further information, get back.
Thanks visiting our forum,
Rakesh. -
Fatal bug with shared JDBC Session Persistence
We are attempting to launch a three-tier site with two clusters, one at the
web layer (JSP/servlet/images) and a separate cluster at the app server
layer (EJBs). We are running WebLogic server 4.5.1 Service Pack 8 on Solaris
2.7. In production we use Solaris JDK 1.2.1.04, and in development we use
JavaSoft JDK 1.2.2. We are able to duplicate this problem with both JDKs. We
are using the WebLogic kona/oracle driver for session persistence because
the Oracle JDBC driver would not work for this purpose - we are using the
Oracle OCI driver for our EJB persistence in a separate pool in the app
server cluster.
We attempted to configure our web cluster to work with in-memory session
replication. We found the performance of the WebLogic proxy to be abysmal -
causing a 5x to 10x performance degredation over shared JDBC persistence. We
were running the proxy on WebLogic, which we were advised would be slow. Its
performance is beyond slow, it is completely unusable and should NEVER be a
recommended or even supported configuration. We do not wish to purchase
separate licenses for iPlanet, refuse to run IIS in a production setting,
and cannot use Apache until WebLogic 5.1, so we are stuck with shared JDBC
persistence until we can upgrade to 5.1.
Using JDBC session persistence with a shared persistent store amongst all
the clustered web servers results in our users getting brand-new sessions
populated with data from OTHER USERS' SESSIONS. This is very easy to
replicate using the provided test JSP and java class. This behavior results
in new users coming to the site and finding themselves logged in as other
users.
The test.jsp file simply accesses the session, prints out some information,
and then adds a few values to the session. The JSP prints out the value of
session.isNew(), the session's ID, and the number of values in the session
space. If you hit this jsp with a new browser window, the session should be
new, and the number of values should be zero.
The test Java class hits a URL with this test.jsp file repeatedly, and
checks to make sure that the session is empty. It keeps a counter of the
number of hits which resulted in non-empty sessions and the total number of
hits. Because this java class does not maintain cookie data of any kind and
merely opens new HTTP connections, it should always receive a brand-new,
non-empty session.
When we set the JDBC session persistence property
weblogic.httpd.session.persistentStoreShared=true and run the test, we see
periodically see the test.jsp file receiving a brand-new (session.isNew() =
true), yet non-empty (session.getValueNames().length != 0) session. This is
extremely bad behavior and makes the shared JDBC session persistence setting
worthless. We were able to duplicate this behavior with both a single server
and multiple servers in a cluster.
If we set weblogic.httpd.session.persistentStoreShared=false, then this test
works fine. This also means that we cannot cluster web servers.
To run the test, simply start a WebLogic instance using the provided
properties file, put the jsp in the document-root somewhere, and then run
SessionTest.java, providing the URL of the test JSP as the only command-line
argument. You will need to modify the properties file to have the proper
database settings and document-root. The java class will display a running
tally of the number of hits, and the number of hits that result in
non-empty, illegal sessions, with a total at the end.
So, we are now in a position where we are completely unable to launch our
site in a clustered, no-single-point-of-failure configuration. Obviously,
clustering was one of the main reasons to choose WebLogic, and we are
extremely distressed that we are unable to get this configuration to work.
Any help would be appreciated.
[web.standalone.properties]
[SessionTest.java]
[test.jsp]
I hope this is not too far fetched, but we are expieriencing a similar
problem with jms (messages are mixed up between queues). This happens only
if we are using message persistence in an oracle db (everything works ok
when we are not using persistent messages). Could it be that there is a
serious bug in the jdbc code/oracle driver code or connection handling
(regarding multi threading)? This would explain that, whenever you use
persistence with oracle databases, messages/sessions (or other) are mixed
up.
- Falk
"Grant Kushida" <[email protected]> wrote in message
news:[email protected]...
> We are attempting to launch a three-tier site with two clusters, one at
the
> web layer (JSP/servlet/images) and a separate cluster at the app server
> layer (EJBs). We are running WebLogic server 4.5.1 Service Pack 8 on
Solaris
> 2.7. In production we use Solaris JDK 1.2.1.04, and in development we use
> JavaSoft JDK 1.2.2. We are able to duplicate this problem with both JDKs.
We
> are using the WebLogic kona/oracle driver for session persistence because
> the Oracle JDBC driver would not work for this purpose - we are using the
> Oracle OCI driver for our EJB persistence in a separate pool in the app
> server cluster.
>
> We attempted to configure our web cluster to work with in-memory session
> replication. We found the performance of the WebLogic proxy to be
abysmal -
> causing a 5x to 10x performance degredation over shared JDBC persistence.
We
> were running the proxy on WebLogic, which we were advised would be slow.
Its
> performance is beyond slow, it is completely unusable and should NEVER be
a
> recommended or even supported configuration. We do not wish to purchase
> separate licenses for iPlanet, refuse to run IIS in a production setting,
> and cannot use Apache until WebLogic 5.1, so we are stuck with shared JDBC
> persistence until we can upgrade to 5.1.
>
> Using JDBC session persistence with a shared persistent store amongst all
> the clustered web servers results in our users getting brand-new sessions
> populated with data from OTHER USERS' SESSIONS. This is very easy to
> replicate using the provided test JSP and java class. This behavior
results
> in new users coming to the site and finding themselves logged in as other
> users.
>
> The test.jsp file simply accesses the session, prints out some
information,
> and then adds a few values to the session. The JSP prints out the value of
> session.isNew(), the session's ID, and the number of values in the session
> space. If you hit this jsp with a new browser window, the session should
be
> new, and the number of values should be zero.
>
> The test Java class hits a URL with this test.jsp file repeatedly, and
> checks to make sure that the session is empty. It keeps a counter of the
> number of hits which resulted in non-empty sessions and the total number
of
> hits. Because this java class does not maintain cookie data of any kind
and
> merely opens new HTTP connections, it should always receive a brand-new,
> non-empty session.
>
> When we set the JDBC session persistence property
> weblogic.httpd.session.persistentStoreShared=true and run the test, we see
> periodically see the test.jsp file receiving a brand-new (session.isNew()
=
> true), yet non-empty (session.getValueNames().length != 0) session. This
is
> extremely bad behavior and makes the shared JDBC session persistence
setting
> worthless. We were able to duplicate this behavior with both a single
server
> and multiple servers in a cluster.
>
> If we set weblogic.httpd.session.persistentStoreShared=false, then this
test
> works fine. This also means that we cannot cluster web servers.
>
> To run the test, simply start a WebLogic instance using the provided
> properties file, put the jsp in the document-root somewhere, and then run
> SessionTest.java, providing the URL of the test JSP as the only
command-line
> argument. You will need to modify the properties file to have the proper
> database settings and document-root. The java class will display a running
> tally of the number of hits, and the number of hits that result in
> non-empty, illegal sessions, with a total at the end.
>
> So, we are now in a position where we are completely unable to launch our
> site in a clustered, no-single-point-of-failure configuration. Obviously,
> clustering was one of the main reasons to choose WebLogic, and we are
> extremely distressed that we are unable to get this configuration to work.
> Any help would be appreciated.
>
>
>
>
-
Certification forms 6i and Java plug-in
Is certified to use forms 6i + patch 4 with Sun Solaris JDK 1.1.8/Java plug-in 1.3?
or what is the certified version?
Document Oracle Forms Server: Client Platform Support Statement of Direction from October 2000 (on OTN) says that
this is planned. Is it already certified?
Thanks.Hello,
All you have to do is to copy the .jar file that contains the Java class(es) in the <devsuite>/forms/java/ directory, configur the <devsuite>/forms/server/formsweb.cfg file to add this jar file to the archive_jini tag to indicate where Forms have to load the classes:
archive_jini=frmall_jinit.jar,...,my_jar_file.jar
Then after, you have 2 possibilities:
- the bean does not have any "screen" representation so you can just handle its functions with the Forms internal FBean package functions (no need to put implementation class on the bean area item property)
- it has a screen representation, so you put its implementation class like you did, and you set its properties with the Set_Custom_Property() built-in and get its properties with the Get_Custom_Property() built-in.
Francois
Maybe you are looking for
-
I have written a socket client and a socket server. The client sends a directory name and the server sends directory files and their content. The client asks for files every five seconds (it has to be made once every day, but for trials I have reduce
-
How can i redeem an itunes gift card if the code number can not be seen
i cant see the code #'s on the back of my itunes gift card. is there any way that i can still use it?
-
Hello, i have SRM ECS which uses BADI n steps. I want to know that if i my approver can add another approver in my circuit. i.e 1)i have created my SC. 2) Approver 1 approves the SC. 3) Approver 2 adds another approver( say approver 3). Is it possibl
-
How do you add more sound effects to the iMovie library
hola i was already suggested to use http://www.freesound.org/ but it dosent show up in imovie so if you know hoe to fix that that woud also be very helpful. i would prefer that the new sounds be free but i would consider a small fee. thanks you to
-
Warning-Variable If automatically Converted
Friends, I am executing a Bw report through Portal.I changed name of Variable .When i run the report through it is giving the warning message 'variable if automatically Converted' I did try with RSRT and also Supress warnings from Server.Still warin