My weblogic is downed!
Hi, I deployed my Application in weblogic server and was safe before, because its users increased server crashed now and only below exceptions was logged.
{javax.xml.ws.WebServiceException: com.ctc.wstx.exc.WstxIOException: socket write error: Connection reset by peer.
com.ctc.wstx.exc.WstxIOException: socket write error: Connection reset by peer.
java.net.SocketException: socket write error: Connection reset by peer.}
can you help me.
Edited by: Mohammad Saadati on May 13, 2009 8:49 PM
Thanks for your interest, I sent for you all exceptions that is raised:
1.
####<May 5, 2009 8:05:30 AM PDT> <Error> <HTTP> <...> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1241535930156> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@df4f9d - appName: '...', name: '....war', context-path: '/...', spec-version: '2.5'] Root cause of ServletException.
javax.xml.ws.WebServiceException: com.ctc.wstx.exc.WstxIOException: socket write error: Connection reset by peer.
at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:111)
at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
at com.sun.xml.ws.transport.http.HttpAdapter.encodePacket(HttpAdapter.java:320)
at com.sun.xml.ws.transport.http.HttpAdapter.access$100(HttpAdapter.java:93)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:454)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
com.ctc.wstx.exc.WstxIOException: socket write error: Connection reset by peer.
at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1687)
at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:585)
at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:146)
at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:108)
at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
at com.sun.xml.ws.transport.http.HttpAdapter.encodePacket(HttpAdapter.java:320)
at com.sun.xml.ws.transport.http.HttpAdapter.access$100(HttpAdapter.java:93)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:454)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.net.SocketException: socket write error: Connection reset by peer.
at jrockit.net.SocketNativeIO.writeBytesPinned(Native Method)
at jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:73)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at weblogic.utils.io.ChunkedOutputStream.writeTo(ChunkedOutputStream.java:193)
at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:436)
at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:1256)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:108)
at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:100)
at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:195)
at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1685)
at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:586)
at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:147)
at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:109)
at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
at com.sun.xml.ws.transport.http.HttpAdapter.encodePacket(HttpAdapter.java:320)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:454)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
2.
####<May 5, 2009 8:43:31 AM PDT> <Error> <HTTP> <...> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1241538211281> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@df4f9d - appName: '...', name: '....war', context-path: '/...', spec-version: '2.5'] Root cause of ServletException.
javax.xml.ws.WebServiceException: javax.xml.bind.MarshalException
- with linked exception:
[com.ctc.wstx.exc.WstxIOException: Socket closed]
at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:322)
at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:142)
at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:108)
at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
at com.sun.xml.ws.transport.http.HttpAdapter.encodePacket(HttpAdapter.java:320)
at com.sun.xml.ws.transport.http.HttpAdapter.access$100(HttpAdapter.java:93)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:454)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.xml.bind.MarshalException
- with linked exception:
[com.ctc.wstx.exc.WstxIOException: Socket closed]
at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:286)
at com.sun.xml.bind.v2.runtime.BridgeImpl.marshal(BridgeImpl.java:90)
at com.sun.xml.bind.api.Bridge.marshal(Bridge.java:107)
at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:317)
at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:142)
at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:108)
at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
at com.sun.xml.ws.transport.http.HttpAdapter.encodePacket(HttpAdapter.java:320)
at com.sun.xml.ws.transport.http.HttpAdapter.access$100(HttpAdapter.java:93)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:454)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
com.ctc.wstx.exc.WstxIOException: Socket closed
at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:511)
at com.sun.xml.bind.v2.runtime.output.XMLStreamWriterOutput.text(XMLStreamWriterOutput.java:150)
at com.sun.xml.bind.v2.runtime.XMLSerializer.leafElement(XMLSerializer.java:321)
at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$1.writeLeafElement(RuntimeBuiltinLeafInfoImpl.java:210)
at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$1.writeLeafElement(RuntimeBuiltinLeafInfoImpl.java:197)
at com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTransducedAccessorImpl.writeLeafElement(TransducedAccessor.java:250)
at com.sun.xml.bind.v2.runtime.property.SingleElementLeafProperty.serializeBody(SingleElementLeafProperty.java:98)
at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:322)
at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:681)
at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:277)
at com.sun.xml.bind.v2.runtime.BridgeImpl.marshal(BridgeImpl.java:90)
at com.sun.xml.bind.api.Bridge.marshal(Bridge.java:107)
at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:317)
at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:142)
at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:108)
at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
at com.sun.xml.ws.transport.http.HttpAdapter.encodePacket(HttpAdapter.java:320)
at com.sun.xml.ws.transport.http.HttpAdapter.access$100(HttpAdapter.java:93)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:454)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:525)
at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:504)
at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:382)
at weblogic.servlet.internal.CharsetChunkOutput.flush(CharsetChunkOutput.java:249)
at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:469)
at weblogic.servlet.internal.CharsetChunkOutput.implWrite(CharsetChunkOutput.java:396)
at weblogic.servlet.internal.CharsetChunkOutput.write(CharsetChunkOutput.java:198)
at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:139)
at weblogic.servlet.internal.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:169)
at com.ctc.wstx.io.UTF8Writer.write(UTF8Writer.java:139)
at com.ctc.wstx.sw.BufferingXmlWriter.flushBuffer(BufferingXmlWriter.java:1103)
at com.ctc.wstx.sw.BufferingXmlWriter.writeRaw(BufferingXmlWriter.java:255)
at com.ctc.wstx.sw.BufferingXmlWriter.writeCharacters(BufferingXmlWriter.java:543)
at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:509)
at com.sun.xml.bind.v2.runtime.output.XMLStreamWriterOutput.text(XMLStreamWriterOutput.java:150)
at com.sun.xml.bind.v2.runtime.XMLSerializer.leafElement(XMLSerializer.java:321)
at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$1.writeLeafElement(RuntimeBuiltinLeafInfoImpl.java:210)
at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$1.writeLeafElement(RuntimeBuiltinLeafInfoImpl.java:197)
at com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTransducedAccessorImpl.writeLeafElement(TransducedAccessor.java:250)
at com.sun.xml.bind.v2.runtime.property.SingleElementLeafProperty.serializeBody(SingleElementLeafProperty.java:98)
at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:322)
at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:681)
at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:277)
at com.sun.xml.bind.v2.runtime.BridgeImpl.marshal(BridgeImpl.java:90)
at com.sun.xml.bind.api.Bridge.marshal(Bridge.java:107)
at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:317)
at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:142)
at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:108)
at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
at com.sun.xml.ws.transport.http.HttpAdapter.encodePacket(HttpAdapter.java:320)
at com.sun.xml.ws.transport.http.HttpAdapter.access$100(HttpAdapter.java:93)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:454)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
Edited by: user11131656 on May 12, 2009 10:28 PM
Edited by: user11131656 on May 12, 2009 10:29 PM
Edited by: Mohammad Saadati on May 13, 2009 8:48 PM
Edited by: Mohammad Saadati on May 13, 2009 9:34 PM
Similar Messages
-
Weblogic slowers down when retrieving data through JMX in SSL mode
weblogic slowers down when retrieving data through JMX in SSL mode..is this has been face by anyone?
kidnly help me..Nihil Somani wrote:
weblogic slowers down when retrieving data through JMX in SSL mode..is this has been face by anyone?
kidnly help me..Hi. This is the JDBC newsgroup, so asking about SSL and JMX isn't going to get much
response, but you'd expect SSL to be slower...
Joe -
Weblogic shutting down abnormally
hi my weblogic server is shutting down abnormally.when i checked the weblogic.log
file i could trace the following error i dont know whether this error is related to the abnormal shutdown of weblogic i am
copying the error message for your reference
ERROR: Mon Apr 08 13:20:00 CEST 2002:<W> <SSLListenThread> Connection rejected: 'Login
timed out after: '25000' ms on socket: 'Socket[addr=eurcic1.emea.citicorp.com/16
9.194.168.43,port=63988,localport=7003}''
please help me out with a solution at the earliest
Regards
SurenderIs it actually shutting down (ie is it clean)? or is it dying or hanging?
-
Weblogic shutting down keep-alive socket improperly?
We were sometimes experiencing strange IE behaviour when surfing on webapps on our Weblogic application servers. After investigation we found that IE has a bug in its resend behaviour, so when resending a POST request it sends the headers (including Content-Length) but forgets the form-data. This causes the server to time out waiting for the data. (Note: We are using Win2K and IE6 SP1 on the clients.)
The IE resend is triggered on a default installation when 31-59 seconds have passed since the last request.
This is because IE will try to reuse a socket that has been told to keep-alive until it has been idle for 60 seconds but WLS will by default close kept-alive sockets when they have been idle for 30 seconds. So in the range 31-59 seconds IE will consider the socket alive but WLS has closed it.
The resend bug is really an IE bug and doesn't concern WLS, but then I saw that IE would function correctly with an Apache server with a default keep-alive timeout of 15 seconds.
Using Ethereal I could get the information depicted in the tables below:
Weblogic with keep-alive timeout 30 secs
old socket
Time 00 : User navigates : IE POST request -> WLS, WLS HTML -> IE
Time 30 : Socket times out : (no network traffic)
Time 45 : User navigates : IE POST request -> WLS, WLS TCP_FIN -> IE
new socket
Time 45 : : IE resends POST request without form-data
Apache with keep-alive timeout 15 secs
old socket
Time 00 : User navigates : IE POST request -> Apache, Apache HTML -> IE
Time 15 : Socket times out : Apache TCP_FIN -> WLS
new socket
Time 45 : User navigates : IE POST request -> Apache, Apache HTML -> IE
To summarize, IE handles Apache well as Apache sends a TCP FIN telegram (to close the connection) as soon as the kept-alive socket times out.
Therefore IE never tries to reuse the socket but instead starts on a fresh one on the next navigation and a resend is never necessary.
Weblogic, on the other hand, doesn't send the TCP FIN (connection close) telegram until IE actually tries to use the connection even though it timed out 15 seconds earlier. In this case IE needs to resend the POST request and this is when the form-data is forgotten.
So, my question now is if WLS behaviour could be caused by not shutting down kept-alive sockets properly at keep-alive timeout? Or why are there no TCP FIN telegrams sent at timeout?
Mike WilsonAfter doing some more investigation I have found that the "silent" shutdown of keep-alive sockets is only seen on the Linux version. The Windows version of Weblogic 8 behaves correctly, like Apache on Linux, but Weblogic on Linux does not...
Anyone can confirm if this is to be considered a bug? -
Weblogic shuts down unexpectedly
Hi all,
My weblogic server 4.5.1 with SP 8 shuts down every 15 mins. Does
anyone has any idea why is that happening? I am new to weblogic... so if
you guys need any additional information from me before you can help me out.
Please let me know. Many thanks!
--TonyWe have a very similar sounding problem. We can start the server and recon users fine for a period of time. Then the recon seems to hang until the Weblogic server is restarted. I can still get into the Design Console or the web app but I can't successfully seem to get any more tcRecon instances. After the error no additional users will show up in the design console.
We have the PeopleSoft connector on OIM 9.1.0.2 and Weblogic 10.3.
Do you have any insight of things to look at?
Thanks. -
Flushing out remaining contents of a queue after weblogic shuts down
Anyway to tab into Weblogic shutdown event, so I can run some clean up code to
disconnect a persistent connection.. etc.
Gary
"Irwin Yoon" <[email protected]> wrote:
I have a queue which runs as a daemon thread. Every so often the queue
wakes up to empty the queue, then goes back to sleep when it's done,
then
wakes up again, etc. The queue is represented as an array. The queue
is
part of a single instance of a class, similar to a startup class.
This is my question: When the weblogic server is shut down, what is
the
best way for the queue to be able to flush out all the remaining items
in
its queue?
Is a weblogic shutdown class the way to go? If so, how could this be
implemented? Any other suggestions?
Thanks,
Irwin -
Weblogic 4.5. with SP11 running on NT
when you hit refersh button on one site multiple times, It gives java.exe error and shut down the webserver.
Any body can help me on this.
Thanks.Thanks Kumar:
I am using JDK 1.2.2 I am not sure if that is certified or not. But it just kills the server and I have to restart the server to make it work The constant error is JAVA.EXE error and nothing more. I am not familiar with the setup of this yet.
The performance is very very slow too. When you refresh the web page Java.exe in the services pannel keep on incresing the usage of memory.
amar
Kumar Allamraju <[email protected]> wrote:
Does the JVM SEGV's or core dumps. Do you see any thread dump?
WebLogic server cannot cause core dumps. what version of JDK you are using?
Make sure you are using the certified JDK mentioned in our platform support page.
Kumar
amar wrote:
Weblogic 4.5. with SP11 running on NT
when you hit refersh button on one site multiple times, It gives java.exe error and shut down the webserver.
Any body can help me on this.
Thanks. -
WebLogic shuts down after 4 hours
Hi:
WL 5.1.0 sp 3
SunOS 5.6
J2 1.2.1_04
I run my application under load for 4 hour and then the server throws a
bunch of exceptions like:
ListenThread.run() failed
<UTILS> UnsyncCircularQueue was full!
when it runs the expand command on the queue. After this it just shuts
down.
Could anybody provide an explanation how this mechanism works and if
there are any tuning parameters to control the size of the queue.
Thanks.Pl see earlier postings on the same topic (under the subject "WLS dies
during stress testing").
Srikant.
Paul Iter wrote:
Hi:
WL 5.1.0 sp 3
SunOS 5.6
J2 1.2.1_04
I run my application under load for 4 hour and then the server throws a
bunch of exceptions like:
ListenThread.run() failed
<UTILS> UnsyncCircularQueue was full!
when it runs the expand command on the queue. After this it just shuts
down.
Could anybody provide an explanation how this mechanism works and if
there are any tuning parameters to control the size of the queue.
Thanks. -
We have the following configuration
WLS 5.1 sp6 on solaris with JDK 1.2.2
Getting the following error
Wed Oct 25 08:34:48 PDT 2000:<I> <ServletContext-General> WatchList: init
Wed Oct 25 08:49:26 PDT 2000:<I> <ServletContext-General> UserDetails: init
Wed Oct 25 09:56:07 PDT 2000:<E> <ConMan> Attempt to sendMsg using a closed
connection
Wed Oct 25 09:56:07 PDT 2000:<E> <RJVM> Exception on send :
weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
Wed Oct 25 09:56:07 PDT 2000:<I> <CliCon-#|movies|0.972487707438> Connection
to client for ClientContext - id: '#|movies|0.972487707438', bound: 'true',
dead: 'false' has been unexpectedly lost because
weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException].
Initiating hard disconnect.
Wed Oct 25 09:59:34 PDT 2000:<I> <CliCon-#|movies|0.972487707438> Removing
ClientContext - id: '#|movies|0.972487707438', bound: 'false', dead: 'false'
because of hard disconnect timeout
Wed Oct 25 09:59:34 PDT 2000:<I> <EventProxy> Auto Unregistered
WEBLOGIC.COMMANDS
Please helpadditional details about the application would be helpful ... at first glance,
it looks like you are attempting to use a connection that is already closed!
Srikant, [email protected], http://weblogic.bea.com/, etc.
Rakesh Gupta wrote:
We have the following configuration
WLS 5.1 sp6 on solaris with JDK 1.2.2
Getting the following error
Wed Oct 25 08:34:48 PDT 2000:<I> <ServletContext-General> WatchList: init
Wed Oct 25 08:49:26 PDT 2000:<I> <ServletContext-General> UserDetails: init
Wed Oct 25 09:56:07 PDT 2000:<E> <ConMan> Attempt to sendMsg using a closed
connection
Wed Oct 25 09:56:07 PDT 2000:<E> <RJVM> Exception on send :
weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
Wed Oct 25 09:56:07 PDT 2000:<I> <CliCon-#|movies|0.972487707438> Connection
to client for ClientContext - id: '#|movies|0.972487707438', bound: 'true',
dead: 'false' has been unexpectedly lost because
weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException].
Initiating hard disconnect.
Wed Oct 25 09:59:34 PDT 2000:<I> <CliCon-#|movies|0.972487707438> Removing
ClientContext - id: '#|movies|0.972487707438', bound: 'false', dead: 'false'
because of hard disconnect timeout
Wed Oct 25 09:59:34 PDT 2000:<I> <EventProxy> Auto Unregistered
WEBLOGIC.COMMANDS
Please help -
WebLogic hangs around after shutdown process appears to complete - Message Driven Bean related
On my current project we have some Ant scripts that automatically
start and stop WebLogic. The stop script equates to (not exactly but
close enough):
java weblogic.Admin -url localhost:8001 -password password -username
username SHUTDOWN
WebLogic is start and shutdown for each system module. All modules
use the exact same script for these two actions. Some of the modules
use Message Driven Beans and consequently, since these use JMS, a
JMSxxx.dat file is generated in the jms_store directory. As part of
the cleanup process the jms_store directory and all files in it are to
be deleted AFTER WebLogic shuts down.
The shutdown process works fine in all cases where JMS is not used and
in all cases where JMS IS used but there are NO message driven beans.
However, when there is a message driven bean the server does not shut
down in a timely manner, sometimes not at all (no error messages are
produced), and the JMSxx.dat file
remains locked. Consequently, all of the tests run via the ant script
for modules come to a grinding halt (i.e. environment could not be
cleaned so further tests would be skewed).
Can anyone shed some light on a definitive order of events during
WebLogic's shutdown process? What is the best way to test for the
server being up? I know there is a ping utility for weblogic - should
this be used or should a connection to a JNDI or JMS listening port do
the trick? Any other ideas would be welcome.
Thanks in advance,
MarkOn my current project we have some Ant scripts that automatically
start and stop WebLogic. The stop script equates to (not exactly but
close enough):
java weblogic.Admin -url localhost:8001 -password password -username
username SHUTDOWN
WebLogic is start and shutdown for each system module. All modules
use the exact same script for these two actions. Some of the modules
use Message Driven Beans and consequently, since these use JMS, a
JMSxxx.dat file is generated in the jms_store directory. As part of
the cleanup process the jms_store directory and all files in it are to
be deleted AFTER WebLogic shuts down.
The shutdown process works fine in all cases where JMS is not used and
in all cases where JMS IS used but there are NO message driven beans.
However, when there is a message driven bean the server does not shut
down in a timely manner, sometimes not at all (no error messages are
produced), and the JMSxx.dat file
remains locked. Consequently, all of the tests run via the ant script
for modules come to a grinding halt (i.e. environment could not be
cleaned so further tests would be skewed).
Can anyone shed some light on a definitive order of events during
WebLogic's shutdown process? What is the best way to test for the
server being up? I know there is a ping utility for weblogic - should
this be used or should a connection to a JNDI or JMS listening port do
the trick? Any other ideas would be welcome.
Thanks in advance,
Mark -
Weblogic 11 G Certification 1Z0-102 Contents Updated?
Hi,
I've been working for 1Z0-102 Weblogic 11g Exam since some time now and I recently checked the exam objectives to validate my prep. It looks like it has been reduced and although objectives still cover clustering and fail over, exam contents do not !
Am I looking at wrong information, or it has been updated? Was it ever there? I can recall having these topics in WLS 11G Cert. Can someone validate?
http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=5001&get_params=p_exam_id:1Z0-102&p_org_id=&lang=
Look at following text from above link :
The Oracle Certified Associate, Oracle WebLogic Server 11g System Administrator should have a firm grasp on the administrative tasks performed by a WebLogic Server 11g System Administrator, including installing and configuring Oracle WebLogic Server 11g, deploying Java EE applications to Oracle WebLogic Server 11g, and configuring Oracle HTTP Server as a Web proxy for Oracle WebLogic Server. OCAs certified as a WebLogic Server 11g System Administrator should also be able to configure Oracle WebLogic Server cluster to support failover and load balancing for applications*.
Certification is obtained by passing the certification exam: 1Z0-102, Oracle WebLogic Server 11g: System Administration I.
Does it mean Cluster is no longer part?
Thanks.It is possible (though infrequent) for exam topics to be updated; there are precedents for this; it happened on DBA OCA/OCP 10gR1->10gR2 and for Solaris 10 under sun. It also happens sometimes after beta.
That is why it is always useful to periodically go back and check as you have sensibly done.
I admit my knowledge of weblogic is patchy. I know very few some obscure parts, a lot of basics I don't know.
From the knowledge I have (which may be imperfect) I believe you are right to question why:
On the exam topics page: http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=5001&get_params=p_exam_id:1Z0-102&p_org_id=&lang= there appears to be noo mention of any clustering topics. On the associated certifcation page http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=458&get_params=p_track_id:Weblogic11g as you rightly say the certification does cover clustering. The suggested training course: http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=609&p_org_id=1001&lang=US&get_params=dc:D58682GC20,p_preview:N .... covers clusters.
At least three possibilities exist:
- Clustering covered under other topics or throughout exam (IMHO unlikely)
- Clustering topics were in exam, but removed, and certiifcation description not changed to suit.
- Clustering topics are on exam but missed from topics list on the webpage
Brandye (cert forum moderator) is usually great at checking this and following up (but she can anlso randomly on holiday etc) .... but IMHO there is more than enough reason here to raise a SR here (note it may take a few days to get an answer):
http://education.oracle.com/pls/eval-eddap-dcd/OU_SUPPORT_OCP.home?p_source=OCP
( Not sure about which Issue type to choose ... its a toss up between ( BEA Certifcation / Certification details or OTHER) ... I think OTHER might be safest).
Post the SR number back on this Thread for Brandye to follow up if she passes by.
~~~~~~~~~~~~~~~~~
My knowledge of this anything that follows is very very sketchy and non authorative. I may be talking rubbish during part of it, and I defer to those who know such technology areas better):
There are/have recently been a number of weblogic related changes ... and Oracle may be steering to view management of weblogic clusters down a different angle:
Looking at the all exams and all certification pages ...
http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=632
I see a number of certifcations / exams which appear to be related to weblogic / weblogic clusters to a greater/lesser degree:
Oracle WebLogic Server 10g System Administrator Certified Expert (WLS 10g OCE via 1z0-108 ) #### This certainly covers clusters ...
Oracle Certified Associate, Oracle WebLogic Server 11g System Administrator ( WLS 11g OCA via 1z0-102)
Oracle Cloud Application Foundation Certified Implementation Specialist (CLOUDAPP OCS via 1Z0-468) ### very loose connection ( beta finishing soon)
Oracle Application Grid 11g Essentials (APPGRID OCS via 1z0-523) ### quite loose connection
Oracle WebLogic Server 12c Certified Implementation Specialist (WLS 12c OCS via 1z0-599) ### Covers cluster
... I suspect as the WLS 11g OCA is at OCA level I postulate it may have been felt appropriate to leave clustering it for a later or different exam (e.g. WLS OCP 11 should that ever appear). Generally the OCS exams are for Oracle Partners and often lean towards installation/deployment of the associated product and things needed by a partner. -
Different error messages for Weblogic-Apache bridge
We are running WLS 5.1 sp5 with Apache as Webserver.
I want to know how could I display more user freindly error messages when
weblogic is down and apache is working. Currently we get the default
Weblogic-Apache down page.
Thanks,
RakeshWe used this but it did not work. Now the default does not show up but it is
not able to find the url that we specify which is reachable if I directly
use in the brower.
"Vinod Mehra" <[email protected]> wrote in message
news:[email protected]..
Checkout the plugin param "ErrorPage" in our documentation.
--Vinod.
Rakesh Gupta wrote:
We are running WLS 5.1 sp5 with Apache as Webserver.
I want to know how could I display more user freindly error messages
when
weblogic is down and apache is working. Currently we get the default
Weblogic-Apache down page.
Thanks,
Rakesh -
HI:
I use the jsp code like the accessories in this mail, the
jsp import a dbquery class ,the .java of the class also in this mail. And
when I run the jsp call the class and run it
the weblogic server down , and the server show me a message like this :
# An EXCEPTION_ACCESS_VIOLATION exception has been detected in native code
outside the VM.
# Program counter=0x1000a94b
and in the browser, the OS also show me the application program java.exe
run error.
I ues intel PIII 550 cpu, and the OS is WinNT4.0, sp6, the weblogic
server I use 5.1 edition, Sp4. jdk1.3 edition , jsp1.1 edition
and I also give the startweblogic.cmd file to show you my java run
environment.
[index.jsp]
[PharmaQueryBean.java]
[startWebLogic.cmd]
The same issue for us.
The same solution : switch to Oracle Thin Client.
Dimitri Rakitine <[email protected]> wrote:
>It uses native libraryi(OCI), so, while it should not, it is possible
>that is can crash.
>
>I would suggest you use Oracle thin JDBC driver - it is 100% java, so
>it will
>not crash the JVM. You can download it from http://otn.oracle.com, if
>you do not have it
>already.
>
>shannon <[email protected]> wrote:
>> HI :
>> I use the jdbc driver=weblogic.jdbc.oci.Driver, but my fellow also
>use this
>> jdbc driver, and on his computer can run these programs, he and I use
>the
>> SAME system, includes the software and hardware.
>
>> thanks , Dimitri Rakitine !
>
>
>> Dimitri Rakitine <[email protected]> wrote in message
>> news:[email protected]...
>>> Which jdbc driver are you using? It looks like it causes an error.
>>>
>>> shannon <[email protected]> wrote:
>>> > HI:
>>> > I use the jsp code like the accessories in this mail, the
>>> > jsp import a dbquery class ,the .java of the class also in this
>mail.
>> And
>>> > when I run the jsp call the class and run it
>>> > the weblogic server down , and the server show me a message like
>this :
>>>
>>> > #
>>> > # An EXCEPTION_ACCESS_VIOLATION exception has been detected in native
>> code
>>> > outside the VM.
>>> > # Program counter=0x1000a94b
>>> > #
>>>
>>> > and in the browser, the OS also show me the application program
>> java.exe
>>> > run error.
>>>
>>> > I ues intel PIII 550 cpu, and the OS is WinNT4.0, sp6, the weblogic
>>> > server I use 5.1 edition, Sp4. jdk1.3 edition , jsp1.1 edition
>>> > and I also give the startweblogic.cmd file to show you my java run
>>> > environment.
>>>
>>> Dimitri
>
>Dimitri
-
Startup Steps performed by weblogic 6.1 SP5
Hi,
I am beginner and very new to weblogic. I am working on an application developed on weblogic 6.1 SP5. There is an issue where weblogic shut down. The server is a two node Cluster server. Weblogic shut down on one node and failed to startup on the second node as well, and we had to restart the server. Reading the logs, only thing we found was there were some thread dumps indicating that there was a deadlock condition due to which the threads were waiting and the server hung.
Could anyone suggest as to what can cause the server to hang?
Also, I wanted to know what are the basic operations that a weblogic server performs during startup like allocating memory, connecting to database etc or provide pointers to any references for weblogic?
Thanks
MinalHi,
I am beginner and very new to weblogic. I am working on an application developed on weblogic 6.1 SP5. There is an issue where weblogic shut down. The server is a two node Cluster server. Weblogic shut down on one node and failed to startup on the second node as well, and we had to restart the server. Reading the logs, only thing we found was there were some thread dumps indicating that there was a deadlock condition due to which the threads were waiting and the server hung.
Could anyone suggest as to what can cause the server to hang?
Also, I wanted to know what are the basic operations that a weblogic server performs during startup like allocating memory, connecting to database etc or provide pointers to any references for weblogic?
Thanks
Minal -
Overrding default Apache-Weblogic bridge error message
We are running WLS 5.1 sp5 with Apache as Webserver. I want to know how
could I display more user freindly error messages when
weblogic is down and apache is working. Currently we get the default
Weblogic-Apache down page.
I tried putting
ErrorPage http://www.mydomain.com/error.html
in apache conf file. Now I do not get the default message, but now it can
not find the above url.
I am able to this url directly in the browser. Please help ?[email protected] (srinivasa reddy) wrote in
<39bb039e$[email protected]>:
>
hi,
I have a basic question, does webloigc support apache-weblogic
bridge with mod_ssl/any ssl installed on apache.
thanks & regards
[email protected]
There is a mod_wl_ssl.so in sp4 (i believe). mod_ssl extends Apaches API
and thereby breaks the WebLogic bridge. For raven installations you need
mod_wl_ssl_rave.so because raven extends the API even further.
Joel
E-Mail: (jbf (at) proceedo dot com)
Maybe you are looking for
-
How do I get my iPod Touch from the iTunes screen without doing a restore?
-
hi friends, i uploaded 2 NOTES in SNOTE 983444 and 981763 983444 shows blue play button ...then it ask dependencies 905220 and 912762..that all done properly.. but 981763 show GRAY DIAMOND.. what it's mean ? one of my friend told that it is
-
Hi, How can i raise an event from one thread, that will be handled by another thread? Thnx in advance.
-
I have Oracle 10g DS. From forms Is it possible to send the report output directly to local printer.
-
Need help with continuum and ringtones
trcaldwel I bought a couple of ringtones this evening on your media stores. the first was fine. I was able download it. The second one which I bought for $2.99 as a ringtone shows me this: 000-000-0000 Subject: Congratulations! You have successfully