Weblogic9.2mp3 - socket timeout exception

we are seeing this with 9.2mp3
Nothing has changed in the application . Could it be a network or testing tool issue (this happens only during perf tests)
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1da4942:Socket[addr=/192.168.98.11,port=43659,localport=8001] - idle timeout: '60000' ms, socket timeout: '120000' ms', in the configured timeout period of '60' secs
     at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:950)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

It could be due to the configuration of the application on 9.2mp3? As you said that this is happening during perf testing, did you check the threadpool size for the application? May be there are not enough threads to accept the load during the perf tests.
I would suggest putting in a optimal value based on your load for the application threadpools and then check if the issues re-appears.
Thanks,
Patrick

Similar Messages

WebService Socket Timeout Exception before reaching timeout duration

Hi
My Server is Websphere Application Server 6.0.2.17
i got some times socket timeout exception before reach timeout duration. and also i have only default websphere settings for web service .
The exception is occurred in 19 seconds after hitting the service . i am not able to get the exact problem . because default timeout time is 300 seconds (i think like that)
Error Log
2/12/09 11:01:28:323 CET 00000f6a SystemOut O WebService Started --> Begin webservice method invocation (Method Name : getCustomerInfo(String cusID))
2/12/09 11:01:47:840 CET 00000f6d SystemOut Exception Occurred : java.net.SocketTimeoutException: Socket operation timed out before it could be completed
WebService Method Invocation Started time 11:01:28
WebService Timeout exception raised time 11:01:47
TimeoutDuration 00:00:19

Hi Mark,
with synchronous messages it is important to consider timeouts from each connection to be established. So soapUI-PI, then PI-BackendSystem plus anything that might be in between. If your timeout soapUI-PI is smaller than the following ones, you'll get that phenomenon. soapUI will cut the connection, but PI will hold it and maybe receive an answer from the backend. This answer will end up in the void, since the original requester (your soapUI) has already disconnected. But for PI, this will be OK and status "successful". PI does not control and monitor the client's connection.
In other words, the cancel of the connection is only performed for that same connection, it is not propagated to any subsequent connections.
Hope that I was clear enough,
Jörg

Socket timeouts while downloading huge amount of mails..................

Problem Statement:
I have created a utility(using JavaMail API) which downloads mails from the Exchange Server 2003(MS Windows server 2003) using IMAP service.
The utility uses 5 different threads(each creating it's own separate IMAP session) to download the mails from the same user mailbox account. A separate main controlling thread has been used, which feeds these 5 threads with the start-end message counts with a batching of 100 messages. The 5 threads also set the message delete flag after downloading/processing the messages. And finally the main controlling thread expunges the mail box account after a certain amount of time(1 hour). (The service also takes care of expunging the messages at the startup as well.)
The utility runs fine for a long time(say 8 to 10 hours) but then it suddenly starts giving socket timeout exceptions and then it continues giving the exceptions. I even introduced a delay of 15 min. and increased the socket timeout period but to no avail. All i had to do was to restart the exchange server and after some time, i again started the utility and it worked finely.
Exception stack trace:
* BYE JavaMail Exception: java.net.SocketTimeoutException: Read timed out
javax.mail.MessagingException: * BYE JavaMail Exception: java.net.SocketTimeoutException: Read timed out;
nested exception is:
com.sun.mail.iap.ConnectionException: * BYE JavaMail Exception: java.net.SocketTimeoutException: Read timed out
at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:477)
at javax.mail.Service.connect(Service.java:275)
at com.newgen.omni.mail.mswrapper.MailServerWrapper.connect(MailServerWrapper.java:102)
at com.newgen.omni.mail.mswrapper.MailServerWrapper.<init>(MailServerWrapper.java:33)
at com.newgen.omni.mail.scheduler.Scheduler.Process(Scheduler.java:352)
at com.newgen.omni.mail.scheduler.Scheduler.run(Scheduler.java:293)
at com.newgen.omni.mail.scheduler.Scheduler.execute(Scheduler.java:1026)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
Caused by: com.sun.mail.iap.ConnectionException: * BYE JavaMail Exception: java.net.SocketTimeoutException: Read timed out
at com.sun.mail.iap.Protocol.handleResult(Protocol.java:299)
at com.sun.mail.iap.Protocol.simpleCommand(Protocol.java:316)
at com.sun.mail.imap.protocol.IMAPProtocol.login(IMAPProtocol.java:290)
at com.sun.mail.imap.IMAPStore.login(IMAPStore.java:517)
at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:458)
... 8 more
The code snippet to make the IMAP connection (all the 6 threads call it separately to create separate sessions):
Properties prop = new Properties();
logger.debugMsg("mailCapture :: Process :: Initializing IMAP context...");
prop.put("mail.imap.appendbuffersize","-1");
prop.put("mail.imap.allowreadonlyselect","true");
prop.put("mail.imap.separatestoreconnection","true");
prop.put("mail.imap.partialfetch","false");
prop.put("mail.imap.connectiontimeout", "1200000");
prop.put("mail.imap.timeout", "1200000");
session = Session.getInstance(prop);
//session.setDebug(true);
logger.debugMsg("mailCapture :: Process :: Get Store...");
store = session.getStore("imap");
try
store.connect(mailServerInfo.strServerIP, Integer.parseInt(mailServerInfo.strServerPort), mailServerInfo.strUsername, mailServerInfo.strPassword);
catch(MessagingException ex)
logger.logException(ex.getMessage(), ex);
Thread.sleep(900000);
throw ex;
I have tried with session debugging as well when the exceptions started coming(restart the service with session debugging true) but it doesnt give me any information worthwhile, either the utility stucks on the store.connect or otherwise if it connects then it stucks while opening the folder while using (sourceMailAccountFolder.open(Folder.READ_WRITE);) and doesn't move any further.
NOTE: While the IMAP service is throwing socket time out exceptions, at the same time I am able to access my account using the http://<ip>/exchange/administrator and the server machine cpu and memory usages are very low as well. I am also having a separte utility which uploads mails using smtp and it is also working fine and uploading the mails whilest the imap utility is throwing the socket timeout exceptions.......
Please help on this as i am not able to resolve it myself.....................

Can simultaneously uploading the mails through smtp affect the imap performance(and hence the javamail).
Note: The mailbox size is over 200000 mails when it started giving exceptions.
When the socket timeout exceptions came(i have experienced them for the last three days), i was still able to send mails using smtp and the telnet also working fine and even without any delays, infact as i said, the utility sometimes connects but then fails, while using sourceMailAccountFolder.open(Folder.READ_WRITE); giving socket timeout errors and then dnt go any further.
Right now i have stopped the smtp uploading the mails(for the first time) but still the javamail takes a long time(variable) to connect to the server and the mail body and attachment accessing speed is also a little slow, will see and post back, if the socket timeout exceptions come again.
Note: My aim is to download more than some 250000 mails within a day through javamail, whilest i am simultaneously uploading them using SMTP.
My other survice, using SMTP pumps in messages within a loop.

Unable to read AsynchronousSocketChannel after getting timeout exception

i am trying to read some data on the server using a AsynchronousSocketChannel .
I have this scenario :
1- Call channel.read : this will print "Received"
2- Call channel.read : this should fail due to timeout exception.
3- Call channel.read : I am sending data in this case but I got the exception "Reading not allowed due to timeout or cancellation"
Below is the source code
My environment is :
OS : Windows 7
JDK :
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
package com.qmic.asynchronous;
import java.io.InputStream;
import java.io.PrintWriter;
import java.net.InetAddress;
import java.net.InetSocketAddress;
import java.net.Socket;
import java.nio.ByteBuffer;
import java.nio.channels.AsynchronousChannelGroup;
import java.nio.channels.AsynchronousServerSocketChannel;
import java.nio.channels.AsynchronousSocketChannel;
import java.nio.channels.CompletionHandler;
import java.util.concurrent.ConcurrentLinkedQueue;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.Future;
import java.util.concurrent.TimeUnit;
public class NIOChannel {
     public static void main(String[] args) {
          try{
               MyAsynchronousTcpServer server = new MyAsynchronousTcpServer();
               Thread serverThread = new Thread(server);
               serverThread.start();
               Socket socket = new Socket(InetAddress.getByName("127.0.0.1"), 9001, InetAddress.getByName("127.0.0.1"), 9003);
               socket.setSoTimeout(30000);
               socket.setKeepAlive(true);
               if (socket.isConnected()){
                    PrintWriter dos = new PrintWriter(socket.getOutputStream());
                    InputStream input = socket.getInputStream();
                    byte[] buffer = new byte[1024];
                    // Data of the first call
                    dos.print("ABCDEFGH");
                    dos.flush();
                    byte[] data = new byte[50];
                    socket.getInputStream().read(data);
                    // Print the result from server, written in handler of first read operation.
                    System.out.println("Result is:" + new String(data));
                    if (data.length > 0){
                         Thread.sleep(10000); // Wait for 10 Seconds so the second read on the server will fail.
                    // Data of the third call
                    dos.print("ABCDEFGH");
                    dos.flush();
          }catch(Exception ex){
               ex.printStackTrace();
     class MyAsynchronousTcpServer implements Runnable{
          final int SERVER_PORT = 9001;
          final String SERVER_IP = "127.0.0.1";
          private int THREAD_POOL_SIZE = 10;
          private int DEFAULT_THREAD_POOL_SIZE = 2;
          ConcurrentLinkedQueue<ListenHandler> handlers = new ConcurrentLinkedQueue<ListenHandler>();
          boolean shutDown = false;
          public void run(){
               //create asynchronous server-socket channel bound to the default group
               try {
                    // Create the ChannelGroup(thread pool).
                    ExecutorService executorService = Executors.newFixedThreadPool(THREAD_POOL_SIZE);
                    AsynchronousChannelGroup group = AsynchronousChannelGroup.withCachedThreadPool(executorService, DEFAULT_THREAD_POOL_SIZE);
                    AsynchronousServerSocketChannel asynchronousServerSocketChannel =
                         AsynchronousServerSocketChannel.open(group);
                    if (asynchronousServerSocketChannel.isOpen())
                         //bind to local address
                         asynchronousServerSocketChannel.bind(new InetSocketAddress(SERVER_IP, SERVER_PORT));
                         while(!shutDown){
                              Future<AsynchronousSocketChannel> asynchronousSocketChannelFuture =asynchronousServerSocketChannel.accept();
                              final AsynchronousSocketChannel channel = asynchronousSocketChannelFuture.get(); // Timeout can be specified in the get() function, thread is blocked here
                              System.out.println("New channel created successfully");
                              // First call, should print Result of call 1 is : 10 (size of ABCDEFGH)
                              ByteBuffer buffer1 = ByteBuffer.allocateDirect(250);
                              channel.read(buffer1, 5, TimeUnit.SECONDS, null, new CompletionHandler<Integer, Object>() {
                                   @Override
                                   public void completed(Integer result, Object attachment) {
                                        System.out.println("Result of call 1 is :" + result);
                                        ByteBuffer response = ByteBuffer.wrap("Received".getBytes());
                                        channel.write(response);
                                   @Override
                                   public void failed(Throwable exc, Object attachment) {
                                        exc.printStackTrace();
                              Thread.sleep(3000);
                              // Second read, should print error InterruptedByTimeoutException
                              ByteBuffer buffer2 = ByteBuffer.allocateDirect(250);
                              channel.read(buffer2, 5, TimeUnit.SECONDS, null, new CompletionHandler<Integer, Object>() {
                                   @Override
                                   public void completed(Integer result, Object attachment) {
                                        System.out.println("Result of call 2 is :" + result);
                                   @Override
                                   public void failed(Throwable exc, Object attachment) {
                                        exc.printStackTrace();
                              Thread.sleep(9000);
                              // Second read operation was failed, no try to read again . AN EXCEPTION IS THROWN HERE : Reading not allowed due to timeout or cancellation
                              ByteBuffer buffer3 = ByteBuffer.allocateDirect(250);
                              channel.read(buffer3, 5, TimeUnit.SECONDS, null, new CompletionHandler<Integer, Object>() {
                                   @Override
                                   public void completed(Integer result, Object attachment) {
                                        System.out.println("Result of call 3 is :" + result);
                                   @Override
                                   public void failed(Throwable exc, Object attachment) {
                                        exc.printStackTrace();
                    else
                         System.out.println("The asynchronous server-socket channel cannot be opened!");
               catch (Exception ex)
                    ex.printStackTrace();
                    System.err.println(ex);
     }

I'm having the same "Unable to read the SIM card" issue. My phone is less than two months old, the unable to read SIM card issue started about a week after I purchased the phone. That was followed by a host of erratic, sporadic issues to the phone becomes unusable and the only way to temporarily fix it is to remove the battery for a few seconds. I've gone through the factory reset with Verizon reps where I purchased the phone from as well as with a Verizon online Chat representative. In a nutshell, I got a ticket to send the phone back to Samsung in Plano, Texas to get the phone fixed, I am going to do that today because this problem is ridiculous.

UDP socket timeout

when i am running my application using jre1.3 it is working fine. tcpdump captured on server of the same is below: (this is correct)
13:01:37.428071 192.168.232.23.52794 > 192.168.233.22.aims_router: udp 21 (DF)
13:01:37.431597 192.168.233.22.aims_router > 192.168.232.23.52794: udp 12 (DF)
where as when i am running my application using jre1.4 it is working not working. tcpdump captured on server of the same is below: (this is not correct)
12:53:16.028002 192.168.232.23.52762 > 192.168.233.22.aims_router: udp 16 (DF)
12:53:16.031922 192.168.233.22.aims_router > 192.168.232.23.52762: udp 9 (DF)
12:53:16.032002 192.168.232.23 > 192.168.233.22: icmp: 192.168.232.23 udp port 52762 unreachable [tos 0xc0]
12:53:23.032577 192.168.232.23.52764 > 192.168.233.22.aims_router: udp 16 (DF)
12:53:23.036566 192.168.233.22.aims_router > 192.168.232.23.52764: udp 9 (DF)
12:53:23.036629 192.168.232.23 > 192.168.233.22: icmp: 192.168.232.23 udp port 52764 unreachable [tos 0xc0]
12:53:30.036143 192.168.232.23.52764 > 192.168.233.22.aims_router: udp 16 (DF)
12:53:30.039451 192.168.233.22.aims_router > 192.168.232.23.52764: udp 9 (DF)
12:53:30.039525 192.168.232.23 > 192.168.233.22: icmp: 192.168.232.23 udp port 52764 unreachable [tos 0xc0]
i searched in google for this i got one link
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6204940
so based on this URL I tried with jdk1.4.2_08(b03), still the problem exists.
it is greatful if any one gave the solution for this problem.
regards,
Radha

I have already done a simple UDP chat application that worked perfectly on the LAN.
And i executed the same application across the Internet, using the IP address found on whatismyipaddress.com
And the application was able to send messages to the other end. And there was no packet loss, as i was trying to send small messages such as Hello, Hi etc. thats all.
When i tried the same thing using TCP, i wasn't able to connect to the other system, and i got SocketException : Timeout Exception..
The logic of the TCP application,
// Server part
1. Create a ServerSocket object.
2. Accept an incoming client.
3. Run a thread to accept message, and print it in some text field.
4. And a send button action event, that converts the string to bytes, and send it across.
// Client part
1. Create a socket, to connect to the other system.
2. Run a thread to accept message, and print it in some text field.
3. And a send button action event, that converts the string to bytes, and send it across.

Invoking web service from OBIEE11g failed socket timeout

Hi,
I encountered an error when I invoke web service from OBIEE 11g. The web serivce resides on Websphere running on other machine.
An error says that "Invoking web service failed due to socket timeout." and it seems that it stopped in just 40 secs.
Is there any settings of WebLogic server to avoid this? This web service normally runs for more than 60 sec.
I have checked several parameters in WebLogic admin console and changed those values, but I still receive the same error.
Invoking the same web service from SOAPUI sustains for more than 60 secs.
Regards,
Fujio Sonehara

Don't be too surprised. Sun figured this bug out in short order. I got the same error message when trying to do the same thing, just for the heck of it. Reference this article for details.
http://java.sun.com/webservices/docs/ea2/jaxrpc/ReleaseNotes.html
It contains information about bugs fixed in the WSDP EA2. So in answer to your question, download the newer pack from
http://java.sun.com/webservices/downloads/webservicespack.html
and your bug will go away. Happy Coding.
Legal Problems?
Legal Solutions, for a lot less than you might think.
[email protected]
http://www.prepaidlegal.com/go/pritchard45

Help with flex4unit ant build.xml: Socket timeout waiting for flexunit report

I'm having trouble setting up ant to build and test my project locally and I'm not sure what the next step is.
Info:
Running on XP/Cygwin.
All of the files that FlexUnit4 references when used in Flash Builder are in my '${basename}/libs' folder (eg FlexUnit4_1.0.swc).
I've placed the flexunit4 task in my ant/libs folder.
I'm getting two errors...
I don't think I've set up the 'socket' stuff right for the tests. It just sits and waits then dies...
[flexunit] Waiting for client connection ...
(about a minute later)
[flexunit] Stopping server ...
[flexunit] End of test data reached, sending acknowledgement to player ...
[flexunit] Closing client connection ...
[flexunit] Closing server on port [1024] ...
BUILD FAILED
java.util.concurrent.ExecutionException: Socket timeout waiting for flexunit report
Plus this is the error I get from the flash player:
ReferenceError: Error #1065: Variable mx.skins.spark::BorderSkin is not defined.
I don't know why it's complaining about Borderskin as I think I have included all the flex4 libs I could find. I suspect this second error is causing the first error?
Any help appreciated. I think I'm just setting it up all wrong.
Screencap of errors:
http://twitpic.com/l7ay8
build.xml:
http://gist.github.com/20804

Finally got everything working using the files from the CI Example which what i probably should have done in the first place.
So a rough guide for anyone just starting out with this:
Download the Flex 4 'workspace' from the digital primates hudson server . This appears to contain flexunit library and examples in various stages of development.
I used Flex Builder 4 Beta 2 to set up my Test Suite and Test Cases.
I then loaded the libs folder from:
workspace.zip\workspace\project\FlexUnit4SampleCIProject
into my flex project's libs folder:
this includes:
FlexUnit4.swc
FlexUnit4CIListener.swc
flexUnit4UIRunner.swc
flexTasks.jar
flexUnitTasks.jar
I didn't need to remove the FlexUnit4 stuff that is 'referenced' automatically by flash builder when you start adding flexunit4 tests/suites.
Then I used a modified version of the TestRunner.mxml found in:
workspace.zip\workspace\project\FlexUnit4SampleCIProject\src\test\flex
The lines to pay attention to are the ones that look like:
static public function currentRunTestSuite():Array {
    var testsToRun:Array = new Array();
    testsToRun.push(packagename.TestSuiteName);
    testsToRun.push(packagename.TestClassName);
    return testsToRun;
Just make sure you update this list to include all of the test suites &/or individual tests you want to run.
I made this a static function and modified the code in the "FlexUnitApplication.mxml" file to use this function so i'd only need to update one list of suites/tests.
FlexUnitApplication.mxml is generated automatically when you run FlexUnit4 tests in the Flash Builder 4 Beta 2 IDE.
This is the build.xml file I'm using in the project:
http://gist.github.com/208211
Change the name of the project from "Flare" to whatever and adjust the other path settings where required (though you might want to write this from scratch at least once so you understand roughly what is going on).
The Debug Flash Player must be installed on the server otherwise you'll get a:
java.util.concurrent.ExecutionException: Socket timeout waiting for flexunit report
...while it waits for the non-existant debugger to attach. (This is obvious but I did forget and was a bit bewildered for a moment)
Need to also ensure the environment variable:FLEX_HOME is set to the location you installed the flex sdk...by editing your .bashrc setting the environment variable the in the Hudson Configuration.
You'll need to point Hudson at your ant installation and your jdk installation. If you downloaded he sdk, be aware you might need to point it to the jdk folder inside the place you installed the sdk.
And I think that's all the problems I had. Hope it's useful to someone... if anyone who actually knows what they are doing can point out any potential issues/better ways of doing things, feel free to comment.
Thanks to Brian (legrosb) and Mike (mlabriola) for their assistance!

Handle timeout exception in rfc call

Dear SAP Experts,
I have been searching for a while and could not find a satisfactory answer to my problem.
I use SAP - CRM and call other SAP and non-SAP systems via RFC.
I need to handle all exceptions, otherwise WEB UI displays a full page exception details, which is unacceptable on a production system.
I have the following piece of code:
CALL FUNCTION FUNCTION_NAME DESTINATION DEST
    EXPORTING
      S_IMPORT              = INPUT_DATA
    IMPORTING
      S_EXPORT              = OUTPUT_DATA
    EXCEPTIONS
      SYSTEM_FAILURE        = 1 MESSAGE err_msg " catch system failure
      COMMUNICATION_FAILURE = 2 MESSAGE err_msg " catch communication errors
      OTHERS                = 99.                " catch everything else
It handles most of exceptions, however, it cannot process timeouts. Is there a way to handle timeout in ABAP RFC call? Is timeout exception uncatchable? If so is there a way around?
Can you please suggest some solution as I am running out of ideas.
Regards,
Dominik

I have found a solution. To approach this I use asynchronous function call.
TRY.
    CALL FUNCTION ZZ_TEST_TIMEOUT' DESTINATION lv_dest STARTING NEW TASK 'TIMEOUT_TASK'
    CALLING me->callback ON END OF TASK
        EXCEPTIONS
          SYSTEM_FAILURE        = 1 MESSAGE err_msg " catch system failure
          COMMUNICATION_FAILURE = 2 MESSAGE err_msg " catch communication errors
          OTHERS                = 99.                " catch everything else
        WAIT UNTIL READY EQ 'X' UP TO 55 SECONDS.
        IF READY NE 'X'.
          RAISE EXCEPTION TYPE CX_TIMEOUT.
        ELSE.
          WRITE / 'success'.
        ENDIF.
CATCH CX_ROOT INTO OREF.
   WRITE / 'TIMEOUT EXCEPTION'.
ENDTRY.
callback sets variable READY to abap_true when data is received.
The trick is to use UP TO 55 SECONDS. after wait, which is shorter than the server timeout. This terminates function call and gives opportunity to code your own timeout behavior.

Error BEA-101083 Socket Timeout

Hello, we have a WebLogic Server 8.1 SP2 and we found the following error:
<Dec 12, 2005 3:33:32 AM CET> <Error> <HTTP> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1cc2438 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:775)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
Any idea?
Thanks

As lot fo people we have the same problem.
But I have still not found a concreate solution.
####<08-May-2006 10:02:36 o'clock CEST> <Error> <HTTP> <quatro> <WlsAdm> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@8db03f0 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
     at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(Lweblogic/time/common/Schedulable;)V(SocketMuxer.java:799)
     at weblogic.time.common.internal.ScheduledTrigger.run()Ljava/lang/Object;(ScheduledTrigger.java:243)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(Optimized Method)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
     at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
     at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:223)
     at weblogic.time.server.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:50)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
     at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
>

FlexBuilder 3 - Profiling - Socket Timeout

I'm working on a desktop AIR application and it's time to do
some profiling. However, I cannot get the profiler to work and I
feel like I've tried
everything. I've seen evidence of others having this
problem, but have yet to find a solution that works for me.
When I launch the application with the profiler, the
application launches and works ok. But in the FlexBuilder console,
I see a "Socket timeout." message repeat on occasion. I never see
the extra popup window that's supposed to allow me to configure the
profiling session.
I use Windows Vista and have no firewalls or anti-virus
running. Here are things I tried:
Uninstalling the Flash Player and FlexBuilder. This upgraded me
from 3.0 to 3.0.1. No change.
Changing the port from 9999 to a few different port numbers.
Installing a fresh copy of FB3 on a Windows XP laptop I have.
It shows the same messasge!
Thinking it may be something in my project, I created a new
very simple project and still got the error.
So, no firewalls and a brand spankin' new installation of
FlexBuilder (with the Flash player that comes with it) in two
totally different environments. I'm running out of ideas to try,
but the app really needs some profiling.
Can anyone give me some ideas?

Adobe Newsbot hopes that the following resources help you:
Broadcast and media:
In Flex Builder, you add the compatibility-version compiler
option to the Additional ..... Applications are not compatible with
signed framework RSLs.
Link:
http://www.adobe.com/go/gntray_ind_broadcast_media
mikemo Â» What to do if Flex Builder says,
âInstalled Flash Player:
If you have installed Flex Builder, and when try to debug you
get an error message that says âInstalled Flash
Player is not a debugger,â or if the Flex
Link:
http://www.morearty.com/blog/2006/06/30/what-to-do-if-flex-builder-says-installed-flash-pl ayer-is-not-a-debugger/
Flex 3:Feature Introductions:Flex 3 RSLs - Adobe Labs:
The signed RSL may have been put into the Flash Player Cache
by visiting ... To use RSLs in Flex Builder, modify the project
properties by adding RSL
Link:
http://labs.adobe.com/wiki/index.php/Flex_3:Feature_Introductions:Flex_3_RSLs
Flex developer, Campbell Anderson, from New Zealand - xsive
blog:
Mar 25, 2008 ... Right click the flash player instance in the
browserâ¦ yep its the latest player ... Is anyone
out there using RSLs yet? or the profiler?
Link:
http://blog.xsive.co.nz/archives/269
Flex 3:Release Notes - Adobe Labs:
3.4.1 Uninstalling Flex Builder 3.4.2 Uninstalling Flash
Player ..... SDK-12685 There is an issue where the line number of
an error is completely wrong,
Link:
http://labs.adobe.com/wiki/index.php/Flex_3:Release_Notes
Disclaimer: This is an automated post from Adobe Newsbot.
Newsbot tries to help forum users by analyzing their post and
suggesting helpful links.

Transaction Timeout Exception

Hello all
Problem...
I am retrieving approx 1200 records from an Oracle database via an CMP EJB findByXXXXX method. The problem is my Transaction times out after 30 seconds.
What I have already done...
I'm using Weblogic 6.0 and have configured the JTA to timeout after 2 minutes. However, I'm still getting a Transaction timeout exception after only 30 seconds. I would Appreciate any help. Thank-you....
Mark.

Sounds like you might be running into this bug:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.transaction&item=379&utag=

Weblogic invoking web service failed due to socket timeout

Hi,
I encountered an error when I invoke web service from OBIEE 11g. The web serivce resides on Websphere running on other machine.
An error says that "Invoking web service failed due to socket timeout." and it seems that it stopped in just 40 secs.
Is there any settings of WebLogic server to avoid this? This web service normally runs for more than 60 sec.
I have checked several parameters by WebLogic admin console and changed those values, but I still receive same errors.
Regards,
Fujio Sonehara

Hey Eason,
As I had previously mentioned, I have checked the FE server certs and have mentioned the signing algorithm it used to sign the certs, which was sha1DSA and not sha1RSA, I even checked my CA list of issued certs and have found all certs are signed the same.
Signature algorithm: sha1DSA
Signature Hash Algorithm: sha1
Public Key: RSA (1024 bit)
I could run request and reinstall all day long it will still get the same certs signed with the algo..
Doing some research I attempted to see if I could change the signing cert for a specific cert template that was being used to issue the Lync FE certs... however seems that from according to
this, that I'd have to completely rebuild my CA before I'd be able to request and issue a cert with the proper signing algorithm?!
This
says its possible but not supported, what do I do in this situation? Is my only option to rebuild teh entire CA and cert infrastructure?
I noticed my CSP is set to Microsoft Base DSS Cryptographic Provider, and under the CSP folder there is no "CNGHashAlgorithm" key so I'm using a "Next Gen CSP" apparently? Is this CSP good enough to support Lync...Straight up where is
the Lync documentation on the CA setup requirements??
This google link doesn't tell you how you should setup a CA for Lync, what settings need to set etc..

Query getting Hung Up and Application giving me TimeOut exception

Hello Guys,
I have an ASP.NET MVC5 application using database SQL Server 2013.
I have stored procedure with multiple steps.
I am facing a strange problem where in when I run a stored procedure that has multiple steps one of the query from the stored procedure hungs up in between the process and my application gives me a Timeout Exception.
When I run the query in a New Query window in MSSQL it just takes 3 seconds to run and gives me desired results.
IMPORTANT : The table from which I am running select statement is having 3 million records, it has additional 2 Inner Joins with both tables having additional 1 million records
In the procedure at a specific step I am trying to count the number of records that have a specific Product as follows:-
SELECT COUNT(sp.ProductId) AS NumberOfProducts
FROM SoldProducts AS sp
INNER JOIN Products AS p ON p.ProductId = sp.ProductId
INNER JOIN ProductTypes AS pt ON pt.ProductTypeId = p.ProductTypeId
WHERE (pt.ProductCode = @ProductCode) AND (sp.ProductSoldTimeStamp >= @StartDate) AND (sp.ProductSoldTimeStamp <= @EndDate)
Query doesn't move forward from this step.
Thanks in adavance.

I am facing a strange problem where in when I run a stored procedure that has multiple steps one of the query from the stored procedure hungs up in between the process and my application gives me a Timeout Exception.
When I run the query in a New Query window in MSSQL it just takes 3 seconds to run and gives me desired results.
Slow in the Application, Fast in SSMS?
José Diz Belo Horizonte, MG - Brasil

Socket timeout on Mac

Hello,
I am trying to run the flexunit ANT task on a Mac but keep getting the following error.
[flexunit] Stopping server ...
[flexunit] End of test data reached, sending acknowledgement to player ...
[flexunit] Closing client connection ...
[flexunit] Closing server on port [1024] ...
"Socket timeout waiting for flexunit report"
I see the test runner launch in Flash Player but then nothing else happens after that. I'm assuming FlexUnit isn't able to communicate with flash player but at this point i am not sure how to remedy the problem.
Does anyone have any suggestions on how to get flexunit and ANT working on a Mac?
Thanks.

Thanks for the help so far. I am using the RC1 SWCs. I've also tried different ports but that didn't help either. The flexUnit.cfg file is getting created.
This is what my flexunit task looks like (defined in a macro)...
            <flexunit swf="@{bin.dir}/@{mxml.name}.swf" toDir="@{report.dir}"
                player="flash"
                headless="true"
                haltonfailure="false"
                verbose="true"
                localTrusted="true" />
And here is my build output...
[flexunit] Using the following settings:
[flexunit]     haltonfailure: [false]
[flexunit]     headless: [true]
[flexunit]     localTrusted: [true]
[flexunit]     player: [flash]
[flexunit]     port: [1024]
[flexunit]     snapshot: [false]
[flexunit]     snapshotFile: [---/controller/controller-shell/report/snapshot.jpg]
[flexunit]     swf: [---/controller/controller-shell/bin/ControllerTestRunner.swf]
[flexunit]     timeout: [60000ms]
[flexunit]     toDir: [---/controller/controller-shell/report]
[flexunit]     verbose: [true]
[flexunit]     xcommand: [xvfb]
[flexunit] Setting up server process ...
[flexunit] Starting server ...
[flexunit] OS: [Mac OSX]
[flexunit] Opening server socket on port [1024].
[flexunit] Waiting for client connection ...
[flexunit] Launching player:
[flexunit] Executing 'open' with arguments:
[flexunit] '---/controller/controller-shell/bin/ControllerTestRunner.swf'
[flexunit] The ' characters around the executable and arguments are
[flexunit] not part of the command.
[flexunit] Created local trust file at [/Users/arumsey/Library/Preferences/Macromedia/Flash Player/#Security/FlashPlayerTrust/flexUnit.cfg]
[flexunit] Stopping server ...
[flexunit] End of test data reached, sending acknowledgement to player ...
[flexunit] Closing client connection ...
[flexunit] Closing server on port [1024] ...
BUILD FAILED
---/controller/build/macros.xml:64: java.util.concurrent.ExecutionException: Socket timeout waiting for flexunit report

Does a timeout exception will occur before every StuckThread Exception ?

Hi,
          What is the difference between weblogic.transaction.internal.TimedOutException and Stuck Thread exception.
          I found the following definitions for both the exceptions.
          Stuck Thread exception :
          WebLogic Server diagnoses a thread as stuck if it is continually working (not idle) for a set period of time. You can tune a server's thread detection behavior by changing the length of time before a thread is diagnosed as stuck, and by changing the frequency with which the server checks for stuck threads. (http://edocs.bea.com/wls/docs81/perform/WLSTuning.html#1125714)
          Timeout Seconds:
          The transaction timeout in seconds. If the transaction is still in the "active" state after this time (counting from begin()), it is automatically rolled back. Once the transaction moves on to the prepared state, however, this timeout parameter does not apply; the transaction is retried until all the resources are committed.(http://edocs.bea.com/wls/docs81/ConsoleHelp/domain_domain_config_jta.html)
          What is this "active" and "prepared" state ?
          And by default, the timeout-seconds is 30 seconds and StuckThread-seconds is 600 seconds. Does that mean that a timeout exception will occur before every StuckThread exception.
          It will be great if anyone can explain me this in detail.
          Thanks a lot in advance,
          Sudhir

Hi,
          yes you're timedOut will occur before you're Stuck Thread alert.
          For information stuck thread don't throw Exception: just an error log like:
          ####<7 avr. 2006 18 h 20 CEST> <Error> <WebLogicServer> <nemausac> <ProdCoreManagedServer1> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '20' for queue: 'weblogic.kernel.Default' has been busy for "1Â 114" seconds working on the request "cofidis.fwk.batch.EjbTraitementBatch_vab2xs_EOImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
          but the thread continue to do process.
          Wich time out , you're transaction is rolledback and you're process continue to do his work But you've got an exception at the next access to a ressources managed in the transaction (sql queyr or try to commit....)
          The transaction is in active state after the begin() and prepared state between the first call (prepared()) in a two phase commit and the second phase (commit()).
          Hope i help you

Weblogic9.2mp3 - socket timeout exception

Similar Messages

Maybe you are looking for