Weblogic.kernel.Default Queue problems
Hello,
We have a problem with our Production server where the threads in the weblogic.kernel.Default queue simply hang up .
The Stuck Thread Max Time and the Stuck Thread Timer Interval have been configured for 60s but many times the threads simply dont get UnStuck. :(
Is there anyway to kill the threads without restarting the Server itself ???
thanks,
sg
We generated varios thread dumps and we found a number of threads in "locked" state with LDAP :
"ExecuteThread: '15' for queue: 'weblogic.kernel.Default'" daemon pri
at java.lang.Object.wait(Native Method)
- waiting on <73e5b9d0> (a com.sun.jndi.ldap.LdapRequest)
at com.sun.jndi.ldap.Connection.readReply(Connection.java:418)
- locked <73e5b9d0> (a com.sun.jndi.ldap.LdapRequest)
at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:701)
The thing is, there is nothing wrong with LDAP. We are simulating new requests to LDAP and LDAP is responding is less than 1 s ! But the thread dump indicates the threads are hung in LDAP :(
The LDAP admin did a thorough check and came up with nothing... Is there anything else I can check for ?
thnx,
sg
Similar Messages
-
I have two servers, serverOne and serverTwo, that are running different applications on WL815, Solaris 10, x86 platform.
Both have ThreadCount=25, Threads Max=400, and Threads Increase = 15.
1. I have noticed when I monitor the weblogic.kernel.Default queue, no matter how much the load is on the server, there are no more than 25 thread in the queue. Why is it?
2. On serverOne, only 6 threads out of the 25 are being used by <WLS Kernel> and the rest of the threads are allocated to the applications. However, on serverTwo, about 19 threads out of 25 are being used by <WLS Kernel>, and ther rest are used by the application. FYI, there are 4 application queues deployed on serverTwo. What is the reason for so many threads being used by <WLS Kernel> on ServerTwo?
Thanks for all your answers in advance!Can you post the complete stacktrace? That may yield a clue.
-
ExecuteThread for queue: 'weblogic.kernel.Default' stuck
Hello!
I have web application deployed on WebLogic 8.1 SP 4 cluster which is seriously loaded (~30 concurrent users) and periodically I get such messages wrote to log file:
<Apr 2, 2007 10:11:54 AM EDT> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '51' for queue: 'weblogic.kernel.Default' has been busy for "233" seconds working on the request "Http Request: /myurl/some_jsp.jsp", which is more than the configured time (StuckThreadMaxTime) of "180" seconds.>
As far as I could find from BEA documentation these messages mean that some threads (it is ExecuteThread#51 here) are runned for too long time.
I've made a thread dump and found that for a few (10-15min) thread is doing the same work:
"ExecuteThread: '51' for queue: 'weblogic.kernel.Default'" daemon prio=1 tid=0x6ca004b8 nid=0x3094 runnable [0x6c9fe000..0x6c9ff868]
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at weblogic.servlet.internal.ChunkUtils.writeChunkNoTransfer(ChunkUtils.java:280)
at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:241)
at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:311)
at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:387)
at weblogic.servlet.internal.ChunkOutput.write(ChunkOutput.java:254)
at weblogic.servlet.internal.MultibyteOutput.write(ChunkOutput.java:482)
at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:125)
at weblogic.servlet.jsp.JspWriterImpl.write(JspWriterImpl.java:455)
As you can see, thread is just writing to the socket for 10-15 minutes!!!
Can you help with some suggestions? Can this problem occure because of huge overloading to the server?
Thanks for all your responses.
ThanksI have installed the Spring application on WebLogic 8.1 SP4 on Red HAt Linux 3.0.
These message doesn't appear for WebLogic 8.1 SP4 on windows.
2007-05-10 10:22:50,356 [l.Default'] DEBUG org.springframework.web.servlet.DispatcherServlet: Rendering view [org.springframework.web.servlet.view.JstlView: unnamed; URL [/util/noAccess.jsp]] in DispatcherServlet with name 'spring'
2007-05-10 10:22:50,376 [l.Default'] DEBUG org.springframework.web.servlet.DispatcherServlet: Could not complete request
java.net.SocketException: Connection reset
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at weblogic.servlet.internal.ChunkUtils.writeChunkTransfer(ChunkUtils.java:267)
at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:239)
at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:311)
at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:387)
at weblogic.servlet.internal.ChunkOutput.write(ChunkOutput.java:254)
at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:125)
at weblogic.servlet.jsp.JspWriterImpl.write(JspWriterImpl.java:455)
at jsp_servlet._util.__noaccess._writeText(__noaccess.java:74)
at jsp_servlet._util.__noaccess._jspService(__noaccess.java:283)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322)
at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:111)
at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:250)
at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:965)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:744)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:663)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:394)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:348)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322)
at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:531)
at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:383)
at weblogic.servlet.FileServlet.findSource(FileServlet.java:281)
at weblogic.servlet.FileServlet.service(FileServlet.java:184)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) -
How to get rid of the weblogic.kernel.Default errors and warning?
Hi there,
When i'm running my application deployed on WLS8.1 SP3 and the application is running fine, but the following error and warnings were thrown.
2004-08-05 11:26:30,453 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] ERROR com.bea.wlw.runtime.core.util.Config - Failed to obtain connection to datasource=cgDataSource, using generic DB properties
<Aug 5, 2004 11:26:30 AM SGT> <Error> <WLW> <000000> <Failed to obtain connection to datasource=cgDataSource, using generic DB properties>
2004-08-05 11:27:12,281 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.default.elementattributes
2004-08-05 11:27:12,282 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.default.elementattributes', using defaults.
2004-08-05 11:27:12,308 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.system.groupIdCache.elementattributes
2004-08-05 11:27:12,308 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.system.groupIdCache.elementattributes', using defaults.
2004-08-05 11:27:12,386 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.region.CodeTableCache.elementattributes
2004-08-05 11:27:12,386 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.region.CodeTableCache.elementattributes', using defaults.
2004-08-05 11:27:13,527 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN com.bea.wlw.netui.script.el.NetUIReadVariableResolver - Could not create a ContextFactory for type "com.bea.netuix.servlets.script.PortalVariableResolver$PortalContextFactory" because the ContextFactory implementation class could not be found.
May i know why this is so? How to get rid of these error and warnings?
Thanks
Derek
Message was edited by derekchan at Aug 4, 2004 8:41 PM
Message was edited by derekchan at Aug 4, 2004 8:42 PMyou didnt seem to have configured the datasource / connection pool / database control with proper db properties
you should check your configuration to see if you have done it right and then you should check your application and the properties settings in the controls to ensure they are right. -
Weblogic.kernel.Default not using all threads
We are running weblogic 8.1 sp4 on HP Tru64 5.1.
We have an admin server and 3 managed servers in a cluster.
When monitoring the weblogic.kernal.Default execute threads through the weblogic console, threads 0 to 15 have zero total requests, and the user is marked '<WLS Kernal>'. Threads 16 to 24 share the entire workload with thousands of requests shared between them, and have user marked as 'n/a' (when idle).
I have done a thread dump, and threads 0 to 15 just seem to be idle.
This is the case for the admin server, server 1 and server 3. But server 2 actually shows all threads 0 to 24 as sharing the workload, and the user is 'n/a' for all threads.
Is there a reason for this?
Below is a snippet of the thread dump showing a thread that is has user '<WLS Kernel>':
**** ExecuteThread: '3' for queue: 'weblogic.kernel.Default' thread 0x207d8e80 Stack trace:
pc 0x03ff805c2cc8 sp 0x200026ecc00 __hstTransferRegisters (line -1)
pc 0x03ff805b2384 sp 0x200026ecc00 __osTransferContext (line -1)
pc 0x03ff805a3d20 sp 0x200026ecd90 __dspDispatch (line -1)
pc 0x03ff805a309c sp 0x200026ecde0 __cvWaitPrim (line -1)
pc 0x03ff805a0518 sp 0x200026ece80 __pthread_cond_wait (line -1)
pc 0x03ffbff31558 sp 0x200026ecea0 monitor_wait (line 625)
pc 0x03ffbff5ea48 sp 0x200026ecf10 JVM_MonitorWait (line 1037)
pc 0x00003001304c sp 0x200026ecf20 -1: java/lang/Object.wait(J)V
pc 0x0000302047dc sp 0x200026ecfd0 2: java/lang/Object.wait()V
pc 0x000030204784 sp 0x200026ecfe0 8: weblogic/kernel/ExecuteThread.waitForRequest()V
pc 0x0000302044ec sp 0x200026ed000 43: weblogic/kernel/ExecuteThread.run()V
pc 0x03ffbff91b28 sp 0x200026ed030 unpack_and_call (line 100)
pc 0x03ffbff89ca4 sp 0x200026ed040 make_native_call (line 331)
pc 0x03ffbff27bb0 sp 0x200026ed0f0 interpret (line 368)
pc 0x03ffbff36bf0 sp 0x200026ed9d0 jni_call (line 583)
pc 0x03ffbff378d8 sp 0x200026eda60 jni_CallVoidMethodA (line 70)
pc 0x03ffbff37980 sp 0x200026eda90 jni_CallVoidMethod (line 88)
pc 0x03ffbff2ecf4 sp 0x200026edb10 java_thread_start (line 592)
pc 0x03ffbff2e720 sp 0x200026edb30 thread_body (line 460)
pc 0x03ff805cf278 sp 0x200026edc00 __thdBase (line -1)Grand central dispatch - infancy, not really doing its job, and I don't think apps have to be specifically written for HT, but they do have to not do things that they use to - prevent threads from going to sleep! or be parked.
high usage is not necessarily high efficiency. often the opposite.
Windows 7 seems to be optimized for multi-core thanks to a lot of reworking. Intel wants and knows it isn't possible to hand code, that the hardware has to be smarter, too. But the OS has a job, and right now I don't think it does it properly. Or handle memory.
Gulftown's 12MB cache will help, and over all should be 20% more efficient doing its work.
With dual processors, and it doesn't look like there are two quick path bridges, data shuffling has led to memory thrashing. Use to be page thrashing with not enough memory. Then core thrashing but having the cores, but not integrated (2008 is often touted as being greatest design so far, but it was FOUR dual-cores, 2009 was the first with a processor that really was new design and (native) 4-core.
One core should be owned by the OS so it is always available for its own work and housekeeping.
The iTunes audio bug last year showed how damaging and not to implement code and how a thread could usurp processing and add a high cpu temperature while basically doing nothing, sort of a denial of service attack on the processor - those 80*C temps people had.
All those new technology features under development and not like OpenCL, GCD and even OpenGL are tested, mature but rather 1.0 foundation for the future. A year ahead of readiness. -
Why are the weblogic.kernel.Default Execute Threads used by WLS Kernel
In my Admin Console, it's displaying 10 out of the 15 weblogic.kernel.Default Execute Threads are used by the WLS Kernel user. The total requests column for these threads are showing 0. The other 5 threads are showing 20K to 40K requests. Why is the WLS Kernel users hogging these threads and not allowing the applications to use them?
Hi,
As work enters a WebLogic Server, it is placed in an execute queue. This work is then assigned to a thread within the queue that performs the work.
By default, a new server instance is configured with a default execute queue, weblogic.kernel.default, that contains 15 threads.
Go through the following link and find the usefull information on this issue.
http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_executequeuetable.html
Regards
Anilkumar kari -
Weblogic.kernel.Default' has become "unstuck"
Running WL 8.1 sp2 on Windows XP Pro. with 2Gb. of memory.
I have an EJB 2.0 CMP application accessing an Oracle 8.1.7 database.
I retrieve 1,440 rows and then start processing each row, and submitt "Jobs" to
a third party product using WebServices.
It only had 3 rows remaining to process when I got;
<03-Feb-2004 13:45:47 o'clock GMT> <Info> <WebLogicServer> <BEA-000339> <ExecuteThread:
'10' for queue: 'weblogic.kernel.Default' has become "unstuck".>
Any pointers?
Thanks.增大JVM堆栈，如果不行的话打开GC详细输出看看
-
Weblogic Kernel Thread Queue - Count
Kernel thread count is configurable, the kernel thread queue can be configured
to grow.
The socket reader threads are a %age of the kernel thread queue. Does it mean
that the number of socket reader threads (allocated as %age of the kernel threads)
change as the kernel thread count changes dynamically ?
thanks,
ParagA [STUCK] thread is a WebLogic managed thread that WebLogic has decided has been busy for too long. This might be quite normal for a background process or batch process. It does not necessarily indicate a real problem. The object allocation and subsequent GC is also normal behaviour.
So is your thread really stuck or is it just running for longer than WebLogic is configured to expect? You can use WebLogic thread pool configurations and the CommonJ API to avoid threads being marked as [STUCK] by declaring that they are long running (and assuming you're using a new enough version of WebLogic that honours this - it used to still mark them as [STUCK]).
If your thread is truly stuck it is more likely to be to do with your code than an object allocation / GC issue. -
Hi,
When I invoke this JSP, the servlet gets the request and sends a reply, but the
JSP never finishes. The connection isn't dropped, the browser icon keeps spinning,
as if it is still trying to load the page. But nothing ever happens. After more
than 10 minutes or more I get a message in the stdout of weblogic server saying
something about a stuck thread.
Note: The JSP sends an SQL statement to Servlet, which in turn calls a DAO class
to execute the sql and return the result back to Servlet. i m using Weblogic 8.1
Please help me as it is very urgent. Production Problem. It occurs randomly.Hi,
It looks like you have an AXIS webservice based Application deployed on the Server which has the following Method: com.test.ws.Stub.getInfo(ClientStub.java:813) the call to that method is happening over HTTPS protocol. getInfo() method might be trying to read a Large amount of Information from some sources which may be taking more than 600 Seconds. 600 Seconds is the Default Duration for WebLogic Threads after which the WebLogic Marks those Threads as Stuck Thread.
So we need to debug the data which is being fetch by the Application code at the following line com.test.ws.Stub.getInfo(ClientStub.java:813)...It might be possible that sometimes while execution of the above method it might be processing or asking for a Large amount of Data which is more than the Configured Thread Timeout period.
As well as it looks like the Above code is trying to get some data from a remote Server/JVM beacuse it is getting stuck while reading Data from a Socket:
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
So u need to check the Other end also from where the code is actually trying to get the Information or Data ....*com.test.ws.Stub.getInfo(ClientStub.java:813)*
Developers can easily findout what the "ClientStub.java" classes method getInfo() is actually doing.
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic/?page_id=2261 (Middleware Magic Is Here) -
Weblogic portal server getting problem it stops responding again again
i am using weblogic portal 10.1 from last few weeks i am getting continuous problem as the server stops responding. in the admin server logs i have found errors mentioned below
####<Aug 31, 2009 11:59:48 AM FJT> <Error> <ContentManagement> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-74D57518D9A8B9659F4E> <> <1251676788241> <BEA-000000> <
com.bea.content.RepositoryException: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 66 seconds
BEA1-74D57518D9A8B9659F4E]'. No further JDBC access is allowed within this transaction.
at com.bea.content.internal.server.dao.DaoBase.doDatabaseAction(DaoBase.java:287)
at com.bea.content.internal.server.dao.DaoBase.doQueryActionAndCloseConnection(DaoBase.java:195)
at com.bea.content.repo.internal.server.dao.NodeDao.hasChildren(NodeDao.java:595)
at com.bea.content.repo.internal.server.persister.JDBCNodePersister.hasChildren(JDBCNodePersister.java:71)
at com.bea.content.repo.internal.server.logic.NodeOpsLogic.hasChildren(NodeOpsLogic.java:1031)
at com.bea.content.repo.internal.server.bean.NodeOpsBean.hasChildren(NodeOpsBean.java:321)
at com.bea.content.repo.internal.server.bean.RepoNodeOps_ehgg7y_ELOImpl.hasChildren(RepoNodeOps_ehgg7y_ELOImpl.java:1229)
at com.bea.content.repo.internal.client.common.Node.hasChildren(Node.java:233)
at com.bea.content.spi.internal.NodeOpsBase.constructNode(NodeOpsBase.java:132)
at com.bea.content.spi.internal.NodeOpsImpl.getNodesFromRepo(NodeOpsImpl.java:306)
at com.bea.content.spi.internal.ExtendedNodeOpsImpl.getNodes(ExtendedNodeOpsImpl.java:55)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodesImpl(InternalNodeOpsBean.java:952)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodes(InternalNodeOpsBean.java:1950)
at com.bea.content.manager.internal.NodeOpsEJB_ihurl6_ELOImpl.getNodes(NodeOpsEJB_ihurl6_ELOImpl.java:2776)
at com.bea.content.manager.internal.NodeOpsImpl.getNodes(NodeOpsImpl.java:240)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.retrieveNodes(SearchTag.java:598)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.doStartTag(SearchTag.java:246)
at jsp_servlet.__searchwap._jspService(__searchwap.java:351)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.continueChainNoWrapper(PageFlowPageFilter.java:455)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:432)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:284)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 66 seconds
BEA1-74D57518D9A8B9659F4E]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:57)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
at com.bea.content.internal.server.common.dbaction.QueryAction.runExecuteStep(QueryAction.java:25)
at com.bea.content.internal.server.common.dbaction.SqlStatementAction.execute(SqlStatementAction.java:115)
at com.bea.content.internal.server.dao.DaoBase.doDatabaseAction(DaoBase.java:280)
at com.bea.content.internal.server.dao.DaoBase.doQueryActionAndCloseConnection(DaoBase.java:195)
at com.bea.content.repo.internal.server.dao.NodeDao.hasChildren(NodeDao.java:595)
at com.bea.content.repo.internal.server.persister.JDBCNodePersister.hasChildren(JDBCNodePersister.java:71)
at com.bea.content.repo.internal.server.logic.NodeOpsLogic.hasChildren(NodeOpsLogic.java:1031)
at com.bea.content.repo.internal.server.bean.NodeOpsBean.hasChildren(NodeOpsBean.java:321)
at com.bea.content.repo.internal.server.bean.RepoNodeOps_ehgg7y_ELOImpl.hasChildren(RepoNodeOps_ehgg7y_ELOImpl.java:1229)
at com.bea.content.repo.internal.client.common.Node.hasChildren(Node.java:233)
at com.bea.content.spi.internal.NodeOpsBase.constructNode(NodeOpsBase.java:132)
at com.bea.content.spi.internal.NodeOpsImpl.getNodesFromRepo(NodeOpsImpl.java:306)
at com.bea.content.spi.internal.ExtendedNodeOpsImpl.getNodes(ExtendedNodeOpsImpl.java:55)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodesImpl(InternalNodeOpsBean.java:952)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodes(InternalNodeOpsBean.java:1950)
at com.bea.content.manager.internal.NodeOpsEJB_ihurl6_ELOImpl.getNodes(NodeOpsEJB_ihurl6_ELOImpl.java:2776)
at com.bea.content.manager.internal.NodeOpsImpl.getNodes(NodeOpsImpl.java:240)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.retrieveNodes(SearchTag.java:598)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.doStartTag(SearchTag.java:246)
at jsp_servlet.__searchwap._jspService(__searchwap.java:351)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.continueChainNoWrapper(PageFlowPageFilter.java:455)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:432)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:284)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Aug 31, 2009 11:59:51 AM FJT> <Error> <ContentManagement> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-74D57518D9A8B9659F4E> <> <1251676791539> <BEA-000000> <
com.bea.content.RepositoryException: An error occurred while trying to find children for node id 162,041.
at com.bea.content.repo.internal.server.dao.NodeDao.hasChildren(NodeDao.java:606)
at com.bea.content.repo.internal.server.persister.JDBCNodePersister.hasChildren(JDBCNodePersister.java:71)
at com.bea.content.repo.internal.server.logic.NodeOpsLogic.hasChildren(NodeOpsLogic.java:1031)
at com.bea.content.repo.internal.server.bean.NodeOpsBean.hasChildren(NodeOpsBean.java:321)
at com.bea.content.repo.internal.server.bean.RepoNodeOps_ehgg7y_ELOImpl.hasChildren(RepoNodeOps_ehgg7y_ELOImpl.java:1229)
at com.bea.content.repo.internal.client.common.Node.hasChildren(Node.java:233)
at com.bea.content.spi.internal.NodeOpsBase.constructNode(NodeOpsBase.java:132)
at com.bea.content.spi.internal.NodeOpsImpl.getNodesFromRepo(NodeOpsImpl.java:306)
at com.bea.content.spi.internal.ExtendedNodeOpsImpl.getNodes(ExtendedNodeOpsImpl.java:55)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodesImpl(InternalNodeOpsBean.java:952)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodes(InternalNodeOpsBean.java:1950)
at com.bea.content.manager.internal.NodeOpsEJB_ihurl6_ELOImpl.getNodes(NodeOpsEJB_ihurl6_ELOImpl.java:2776)
at com.bea.content.manager.internal.NodeOpsImpl.getNodes(NodeOpsImpl.java:240)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.retrieveNodes(SearchTag.java:598)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.doStartTag(SearchTag.java:246)
at jsp_servlet.__searchwap._jspService(__searchwap.java:351)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.continueChainNoWrapper(PageFlowPageFilter.java:455)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:432)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:284)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
com.bea.content.RepositoryException: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 66 seconds
BEA1-74D57518D9A8B9659F4E]'. No further JDBC access is allowed within this transaction.
at com.bea.content.internal.server.dao.DaoBase.doDatabaseAction(DaoBase.java:287)
at com.bea.content.internal.server.dao.DaoBase.doQueryActionAndCloseConnection(DaoBase.java:195)
at com.bea.content.repo.internal.server.dao.NodeDao.hasChildren(NodeDao.java:595)
at com.bea.content.repo.internal.server.persister.JDBCNodePersister.hasChildren(JDBCNodePersister.java:71)
at com.bea.content.repo.internal.server.logic.NodeOpsLogic.hasChildren(NodeOpsLogic.java:1031)
at com.bea.content.repo.internal.server.bean.NodeOpsBean.hasChildren(NodeOpsBean.java:321)
at com.bea.content.repo.internal.server.bean.RepoNodeOps_ehgg7y_ELOImpl.hasChildren(RepoNodeOps_ehgg7y_ELOImpl.java:1229)
at com.bea.content.repo.internal.client.common.Node.hasChildren(Node.java:233)
at com.bea.content.spi.internal.NodeOpsBase.constructNode(NodeOpsBase.java:132)
at com.bea.content.spi.internal.NodeOpsImpl.getNodesFromRepo(NodeOpsImpl.java:306)
at com.bea.content.spi.internal.ExtendedNodeOpsImpl.getNodes(ExtendedNodeOpsImpl.java:55)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodesImpl(InternalNodeOpsBean.java:952)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodes(InternalNodeOpsBean.java:1950)
at com.bea.content.manager.internal.NodeOpsEJB_ihurl6_ELOImpl.getNodes(NodeOpsEJB_ihurl6_ELOImpl.java:2776)
at com.bea.content.manager.internal.NodeOpsImpl.getNodes(NodeOpsImpl.java:240)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.retrieveNodes(SearchTag.java:598)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.doStartTag(SearchTag.java:246)
at jsp_servlet.__searchwap._jspService(__searchwap.java:351)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.continueChainNoWrapper(PageFlowPageFilter.java:455)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:432)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:284)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 66 seconds
BEA1-74D57518D9A8B9659F4E]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:57)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
at com.bea.content.internal.server.common.dbaction.QueryAction.runExecuteStep(QueryAction.java:25)
at com.bea.content.internal.server.common.dbaction.SqlStatementAction.execute(SqlStatementAction.java:115)
at com.bea.content.internal.server.dao.DaoBase.doDatabaseAction(DaoBase.java:280)
at com.bea.content.internal.server.dao.DaoBase.doQueryActionAndCloseConnection(DaoBase.java:195)
at com.bea.content.repo.internal.server.dao.NodeDao.hasChildren(NodeDao.java:595)
at com.bea.content.repo.internal.server.persister.JDBCNodePersister.hasChildren(JDBCNodePersister.java:71)
at com.bea.content.repo.internal.server.logic.NodeOpsLogic.hasChildren(NodeOpsLogic.java:1031)
at com.bea.content.repo.internal.server.bean.NodeOpsBean.hasChildren(NodeOpsBean.java:321)
at com.bea.content.repo.internal.server.bean.RepoNodeOps_ehgg7y_ELOImpl.hasChildren(RepoNodeOps_ehgg7y_ELOImpl.java:1229)
at com.bea.content.repo.internal.client.common.Node.hasChildren(Node.java:233)
at com.bea.content.spi.internal.NodeOpsBase.constructNode(NodeOpsBase.java:132)
at com.bea.content.spi.internal.NodeOpsImpl.getNodesFromRepo(NodeOpsImpl.java:306)
at com.bea.content.spi.internal.ExtendedNodeOpsImpl.getNodes(ExtendedNodeOpsImpl.java:55)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodesImpl(InternalNodeOpsBean.java:952)
at com.bea.content.manager.internal.InternalNodeOpsBean.getNodes(InternalNodeOpsBean.java:1950)
at com.bea.content.manager.internal.NodeOpsEJB_ihurl6_ELOImpl.getNodes(NodeOpsEJB_ihurl6_ELOImpl.java:2776)
at com.bea.content.manager.internal.NodeOpsImpl.getNodes(NodeOpsImpl.java:240)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.retrieveNodes(SearchTag.java:598)
at com.bea.content.manager.servlets.jsp.taglib.SearchTag.doStartTag(SearchTag.java:246)
at jsp_servlet.__searchwap._jspService(__searchwap.java:351)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.continueChainNoWrapper(PageFlowPageFilter.java:455)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:432)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:284)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)and a lot of errors like these and finally in logs at the end we find
####<Aug 31, 2009 3:27:02 PM FJT> <Error> <WebLogicServer> <content-oam> <AdminServer> <[STANDBY] ExecuteThread: '268' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1251689222980> <BEA-000337> <[STUCK] ExecuteThread: '207' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "2,040" seconds working on the request "Http Request: /WapWeb/siteController.jsp", which is more than the configured time (StuckThreadMaxTime) of "2,000" seconds. Stack trace:
weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35)
org.apache.beehive.netui.pageflow.internal.DefaultReloadableClassHandler.loadClass(DefaultReloadableClassHandler.java:188)
org.apache.beehive.netui.pageflow.FlowControllerFactory.getFlowControllerClass(FlowControllerFactory.java:533)
org.apache.beehive.netui.pageflow.FlowControllerFactory.createPageFlow(FlowControllerFactory.java:189)
org.apache.beehive.netui.pageflow.FlowControllerFactory.getPageFlowForPath(FlowControllerFactory.java:163)
org.apache.beehive.netui.pageflow.FlowControllerFactory.getPageFlowForRequest(FlowControllerFactory.java:127)
org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:244)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
weblogic.security.service.SecurityManager.runAs(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Aug 31, 2009 3:27:03 PM FJT> <Error> <WebLogicServer> <content-oam> <AdminServer> <[STANDBY] ExecuteThread: '268' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1251689223109> <BEA-000337> <[STUCK] ExecuteThread: '206' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "2,040" seconds working on the request "Http Request: /WapWeb/siteController.jsp", which is more than the configured time (StuckThreadMaxTime) of "2,000" seconds. Stack trace:
weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35)
org.apache.beehive.netui.pageflow.internal.DefaultReloadableClassHandler.loadClass(DefaultReloadableClassHandler.java:188)
org.apache.beehive.netui.pageflow.FlowControllerFactory.getFlowControllerClass(FlowControllerFactory.java:533)
org.apache.beehive.netui.pageflow.FlowControllerFactory.createPageFlow(FlowControllerFactory.java:189)
org.apache.beehive.netui.pageflow.FlowControllerFactory.getPageFlowForPath(FlowControllerFactory.java:163)
org.apache.beehive.netui.pageflow.FlowControllerFactory.getPageFlowForRequest(FlowControllerFactory.java:127)
org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:244)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
weblogic.security.service.SecurityManager.runAs(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Aug 31, 2009 3:27:55 PM FJT> <Warning> <Socket> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '212' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1251689275482> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
####<Aug 31, 2009 3:29:59 PM FJT> <Error> <PortalAdminTools> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '83' for queue: 'weblogic.kernel.Default (self-tuning)'> <Webmasters> <> <> <1251689399276> <BEA-415121> <the treeMode cannot be found>
####<Aug 31, 2009 3:29:59 PM FJT> <Error> <org.apache.beehive.netui.pageflow.internal.DefaultExceptionsHandler> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '83' for queue: 'weblogic.kernel.Default (self-tuning)'> <Webmasters> <> <> <1251689399282> <BEA-000000> <Could not find exception handler method handleException for java.lang.NullPointerException.>
####<Aug 31, 2009 3:29:59 PM FJT> <Error> <org.apache.beehive.netui.pageflow.internal.DefaultExceptionsHandler> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '83' for queue: 'weblogic.kernel.Default (self-tuning)'> <Webmasters> <> <> <1251689399283> <BEA-000000> <Could not find exception handler method handleException for java.lang.RuntimeException.>
####<Aug 31, 2009 3:29:59 PM FJT> <Error> <org.apache.beehive.netui.pageflow.internal.DefaultExceptionsHandler> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '83' for queue: 'weblogic.kernel.Default (self-tuning)'> <Webmasters> <> <> <1251689399283> <BEA-000000> <Could not find message-resources for bundle org.apache.struts.action.MESSAGE>
####<Aug 31, 2009 3:29:59 PM FJT> <Warning> <global.internal.AbstractBaseController$LoggerCatalog> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '83' for queue: 'weblogic.kernel.Default (self-tuning)'> <Webmasters> <> <> <1251689399283> <BEA-000000> <Exception occured trying to instantiate the null bean.
java.lang.NullPointerException
at util.tree.TreeController.constructRootWithoutChildren(TreeController.java:483)
at util.tree.TreeController.view(TreeController.java:172)
at sun.reflect.GeneratedMethodAccessor637.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:879)
at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
at global.internal.AbstractBaseController.internalExecute(AbstractBaseController.java:348)
at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1170)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1201)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.renderInternal(ScopedContentCommonSupport.java:266)
at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.render(PageFlowStubImpl.java:135)
at com.bea.netuix.servlets.controls.content.NetuiContent.preRender(NetuiContent.java:290)
at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:426)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:712)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:724)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:146)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:188)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:142)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:377)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:253)
at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:206)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:191)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:266)
at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:656)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.jsptools.servlet.PagedResultServiceFilter.doFilter(PagedResultServiceFilter.java:82)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Aug 31, 2009 3:31:31 PM FJT> <Critical> <Health> <content-oam> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1251689491464> <BEA-310003> <Free memory in the server is 4,431,384 bytes. There is danger of OutOfMemoryError>
####<Aug 31, 2009 3:33:25 PM FJT> <Critical> <Health> <content-oam> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1251689605339> <BEA-310003> <Free memory in the server is 2,960,928 bytes. There is danger of OutOfMemoryError>
####<Aug 31, 2009 3:34:07 PM FJT> <Warning> <Socket> <content-oam> <AdminServer> <[ACTIVE] ExecuteThread: '133' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1251689647279> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs> -
JMS Queue problems causing EJB to rollback....
We recently purchased WLS 6.1 and we have been using the product for the last few
months. I am having a problem which I have detailed below. I have provided as much
information as possible. If you need additional information, please let me know.
Server A Config:
Pentium III, 1000Mhz
Windows 2000, SP2
WLS WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
Server B Config:
SunBlade 100
Solaris 5.8
WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
Server A contains a session EJB called GoalManager. This EJB has a method named cancel().
The transactional attribute for all methods supported by this bean is REQUIRED. GoalManager
uses a transactional data source deployed on Server A named "goal". There is nothing
special about this data source aside from the fact that I have enabled two phase
commit for it because a previous error was indicating that this was a required setting
for the pool. A JMS server exists on Server B. A queue named "emailQueue" is set
up as a destination on this JMS server. I also have a MDB on Server B that listens
for messages on this queue. When a message is received, the MDB's onMessage() method
extracts some properties from the message and sends an email to the specified recipient
in the message. I have confirmed that this queue and MDB are working properly because
I ran a small test program from the command prompt which creates a message and sends
it to the queue on Server B. The MDB gets the message and sends the email to the
correct recipient, so I am sure there are no misconfigurations on the server.
The problem is as follows: The cancel() method in the GoalManager EJB on Server A
performs some database work. If no exceptions are raised, the last task in the method
attempts to access the queue on Server B and send a message to the queue. Here is
the code that I am using to access the queue:
QueueConnectionFactory queueFactory = (QueueConnectionFactory)context.lookup( "javax.jms.QueueConnectionFactory");
QueueConnection queueConnection = queueFactory.createQueueConnection();
Queue queue = (Queue)context.lookup( "emailQueue");
QueueSession queueSession = queueConnection.createQueueSession( false, Session.AUTO_ACKNOWLEDGE);
QueueSender queueSender = queueSession.createSender( queue);
The cancel() method executes without error, but when the EJB container on Server
A attempts to commit the transaction at the end of the cancel() method, I am receiving
the following error on Server A's log:
<Error> <EJB> <Exception during commit of transaction Name=[EJB com.frx.emp.go.ejb.session.goal.GoalManagerBean.cancelGoal(com.frx.emp.entity.Employee,com.frx.emp.go.entity.Goal)],
Xid=0:7c2dda32cf39a36e(6911242),
Status=Rolled back. [Reason=javax.transaction.xa.XAException],
numRepliesOwedMe=0,
numRepliesOwedOthers=0,
seconds since begin=2,
seconds left=10,
ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=server1),
ServerResourceInfo[JMS_EMailServer_NotDurable]=(state=rolledback,assigned=server1),
SCInfo[FRX+server1]=(state=rolledback),
SCInfo[frxnet+wlsvr1]=(state=rolledback),
properties=({weblogic.transaction.name=[EJB com.frx.emp.go.ejb.session.goal.GoalManagerBean.cancelGoal(com.frx.emp.entity.Employee,com.frx.emp.go.entity.Goal)],
weblogic.jdbc=t3://172.16.200.9:9005}),
OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=server1+172.16.200.9:9005+FRX+,
Resources={})],
CoordinatorURL=server1+172.16.200.9:9005+FRX+): javax.transaction.xa.XAException
at weblogic.jms.backend.BEXAResource.prepare(BEXAResource.java:853)
at weblogic.transaction.internal.ServerResourceInfo.prepare(ServerResourceInfo.java:1124)
at weblogic.transaction.internal.ServerResourceInfo.prepare(ServerResourceInfo.java:370)
at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:186)
at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:1822)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1607)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:218)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.frx.emp.go.ejb.session.goal.GoalManagerBean_e3dvd2_EOImpl.cancelGoal(GoalManagerBean_e3dvd2_EOImpl.java:459)
at com.frx.emp.go.web.handler.UpdateGoalHandler.handleRequest(UpdateGoalHandler.java:55)
at com.frx.emp.web.mvc.HandlerMappedController.service(HandlerMappedController.java:115)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Could not prepare resource 'JMS_EMailServer_NotDurable
- with nested exception:
[javax.transaction.xa.XAException]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1475)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.frx.emp.go.ejb.session.goal.GoalManagerBean_e3dvd2_EOImpl.cancelGoal(GoalManagerBean_e3dvd2_EOImpl.java:459)
at com.frx.emp.go.web.handler.UpdateGoalHandler.handleRequest(UpdateGoalHandler.java:55)
at com.frx.emp.web.mvc.HandlerMappedController.service(HandlerMappedController.java:115)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Just a quick note, I tried to change the following line to specify a "transacted"
JMS session by passing "true" to the statement below. When I tested this, the cancel()
method raised no exceptions, but the MDB on Server B is never invoked and the email
is never sent. Strange.
QueueSession queueSession = queueConnection.createQueueSession( true, Session.AUTO_ACKNOWLEDGE);
If you need more info, let me know. I thank you for your help.
Correct. According to the trace you have it set at 10 seconds, while the default is 30 seconds.
Tom
SAF wrote:
> Thanks for the reply.
>
> Increase the trx time? You mean JTA, right?
>
> I already opened a case with BEA, so I'm waiting to get a response from them.
>
> Thanks again,
>
> Raffi
>
> Tom Barnes <[email protected]> wrote:
> >Hi,
> >
> >I looked at the BEXAResource.java source code which the stack trace points
> >at. It seems that from the
> >JMS server's resource manager's point of view, it never heard of the transaction
> >before, indicating
> >that the transaction may have already rolled back. I think this could
> >happen if the transaction
> >times out before commit() is called, but I'm not sure what is wrong in your
> >case -- as according
> >to the trace you provided, your tx is 2 seconds old and your tx-timout is
> >10 seconds.
> >
> >In any case, it looks like the culprit may be in the transaction code and
> >not the JMS code...
> >
> >I suggest:
> > A) increasing your tx timeout (what the heck give it a try)
> > B) could it somehow be a clock synchronization problem? are multiple
> >servers involved?
> > C) posting to the transaction newsgroup
> > D) contacting customer support
> >
> >Tom
> >
> >SAF wrote:
> >
> >> We recently purchased WLS 6.1 and we have been using the product for the
> >last few
> >> months. I am having a problem which I have detailed below. I have provided
> >as much
> >> information as possible. If you need additional information, please let
> >me know.
> >>
> >> Server A Config:
> >> Pentium III, 1000Mhz
> >> Windows 2000, SP2
> >> WLS WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
> >>
> >> Server B Config:
> >> SunBlade 100
> >> Solaris 5.8
> >> WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
> >>
> >> Server A contains a session EJB called GoalManager. This EJB has a method
> >named cancel().
> >> The transactional attribute for all methods supported by this bean is
> >REQUIRED. GoalManager
> >> uses a transactional data source deployed on Server A named "goal". There
> >is nothing
> >> special about this data source aside from the fact that I have enabled
> >two phase
> >> commit for it because a previous error was indicating that this was a
> >required setting
> >> for the pool. A JMS server exists on Server B. A queue named "emailQueue"
> >is set
> >> up as a destination on this JMS server. I also have a MDB on Server B
> >that listens
> >> for messages on this queue. When a message is received, the MDB's onMessage()
> >method
> >> extracts some properties from the message and sends an email to the specified
> >recipient
> >> in the message. I have confirmed that this queue and MDB are working properly
> >because
> >> I ran a small test program from the command prompt which creates a message
> >and sends
> >> it to the queue on Server B. The MDB gets the message and sends the email
> >to the
> >> correct recipient, so I am sure there are no misconfigurations on the
> >server.
> >>
> >> The problem is as follows: The cancel() method in the GoalManager EJB
> >on Server A
> >> performs some database work. If no exceptions are raised, the last task
> >in the method
> >> attempts to access the queue on Server B and send a message to the queue.
> >Here is
> >> the code that I am using to access the queue:
> >>
> >> QueueConnectionFactory queueFactory = (QueueConnectionFactory)context.lookup(
> >"javax.jms.QueueConnectionFactory");
> >> QueueConnection queueConnection = queueFactory.createQueueConnection();
> >> Queue queue = (Queue)context.lookup( "emailQueue");
> >> QueueSession queueSession = queueConnection.createQueueSession( false,
> >Session.AUTO_ACKNOWLEDGE);
> >> QueueSender queueSender = queueSession.createSender( queue);
> >>
> >> The cancel() method executes without error, but when the EJB container
> >on Server
> >> A attempts to commit the transaction at the end of the cancel() method,
> >I am receiving
> >> the following error on Server A's log:
> >>
> >> <Error> <EJB> <Exception during commit of transaction Name=[EJB com.frx.emp.go.ejb.session.goal.GoalManagerBean.cancelGoal(com.frx.emp.entity.Employee,com.frx.emp.go.entity.Goal)],
> >> Xid=0:7c2dda32cf39a36e(6911242),
> >> Status=Rolled back. [Reason=javax.transaction.xa.XAException],
> >> numRepliesOwedMe=0,
> >> numRepliesOwedOthers=0,
> >> seconds since begin=2,
> >> seconds left=10,
> >> ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=server1),
> >> ServerResourceInfo[JMS_EMailServer_NotDurable]=(state=rolledback,assigned=server1),
> >> SCInfo[FRX+server1]=(state=rolledback),
> >> SCInfo[frxnet+wlsvr1]=(state=rolledback),
> >> properties=({weblogic.transaction.name=[EJB com.frx.emp.go.ejb.session.goal.GoalManagerBean.cancelGoal(com.frx.emp.entity.Employee,com.frx.emp.go.entity.Goal)],
> >>
> >> weblogic.jdbc=t3://172.16.200.9:9005}),
> >> OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=server1+172.16.200.9:9005+FRX+,
> >> Resources={})],
> >> CoordinatorURL=server1+172.16.200.9:9005+FRX+): javax.transaction.xa.XAException
> >> at weblogic.jms.backend.BEXAResource.prepare(BEXAResource.java:853)
> >> at weblogic.transaction.internal.ServerResourceInfo.prepare(ServerResourceInfo.java:1124)
> >> at weblogic.transaction.internal.ServerResourceInfo.prepare(ServerResourceInfo.java:370)
> >> at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:186)
> >> at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:1822)
> >> at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1607)
> >> at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:218)
> >> at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
> >> at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
> >> at com.frx.emp.go.ejb.session.goal.GoalManagerBean_e3dvd2_EOImpl.cancelGoal(GoalManagerBean_e3dvd2_EOImpl.java:459)
> >> at com.frx.emp.go.web.handler.UpdateGoalHandler.handleRequest(UpdateGoalHandler.java:55)
> >> at com.frx.emp.web.mvc.HandlerMappedController.service(HandlerMappedController.java:115)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> >> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
> >> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
> >> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
> >> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
> >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >> --------------- nested within: ------------------
> >> weblogic.transaction.RollbackException: Could not prepare resource 'JMS_EMailServer_NotDurable
> >> - with nested exception:
> >> [javax.transaction.xa.XAException]
> >> at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1475)
> >> at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
> >> at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
> >> at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
> >> at com.frx.emp.go.ejb.session.goal.GoalManagerBean_e3dvd2_EOImpl.cancelGoal(GoalManagerBean_e3dvd2_EOImpl.java:459)
> >> at com.frx.emp.go.web.handler.UpdateGoalHandler.handleRequest(UpdateGoalHandler.java:55)
> >> at com.frx.emp.web.mvc.HandlerMappedController.service(HandlerMappedController.java:115)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> >> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
> >> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
> >> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
> >> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
> >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >>
> >> Just a quick note, I tried to change the following line to specify a "transacted"
> >> JMS session by passing "true" to the statement below. When I tested this,
> >the cancel()
> >> method raised no exceptions, but the MDB on Server B is never invoked
> >and the email
> >> is never sent. Strange.
> >>
> >> QueueSession queueSession = queueConnection.createQueueSession( true,
> >Session.AUTO_ACKNOWLEDGE);
> >>
> >> If you need more info, let me know. I thank you for your help.
> >
-
Hi All,
i am facing a strange problem, when i start the weblogic server after starting successfully it throws an exception :-
<1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Socket> <BEA-000440> <Native IO Enabled.>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "admin_svr" for doma
in "charter" running in Development Mode>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 16
818, ip address *.*>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <WebLogicServer> <BEA-000213> <Adding address: 10.55.13.58 to licensed client list>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to
the repository.>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Configuration Management> <BEA-150007> <The booted configuration ./config.xml has
been backed up at /home/chrtr18/domains/charter/./config.xml.booted.>
<1-Nov-2007 3:12:04 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
)] FileServlet: init>
<1-Nov-2007 3:12:04 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
)] FileServlet: Using standard I/O>
<1-Nov-2007 3:12:22 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
)] actions: init>
<1-Nov-2007 3:13:24 o'clock AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal
.BasicServerRef@109 - hostID: '8499232654163808380S:10.55.13.31:[16818,16818,-1,-1,-1,-1,-1,0,0]:charter:admin_svr', oid: '265
', implementation: 'weblogic.jms.dispatcher.DispatcherImpl@e5f0d2'
java.lang.SecurityException: [Security:090398]Invalid Subject: system.
java.lang.SecurityException: [Security:090398]Invalid Subject: system
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:698)
at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:205)
at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:841)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:307)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1114)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1032)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:225)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:809)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:782)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:718)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:664)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
Is i am missing something...any suggestion will help...
Thanks.Hi All,
i am facing a strange problem, when i start the weblogic server after starting successfully it throws an exception :-
<1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Socket> <BEA-000440> <Native IO Enabled.>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "admin_svr" for doma
in "charter" running in Development Mode>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 16
818, ip address *.*>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <WebLogicServer> <BEA-000213> <Adding address: 10.55.13.58 to licensed client list>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to
the repository.>
<1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Configuration Management> <BEA-150007> <The booted configuration ./config.xml has
been backed up at /home/chrtr18/domains/charter/./config.xml.booted.>
<1-Nov-2007 3:12:04 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
)] FileServlet: init>
<1-Nov-2007 3:12:04 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
)] FileServlet: Using standard I/O>
<1-Nov-2007 3:12:22 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
)] actions: init>
<1-Nov-2007 3:13:24 o'clock AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal
.BasicServerRef@109 - hostID: '8499232654163808380S:10.55.13.31:[16818,16818,-1,-1,-1,-1,-1,0,0]:charter:admin_svr', oid: '265
', implementation: 'weblogic.jms.dispatcher.DispatcherImpl@e5f0d2'
java.lang.SecurityException: [Security:090398]Invalid Subject: system.
java.lang.SecurityException: [Security:090398]Invalid Subject: system
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:698)
at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:205)
at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:841)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:307)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1114)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1032)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:225)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:809)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:782)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:718)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:664)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
Is i am missing something...any suggestion will help...
Thanks. -
Administrative requests hang and default queue is gone
Hi,
We have a recurring problem with our WebLogic 6.1 SP 1 server.
Periodically the server will hang and not respond to admin commands,
not
even a "java weblogic.Admin PING". It has to be stopped by killing
the OS process.
We've dumped the threads using SIGQUIT and examined them for
deadlocks, but something more striking turned up: all the "default
queue" threads were gone. In a healthy, live server there were
something like 60 threads, several of them from the "default queue",
but in our hung servers, these would be nonexistent.
From what I understand, the default queue contains the threads that do
most of the work, like servicing EJB requests, so it makes sense that
if they're not there, the server would not respond to anything. But I
don't see how they could die without there being any kind of
information about their death. There's nothing about it in the
weblogic server log, and nothing in stdout or stderr.
Has anybody experienced the same behavior? Does anyone know what
causes it?
Thanks,
Jim Doyle
[email protected]This is surprising. Are you seeing any OutOfMemory errors or strain on the
server's resources ?
Is the server under load ?
Jim Doyle wrote:
Hi,
We have a recurring problem with our WebLogic 6.1 SP 1 server.
Periodically the server will hang and not respond to admin commands,
not
even a "java weblogic.Admin PING". It has to be stopped by killing
the OS process.
We've dumped the threads using SIGQUIT and examined them for
deadlocks, but something more striking turned up: all the "default
queue" threads were gone. In a healthy, live server there were
something like 60 threads, several of them from the "default queue",
but in our hung servers, these would be nonexistent.
From what I understand, the default queue contains the threads that do
most of the work, like servicing EJB requests, so it makes sense that
if they're not there, the server would not respond to anything. But I
don't see how they could die without there being any kind of
information about their death. There's nothing about it in the
weblogic server log, and nothing in stdout or stderr.
Has anybody experienced the same behavior? Does anyone know what
causes it?
Thanks,
Jim Doyle
[email protected] -
This looks like it might be a bug in 6.1SP5,
weblogic/kernel/Kernel.java at line 85.
It's trying to do the right thing to ignore an exception if in
an applet but it's ignoring the wrong exception
(SecurityException, when it looks like the stack
trace is throwing a java.security.AccessControlException).
If you need a fix, this would need to go through support
and be filed as a problem with WLS Core.
"Ram Gopal" <[email protected]> wrote in message
news:[email protected]...
>
> We are in the process of migrating from Weblogic 6.1 SP2 to SP5. We have
an applet
> that subscribes to a JMS Topic.
> The applet is throwing the following exception with SP5:
>
> java.lang.ExceptionInInitializerError:
java.security.AccessControlException: access
> denied (java.util.PropertyPermission weblogic.kernel.allowQueueThrottling
read)
>
> at java.security.AccessControlContext.checkPermission(Unknown Source)
>
> at java.security.AccessController.checkPermission(Unknown Source)
>
> at java.lang.SecurityManager.checkPermission(Unknown Source)
>
> at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
>
> at java.lang.System.getProperty(Unknown Source)
>
> at weblogic.kernel.Kernel.initAllowThrottleProp(Kernel.java:79)
>
> at weblogic.kernel.Kernel.<clinit>(Kernel.java:54)
>
> at
weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactory
Delegate.java:166)
>
> at java.lang.Class.newInstance0(Native Method)
>
> at java.lang.Class.newInstance(Unknown Source)
>
> at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:147)
>
> at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
>
> at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
>
> at javax.naming.InitialContext.init(Unknown Source)
>
> at javax.naming.InitialContext.<init>(Unknown Source)
>
> at
com.fedex.efm.frontend.model.JMSMessageProcessor.<init>(JMSMessageProcessor.
java:266)
>
> at
com.fedex.efm.frontend.view.EFMAbstractApplet.startMessageProcessor(EFMAbstr
actApplet.java:81)
>
> at
com.fedex.efm.frontend.view.EFMAbstractApplet.start(EFMAbstractApplet.java:1
87)
>
> at com.fedex.efm.frontend.view.EFMApplet.start(EFMApplet.java:430)
>
> at sun.applet.AppletPanel.run(Unknown Source)
>
> at java.lang.Thread.run(Unknown Source)
>
>
> Any ideas as to what I am missing?
>
> Thanks,
> Ram
I suggest going through customer support, I don't know what
the resolution was. You might also try the security newsgroup,
as no JMS code has been called by the application yet at
the point the exception is thrown.
Tom
lee wrote:
> All:
> We are upgrading weblogic 6.0 to weblogic 6.1 and encounted exactly the same error. Just wondering if you guys were able to fix the issue with bea.
>
> Your response is highly appreciated.
>
> Thanks!
>
> Li
-
We are in the process of migrating from Weblogic 6.1 SP2 to SP5. We have an applet
that
subscribes to a JMS Topic. The applet is throwing the following exception with
SP5:
java.lang.ExceptionInInitializerError: java.security.AccessControlException: access
denied
(java.util.PropertyPermission weblogic.kernel.allowQueueThrottling read)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
at java.lang.System.getProperty(Unknown Source)
at weblogic.kernel.Kernel.initAllowThrottleProp(Kernel.java:79)
at weblogic.kernel.Kernel.<clinit>(Kernel.java:54)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Unknown Source)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.fedex.efm.frontend.model.JMSMessageProcessor.<init>(JMSMessageProcessor.java:266)
at com.fedex.efm.frontend.view.EFMAbstractApplet.startMessageProcessor(EFMAbstractApplet.java:81)
at com.fedex.efm.frontend.view.EFMAbstractApplet.start(EFMAbstractApplet.java:187)
at com.fedex.efm.frontend.view.EFMApplet.start(EFMApplet.java:430)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Any ideas as to what I am missing?
Thanks,
RamPrasad,
It's one thing not to have to modify the security policy on the server,
but on a client and applets have even bigger restrictions this might
very well be the only way since the default applet restrictions would
not allow a lot of permissions granted by default for normal Java
applications.
Dejan
Prasad Peddada wrote:
Deyan D. Bektchiev wrote:
Ram,
You are missing a permission grant in your policy file and the
SecurityManager doesn't allow the code to read that property.
You have either configured a different security manager or have the
wrong file in use.
For applets this file might be in the user's home directory and named
.java.policy
you need to have the following line somethere in it:
grant {
permission java.util.PropertyPermission "*", "read,write";
Which will allow any applet to read and write any JVM property.
Look at Java permissions is you need more info:
http://java.sun.com/j2se/1.3/docs/guide/security/permissions.html
--dejan
Ram Gopal wrote:
We are in the process of migrating from Weblogic 6.1 SP2 to SP5. We
have an applet
that
subscribes to a JMS Topic. The applet is throwing the following
exception with
SP5:
java.lang.ExceptionInInitializerError:
java.security.AccessControlException: access
denied
(java.util.PropertyPermission weblogic.kernel.allowQueueThrottling
read) at java.security.AccessControlContext.checkPermission(Unknown
Source) at java.security.AccessController.checkPermission(Unknown
Source) at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPropertyAccess(Unknown Source) at
java.lang.System.getProperty(Unknown Source) at
weblogic.kernel.Kernel.initAllowThrottleProp(Kernel.java:79) at
weblogic.kernel.Kernel.<clinit>(Kernel.java:54) at
weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
at java.lang.Class.newInstance0(Native Method) at
java.lang.Class.newInstance(Unknown Source) at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at
javax.naming.InitialContext.init(Unknown Source) at
javax.naming.InitialContext.<init>(Unknown Source) at
com.fedex.efm.frontend.model.JMSMessageProcessor.<init>(JMSMessageProcessor.java:266)
at
com.fedex.efm.frontend.view.EFMAbstractApplet.startMessageProcessor(EFMAbstractApplet.java:81)
at
com.fedex.efm.frontend.view.EFMAbstractApplet.start(EFMAbstractApplet.java:187)
at com.fedex.efm.frontend.view.EFMApplet.start(EFMApplet.java:430)
at sun.applet.AppletPanel.run(Unknown Source) at
java.lang.Thread.run(Unknown Source)
Any ideas as to what I am missing?
Thanks,
Ram
This is a WLS bug. You shouldn't have to modify security policy.
Please approach support for a fix.
Cheers,
-- Prasad
Maybe you are looking for
-
SAP Certification and SAP TechEd '07
If you are interested in discounted SAP certification exams available exclusively to SAP TechEd '07 full conference attendees, please review the information published on each of the conference websites by selecting one of the locations below. You'll
-
Port Forwarding to change xbox nat type
I have wasted the last 2 hours of my life, trying to figure this out. Ill try to make it short, but bear with me. xbox nat type is strict. Im fed up with this. Xbox is connected wirelessly to apple base station. Ive heard you cant get the NAT type to
-
Videos load the third 2-3 seconds then stop, flash version 11,8,800,94, Windows 8
Every website i browse that used flash, example- youtube, loads the first 2-3 seconds of videos or whatever flash application they use then stops loading the rest. This all started when i downloaded the latest version that was available for windows 8
-
Imovie 11' quits when importing movies from my camcorder
I have a question. I have imovie 11'...and have made movies with iMovie before, but now that i have upgraded to iMovie 11', its is having troble with the import of the video from the camcorder and i am using a firewire, like i usually do. when I upl
-
I cannot open any site with firefox, but have no problems with explorer. on the tabbar ontop it says untitled and when I click on ant bookmarsite or click on a link in an email from outlook, the untitled will change into loading (for only one split s