Weblogic 10.3 SocketException at out.flush

I have a server/jsp where I am doing out.flush().
This throws following exception:
java.net.SocketException: Connection reset by peer: socket write error
     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.ChunkOutput.writeChunkNoTransfer(ChunkOutput.java:548)
     at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:505)
     at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:382)
     at weblogic.servlet.internal.CharsetChunkOutput.flush(CharsetChunkOutput.java:249)
     at weblogic.servlet.internal.ChunkOutputWrapper.flush(ChunkOutputWrapper.java:171)
     at weblogic.servlet.jsp.JspWriterImpl.flush(JspWriterImpl.java:98)
     at jsp_servlet._xxx.__yyy._jspService(__yyy.java:146)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
1. the problem is always reproducible.
2. Not seen on other App Server.
3. Not Seen on Mozilla. Have seen the problem with IE only.
There are no user actions to stop/cancel the operation.
Most of the times, the page is rendered correctly but we see this error in log.
I have seen several posts where people have experienced this problem but no solution for it.

The time-out you are getting is that related to a transaction?
You can set the transaction time-out in the WebLogic console go to the JTA page for the domain, and change the value in the Timeout Seconds field.
When you are using EJBs, you can also set the time-out on a EJB basis, instead of configuring the time-out for the whole domain.
For example, in weblogic-ejb-jar.xml, you can configure the time-out by using:
<weblogic-ejb-jar ...>
 <weblogic-enterprise-bean>
 <ejb-name>YOUR_EJB_NAME</ejb-name>
 <enable-call-by-reference>True</enable-call-by-reference>
 <stateless-session-descriptor>
 <pool>
 <initial-beans-in-free-pool>25</initial-beans-in-free-pool>
 <max-beans-in-free-pool>50</max-beans-in-free-pool>
 </pool>
 </stateless-session-descriptor>
 <transaction-descriptor>
 <trans-timeout-seconds>600</trans-timeout-seconds>
 </transaction-descriptor>
 </weblogic-enterprise-bean>
</weblogic-ejb-jar>The transactions this EJB spawns can last for 10 minutes.

Similar Messages

Out.flush

We have a servlet whose service method is along these lines
 PrintWriter out = response.getWriter();
 [or ServletOutputStream out = response.getOutputStream();]
 out.println(someStuff);
 out.flush();
 [lots of heavy processing]
 The aim of which is to send a message to the user's screen so they don't
 have to wait for the processing to be finished. From what (little) I
 understand the out.flush should ensure that this happens, but it doesn't -
 the server doesn't respond until after the processing. (This happens whether
 we use the printwriter or the servletoutputstream)
 Does anyone have any idea why this doesn't work, or, perhaps more
 importantly, what would work.


Even if you got it to work, a proxy server or firewall could/would break it
 (due to the cache and collect implementations that most proxies do).
 Better to break the processing in two:
 1) The work to be done is assigned a uid or something similar to prevent it
 from being done twice
 2) The user presses the button which passes the uid in a hidden field (for
 example)
 3) The serlvet responds by kicking off the big process with jms and sends
 back a page that displays a "processing..." message and uses javascript to
 redirect (with a place to click just in case javascript is turned off)
 4) The url redirected to includes the uid to identify the process for which
 the result is desired
 5) When the process is completed, the information is placed in some known
 location (e.g. HttpSession or database) and the pending request to find the
 result can return the result
 Cameron Purdy
 [email protected]
 http://www.tangosol.com
 WebLogic Consulting Available
 "Terry" <[email protected]> wrote in message
 news:[email protected]...
 > We have a servlet whose service method is along these lines
 >
 > PrintWriter out = response.getWriter();
 > [or ServletOutputStream out = response.getOutputStream();]
 >
 > out.println(someStuff);
 > out.flush();
 > [lots of heavy processing]
 >
 >
 > The aim of which is to send a message to the user's screen so they don't
 > have to wait for the processing to be finished. From what (little) I
 > understand the out.flush should ensure that this happens, but it doesn't -
 > the server doesn't respond until after the processing. (This happens
 whether
 > we use the printwriter or the servletoutputstream)
 >
 > Does anyone have any idea why this doesn't work, or, perhaps more
 > importantly, what would work.
 >
 >
 >

JDK 1.6_07 with Windows: System.out.flush() does not work...

I wonder if this is a known issue: Since I upgrade the jdk1.6 version to the _07 pack, text IO does not work anymore with WinXP cmd.exe window. Assuming a static import of System.out, I use:
static void prompt()
out.print(pr); //pr is a prompt string...
out.flush();
}works as usual with Unix/Linux, but with windows nothing will be written to the terminal, until I make at least one input. In that case a barrage of cached prompts appear all at once.
Do we have a bug for it, can we work around somehow?
Thomas

Since this code works correctly in Java 6u10 on Windows XP
System.out.print("This is the data");
System.out.flush();You are apparently doing something unusual or wrong. What is "out"?
Show a small sample program that compiles and exhibits the problem when executed.

Strange problem with out.flush

Code:
package com.test.servlets;
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.IOException;
import java.io.PrintWriter;
public class MultiThreadTest extends HttpServlet {
public void doGet(HttpServletRequest req,HttpServletResponse resp) throws ServletException,IOException {
 doPost(req,resp);
public synchronized void doPost(HttpServletRequest req,HttpServletResponse resp) throws ServletException,IOException {
 PrintWriter out = resp.getWriter();
 out.println("Multi Thread Test");
 out.flush();
 try {
 Thread.currentThread().sleep(10000);
 catch(InterruptedException ie) {
 ie.printStackTrace(out);
 out.println("<a href=MultiThreadTest>Multi Thread Test</a> ");
}When i shield the out.fulsh() with "//"
The ie println all the text at one time after the sleep time,
So i use out.flush() to fulsh the text which before the sleep().
Then,ie show the "Multi Thread Test" and then after 10 seconds ,show the ""Multi Thread Test
But the strange thing is ,this time, the ie shows:
Multi Thread Test
<a href=MultiThreadTest>Multi Thread Test</a> 
It displays the HTML source code,why?

G'day mate,
To the best of my knowledge doGet() and doPost() are both already multi-thread enabled, unless your application explicitly implements the "SingleThreaded" interface, which your code doesn't appear to do. As it is the servlet containers 'job' to handle threading issues I wouldn't expect to be able to override the doPost() method without getting strange output.
I reckon your best bet would be to create a javabean from within doPost(), pass it the request and response objects and let it handle the timing...... also set doPost() back to it's default, otherwise only one request will be serviced at a time. If that is what you want to happen then implement the affore mentioned interface.
Hope this helps.
Regards
Davo

Out.flush() not working

I can't get the out.flush to work. The page is paused until all values are finished then it is displayed. Here is my example code.
<pre>
import java.io.*;
import java.sql.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class MyTest extends HttpServlet {
 public void init(ServletConfig conf) throws ServletException {
super.init(conf);
public void service(HttpServletRequest req, HttpServletResponse res)
throws IOException {
// res.setContentType("text/html"); //this nor the one below works
res.setContentType("multipart/x-mixed-replace;boundary=\"boundary\"");
PrintWriter out = res.getWriter();
for(int x=0;x<3;x++){
 out.println(" x = "+x);
 out.flush();
 try{
 Thread.sleep(1000); //in milliseconds - 1000 milliseconds = 1 second
 catch(InterruptedException ie){}
</pre>

You were hoping that the output of the servlet would be sent piece by piece to the client browser as you generated it? That is not how it works. Nothing is sent until you return from the service method. It is possible to do what I think you were hoping, but you have to work with the browser and have it refresh periodically. I have seen examples of that but I am not competent to try to explain it.

WebLogic 10.3.6 Times Out When Starting Web App

When starting our web app on WebLogic 10.3.6 using startWebLogic.sh on OEL (8 cores, 64 GB box), after about 5 to 6 minutes we receive a timeout error from WebLogic saying that it timed out trying to start the web app. The web app has some pre-computed indices to load which will take an estimated 10 to 15 minutes to load. Is there are way to control this timeout?

The time-out you are getting is that related to a transaction?
You can set the transaction time-out in the WebLogic console go to the JTA page for the domain, and change the value in the Timeout Seconds field.
When you are using EJBs, you can also set the time-out on a EJB basis, instead of configuring the time-out for the whole domain.
For example, in weblogic-ejb-jar.xml, you can configure the time-out by using:
<weblogic-ejb-jar ...>
 <weblogic-enterprise-bean>
 <ejb-name>YOUR_EJB_NAME</ejb-name>
 <enable-call-by-reference>True</enable-call-by-reference>
 <stateless-session-descriptor>
 <pool>
 <initial-beans-in-free-pool>25</initial-beans-in-free-pool>
 <max-beans-in-free-pool>50</max-beans-in-free-pool>
 </pool>
 </stateless-session-descriptor>
 <transaction-descriptor>
 <trans-timeout-seconds>600</trans-timeout-seconds>
 </transaction-descriptor>
 </weblogic-enterprise-bean>
</weblogic-ejb-jar>The transactions this EJB spawns can last for 10 minutes.

Jsp using out.flush() with no effect on Windows 7 IE9

I have several JSPs with long running java code inside. To inform the user about the progress I use this html code
<div id="working">
Current row number: 0 
Current row data: n/a 
</div>
and within my loop the js snippet to update the counter
%>
 <script language=javascript>
 document.getElementById("rowNumber").firstChild.nodeValue="<%=rowNumber%>";
 document.getElementById("rowData").firstChild.nodeValue="<%=firstValue%>";
 </script>
<% out.flush();
This works fine in IE8 on a Windows XP while the JSP is running on a Tomcat 6.0.10 on java 1.6. The user gets the counter updated after each flush(). This could be seen easily in the source code and the progress of the snippets coming from the JSP back to the client.
Now we change to Windows 7 IE9 on the client (same server setup) and this behaviour doesn't work at all. The counter is never displayed, the browser source code is never updated on the out.flush(). For the user it looks like having no counter behaviour at all!
It looks like the Win7 TCP/IP stack (or Java?) buffer the javascript snippets and therefore the browser could not render the counter.
Has anybody an idea why this happens? And is there another trick to get a "counter" working with a long running jsp on Win 7?
Best regards
Edited by: 936263 on May 23, 2012 8:53 AM

Hi,
Does this driver apply to Windows 7? Maybe there is some compatibility issue, could you get a updated driver?
Alex Zhao
TechNet Community Support

Out.flush() inside f:view

Hello all!
On my JSF page I would like to post the page so far to the client (browser) on a specific point.
The problem: calling out.flush() inside <f:view> results in Illegal to flush within a custom tagany idea?
Marcus

why do you call
<% out.flush(); %> ?
If you want just to send the page to the client you don't need to do this...
This is enough...
<html>
<head><title>test</title></head>
<body>
<f:view>
some content
some other content
</f:view>
</body>
</html>

Does out.flush() work in a JSP page without buffering?

 All:
 I am using WLS 4.51 and have found that it is not possible to flush the contents
 of the ServletOutputStream. I have seen this behavior in JSPs and Servlets.
 What I am trying to achieve is a simple status message that is displayed on the
 client for a long running transaction.
 TIA
 Brian


Hi.
You can use JSTL perfectly in ADF. I don't share the opinion of Oracle not recommends... there are a lot of official pages saying how to use JSTL in ADF.
<af:outputText value="#{fn:length(yourList)}"/>Yannick is saying that you can't mix lifecycles. Take care using $ or # operators :).
For example if you are using a JSTL c:forEach. Next code is going to crash:
<c:forEach var="..." value="${list}">
 <af:outputText value="#{list.item}"/>
</c:forEach>Because # is evaluated in prepareModel phase and $ while rendering.
I hope this help you.

What does out.flush(); do?

I can't find it in the API.

what does toilet.flush(); do? same thingTo extend the analogy, is
[url=http://java.sun.com/j2se/1.4.2/docs/api/java/io/Pr
>
ntWriter.html#PrintWriter(java.io.Writer,%20boolean)]Pr
ntWriter's autoFlush like those smart toiletsthat sense when to flush?And are there any output streams or writers that have
to be flushed twice like our toilet here at work?
Well, fortunately, Java (and the TCP/IP stack) hide the plumbing from you, so no. Internally, there could be a reflush (packet loss resend).

Configure Oracle Access Manager - from weblogic OIF instance page bombs out

I am trying to integrate OIF with Oracle Access Manager as SP integration module. But, when clicked on "Configure Oracle Access Manager" it throws the following error:
Oracle Access Manager cannot be configured properly. Make sure the Oracle Access Manager SDK Server has been configured properly and the required environment variables have been set. Details can be found on Online Help and Administrative Guide.
I have updated the environment variables and classpath, also confirmed the Access Server SDK to work properly by testing java JAccessGate.
any help is greatly appreciated.
The diagnostic logs show these errors:
========================
Login of admin identity cn=usca_iam_admin failed. Please check to make sure the admin user ID is valid.
at com.oblix.accessmgr.ObAccessManager.sendRequest(ObAccessManager.java:163)
at com.oblix.accessmgr.ObAccessManager.setAdmin(ObAccessManager.java:195)
at oracle.security.fed.admin.config.mbeans.OAMConfigUtils.configureOAM(Unknown Source)
at oracle.security.fed.admin.config.mbeans.AdminUtilMXBeanImpl.configureOAM(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:889)
at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMBeanInterceptor.internalInvoke(ContextClassLoaderMBeanInterceptor.java:94)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:245)
at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartInterceptor.internalInvoke(MBeanRestartInterceptor.java:116)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:245)
at oracle.as.jmx.framework.generic.spi.security.AbstractMBeanSecurityInterceptor.internalInvoke(AbstractMBeanSecurityInterceptor.java:174)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:245)
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.invoke(OracleStandardEmitterMBean.java:803)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:268)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323)
at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
My Oracle Access Manager is 10.1.4.3 and OIF is 11.1.1.3
thanks

Hello,
I'm having the same problem. Did anybody find a solution to fix it?
Any help is appreciated.
Regards,
Ignacio.

Weblogic.transaction.RollbackException: Transaction timed out after 32 seconds

following is the scenario.
EJB1{
method1{
createTransaction();
connectToDiffrentWebloic();
updateTransaction();

following is the scenario.
EJB1{
method1{
createTransaction();
connectToDiffrentWebloic();
updateTransaction();

System.out will not flush before input

Hello everyone,
I am using Netbeans 5.5, JDK6, and J2EE. I am new to the environment so I wrote a test application that would prompt a user to enter a string and then echo it. I have:
String str = "";
BufferedReader br = new BufferedReader(new nputStreamReader(System.in));
System.out.print("Enter a string: ");
System.out.flush();
try
str = br.readLine();
catch(IOException ex)
System.out.print(ex.toString());
System.out.print(str);
What is really bizarre is that System.out will NOT flush no matter what. My application will always ask for input before it even prompts the user for the string. This is what the output looks like when running:
init:
deps-jar:
compile:
run:
hello
Enter an string: hello
BUILD SUCCESSFUL (total time: 5 seconds)
Notice how I had to enter the string first? The only way that I have seen that it flushes is if I used println() instead of print. But what if I don't want the prompt to have an end line in it. This just seems like weird behavior. Also, I have tried using a Scanner for input and the results are the same. Not really sure what to do. Any help would be most appreciated. Thanks.

are you running this inside netbeans as well? the "console" view in netbeans (and eclipse, and probably other IDEs) is not a real console, it's a GUI component that the IDE writes to. it's behaviour isn't guaranteed to act like a real console. I've seen this sort of thing on eclipse before, but never used netbeans. but it still stands that an IDE's console view isn't an actual console/terminal window. that may well be the root of the problem

WebLogic Server Times OUT during DEBUG mode startup

Hi,
I am having a issue where my WebLogic Server 10.3 times out when I try to run it in debug mode in my workshop. Below is the error I get.
"Timeout waiting for Oracle WebLogic Server v10.3 at localhost to start. Server did not start after 480s. "
Do anyone have any idea why this is happening? I have reinstalled workshop but still same error.
Thanks

I have also seen this error when the debug mode does not start.
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
C:\bea103\JDK160~1\bin\java -client -Debug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms1200m -Xmx1200m -XX:CompileThreshold=8000 -XX:PermSize=192m -XX:MaxPermSize=192m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\bea103\WLSERV~1.3 -Dwls.home=C:\bea103\WLSERV~1.3\server -Dweblogic.home=C:\bea103\WLSERV~1.3\server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -DKS_URL=rmi://10.87.40.196:1188/KS -Dweblogic.ext.dirs=C:\bea103\patch_wlw1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_wlp1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_cie670\profiles\default\sysext_manifest_classpath;C:\bea103\wlportal_10.3\p13n\lib\system;C:\bea103\wlportal_10.3\light-portal\lib\system;C:\bea103\wlportal_10.3\portal\lib\system;C:\bea103\wlportal_10.3\info-mgmt\lib\system;C:\bea103\wlportal_10.3\analytics\lib\system;C:\bea103\wlportal_10.3\apps\lib\system;C:\bea103\wlportal_10.3\info-mgmt\deprecated\lib\system;C:\bea103\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\bea103\wlportal_10.3\portal\lib\security -Dweblogic.Name=AdminServer -Djava.security.policy=C:\bea103\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]

WebLogic Server 6.1 Transaction Time out Transaction

Hi all,
I got the following time out exception when executing a session bean. However, the exception does not happen every time when being executed.
Original Exception Stack Trace:
javax.transaction.TransactionRolledbackException: EJB Exception: : javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
     at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
     at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
     at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
     at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
     at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
     at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
     at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
     at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
     at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
     at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
     at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
     at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
     at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
     at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
     at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
     at $Proxy80.execute(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
     weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
     at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
     at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
     at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
     at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
     at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
     at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
     at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
     at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
     at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
     at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
     at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
     at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
     at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
     at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
     at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
     at $Proxy80.execute(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
     javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
     at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
     at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
     at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
     at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
     at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
     at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
     at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
     at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
     at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
     at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
     at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
     at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
     at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
     at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
     at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
     at $Proxy80.execute(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
     weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
     at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
     at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
     at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
     at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
     at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
     at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
     at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
     at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
     at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
     at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
     at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
     at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
     at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
     at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
     at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
     at $Proxy80.execute(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
     weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
     at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
     at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
     at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
     at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
     at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
     at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
     at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
     at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
     at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
     at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
     at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
     at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
     at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
     at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
     at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
     at $Proxy80.execute(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
     at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
     at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
     at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
     at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
     at $Proxy80.execute(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
     at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
Thanks,
Kaoru

No, I haven't set the attribute in the weblogic-ejb-jar.xml.
The transaction type of the stateless session bean is container. So, I suppose it uses the JTA time-out value which is now set to 30 secs.
Thanks,
Kaoru

Weblogic 10.3 SocketException at out.flush

Similar Messages

Maybe you are looking for