Sockets write/close operations hangs application

Hi!
I've got a trouble with my web-application. It'a s chat system, that uses Keep-Alive connections for messages output and that recieves messages through another socket.
Everything is fine with receiving messages. But after message is received, I need to send it to all recepients. So, I use Socket.write() method. If writing is failed, or user is logged off, I use Socket.close().
Problem is, that sometimes Socket.write() and Socket.close() are blocking their threads.
How can I avoid such a blocking behaviour?
If I'll rewrite everything to use not sockets, but socket channels, can it help to solve my problem?
Thanks.

If writes are blocking it can only mean that readers aren't reading. Fix that, and forget about the syncrhonization suggestion which is nonsense.
You can also use NIO in non-blocking mode to avoid blocking in writes, and it does lead to more scalable applications, but be prepared for about a 10x increase in complexity.

Similar Messages

  • Oracle Application Server crashes due to Socket Write Error

    I am using Oracle Application Server 9.0.3. Simple JSP application is running on it. We are using the application server connection pooling functionality. Following errors are occuring on it frequently and it causes the application server crash.
    First application response gets slow and eventually application server gets lock and it wont respond and we have to restart the application server. Our application is in production mode and we need to solve this issue immediately.
    ----------------Error1---------------------
    com.evermind.server.http.HttpIOException: Connection aborted by peer: socket write error
         at com.evermind.server.http.EvermindServletOutputStream.write(EvermindServletOutputStream.java:249)
         at com.evermind.server.http.EvermindJSPWriter.writeOut(EvermindJSPWriter.java:424)
         at com.evermind.server.http.EvermindJSPWriter.jspflush(EvermindJSPWriter.java:341)
         at com.evermind.server.http.EvermindJSPWriter.write(EvermindJSPWriter.java:490)
         at com.evermind.server.http.EvermindJSPWriter.write(EvermindJSPWriter.java:415)
         at schedule.schedulehome._jspService(_schedulehome.java:542)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:560)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:148)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:72)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
         at java.lang.Thread.run(Thread.java:479)
    ------------Error2---------------------
    com.evermind.server.http.HttpIOException: Connection aborted by peer: socket write error
         at com.evermind.server.http.EvermindServletOutputStream.write(EvermindServletOutputStream.java:249)
         at com.evermind.server.http.EvermindJSPWriter.writeOut(EvermindJSPWriter.java:424)
         at com.evermind.server.http.EvermindJSPWriter.jspflush(EvermindJSPWriter.java:341)
         at com.evermind.server.http.EvermindJSPWriter.write(EvermindJSPWriter.java:490)
         at com.evermind.server.http.EvermindJSPWriter.write(EvermindJSPWriter.java:415)
         at schedule.schedulehome._jspService(_schedulehome.java:557)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:560)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:148)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:72)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
         at java.lang.Thread.run(Thread.java:479)

    I am using Oracle Application Server 9.0.3. Simple JSP application is running on it. We are using the application server connection pooling functionality. Following errors are occuring on it frequently and it causes the application server crash.
    First application response gets slow and eventually application server gets lock and it wont respond and we have to restart the application server. Our application is in production mode and we need to solve this issue immediately.
    ----------------Error1---------------------
    com.evermind.server.http.HttpIOException: Connection aborted by peer: socket write error
         at com.evermind.server.http.EvermindServletOutputStream.write(EvermindServletOutputStream.java:249)
         at com.evermind.server.http.EvermindJSPWriter.writeOut(EvermindJSPWriter.java:424)
         at com.evermind.server.http.EvermindJSPWriter.jspflush(EvermindJSPWriter.java:341)
         at com.evermind.server.http.EvermindJSPWriter.write(EvermindJSPWriter.java:490)
         at com.evermind.server.http.EvermindJSPWriter.write(EvermindJSPWriter.java:415)
         at schedule.schedulehome._jspService(_schedulehome.java:542)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:560)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:148)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:72)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
         at java.lang.Thread.run(Thread.java:479)
    ------------Error2---------------------
    com.evermind.server.http.HttpIOException: Connection aborted by peer: socket write error
         at com.evermind.server.http.EvermindServletOutputStream.write(EvermindServletOutputStream.java:249)
         at com.evermind.server.http.EvermindJSPWriter.writeOut(EvermindJSPWriter.java:424)
         at com.evermind.server.http.EvermindJSPWriter.jspflush(EvermindJSPWriter.java:341)
         at com.evermind.server.http.EvermindJSPWriter.write(EvermindJSPWriter.java:490)
         at com.evermind.server.http.EvermindJSPWriter.write(EvermindJSPWriter.java:415)
         at schedule.schedulehome._jspService(_schedulehome.java:557)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:560)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:148)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:72)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
         at java.lang.Thread.run(Thread.java:479)

  • In AIR 3.x, a socket write()+flush() on a client will hang app if peer adverts TCP ZERO WINDOW

    In AIR 3.x, a socket write() + flush() on a client will hang (and freeze the entire app) if the socket peer advertises a ZERO TCP Window, i.e. no space available in peer receiver's socket buffer.
    AIR on Windows insists that the developer flush() the socket in order to write (any data at all).  When the peer (receiver) advertises a 0 byte tcp window, the client flush() call can sometimes take 10 seconds (i.e. 10000 milliseconds), whereas normally it should take 10 to 50 milliseconds.
    Additionally, AIR stayed in hung position.  Since the socket had TCP KEEPALIVE option enabled (at the server), the socket stayed open.  I let it stay hung overnight.  The next day when I rebooted the server, the socket got closed and finally the AIR program "RETURNED FROM the sock.flush()" call.  A timestamp before and after the call to flush() showed that the flush() call was in hung state for 56472475 milliseconds, i.e. 15.7 hours!  After it returned from the flush() call the AIR app was responsive and seemed to work properly.  Thus proving that it was indeed stuck (or blocked) on the flush() call for 15 hours trying to drain the data to a socket with zero tcp window condition.
    A tcp zero window condition on 1 socket hanging an entire app sounds concerning.
    Solution Suggestions:
    (1) What is needed is for the OutputProgress event to include a field for 'bytes that can be written safely without blocking on the socket', i.e. 'space available in underlying platform socket buffer' which would account for the socket send buffer size.
    (2) An alternative solution would be for AIR to provide a write-timeout setsockopt (or a writeTimeout() method on the socket), and return flush with an error (or EWOULDBLOCK), and call the OUTPUTPROG event only when there is enough space available.
    If there are any other workarounds, please let me know.
    Thank you.

    Question:  Does Adobe AIR expose the getsockopt() and setsockopt() calls on a socket?  It would be useful to apps to tune the io buffer sizes.
    Additional Details:
    RTT = 100+ milliseconds
    TCP Window Scaling enabled
    Secure Socket
    Hard to reproduce with plain TCP socket, but occurs without fail with SecureSocket.  Not knowing the underlying code base, am wondering if it is because the SSL encryption overhead (bytes) throws off the buffer available size compution in secure_sock.flush() .
    Thanks.

  • Simple Webserver SocketException: socket write error

    I'm stuck and need some help solving this problem.
    When I try to get the 404 message with the webserver, I get this in the output console:
    "HttpRequest - java.net.SocketException: Connection reset by peer: socket write error"
    I have found the part that makes the problem, but I can't find a solution.
    I hope someone can help me with this!
                try
                    outputStream.writeBytes(entityBody);
    import java.io.*;
    import java.net.*;
    import java.util.*;
    public final class WebServer
        public static void main(String[] args) throws Exception
            //Port number
            int port = 8080;
            // Establish the listen socket.
            ServerSocket webSocket = new ServerSocket(port);
            // Process HTTP service requests in an infinite loop.
            while(true)
                // Listen for a TCP connection request
                Socket tcpSocket = webSocket.accept();
                HttpRequest httpRequest = new HttpRequest(tcpSocket);
                Thread thread = new Thread(httpRequest);
                thread.start();
    import java.io.*;
    import java.net.*;
    import java.util.*;
    public class HttpRequest implements Runnable
        final static String CRLF = "\r\n";
        private Socket socket;
        private String path = "public_html/";
        public HttpRequest(Socket socket)
            this.socket = socket;
        public void run()
            try
                processReguest();
            catch(Exception ex)
                System.err.println(ex);
        private void processReguest() throws Exception
            // Get a reference to the socket's input and output streams.
            InputStreamReader inputReader = new InputStreamReader(socket.getInputStream());
            DataOutputStream outputStream = new DataOutputStream(socket.getOutputStream());
            BufferedReader buffReader = new BufferedReader(inputReader);
            String requestLine = buffReader.readLine();
            System.out.println();
            System.out.println(requestLine);
            String headerLine = null;
            while((headerLine = buffReader.readLine()).length() != 0)
                System.out.println(headerLine);
            // Extract the filename from the request line
            StringTokenizer tokens = new StringTokenizer(requestLine);
            tokens.nextToken();
            String fileName = tokens.nextToken();
            //Prepend a "." so that the file request is within the current directory
            fileName = path + "." + fileName;
            //Open the request file
            FileInputStream fileInputStream = null;
            boolean fileExists = true;
            try
                fileInputStream = new FileInputStream(fileName);
            catch(FileNotFoundException ex)
                fileExists = false;
            //Construct the response message.
            String statusLine = null;
            String connection = null;
            String contentLength = null;
            String contentTypeLine = null;
            String entityBody = null;
            String contentType = contentType(fileName);
            if(!requestLine.startsWith("GET") && !requestLine.startsWith("HEAD"))
                statusLine = "HTTP/1.0 405 Method Not Allowed" + CRLF;
                contentLength = "Content-Length: 0" + CRLF;
                connection = "Connection: close" + CRLF;
                contentTypeLine = "Content-type: " + "text/html" + CRLF;
                entityBody = "<HTML><HEAD><TITLE>405 - Method Not Allowed</TITLE></HEAD><BODY>405 - Method Not Allowed</BODY></HTML>";
                fileInputStream = null;
                fileExists = false;
            else if(fileExists && !contentType.equals("application/octet-stream"))
                statusLine = "HTTP/1.0 200 OK" + CRLF;
                contentTypeLine = "Content-type: " + contentType(fileName) + CRLF;
                connection = "Connection: close" + CRLF;
                contentLength = "Content-Length: " + Integer.toString(fileInputStream.available()) + CRLF;
            else if(fileExists && contentType.equals("application/octet-stream"))
                statusLine = "HTTP/1.0 415 Unsupported Media Type" + CRLF;
                contentLength = "Content-Length: 0" + CRLF;
                connection = "Connection: close" + CRLF;
                contentTypeLine = "Content-type: " + "text/html" + CRLF;
                entityBody = "<HTML><HEAD><TITLE>415 - Unsupported Media Type</TITLE></HEAD><BODY>415 - Unsupported Media Type</BODY></HTML>";
                fileInputStream = null;
                fileExists = false;
            else
                statusLine = "HTTP/1.0 404 Bad Request" + CRLF;
                contentLength = "Content-Length: 0" + CRLF;
                connection = "Connection: close" + CRLF;
                contentTypeLine = "Content-type: " + "text/html" + CRLF;
                entityBody = "<HTML><HEAD><TITLE>404 - Not Found</TITLE></HEAD><BODY>404 - Not Found</BODY></HTML>";
            // Send the status line
            outputStream.writeBytes(statusLine);
            // Send the connection status
            outputStream.writeBytes(connection);
            // Send the Content-Length
            outputStream.writeBytes(contentLength);
            // Send the content type line
            outputStream.writeBytes(contentTypeLine);
            //Send a blank line to indicate the end of the header lines.
            outputStream.writeBytes(CRLF);
            // Send the enity body
            if(fileExists)
                //Den här funkar??
                sendBytes(fileInputStream, outputStream);
                fileInputStream.close();
            else
                try
                    outputStream.writeBytes(entityBody);
                catch(SocketException ex)
                    System.out.println(ex);
            socket.close();
            inputReader.close();
            outputStream.close();
            buffReader.close();
        private void sendBytes(FileInputStream fileInputStream, DataOutputStream outputStream) throws IOException
            //Construct a 1k buffer to hold bytes on their way to the socket
            byte[] buffer = new byte[1024];
            int bytes = 0;
            // Copy request file inte socket's output stream
            while((bytes = fileInputStream.read(buffer)) != -1)
                outputStream.write(buffer,0, bytes);
        private String contentType(String fileName)
            if(fileName.endsWith(".htm") || fileName.endsWith(".html"))
                return "text/html";
            else if(fileName.endsWith(".jpg") || fileName.endsWith(".jpeg"))
                return "image/jpeg";
            else if(fileName.endsWith(".gif"))
                return "image/gif";
            else if(fileName.endsWith(".png"))
                return "image/png";
            else if(fileName.endsWith(".txt"))
                return "text/plain";
            return "application/octet-stream";
    }

    You've told the client that the content length is zero bytes so I presume it closes the connection as soon as it finishes receiving headers. It depends what client you're using of course but that seems reasonable behaviour...

  • How to close a Webdynpro Application with some action, if it is opened with a Tcode

    Hi Experts,
         I am looking to get some info regarding my post over here.
    Scenario 1:
    I opened my webdynpro application in SAP GUI (created a tcode for my webdynpro application and ).
    Now, I have to add some button where I have to write a piece of code to close the GUI screen along with the webdynpro application. (ie, entire Tcode where the webdynpro application is shown, should be closed)
    Please let me know if you have some info on this.
    Scenario 2:
    If the above scenario is not possible, then I wanted to know if I can call some screen in SAP GUI.
    Note: The GUI screen must be called only from the webdynpro application that is opened with a tcode in SAP GUI.

    Hello,
    Please try this:-
    Window Plugs: Startup and Exit - Web Dynpro for ABAP - SAP Library
    You can close the WD Application by follwoing way-
    Create a button in a view and assign an action on it.
    Create on exit plug in window level and fire that in the view button action level.
    Z2-wd comp.
    NAME
    EXT:-Window
    exit plug name.
    DATA lo_z2 TYPE REF TO ig_z2 .
    lo_z2 =   wd_this->get_z2_ctr( ).
      lo_z2->fire_ext_plg(

  • Urgent helep: socket write error

              Hi All,
              My application is continuously writing the following error message to the domain
              log of WLS eventhough app is running ok
              javax.servlet.ServletException: Connection aborted by peer: socket write error
                   <<no stack trace available>>
              My major concern is that,it will fill up the heap soon.
              Did anybody run into similar issue?
              Thanks in advance.
              RC
              

    Please do not cross-port.
              RC wrote:
              > Hi All,
              > My application is continuously writing the following error message to the domain
              > log of WLS eventhough app is running ok
              >
              > javax.servlet.ServletException: Connection aborted by peer: socket write error
              > <<no stack trace available>>
              >
              > My major concern is that,it will fill up the heap soon.
              > Did anybody run into similar issue?
              > Thanks in advance.
              >
              > RC
              Rajesh Mirchandani
              Developer Relations Engineer
              BEA Support
              

  • JCOM throwing SocketException: Connection reset by peer: socket write error

    I have an ejb which is calling a simple ActiveX component using JCOM.
    Ocassionally the ejb loses the ability to connect to the ActiveX component. Any attempt to call a method results in a java.net.SocketException: Connection reset by peer: socket write error.
    However the ActiveX component continues to run correctly. I can still connect to it using a vb test client. This is using com to connect, not DCOM as used by JCOM(JIntegra).
    The application server and the ActiveX component are running on the same server.
    Any suggestions as to why the JIntegra DCOM request could be failing?
    Thanks,
    Greg.

    I have an ejb which is calling a simple ActiveX component using JCOM.
    Ocassionally the ejb loses the ability to connect to the ActiveX component. Any attempt to call a method results in a java.net.SocketException: Connection reset by peer: socket write error.
    However the ActiveX component continues to run correctly. I can still connect to it using a vb test client. This is using com to connect, not DCOM as used by JCOM(JIntegra).
    The application server and the ActiveX component are running on the same server.
    Any suggestions as to why the JIntegra DCOM request could be failing?
    Thanks,
    Greg.

  • Two Socket errors: Socket write and Socket reset

    does anyone know the reasons and remedies for the error
    java.net.SocketException: Software caused connection abort: socket write error
    and
    java.net.SocketException: Connection reset by peer: socket write error
    please reply if someone knows
    thanks

    These are basically the same error triggered in different places.
    This occurs when the other end of the connection closes while the client is still writing to it.

  • Persistent socket connection - socket write error

    I'm connecting to a server using sockets. My application acts like a client, sending requests, and also like a server, listenning for notifications. I was using a client socket for the first task (send a message when required) and a server socket for the second (permanently listen for incoming messages). This needs to be some kind of persistent connection.
    It happens now I'm required to send and receive using the same port. The only way I found to do this is to have a single socket (client) bound to a certain port. It connects to the server and one thread keeps listenning for incoming messages (by reading the input stream) while another process is launched whenever I need to send a message (by writing to the socket's output stream). The socket is created only once (when the application starts) and its output/input streams reused whenever needed.
    This works well for a while. However, when I try to send a message after some idle time (lets say 20 minutes) strange things happen. The first attempt to send a message returns success (although nothing is actually received by the server). The second attempt returns java.net.SocketException: Software caused connection abort: socket write error. I don't understand this behaviour. Can there be a timeout? I only write to the socket after testing if it's connected.. So why is this failing? Also, any other ideas on how to send and receive using the same port? A different and better approach maybe..
    Thanks in advance

    Socket.isConnected just tells you whether you have personally called Socket.connect() or new Socket(host, port,...). It doesn't tell you anything about the state of the connection.
    You should certainly issue periodic application 'pings' at suitable intervals, and many application protocols do this. For example, Java RMI reuses connections that are less than 15 seconds old but only if they pass a ping test.
    In general however you can't insist on a persistent connection over TCP/IP, especially if you have this kind of hardware in the circuit. What you can do is recognize when the connection has been lost and form a new one. The network is going to fail somewhere some time and your program has to be robust against that.

  • Random "socket write error"

    Hello,
    We are running CF 9.01 standard on IIS 6 (Windows server 2003) on mutiple servers.
    I've noticing a few instances of these errors on every server, almost on a daily bases:
    10/28 13:32:26 error Error while reading header HTTPREFERER
    java.net.SocketException: Software caused connection abort: socket write error
          at java.net.SocketOutputStream.socketWrite0(Native Method)
          at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    NOTE: the header name can be anything, but the stack always starts like this.
    A few times, yesterday for example, a server can suddenly show tons of these errors and then it becomes unresponsive, with queued CFM requests. Only a restart of the service frees this condition.
    Our CFM pages perform a lot of CFHTTP calls, 99% of the time to localhost; in any case the local network is very solid. At the same time CFM is having these issues other pages, for example .NET pages, work perfectly.
    any insight? this problem is affecting our production website. thanks!

    I think, this is nothing to do with Oracle or Ur applications.
    It is totally N/W issue. Contact the N/W support.

  • Reader/Writer.close() is slow

    I've written a multi-threaded application that does a lot of disk I/O using Buffered and File Reader/Writers. Each thread is reading and writing it's OWN file. Everything works great except the performance of the Reader/Writer.close() method. When I'm running say 10 threads at a time and my code calls close() it can take anywhere from 1 - 3 seconds for the call to return. If I only run 5 threads then close() returns in a respectable timeframe.
    Can someone please explain what could be causing close() to take so long to return?
    Thanks!

    Each thread has to vie for CPU time with other processes on your system. More threads means more scheduling of processes, the threads do not run at the same time--it's just an illusion created by scheduling. When you have 10 threads, you have more scheduling going on--hence more wait when you want to close out: you have wait for each to gain enough active CPU time to flush and close, but there can only be up to as many threads running at one time as your system has CPUs*Threads/CPU. Just because you have more Java threads, does not mean that you're processing faster--it just means there is seperate processing going on as the system can schedule resources for your threads to work in with the rest of the system processes all of them essentially competing for many of the same resources.

  • How do I close all running applications before launching my java app?

    Does anyone know of anyway I can code to close all running applications, even if I don't know the process names to begin with?
    Is there open source code than anyone has written to do this. Other applications interfere with my app and I need to terminate all running apps/processes before launching my app. Please advise.

    I see we aren't all on the same wavelength here, let
    me rephrase:
    How can I write JAVA code that will terminate all
    running applications so as not to interfere with the
    security of my application's content, as it is
    extremely sensitive content and I need to know that
    no applications are running which could defeat it.
    I would like my application to terminate all running
    applications, is this possible to write in java code.Do you consider all the processes running in the background (launched by the OS) as part of "all running applications"? Do you not consider the OS itself as part of it as well? You're really barking up the wrong tree. But go ahead, I know you won't be convinced regarding the wonkiness of your thinking.

  • Window close operations, please explain

    Hi:
    Can someone help me explain the differences between HIDE_ON_CLOSE, DISPOSE_ON_CLOSE and EXIT_ON_CLOSE? What I want to do is, I want to click a button, which will bring up a second JFrame, after I am done with it, I need it to go away. So, which close operation should I use??
    Thanks

    It sounds like you should choose between DISPOSE_ON_CLOSE and HIDE_ON_CLOSE.
    The difference between the two is that DISPOSE_ON_CLOSE frees up the resources used by the JFrame when it's closed, whereas HIDE_ON_CLOSE doesn't.
    It's a tradeoff between space and time.
    HIDE_ON_CLOSE would save you a little time by not requiring the frame to initialize and shutdown every time it's opened or closed, but it keeps the frame's resources in memory even when it isn't showing.
    DISPOSE_ON_CLOSE takes a little longer because it frees and reallocates the frame's resources when it is opened and closed, but it doesn't keep all that stuff in memory when the frame isn't showing.
    EXIT_ON_CLOSE would definitely not work since it would shut down you whole application when the second JFrame closed.

  • Connection reset by peer: socket write error

    Anybody can help me?
    I run vdbench to test our NAS server, but it always failed with "
    Slave localhost-0 aborting: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
    Error:         Windows System Error code: 64: ",  how to solve this fail ?
    conf file:
    fsd=fsd,anchor=Y:\dir,count=(11,15),depth=10,width=2,files=1,size=(10k,20,100k,20,160k,20,8m,20,10m,10,1g,5,2g,5)
    fwd=fwd1,fsd=(fsd11,fsd12,fsd13,fsd14,fsd15),rdpct=85,xfersize=(10k,22,100k,22,160k,22,8m,22,10m,12),fileio=random,fileselect=random,threads=5
    rd=rd1,fwd=fwd1,operations=read,fwdrate=max,format=yes,elapsed=10,interval=1
    logfile.html:
    14:22:49.510 Vdbench distribution: vdbench50401
    14:22:49.510
    14:22:49.526 input argument scanned: '-fcifs'
    14:22:49.526 java.vendor                   Sun Microsystems Inc.
    14:22:49.526 java.home                     C:\Program Files\Java\jre6
    14:22:49.526 java.vm.specification.version 1.0
    14:22:49.526 java.vm.version               16.3-b01
    14:22:49.526 java.vm.vendor                Sun Microsystems Inc.
    14:22:49.526 java.specification.version    1.6
    14:22:49.526 java.class.version            50.0
    14:22:49.526 user.name                     zcuser1002
    14:22:49.526 user.dir                      C:\Users\zcuser1002\Desktop\Y-vdbench-1021
    14:22:49.526 java.class.path               C:\Users\zcuser1002\Desktop\Y-vdbench-1021\;C:\Users\zcuser1002\Desktop\Y-vdbench-1021\classes;C:\Users\zcuser1002\Desktop\Y-vdbench-1021\vdbench.jar
    14:22:49.526 os.name                       Windows Server 2008 R2
    14:22:49.526 os.arch                       amd64
    14:22:49.526 os.version                    6.1
    14:22:49.526 sun.arch.data.model           64
    14:22:49.557 'fsd=fsd,count=(start,count)' added fsd11 Y:\dir11
    15:08:57.031       2704    0.0  0.00   0.9 4.42   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:08:58.030       2705  343.0 386.6   8.5 4.36   0.0    0.0  0.00  343.0 386.6  0.00 42.22  42.22  129071   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:08:59.031       2706   15.0 983.4   0.0 3.41   0.0    0.0  0.00   15.0 983.4  0.00  1.85   1.85  129160   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:09:51.406 localhost-0: anchor=Y:\dir15: Created 420 of 1024 files (41.02%)
    15:10:02.202       2707  12143 31.35   8.0 6.25   0.0    0.0  0.00  12143 31.35  0.00  1513 1513.9  130736   0.0  0.00   0.0  0.00  65.0 59795  65.0 202.8  67.0 44969   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.234       2708    0.0  0.00   8.6 8.40   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.249       2709    0.0  0.00  43.7 37.5   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00  27.0  4268   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.265       2710    0.0  0.00   0.0 0.00   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.296       2711    0.0  0.00 100.0 81.2   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.312       2712    0.0  0.00   0.0 0.00   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.312 localhost-0: 15:10:02.218 op: write  lun: Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file lba:   1484652544 0x587E0000 xfer:   131072 errno: Windows System Error code: 64: ??¡§????????????
    15:10:02.327 localhost-0: 15:10:02.234 op: write  lun: Y:\dir14\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file lba:   1971847168 0x75880000 xfer:   131072 errno: Windows System Error code: 64: ??¡§????????????
    15:10:02.343       2713    0.0  0.00 100.0 74.9   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.343
    15:10:02.343 **********************************************************
    15:10:02.343 Slave localhost-0 aborting: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
    Error:         Windows System Error code: 64: ??¡§????????????
    lba:           1484652544
    xfersize:      131072
    blocks_done:   11327
    bytes_done:    1484652544
    open_for_read: false
    15:10:02.343 **********************************************************
    15:10:02.343
    15:10:18.013 Exception from slave: localhost-0
    15:10:18.013
    15:10:18.013 common.failure():
      java.net.SocketException: Connection reset by peer: socket write error
    java.net.SocketException: Connection reset by peer: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)
    at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown Source)
    at java.io.ObjectOutputStream.reset(Unknown Source)
    at Vdb.SlaveSocket.putMessage(SlaveSocket.java:277)
    at Vdb.CollectSlaveStats.<init>(CollectSlaveStats.java:121)
    at Vdb.Reporter.run(Reporter.java:183)
    localhost-0.stdout.html:
    stdout/stderr for slave=localhost-0
    14:22:50.072 14:22:50.072 SlaveJvm execution parameter:  '-m localhost'
    14:22:50.072 14:22:50.072 SlaveJvm execution parameter:  '-n localhost-10-141104-14.22.49.432'
    14:22:50.072 14:22:50.072 SlaveJvm execution parameter:  '-l localhost-0'
    14:22:50.072 14:22:50.072 SlaveJvm execution parameter:  '-p 5570'
    14:22:50.072 14:22:50.072 SlaveJvm positional parameter: 'SlaveJvm'
    14:22:50.118 14:22:50.118 successfully connected to master localhost
    14:22:50.118 14:22:50.118 Connection to localhost using port 5570 successful
    14:22:50.571 14:22:50.571 execute(): ls -l Y:\dir11
    14:22:50.618 14:22:50.618 execute(): ls -l Y:\dir12
    14:22:50.633 14:22:50.633 execute(): ls -l Y:\dir13
    14:22:50.664 14:22:50.664 execute(): ls -l Y:\dir14
    14:22:50.680 14:22:50.680 execute(): ls -l Y:\dir15
    14:22:50.711 14:22:50.711 Configuration interpretation took 0.45 seconds
    Link to Run Definitions:         <A HREF="#_225912260">format_for_rd1 For loops: None</A>
                                     <A HREF="#_156265924">rd1 For loops: None</A>
    14:22:50.852 14:22:50.852 Beginning of run setup
    14:22:50.852 14:22:50.852 **********************
    14:22:50.852
    14:22:50.852
    14:22:51.538 14:22:51.538 Completed the creation of the directory list for Y:\dir11: 2046 directories.
    14:22:56.811 14:22:56.811 Memory total Java heap:   77.438 MB; Free:   32.782 MB; Used:   44.655 MB;
    14:22:56.874 14:22:56.874 checkMemory()
    14:22:56.874 14:22:56.874 Memory total Java heap:   77.438 MB; Free:   52.364 MB; Used:   25.074 MB;
    14:23:03.426 14:23:03.426 Generated     1024 file names; total anchor size: 130.841g
    14:23:03.426 14:23:03.426 Writing control file for anchor=Y:\dir11 at start of run.
    14:23:03.457 14:23:03.441 Completed control file for anchor=Y:\dir11 at start of run.  dirs: 2046/2046 files: 1024/88 sizes: 130.841g/8.721g/0/0.0
    14:23:03.457 14:23:03.441 During anchor creation for anchor=Y:\dir11 there were 2046 directories and 88 files
    14:23:03.551 14:23:03.551 Completed the creation of the directory list for Y:\dir12: 2046 directories.
    14:23:08.902 14:23:08.902 Memory total Java heap:   77.438 MB; Free:   24.149 MB; Used:   53.288 MB;
    14:23:08.964 14:23:08.964 checkMemory()
    14:23:08.964 14:23:08.964 Memory total Java heap:   77.438 MB; Free:   50.640 MB; Used:   26.798 MB;
    14:23:15.579 14:23:15.579 Generated     1024 file names; total anchor size: 130.841g
    14:23:15.579 14:23:15.579 Writing control file for anchor=Y:\dir12 at start of run.
    14:23:15.594 14:23:15.594 Completed control file for anchor=Y:\dir12 at start of run.  dirs: 2046/2046 files: 1024/74 sizes: 130.841g/7.092g/0/0.0
    14:23:15.594 14:23:15.594 During anchor creation for anchor=Y:\dir12 there were 2046 directories and 74 files
    14:23:15.688 14:23:15.688 Completed the creation of the directory list for Y:\dir13: 2046 directories.
    14:23:21.210 14:23:21.210 Memory total Java heap:   74.688 MB; Free:   19.725 MB; Used:   54.963 MB;
    14:23:21.273 14:23:21.273 checkMemory()
    14:23:21.273 14:23:21.273 Memory total Java heap:   76.562 MB; Free:   48.176 MB; Used:   28.386 MB;
    14:23:28.168 14:23:28.168 Generated     1024 file names; total anchor size: 130.841g
    14:23:28.168 14:23:28.168 Writing control file for anchor=Y:\dir13 at start of run.
    14:23:28.184 14:23:28.184 Completed control file for anchor=Y:\dir13 at start of run.  dirs: 2046/2046 files: 1024/84 sizes: 130.841g/8.886g/0/0.0
    14:23:28.184 14:23:28.184 During anchor creation for anchor=Y:\dir13 there were 2046 directories and 84 files
    14:23:28.262 14:23:28.262 Completed the creation of the directory list for Y:\dir14: 2046 directories.
    14:23:33.785 14:23:33.785 Memory total Java heap:   74.250 MB; Free:   17.213 MB; Used:   57.037 MB;
    14:23:33.863 14:23:33.863 checkMemory()
    14:23:33.863 14:23:33.863 Memory total Java heap:   72.812 MB; Free:   42.829 MB; Used:   29.983 MB;
    14:23:40.976 14:23:40.976 Generated     1024 file names; total anchor size: 130.841g
    14:23:40.976 14:23:40.976 Writing control file for anchor=Y:\dir14 at start of run.
    14:23:40.976 14:23:40.976 Completed control file for anchor=Y:\dir14 at start of run.  dirs: 2046/2046 files: 1024/87 sizes: 130.841g/8.778g/0/0.0
    14:23:40.976 14:23:40.976 During anchor creation for anchor=Y:\dir14 there were 2046 directories and 87 files
    14:23:41.054 14:23:41.054 Completed the creation of the directory list for Y:\dir15: 2046 directories.
    14:23:46.296 14:23:46.296 Memory total Java heap:   74.062 MB; Free:   42.390 MB; Used:   31.672 MB;
    14:23:46.374 14:23:46.374 checkMemory()
    14:23:46.374 14:23:46.374 Memory total Java heap:  101.000 MB; Free:   68.809 MB; Used:   32.191 MB;
    14:23:52.958 14:23:52.958 Generated     1024 file names; total anchor size: 130.841g
    14:23:52.958 14:23:52.958 Writing control file for anchor=Y:\dir15 at start of run.
    14:23:52.989 14:23:52.973 Completed control file for anchor=Y:\dir15 at start of run.  dirs: 2046/2046 files: 1024/96 sizes: 130.841g/8.995g/0/0.0
    14:23:52.989 14:23:52.973 During anchor creation for anchor=Y:\dir15 there were 2046 directories and 96 files
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd11,operation=read:    20.0
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd12,operation=read:    20.0
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd13,operation=read:    20.0
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd14,operation=read:    20.0
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd15,operation=read:    20.0
    14:23:53.051 14:23:53.051 Started 8 threads for fwd=format,fsd=fsd11
    14:23:53.114 14:23:53.114 Started 8 threads for fwd=format,fsd=fsd12
    14:23:53.161 14:23:53.161 Started 8 threads for fwd=format,fsd=fsd13
    14:23:53.207 14:23:53.207 Started 8 threads for fwd=format,fsd=fsd14
    14:23:53.270 14:23:53.270 Started 8 threads for fwd=format,fsd=fsd15
    14:23:53.270 14:23:53.270 Started 40 FwgThreads
    14:23:53.270 14:23:53.270 Waiting for task synchronization
    14:23:53.270 14:23:53.270 task_wait_start_complete() end
    <a name="_225912260"></a><i><b>14:23:53.971 Starting RD=format_for_rd1</b></i>
    14:23:54.002 14:23:54.002 task_run_all(): 41 tasks
    14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir15 mkdir complete.
    14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir11 mkdir complete.
    14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir13 mkdir complete.
    14:23:54.066 14:23:54.066 Message to master: anchor=Y:\dir14 mkdir complete.
    14:23:54.066 14:23:54.066 Message to master: anchor=Y:\dir12 mkdir complete.
    14:24:24.685 14:24:24.685 Message to master: anchor=Y:\dir14: Created 130 of 1024 files (12.70%)
    14:24:56.311 14:24:56.311 Message to master: anchor=Y:\dir12: Created 130 of 1024 files (12.70%)
    14:25:40.473 14:25:40.464 Message to master: anchor=Y:\dir13: Created 140 of 1024 files (13.67%)
    14:32:52.125 14:32:52.125 Message to master: anchor=Y:\dir12: Created 140 of 1024 files (13.67%)
    14:33:30.374 14:33:30.374 Message to master: anchor=Y:\dir12: Created 160 of 1024 files (15.63%)
    14:34:33.842 14:34:33.842 Message to master: anchor=Y:\dir14: Created 170 of 1024 files (16.60%)
    14:35:49.810 14:35:49.810 Message to master: anchor=Y:\dir14: Created 180 of 1024 files (17.58%)
    14:36:34.451 14:36:34.451 Message to master: anchor=Y:\dir14: Created 190 of 1024 files (18.55%)
    14:38:13.437 14:38:13.437 Message to master: anchor=Y:\dir14: Created 200 of 1024 files (19.53%)
    14:39:01.966 14:39:01.966 Message to master: anchor=Y:\dir11: Created 210 of 1024 files (20.51%)
    14:39:57.837 14:39:57.837 Message to master: anchor=Y:\dir15: Created 220 of 1024 files (21.48%)
    14:41:51.763 14:41:51.763 Message to master: anchor=Y:\dir13: Created 220 of 1024 files (21.48%)
    14:42:31.156 14:42:31.156 Message to master: anchor=Y:\dir14: Created 240 of 1024 files (23.44%)
    14:45:32.607 14:45:32.607 Message to master: anchor=Y:\dir15: Created 260 of 1024 files (25.39%)
    14:46:44.611 14:46:44.611 Message to master: anchor=Y:\dir11: Created 270 of 1024 files (26.37%)
    14:47:53.707 14:47:53.707 Message to master: anchor=Y:\dir14: Created 280 of 1024 files (27.34%)
    14:48:25.032 14:48:25.032 Message to master: anchor=Y:\dir12: Created 280 of 1024 files (27.34%)
    14:48:56.946 14:48:56.946 Message to master: anchor=Y:\dir13: Created 290 of 1024 files (28.32%)
    14:50:40.869 14:50:40.868 Message to master: anchor=Y:\dir11: Created 300 of 1024 files (29.30%)
    14:51:22.062 14:51:22.062 Message to master: anchor=Y:\dir15: Created 330 of 1024 files (32.23%)
    14:53:55.390 14:53:55.390 Message to master: anchor=Y:\dir14: Created 350 of 1024 files (34.18%)
    14:56:20.897 14:56:20.897 Message to master: anchor=Y:\dir14: Created 360 of 1024 files (35.16%)
    14:58:08.513 14:58:08.513 Message to master: anchor=Y:\dir11: Created 360 of 1024 files (35.16%)
    14:59:34.933 14:59:34.933 Message to master: anchor=Y:\dir12: Created 360 of 1024 files (35.16%)
    15:02:15.234 15:02:15.234 Message to master: anchor=Y:\dir13: Created 370 of 1024 files (36.13%)
    15:02:48.482 15:02:48.482 Message to master: anchor=Y:\dir14: Created 380 of 1024 files (37.11%)
    15:04:27.359 15:04:27.359 Message to master: anchor=Y:\dir13: Created 380 of 1024 files (37.11%)
    15:05:57.406 15:05:57.406 Message to master: anchor=Y:\dir15: Created 390 of 1024 files (38.09%)
    15:07:18.982 15:07:18.982 Message to master: anchor=Y:\dir11: Created 390 of 1024 files (38.09%)
    15:08:15.419 15:08:15.419 Message to master: anchor=Y:\dir11: Created 410 of 1024 files (40.04%)
    15:08:50.624 15:08:50.624 Message to master: anchor=Y:\dir13: Created 410 of 1024 files (40.04%)
    15:09:51.406 15:09:51.406 Message to master: anchor=Y:\dir15: Created 420 of 1024 files (41.02%)
    15:10:02.202 15:10:02.202 file_write error2: 64
    15:10:02.202 15:10:02.202 file_write error2: 64
    15:10:02.202 15:10:02.202 handle: 0000000000000B38
    15:10:02.202 15:10:02.202 seek:   0000000075880000
    15:10:02.202 15:10:02.202 handle: 0000000000000BC0
    15:10:02.202 15:10:02.202 length: 0000000000020000
    15:10:02.202 15:10:02.202 seek:   00000000587E0000
    15:10:02.202 15:10:02.202 buffer: 0000000034430000
    15:10:02.202 15:10:02.202 length: 0000000000020000
    15:10:02.202 15:10:02.202 buffer: 000000002E3E0000
    15:10:02.234 15:10:02.234
    15:10:02.234 15:10:02.234 Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
    15:10:02.234 15:10:02.234 Error:         Windows System Error code: 64: ??¡§????????????
    15:10:02.234 15:10:02.234 lba:           1484652544
    15:10:02.234 15:10:02.234 xfersize:      131072
    15:10:02.234 15:10:02.234 blocks_done:   11327
    15:10:02.234 15:10:02.234 bytes_done:    1484652544
    15:10:02.234 15:10:02.234 open_for_read: false
    15:10:02.234 15:10:02.234
    15:10:02.234 java.lang.RuntimeException: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
    15:10:02.234 Error:         Windows System Error code: 64: ??¡§????????????
    15:10:02.234 lba:           1484652544
    15:10:02.234 xfersize:      131072
    15:10:02.234 blocks_done:   11327
    15:10:02.234 bytes_done:    1484652544
    15:10:02.234 open_for_read: false
    15:10:02.234  at Vdb.common.failure(common.java:308)
    15:10:02.234  at Vdb.ActiveFile.writeError(ActiveFile.java:611)
    15:10:02.234  at Vdb.ActiveFile.writeBlock(ActiveFile.java:458)
    15:10:02.234  at Vdb.FwgThread.doSequentialWrite(FwgThread.java:327)
    15:10:02.234  at Vdb.OpCreate.doOperation(OpCreate.java:51)
    15:10:02.234  at Vdb.OpFormat.doOperation(OpFormat.java:91)
    15:10:02.234  at Vdb.FwgThread.run(FwgThread.java:157)

    'Socket write error' is merely the master finding out that the slave aborted unexpectedly.
    It it the '64' you have to worry about.
    Windows system error code 64:
    (It appears that the Vdbench translation from number to text may have some language issues and therefore can not properly print it).
    ERROR_NETNAME_DELETED
    64 (0x40)
    The specified network name is no longer available.

  • Default close operation in JInternalFrames?

    I have 1 JFrame which contains many (between 4 and 25) JInternalFrames
    Now the problem is, i have set all the JInternalFrames up with the following code
            mainFrame.add(rtg);
            jnf.setVisible(true);
            jnf.setLocation(50, 50);
            jnf.setSize(100, 100);
            jnf.setResizable(true);
            jnf.setClosable(true);
    // Where jnf is the name of a JInternalFrame.while using netbeans i noticed that (by default) the closing operation is...
    setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);Unfortunatly when i click the close button, on any JInternalFrame with this operation added to it, closes the whole application... and with out the above line, then the JInternalFrame has no close button alltogether....
    Could anyone give me the correct code to close individual windows when using JInternalFrames,?
    Thanks in Advance.

    Read the API. EXIT_ON_CLOSE isn't a valid defaultColseOperation for JInternalFrame.
    I tested it and found there is no error, but closing the internal frame certainly doesn't close the application. It doesn't even close the JInternalFrame.import javax.swing.*;
    public class ExitInternalFrame {
       public static void main(String[] args) {
          SwingUtilities.invokeLater(new Runnable() {
             @Override
             public void run() {
                new ExitInternalFrame().makeUI();
       public void makeUI() {
          JInternalFrame internalFrame = new JInternalFrame();
          internalFrame.setVisible(true);
          internalFrame.setClosable(true);
          internalFrame.setBounds(0, 0, 200, 200);
          internalFrame.setDefaultCloseOperation(WindowConstants.EXIT_ON_CLOSE);
          JDesktopPane desktopPane = new JDesktopPane();
          desktopPane.add(internalFrame);
          JFrame frame = new JFrame();
          frame.setDefaultCloseOperation(WindowConstants.EXIT_ON_CLOSE);
          frame.setSize(400, 400);
          frame.add(desktopPane);
          frame.setLocationRelativeTo(null);
          frame.setVisible(true);
    }db

Maybe you are looking for