Connection Reset issue in Weblogic 8.1

Hi,
We have an application running on weblogic 8.1. Please let men explain the steps that we carried out:
1. A new user was being enrolled through the applciation.
2. To make the connection object the value of the properties DriverClass, ConnectionURL, UserId and Password was obtained from the config.xml.
3. preparedStatement.executeUpdate() inserted data in the database.
This works fine initially but when i leave the system idle for an hour or so and then try to access the application we get an error:
java.sql.SQLException: Io exception: Connection reset
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3675)
at oracle.jdbc.ttc7.TTC7Protocol.open(TTC7Protocol.java:618)
at oracle.jdbc.driver.OracleStatement.open(OracleStatement.java:575)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2803)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:608)
at workout.security.weblogic.realm.rdbms.RDBMSDelegate.addGroupMember(RDBMSDelegate.java:757)
at workout.security.weblogic.realm.rdbms.RDBMSRealm.addGroupMember(RDBMSRealm.java:446)
at workout.security.weblogic.RDBMSSecurityRealm.add(RDBMSSecurityRealm.java:84)
at workout.util.LDAPClientHelper.add(LDAPClientHelper.java:39)
at workout.ejb.Enrollment.EnrollmentBean.enroll(Unknown Source)
at workout.ejb.Enrollment.Enrollment_q1qync_EOImpl.enroll(Enrollment_q1qync_EOImpl.java:206)
at workout.ejb.Enrollment.Enrollment_q1qync_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at workout.ejb.Enrollment.Enrollment_q1qync_EOImpl_812_WLStub.enroll(Unknown Source)
at workout.beans.UserProfile.enroll(Unknown Source)
at jsp_servlet._customer_service._consumer_enrollment.___processall._jspService(___processall.java:1524)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
After some more attempts the system appears to work fine.
If anyone can advise then it will be of great help.
Thanks & Regards
Neeraj Kanodia

For those interested, I have some updates on this subject and someone out there sent me a mail asking if I ever found anything out.
Basically, when I encountered this issue the first time, I was working on a SP2 Portal. We were having numerous small bugs like this one with SP2 that centered around the back button or refresh button. BEA gave us a "super patch" back in July or so that when applied to our SP2 project, fixed our issue. I have sense moved onto SP3, and I did not see the compression issue (so I think SP3 must have the patches correctly setup...like I would assume it would).

Similar Messages

Connection reset by peer issue

Hello,
Our application is occasionally getting messages like :
weblogic java.net.SocketException: Connection reset by peer: JVM_recv
in socket input stream read
although it eventually recovers (we have the jdbc refreshTestMinutes
set to 5). We are using Weblogic 5.1 Service Pack 12 and Jdk1.3.1_04
connecting to SQL Server 2000 on another machine.
After scratching our heads with what might be wrong with our
application, we think it might be a network issue. Theres nothing in
the SQL Server logs to indicate that there has been a problem on that
side.
Has anyone had this problem and resolved it, and if so how? Are we on
the right track?
Thanks,
Caroline Sturtridge

Thanks for those suggestions, we'll try them and see if they work.
Strangely, I wrote a small program to keep a socket open between the
two machines (completely separate from the main application) and we've
not had a problem since...
Z
"Slava Imeshev" <[email protected]> wrote in message news:<[email protected]>...
Hi Zeetha,
"zeetha" <[email protected]> wrote in message
news:[email protected]..
Hello,
Our application is occasionally getting messages like :
weblogic java.net.SocketException: Connection reset by peer: JVM_recv
in socket input stream read
although it eventually recovers (we have the jdbc refreshTestMinutes
set to 5). We are using Weblogic 5.1 Service Pack 12 and Jdk1.3.1_04
connecting to SQL Server 2000 on another machine.
After scratching our heads with what might be wrong with our
application, we think it might be a network issue. Theres nothing in
the SQL Server logs to indicate that there has been a problem on that
side.
Has anyone had this problem and resolved it, and if so how? Are we on
the right track?It's definitely a network issue. I faced this kind of problem before.
o You need to use test connections on reserve to true.
o You need to talk to your network admin and find out
if there are any firewalls/proxies between the app server
and the database. They can be dropping connections
after a period of incativity.
o Ask the network admin to check error counters on the switch
ports. Sometimes when the switch port is set to 100Mbit/Firm
and other side use 100MBit/Auto, the parites can't negotiate
speed and fall down to speed of 10th of kilobytes, having
multiple errors etc. Cisco switches like doing this.
Hope this helps.
Regards,
Slava Imeshev

Connection Reset Hangs WebLogic

We are using WLS 6.1 Sp2 and Oracle 8.1.7 and sometimes we get a "Connection Reset
by Peer" error from the database that hangs the WebLogic. Does anybody know if
there is anything to prevent at leaset WebLogic from hanging?
Thanks,
-Jalil

Jalil wrote:
We are using WLS 6.1 Sp2 and Oracle 8.1.7 and sometimes we get a "Connection Reset
by Peer" error from the database that hangs the WebLogic. Does anybody know if
there is anything to prevent at leaset WebLogic from hanging?
Thanks,
-JalilThat means the DBMS or network has dropped the connection from the driver.
Which JDBC driver are you using? If it's a type-2 driver like ours (uses DBMS-
supplied native code for connectivity), sometimes the native code will hang,
and the JVM can't do anything with that thread. I recommend you try using
Oracle's latest thin (all Java) driver.
Joe

Configuration Issue in connecting oracle AQ in weblogic server 10.3.5

Hi,
I am working in Message driven bean and want to receive the message from queue called IEDWM_QUEUE and
have made all the necessary configurations for connecting oracle AQ in weblogic .... Created Foriegnserver,connections factories,destination in JMS Module(weblogic).
But Still i couldn't able to connect to JMS Destination, getting the below error
Jan 16, 2012 12:40:15 PM GMT+05:30> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: CandidateConsumer is unable to connect to the JMS destination: Queues
IEDWM_QUEUE. The Error was:
avax.naming.NamingException: The configuration of the AQjmsInitialContext is not complete. The configuration must contain datasource or (db_url,java.naming.security.principal,java.naming.security.credentials) or both
Kindly tell me if you need any further information and I request you to provide the solution, it will be more helpful for us..
With Regards,
Sridhar.T

Hi,
If I recall correctly:
1 - Ensure you have configured and targeted a Data Source for Oracle, and check your statistics or logs to make sure that it is working.
2 - Reference this Data Source as per the AQ instructions. I think this involves using a specific property name in the context properties for the AQ initial context, where the context properties are set as part of foreign server configuration.
Tom

Connection Reset while making http web service call to remote server

Hello guys,
Our environment details are as follows:
WebLogic version: 10.3.3
Cluster: yes
Database: Oracle
Web service server: Remote application
When our WebLogic server makes a http Web service call to another remote application which runs on IIS server for creating a record. The record gets created in remote application but WebLogic server log says java.net.SocketException: Connection reset and the same record doesn't get created in WebLogic application. We have confirmed that remote application is running and it is behaving as expected. Also, we installed web service client on our WebLogic machine just to isolate any network related issues, when we make a same request through this client it works fine and we get answer. At this point in time, it looks like it could be WebLogic or application which is behaving goofy. we are running out of ideas, it would be nice if someone have any thoughts on it like turning on any flags or any other troubleshooting steps. Please, let me know.
Here is the stack trace:
####<Sep 18, 2011 12:31:40 AM MDT> <Info> <com.blah.blah> <server1> <WLSserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defaul
t (self-tuning)'> <user> <BEA1-69D606DA85BDB1A0A7D5> <> <1316327500388> <BEA-000000> <ERROR com.blah.blah - Error during creating a order remoteappja
va.net.SocketException: Connection reset
com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: Connection reset
at com.sun.jersey.api.client.Client.handle(Client.java:569)
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:556)
at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:69)
at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:451)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:173)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at weblogic.net.http.MessageHeader.isHTTP(MessageHeader.java:220)
at weblogic.net.http.MessageHeader.parseHeader(MessageHeader.java:143)
at weblogic.net.http.HttpClient.parseHTTP(HttpClient.java:462)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:364)
at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
at weblogic.net.http.HttpURLConnection.getResponseCode(HttpURLConnection.java:952)
at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:215)
at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)
... 58 more
>
thanks a lot for your help in advance
Regards,

Here's what the issue was for us:
When the web service was initializing, Weblogic? was trying to retrieve the WSDL first before initializing the service.
Though the web service URL was proper, the WSDL itself was unresolvable. This led to this strange connection reset error.
So, if you're experiencing this consistently, check your WSDL URL.
We used "strace" to discover this problem by running it for a brief time while the web service initialization was attempted - and it very clearly showed that the code was attempting to laod something from a bogus address / IP

JDBC Connection reset by peer: JVM_recv in socket input stream read

Hey Guys,
Has anyone seen this issue? We get this error in our Weblogic app logs at times and no one is able to login to our application. Our database server and SQL server seem fine at a high level. Any ideas what is causing this?
com.s1.arch.persistence.exception.PersistenceException weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server, java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
Thanks

please make sure that there is no Firewall between your servers and DB server. this message usually happen when there is a fire wall between the servers. if yes please make sure that the connection time on fire wall is longer than the time needed to complete an operation another thing that you need to check if you have a fire wall which is to make sure that Oracle DBMS return the request to the same port that it is listening to (1521 default).

Re: Connection reset by peer: Connection reset by peer

 >This is not a problem. It is an error message that you can safely ignore (that
 we should not be printing) and have fixed in version 6.0.
 Sorry but we are upgrading from 5.1 to 6.1sp2 and this became a problem for us.
 Indeed we just ignored this exception in 5.1, but today with 6.1sp2, we get it
 each time we do a RequestDispatcher.forward(). The forward is done, but every
 attributes set on the request are lost !!
 At first I thought it was related with the NT Muxer, or the NT Performance Pack,
 I removed the property NativeIOEnabled but I still get a :
 ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection reset by
 peer: socket write error
 at java.net.SocketOutputStream.socketWrite(Native Method)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
 at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
 at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
 at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
 at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
 at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
 at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
 at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
 at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
 at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
 at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


 Yann,
 This is not a J2EE Connector problem. From the stack trace it looks like you might
 have better luck posting this to the Servlet newsgroup.
 Also, just so that you are aware, this newsgroup is not monitored regularly so
 if your issue/question is not getting answered in a timely manner, please send
 a request to BEA Support.
 >
 >>This is not a problem. It is an error message that you can safely ignore
 >(that
 >we should not be printing) and have fixed in version 6.0.
 >
 >--
 >
 >Sorry but we are upgrading from 5.1 to 6.1sp2 and this became a problem
 >for us.
 >Indeed we just ignored this exception in 5.1, but today with 6.1sp2,
 >we get it
 >each time we do a RequestDispatcher.forward(). The forward is done, but
 >every
 >attributes set on the request are lost !!
 >At first I thought it was related with the NT Muxer, or the NT Performance
 >Pack,
 >I removed the property NativeIOEnabled but I still get a :
 >
 >ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection
 >reset by
 >peer: socket write error
 > at java.net.SocketOutputStream.socketWrite(Native Method)
 > at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
 > at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
 > at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
 > at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
 > at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
 > at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
 > at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
 > at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
 > at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
 > at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
 > at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
 > at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
 > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 > at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
 > at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >
 >

Connection reset by peer : Socket write

Hi, everybody
I am working with weblogic5.1 with servicepack 8. Our server is running for
24X7X365 but i got some weired error this morning saying that "IO Exception
:Connection reset by peer : Socket write
error". I believe this has to do with weblogic.
Can somebody guide me on this issue.
Any help would be appreciated.
Thanks
Gautam

Pretty difficult to track such kind of things if it is not easily
reproducible. Could you also try it out with SP9? Also, try posting it
on the JDBC newsgroup. Maybe, Joe Weinstein might have more answers.
Shiva.
"G.........." wrote:
LoggingService is one of class that calls db methods.well, we get
connection from pool and return it pool .we are refreshing connection
pool regularly, following is some of the entries in properties
file initialCapacity=5,\
maxCapacity=10,\
capacityIncrement=1,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\ No this message is not easily
reproductible.JDK version 1.2.2 and os is windows NT4.0 ThanksGautam
"Shiva Paranandi" <[email protected]> wrote in message
news:[email protected] does this
"com.gdaxs.util.LoggingService.logSystemErrorMsg" do? How is
your pool usage? Do you use the connection pools for a long
time? Also, can you check if this happens after a pool
refresh or not? Is this message easily reproducable? What is
the jdk version you are using and what OS?
Shiva.
"G.........." wrote:
Here is complete stack trace.
Io exception: Connection reset by peer: JVM_recv in socket
input stream read
Stack trace:
java.sql.SQLException: Io exception: Connection reset by
peer: JVM_recv in socket input stream read
at
com.gdaxs.util.LoggingService.logSystemErrorMsg(LoggingService.java:309)
at
com.gdaxs.DBManager.DataRetrieverBean.getCloseOrders(DataRetrieverBean.java:2208)
at
com.gdaxs.DBManager.DataRetrieverBeanEOImpl.getCloseOrders(DataRetrieverBeanEOImpl.java:2656)
at
com.gdaxs.DBManager.DataRetrieverBeanEOImpl_ServiceStub.getCloseOrders(DataRetrieverBeanEOImpl_ServiceStub.java:343)
at
com.gdaxs.closedOrdersBean.init(closedOrdersBean.java:95)
at
jsp_servlet._closedorders._jspService(_closedorders.java:236)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
and after it series of exception like below
Io exception: Connection reset by peer: socket write error
Stack trace:
java.sql.SQLException: Io exception: Connection reset by
peer: socket write error
at
com.gdaxs.util.LoggingService.logSystemErrorMsg(LoggingService.java:309)
at
com.gdaxs.traderadministrator.LDAPInterfaceBean.getTradingAccounts(LDAPInterfaceBean.java:285)
at
com.gdaxs.traderadministrator.LDAPInterfaceBean.getTraderCredentials(LDAPInterfaceBean.java:137)
at
com.gdaxs.traderadministrator.LDAPInterfaceBeanEOImpl.getTraderCredentials(LDAPInterfaceBeanEOImpl.java:99)
at
com.gdaxs.traderadministrator.LDAPInterfaceBeanEOImpl_ServiceStub.getTraderCredentials(LDAPInterfaceBeanEOImpl_ServiceStub.java:109)
at
com.gdaxs.traderadministrator.TraderAdministrator.onMessage(TraderAdministrator.java:278)
at
progress.message.jclient.Session.ew_(progress/message/jclient/Session.java)
at
progress.message.jclient.QueueSession.run(progress/message/jclient/QueueSession.java)
at
progress.message.jclient.sl.run(progress/message/jclient/Session$SessionThread.java)
Thanks
Gautam"Shiva Paranandi" <[email protected]> wrote in
message news:[email protected]...> Could you
post the entire exception?
Shiva.
"G.........." wrote:
Hi, everybody
I am working with weblogic5.1 with servicepack 8. Our
server is running for
24X7X365 but i got some weired error this morningsaying that "IO Exception
:Connection reset by peer : Socket write
error". I believe this has to do with weblogic.
Can somebody guide me on this issue.
Any help would be appreciated.
Thanks
Gautam
[att1.html]

Socket read error: connection reset by peer

Hi.
Has anybody experienced the error message �Socket read error: connection reset by peer�
Please see below for detailed information.
Appreciate your help
Regards
RT
Enviroment specification
Server: HP/UX 11.00 64-bit, Oracle RDBMS 8.1.6.0.0 64-bit
2 firewalls between client and db.
Client:
Win 2000,
SP3,
Oracle Client 8.1.7.0.0 ,JDBC OCI (thin JDBC driver,class12.zip)
JDK 1.3
JRUN3.0
The TCP protocol is being used in the communication
Error messages
Web Users receive: Socket read error: connection reset by peer
Trace files on the sever: Read unexpected EOF ERROR on 18.
Explanation: The error in the server sqlnet trace file, suggests that a client connection has terminated abnormally, i.e. client machine powered off, a cable removed or a network connection aborted without warning. No user has complained of such a problem and there is no client trace with an error.
The problem
The users of the java web application, experiencing an exception almost once or twice a day.
The JRUN web-server reports broken connections to the db and client are receiving "connection reset by peer".
At the moment when the errors occurs the users just have to wait a while(2-10 min) and then they can use the web application again.(no action is taken)
This problem can not be reproduced. The problem happens only occasionally when the network is under heavy load and new DB connection is being created.
The application
The java web-application uses a customized connection pooling against the database. This pool is shared among all the users of the website. whenever a user process needs to fetch data from the database, a free connection from this pool is allocated. The application is testing if the connection is valid before making a transaction (select '1' from dual). When the error occurs a ORA-3113 end-of-file on communication channel is returned to the application.
The path between the client and db involves at least two firewalls. The firewalls are opened for sql*net traffic. The network group can tell that enquiries from the app.server is not getting feedback from the db. They have not however, identified if the enquiries are reaching the db-srever, or if they are stopped earlier in the network.
Around 1000 users, are using other applications which uses dedicated sqlnet connections against the db and they have not experienced any problems.
Issues considered
Connection pooling
It is a customized connection pooling, developed by Lindorff developers.
I have read through the source code for the connection pooling and it does the job as it should, and in case of bad connection, it tries to create a new connection.
The log file shows that the call to the method DriverManager.getConnection() hangs until the server goes down, which is probably because of the fact that the method DriverManager.setLoginTimeout(), does not take effect and timeout value is Zero. ( According to oracle , Oracle JDBC does not support login timeouts and calling the static DriverManager.setLoginTimeout() method will have no effect).
Firewall
One thing to consider is when the firewall may decide to shut down the socket due to long inactivity of a connection. This will cause problems to JDBC Connection Pool because the pool is not aware of this disconnection at the TCP/IP level; until someone checks out the connection from the pool and tries to use it. The user will get a Socket read error: connection reset by peer.
Jrun timeout paramter is less than the firewall�s timeout so the firewall will not close a connection before Jrun does.
Number of processes the DB can handle
Processes parameter is 1300, , they have not experienced the Oracle error msg �max # of processes reached�.
Port redirection through a firewall:
Since the firewall has a sql net proxy Port redirection through a firewall is not a problem. Problems with port redirection only appear at connect time, but in this situation the connections fail long after the connection is established.
The network group
The network people who investigaged the problem at Lindorff report that there are a significant amount of "dropped packages" between the database server and the jdbc client (web-application) 24 hrs. The reason for this is "unknown established TCP packet" which means that the firewall does not consider these packages to be part of an already established session. The network group believes this happen because one of the hosts send a RESET or FIN signal which the firewall have noticed but are not received by the other host.
It seems like the firewall are dropping packages bacause of "Unknown
established TCP packet" from both the JDBC client and the TNSLISTENER on the database server. The dropped packages are SQL*Net v2 traffic so clearly Oracle products are involved

Presumably something is working.
Thus the problem is not with your code. At least not the database part that you have control over.
That error occurs when the other side closes the socket. Presumably you are catching lost connection exceptions and trying to restore it.

Timeouts, connection reset, and EOF on socket type HTTP, etc.

We've created our own HTTP client simulation tool to run multiple virtual users against Weblogic, but we're seeing lots of errors when we ramp up the number of virtual users. So I'm just trying to figure out if it's something about the way we're handling the sockets in the simulator, or some type of configuration on Weblogic. These are the types of messages I see in the log:
Tue Apr 18 16:48:13 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4803,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:13 EDT 2000: <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
Tue Apr 18 16:48:13 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4806,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:13 EDT 2000: <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
Tue Apr 18 16:48:15 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4815,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:15 EDT 2000: <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
Tue Apr 18 16:48:21 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:37 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4816,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:42 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4817,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:51 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:51 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Thanks in advance,
Mike Gorman, Director of Architecture
YOUcentric, Inc.
Charlotte, NC
704-643-1000 x518
http://www.youcentric.com

Mike,
Try increasing the value of weblogic.login.readTimeoutMillis.
Mike Gorman wrote:
>
We've created our own HTTP client simulation tool to run multiple virtual users against Weblogic, but we're seeing lots of errors when we ramp up the number of virtual users. So I'm just trying to figure out if it's something about the way we're handling the sockets in the simulator, or some type of configuration on Weblogic. These are the types of messages I see in the log:
Tue Apr 18 16:48:13 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4803,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:13 EDT 2000: <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
Tue Apr 18 16:48:13 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4806,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:13 EDT 2000: <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
Tue Apr 18 16:48:15 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4815,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:15 EDT 2000: <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
Tue Apr 18 16:48:21 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:37 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4816,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:42 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4817,localport=7001] See property weblogic.login.readTimeoutMillis.
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:47 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:51 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Tue Apr 18 16:48:51 EDT 2000: <PosixSocketMux> EOF on socket type HTTP
Thanks in advance,
Mike Gorman, Director of Architecture
YOUcentric, Inc.
Charlotte, NC
704-643-1000 x518
http://www.youcentric.com
Stuart Lawrence
Software Engineer
BEA WebXpress http://www.bea.com

My Internet Connection Dropping Issues...

I too am having the occasional Internet connection dropping issues. Phone and TV continue to work.
Since I had Fios installed last November I am on my third ONT and 2nd router. When I called in my latest drop yesterday the call center person told me I had a hardware issue because my computer had a valid IP address assigned. I tried to teach her something about DHCP but she would not listen to me. I asked her to please reboot the ONT and she refused because "nothing was indicating a problem with it". Whatever...
Each time the Internet goes out the router acts fat and happy. I have full green on WAN Coax, and strangely enough, a flashing green Internet activity indicator. Logging into the router shows that I am MOCA connected and assigned a WAN IP address. But I can't get out past the router at all. On the event that led to me getting a replacement router the lady said she could talk to the ONT just fine, but not the router. We reset the router and ONT port numerous times and the connection finally came back up.
I am not sure of the protocol between the ONT and router, but I think the ONT is keeping enough signal going to make the router "think" its happy, but then the ONT is not passing packets at some point. After yesterdays call and the refusal to reset the ONT I just hung up on her and reset it myself. Of course everything started working just fine...like I thought it would.
So what is the issue here? Is MOCA a mess? Is an Ethernet connection to the ONT better? I am utterly disgusted with this miserable system and can't afford to continue having these outages.
I should also add the other wonderful features I have seen. When I tried to powercycle the *new* router yesterday it decided to dump its entire config including my port forwarding. Nice... And I have given up using wireless because if I set the router for WPA it locks up so hard that it takes a master reset to get going again.
Anyone have some advice on getting this system stable?

I would try using a non-verizon router. I used the Netgear router and it fixed my problem. The Verizon router seem to be pieces of garbage and they over-hear.

SSL: Connection reset by peer ; Failed to enable crypto error while calling the report using bing API with SOAP client

Hi,
I am trying to fetch report using bing API and making a SOAP call for fetching the data. I get the following error:
[Warning] fopen(): SSL: Connection reset by peer [file] /var/www/sites/psmedia/perfectstormmedia/tools/class/msn_api.class.php [line] 780
02-04-2015 10:17:41 (BST) : [Warning] fopen(): Failed to enable crypto [file] /var/www/sites/psmedia/perfectstormmedia/tools/class/msn_api.class.php [line] 780
02-04-2015 10:17:41 (BST) : [Warning] fopen(https://download.api.bingads.microsoft.com/ReportDownload/Download.aspx?q=rzr63XFt5qJduddohoIRyOYAP%2f1%2ftsnhk8L%2bzBmUpdU2CQlcUB98RpY%2bbOaLFFGMqAC4IUUadC%2fNdNnJqeVCY%2f%2bpy6noVsVA%2fMJp47a3Xb1VjABfKhcdKy6vqpgEdcQg%2fQZ7QcEpZ3bEloJjUtGpDquFk53BnkeHEPVWZkDYcsQegRz%2fpG4t4w6gKCCRmhArd6osr6ZU9CMJ3lbxtGXjcQEMPvP2apNyr9P%2fc8niyfWA2aBcm1aEmOLX2KL3aRJ4rz9N7gG7uBslVZH%2b4rUjHdB7CMkbb%2fHyHwvPTqGPbPCHnicefr%2b%2fDP70hlkBEGfyOOswK67%2bl1zh7CyIv%2bcMlaDsuDX1HeFf4uORfD41H1z7):
failed to open stream: operation failed [file] /var/www/sites/psmedia/perfectstormmedia/tools/class/msn_api.class.php [line] 780
Whenever I execute my script. Can you please let me know what we can do to solve this issue. The version of PHP we are using is 5.3.3 with open ssl.

Hi Shobha,
I can't confirm what version of PHP you are using, but to err on the side of caution please use the version specified in the sample/SDK:
PHP 5.4.14 has been installed from PHP.
Here is our code examples:
https://msdn.microsoft.com/en-US/library/bing-ads-overview-getting-started-php-with-web-services.aspx
Thanks,
Itai

Connection reset error while calling web service deployed on tomcat

Hello Friends,
I am trying to invoke a web service from web dynpro application. The web service is deployed on tomcat 5.5 server.
I am creating an adaptive web service model using wsdl file. The model gets created without any error.
But when application is deployed and run it is giving following exception:
java.net.SocketException: Connection reset
 at java.net.SocketInputStream.read(SocketInputStream.java:168)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
 ... 102 more
I tried to call the service from a simple java application. There the service works fine.
Also, in the web services navigator, if I specify the wsdl url for testing it gives the same error of "Connection reset".
I don't think this is a proxy server issue as the tomcat is within the local network.
Can someone please help me with this?
Thanks and regards,
Mayuresh
Edited by: Mayuresh Kanvinde on Mar 27, 2008 7:03 PM

Hi Sumit,
Thanks for the reply.
Here is the stack trace:
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://<host>:<port>/WebServicesTest/DummyWebService?wsdl' and service factory configuration 'null'
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:422)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
 at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
 at com.tcs.vis.Vishy.<init>(Vishy.java:73)
 at com.tcs.app.AppView.wdDoInit(AppView.java:101)
 at com.tcs.app.wdp.InternalAppView.wdDoInit(InternalAppView.java:143)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
 at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
 at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
 at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
 at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
 at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:91)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:420)
 ... 45 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
 at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:147)
 ... 49 more
Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Connection reset -> java.net.SocketException: Connection reset
 at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
 at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
 ... 50 more
Caused by: java.net.SocketException: Connection reset
 at java.net.SocketInputStream.read(SocketInputStream.java:168)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
 at com.sap.engine.services.webservices.jaxm.soap.LimitedInputStream.read(LimitedInputStream.java:61)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.readData(EncodedDataReader.java:269)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.fetchData(EncodedDataReader.java:332)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:165)
 at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
 at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.addInputFromInputStream(AdvancedXMLStreamReader.java:292)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:220)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
 at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
 at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
 at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1023)
 ... 52 more
Thanks and regards,
Mayuresh
Edited by: Mayuresh Kanvinde on Mar 28, 2008 1:10 PM

Io Excpetion Connection Reset In OWB Mapping

Hi,
While executing a mapping in OWB i am getting an error Io Exception Connection Reset.
This happens when execution of mapping involves more than 50 lakhs of records.
Please any one can help.

You say: "But the connection is taking more than expected time".
So I am think of a network issue. Check the DNS and/or entries in the HOSTS file if they are according to the prereqs.
Eric

XI 2.0 Inbound file adapter : Connection reset by peer

I am using XI 2.0 and have an inbound file adapter. It polls every 5 minutes. But at least 1 or twice a day the file adapter stops with the following error message.
"java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read" occurred \par
There have been times when this runs for days or weeks without any problems.
Has anyone else seen this issue and how do your correct it?
Currently I have to go into the file adpaters and restart them manually. It would be nice if there was some way to automate this function. Any ideas?
Regards,
Jim

With JDK 5.0 use ojdbc5.jar instead of ojdbc14.jar.

Connection Reset issue in Weblogic 8.1

Similar Messages

Maybe you are looking for