13 Replies Latest reply: Aug 13, 2010 9:11 PM by 843810 RSS

    Exception in websphere 6 application server

    843810
      I have deployed an application in websphere version 6, when moved to production, it worked fine initially for 3 hours with 30 users. I have kept the settings of websphere that was there at the time of installation, no tuning nothing.

      I am getting response issues, and following exception in websphere trace logs ,
      if any one can help, now things are in production and it is very seveare for me, I really appriciate any help.



      Logs...




      [12/16/05 16:43:01:499 GMT-05:30] 00000d5f jsp W org.apache.jasper.runtime.PageContextImpl release failed to flush response buffer during PageContext.release().
      java.io.IOException: Stream closed
      at org.apache.jasper.runtime.JspWriterImpl.ensureOpen(JspWriterImpl.java(Inlined Compiled Code))
      at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java(Compiled Code))
      at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java(Compiled Code))
      at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java(Inlined Compiled Code))
      at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java(Compiled Code))
      at com.ibm._jsp._searchScreen._jspService(_searchScreen.java(Compiled Code))
      at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java(Compiled Code))
      at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java(Compiled Code))
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java(Compiled Code))
      at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java(Inlined Compiled Code))
      at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java(Compiled Code))
      at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java(Compiled Code))
      at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java(Compiled Code))
      at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java(Compiled Code))
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java(Compiled Code))
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java(Compiled Code))
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java(Compiled Code))
      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))







      Another Exception is:




      [12/16/05 16:26:52:307 GMT-05:30] 00000d32 SystemErr R java.lang.Error: java.net.SocketException: A system call received a parameter that is not valid.
      at sun.nio.ch.Net.localAddress(Net.java(Inlined Compiled Code))
      at sun.nio.ch.SocketChannelImpl.localAddress(SocketChannelImpl.java(Inlined Compiled Code))
      at sun.nio.ch.SocketAdaptor.getLocalPort(SocketAdaptor.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.TCPConnLink.getLocalPort(TCPConnLink.java(Inlined Compiled Code))
      at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.init(HttpServiceContextImpl.java(Compiled Code))
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceContextImpl.init(HttpInboundServiceContextImpl.java(Compiled Code))
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java(Compiled Code))
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java(Compiled Code))
      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
      Caused by: java.net.SocketException: A system call received a parameter that is not valid.
      at sun.nio.ch.Net.localInetAddress(Native Method)
        • 1. Re: Exception in websphere 6 application server
          843810
          Please any body help , other wise ABN Amro the client I am working for will really in trouble, since it is the problem in production , also the websphere AS version 6 gets hanged in between and stops responding, http server is not installed seperately
          • 2. Re: Exception in websphere 6 application server
            843810
            hi, I've face the same problem. Have u found any solution for this?
            thx in advance.
            • 3. Re: Exception in websphere 6 application server
              843810
              Hi there
              Is this a IBM JVM? Looking thru the stacktrace... (assuming there is absolutely no coding error), can u try to disable Inlining? -XX:-Inline and see if problem goes away or worse? Not sure if the JVM has this flag...

              Hope this helps.
              • 4. Re: Exception in websphere 6 application server
                843810
                Did you get a resolve for this issue? I am seeing the same error on AIX 5.3
                What operation system and patched level of WebSphere do you have ?
                • 5. Re: Exception in websphere 6 application server
                  843810
                  I'm seeing a similar exception running Tomcat 4.1.x on an IBM server (AIX 5.2) with a JRE 1.4.2. This SocketException happens only occasionally, and it looks like it's Tomcat code that triggers the it (my code doesn't explicitly use sockets). Any suggestions are welcome.

                  Stack trace:
                  java.net.SocketException: A system call received a parameter that is not valid.
                          at java.net.PlainSocketImpl.socketSetOption(Native Method)
                          at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:268)
                          at java.net.Socket.setTcpNoDelay(Socket.java(Compiled Code))
                          at org.apache.tomcat.util.net.PoolTcpEndpoint.setSocketOptions(PoolTcpEndpoint.java(Compiled Code))
                          at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java(Compiled Code))
                          at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
                          at java.lang.Thread.run(Thread.java:568)
                  • 6. Re: Exception in websphere 6 application server
                    843810
                    Hi,

                    I have got the same problem, for some reason, we get the following excpetion.
                    Have you done any fixes for your similar kind of problem. If so please help me. Thanks
                    We also use IBM JRE...


                    0 API-3 14:18:55.461 java.net.SocketException: A system call received a parameter that is not valid.
                    at java.net.PlainSocketImpl.socketSetOption(Native Method)
                    at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:266)
                    at java.net.Socket.setTcpNoDelay(Socket.java:778)
                    at kana.cms.server.NodeRequestListener$RequestListenerThread.handleRequest(NodeRequestListener.java:436)
                    at kana.cms.server.NodeRequestListener$RequestListenerThread.run(NodeRequestListener.java:359)


                    On the secondary node the following exception is being thrown continously:
                    1 API-3 14:18:56.455 java.net.SocketException: Connection reset
                    at java.net.SocketInputStream.read(SocketInputStream.java:194)
                    at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2182)
                    at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2195)
                    at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2667)
                    at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:764)
                    at java.io.ObjectInputStream.<init>(ObjectInputStream.java:283)
                    at kana.shared.util.ObjectInputStreamExtended.<init>(ObjectInputStreamExtended.java:17)
                    at kana.cms.server.NodeRequestListener$RequestListenerThread.handleRequest(NodeRequestListener.java:440)
                    at kana.cms.server.NodeRequestListener$RequestListenerThread.run(NodeRequestListener.java:359)
                    • 7. Re: Exception in websphere 6 application server
                      843810
                      Hi, was there any solution to this problem ?
                      thanks
                      • 8. Re: Exception in websphere 6 application server
                        843810
                        Receiving same exception with IBM JRE 5 but in Glassfish. Any resolution.

                        [#|2008-12-29T10:15:51.557-0800|SEVERE|sun-appserver9.1|com.sun.xml.ws.server.sei.EndpointMethodHandler|_ThreadID=23;_ThreadName=httpSSLWorkerThread-20080-3;_RequestID=443b3cb9-0425-4546-8e92-ec184dcf9eaa;|JMSException encountered in publishMessage [PublishRunMessageBean-1627248] : ; nested exception is: com.sun.messaging.jms.JMSException: [SEND_REPLY(9)] [C4036]: A broker error occurred. :[500] transaction failed: java.io.IOException: A system call received a parameter that is not valid. user=admin, broker=sea-ax0073:20076(58591)
                        javax.ejb.EJBException: JMSException encountered in publishMessage [PublishRunMessageBean-1627248] : ; nested exception is: com.sun.messaging.jms.JMSException: [SEND_REPLY(9)] [C4036]: A broker error occurred. :[500] transaction failed: java.io.IOException: A system call received a parameter that is not valid. user=admin, broker=sea-ax0073:20076(58591)
                        com.sun.messaging.jms.JMSException: [SEND_REPLY(9)] [C4036]: A broker error occurred. :[500] transaction failed: java.io.IOException: A system call received a parameter that is not valid. user=admin, broker=sea-ax0073:20076(58591)
                             at com.sun.messaging.jmq.jmsclient.ProtocolHandler.throwServerErrorException(ProtocolHandler.java:3940)
                             at com.sun.messaging.jmq.jmsclient.ProtocolHandler.writeJMSMessage(ProtocolHandler.java:1926)
                             at com.sun.messaging.jmq.jmsclient.WriteChannel.sendWithFlowControl(WriteChannel.java:154)
                             at com.sun.messaging.jmq.jmsclient.WriteChannel.writeJMSMessage(WriteChannel.java:107)
                             at com.sun.messaging.jmq.jmsclient.Transaction.send(Transaction.java:505)
                             at com.sun.messaging.jmq.jmsclient.SessionImpl.writeJMSMessage(SessionImpl.java:768)
                             at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.writeJMSMessage(MessageProducerImpl.java:198)
                             at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.writeJMSMessage(MessageProducerImpl.java:187)
                             at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.send(MessageProducerImpl.java:570)
                             at com.sun.messaging.jmq.jmsclient.QueueSenderImpl.send(QueueSenderImpl.java:97)
                             at com.stc.jmsjca.core.WMessageProducer.send(WMessageProducer.java:286)
                        • 9. Re: Exception in websphere 6 application server
                          jschellSomeoneStoleMyAlias
                          bgrant88 wrote:
                          Receiving same exception with IBM JRE 5 but in Glassfish. Any resolution.
                          1. Don't post new questions on old threads.
                          2. This isn't even close to same as the other ones.
                          • 10. Re: Exception in websphere 6 application server
                            843810
                            I found that helpful
                            http://javafuck.wordpress.com/2010/07/28/websphere-workaround-ssl-connection/

                            Edited by: beep02 on Aug 2, 2010 6:05 AM
                            • 11. Re: Exception in websphere 6 application server
                              843810
                              hi,

                              jasper -> jsp compiler into servlet ( released with Websphere com.ibm.ws.webcontainer_x.x.x.jar)
                              1) compiling jsp -> java code for a servlet
                              2) executing the servlet
                              pb with response from servlet -> pb with response from jsp.
                              • 12. Re: Exception in websphere 6 application server
                                843810
                                maybe bad network/http paramerters (calling another remote servlet no response from it ?) ...
                                • 13. Re: Exception in websphere 6 application server
                                  843810
                                  for the ssl with WAS, the format trustore matter, it has to be pkcs12 and don't use SSL system properties from jvm. don't mix up type if you system properties. (overrides WAS SSL properties for the jvm).