Socket closed exception

Hi all,
I am trying to execute an XI scenario in which i am sending data from sap R/3 system to a table in Oracle 8.0 system using JDBC adapter.
The XI server has JDBC 9.0 driver.
On sending the message, status shown on the XI server is successful, but no data is getting posted in the table.
In XI runtime workbench, in component monitoring, the error shown with the JDBC driver is SOCKET CLOSED.
Pls if anybody can help me with this problem.
Its very urgent.
Thanks in advance.
Regards
Neetu

Hi,
The error shown in the Adapter Monitor in Runtime Workbench is:
Receiver Adapter v1027 for Party '', Service 'HURES':
Configured at 16:35:07 2006-05-12
Last message processing started 15:16:02 2006-05-13, Error: Transform error in xml processor class, rollback:
ERROR:Processing request: Error when executing statement for table/stored proc. 'sap_promotion': java.sql.SQLException: Io exception: Socket closed
     at com.sap.aii.adapter.jdbc.xml2sql.service(xml2sql.java:175)
     at com.sap.aii.adapter.jdbc.XI2JDBC.onInternalMessage(XI2JDBC.java:266)
     at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.callSapAdapter_i(SapAdapterServiceFrameImpl.java:170)
     at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.callSapAdapter(SapAdapterServiceFrameImpl.java:146)
     at com.sap.aii.af.modules.CallAdapterWithMessageBean.process_receiver(CallAdapterWithMessageBean.java:206)
     at com.sap.aii.af.modules.CallAdapterWithMessageBean.process(CallAdapterWithMessageBean.java:161)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl1.process(ModuleLocalLocalObjectImpl1.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
     at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:216)
     at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0.onMessage(AFWListenerLocalObjectImpl0.java:103)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:262)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:611)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:353)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:98)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:419)
     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:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Regards
Neetu

Similar Messages

SQLException: Io exception: socket closed: Bad file number;

Hi,
My server application connects oracle 8i using thin driver.
My code opens a connection and create a statement object:
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection connection = DriverManager.getConnection(url, username, password);
connection.setAutoCommit(false);
Statement statement = connection.createStatement();
After a few hours it runs just fine I get the following error:
java.sql.SQLException: Io exception: socket closed: Bad file number;
The code line that couses this exception is:
statement.executeQuery("my SQL query");
after this there are more errors:
;java.sql.SQLException: Protocol violation;
(in code line: connection.execCommit())
and than a repeated exception of :
java.sql.SQLException: Io exception: Broken pipe;
Does anyone knows a solution? (is the problem in my code or in the oracle account?)
Thank!!!

Which package you are using? if you don't have
classes12.zip, try again by including that package in
the classpath. If you are already using classes12.zip
then try by including nls_charset12.zip in the
classpath.
You can get these packages in Oracle (otn) website.
SudhaThanks!
I had classes12.zip in my classpath, but my classpath also had: classes111.zip
so i removed classes111.zip from the classpath and as far as now,
the problem did not occur again!
(i also added nls_charset12.zip just to be sure)
Lilach

JCOM on WLS 8.1 - SocketException: Socket closed

After creating my application and accessing it - if I don't use it for a while
I get the following exception when I access it. Other than creating a timer to
ping it every 10 seconds or so - is there some way to keep the socket open?
- Mike Reiche
java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
at java.net.SocketOutputStream.write(SocketOutputStream.java:124)
at com.linar.jintegra.RpcConnectionHandler.send(RpcConnectionHandler.java:272)
at com.linar.jintegra.Rpc.invoke(Rpc.java:239)
at com.linar.jintegra.RemObjectExporter.invoke(RemObjectExporter.java:346)
at com.linar.jintegra.StdObjRef.invoke(StdObjRef.java:57)
at com.linar.jintegra.Dispatch.vtblInvoke(Dispatch.java:763)
at excel._ApplicationProxy.getDefaultFilePath(_ApplicationProxy.java:1938)
at excel.Application.getDefaultFilePath(Application.java:2237)

Has anyone gotten an answer on this error? I also get a Socket Closed IOException
after a couple of minutes of not communicating to a remote DCOM application.
I also have to restart Weblogic to get it to communicate again. Works great as
long as I make a request every 10 or 20 seconds.
Rick Holland
>
I am having this exact same problem. I have a support case opened with
BEA about
it, and will let you know if I come up with a solution...
In my case, however, I am gonna have a very hard time sending BEA a repeatable
testcase that demonstrates this problem, as I access a DCOM app that
I cant redistribute.
Would your code be something that you can share with BEA? If so, that
would be
of tremendous help.
"Mike Reiche" <mreiche@no_spam.com> wrote:
After creating my application and accessing it - if I don't use it for
a while
I get the following exception when I access it. Other than creating
a timer to
ping it every 10 seconds or so - is there some way to keep the socket
open?
- Mike Reiche
java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
at java.net.SocketOutputStream.write(SocketOutputStream.java:124)
at com.linar.jintegra.RpcConnectionHandler.send(RpcConnectionHandler.java:272)
at com.linar.jintegra.Rpc.invoke(Rpc.java:239)
at com.linar.jintegra.RemObjectExporter.invoke(RemObjectExporter.java:346)
at com.linar.jintegra.StdObjRef.invoke(StdObjRef.java:57)
at com.linar.jintegra.Dispatch.vtblInvoke(Dispatch.java:763)
at excel._ApplicationProxy.getDefaultFilePath(_ApplicationProxy.java:1938)
at excel.Application.getDefaultFilePath(Application.java:2237)

JDBC Adaper "socket closed"

Hello All,
We are trying to update a database table in Oracle through SAP XI.
Our scenario is IDOC to JDBC.
We are facing a problem during the JDBC connectivity between XI and Oracle.
In adapter monitoring the error saying that Java.sql.SQLException: IO Exception: "socket closed".
We are using XI 3.0 with Oracle 9.2 and at the other end the Database system(where the updation is to be done) is based on Oracle 8.1
The above process works when we try to update the database table (created on Oracle 8i) throgh JAVA Application.
When this updation occurs throgh XI it fails!!
Thanks in Adv.
Rajesh Yallabandi

Good day Yallabandi,
Can other SQL statment works?
If not then:
Please check that you supplied the JDBC adapter with the right and most updated matching JDB\CODBC driver for your destination database.
You also need to load the right jars to your Adapter framwork using the SDM tool.
Follow the "How To Install and configure JDBC" guide
supplied by SAP (get it on the service market place).
Good luck.
Nimrod Gisis
Message was edited by: Nimrod Gisis

JSSE causes OSB business services to receive Socket Closed

Using WL 10.3.3 & OSB 11gR1 on jrockit 1.6.0_45 Redhat:
After enabling the "Use JSSE SSL" option in the managed servers's SSL tab ( because web service clients want to use SHA256 certificates ), OSB business services ( outbound to service providers ) fail with
Exception - Body: <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Fault xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>BEA-380000</faultcode>
<faultstring>General runtime error: socket closed</faultstring>
After a lot of debugging, I've found that the Connection Timeout option within the OSB HTTP transport is involved.
OSB business services which use https AND have a non-zero value for HTTP transport's Connection timeout cause the Socket Closed error.
Business services which do not use HTTPS or do not have a Connection Timeout do not receive the error.
While setting the Connection Timeout to 0 allows the transaction to succeed, that leaves the OSB server vulnerable when the service provider host is not available.
So I've reset the Connection Timeout values to 0, and added this JVM parameter to each OSB managed server
-Dweblogic.http.client.defaultConnectTimeout=5000

There are few BUGs reported for similar issues.
OSB Server Showing "java.io.IOException: SSLEngine is closed" When Attempting to Connect to an External Web Service Using Two-Way SSL (Doc ID 1465618.1)

New root certificates cause socket closed error

We have planning 9.3.1 services with ldap authentication. When we replaced our root certificates in dev we began getting errors. Mostly everything works, but after some inactivity a good log in will be flagged as an invalid user and throw the following exceptions:
2010-03-29 07:43:48,141 [[ORB=_it_orb_id_1,Pool=1]::id-3] WARN com.hyperion.css.spi.impl.ldap.LDAPProvider.authenticate(Unknown Source) - javax.naming.ServiceUnavailableException: ldaps.lirr.org:636; socket closed; remaining name ''
2010-03-29 07:43:48,141 [[ORB=_it_orb_id_1,Pool=1]::id-3] WARN com.hyperion.css.CSSAPIImpl.authenticate(Unknown Source) - com.hyperion.css.CSSAuthenticationException: Failed to authenticate user tlbarat against provider Novel1 Error Code: 2
NestedException:
javax.naming.ServiceUnavailableException: ldaps.lirr.org:636; socket closed; remaining name ''
Does anyone know what we could be doing wrong? We changed to a load balanced virtual server. Could this have caused our issue? We tried setting java option -Dsun.net.inetaddr.ttl=0 but it didn't work. We need to move the change to prod next week. Any insight would be appreciated.

The socket is being closed by the receiver, since it feels that the end of HTTP body stream has been reached. This could happen due to a number of reasons and cannot be directly discerened from your code.
Does changing the buffer size help?
Ironluca

InitialDirContext Throwing ServiceUnavailableException socket closed

Any assistance is appreciated.
Problems occurring when multiple DirContext instances are created. Attempting to make a SSL connection to Active Directory on port 636. A single successful context can be established in the below code. However, a second instantiation of InitialDirContext(env) results in a javax.naming.ServiceUnavailableException: [domain]:636; socket closed error. Multiple contexts are desired to establish a connection pool.
A few items to note. Establishing four unsecure DirContext on port 389 works successfully. I can establish a DirContext on port 636, use the context, close the context then establish new contexts without a problem. A server certificate was imported to the C:\j2sdk1.4.2_11\jre\lib\security\cacerts file. Testing on a local computer. Below is sample code:
public static void main(String[] args) {
 try {
 System.setProperty("javax.net.debug","all");
 // Set up the environment for creating the initial context
 Hashtable env = new Hashtable();
 env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
 env.put(Context.SECURITY_PRINCIPAL, "[USER DN]");
 env.put(Context.SECURITY_CREDENTIALS, "[PWD]");
 //NON SSL
 //env.put(Context.PROVIDER_URL, "ldap://[server]:389");
 //SSL
 env.put(Context.PROVIDER_URL, "ldap://[server]:636");
 env.put(Context.SECURITY_PROTOCOL, "ssl");
 env.put(Context.SECURITY_AUTHENTICATION, "simple");
 // Create the initial context
 DirContext ctx = null;
 DirContext ctx2 = null;
 DirContext ctx3 = null;
 DirContext ctx4 = null;
 try {
 //Works every time...
 ctx = new InitialDirContext(env);
 } catch (NamingException e) {
 e.printStackTrace();
 try {
 //Fails on port 636, works on port 389
 ctx2 = new InitialDirContext(env);
 } catch (NamingException e) {
 e.printStackTrace();
 try {
 //Works on port 636 (after 2nd attempt fails) and port 389
 ctx3 = new InitialDirContext(env);
 } catch (NamingException e) {
 e.printStackTrace();
 try {
 //Fails on port 636, works on port 389
 ctx4 = new InitialDirContext(env);
 } catch (NamingException e) {
 e.printStackTrace();
 Attributes attrs = ctx.getAttributes("[A USER DN]");
 System.out.println("Total attributes returned: " + attrs.size());
 try {
 ctx.close();
 ctx2.close();
 ctx3.close();
 ctx4.close();
 } catch (NamingException e) {
 e.printStackTrace();
 } catch (Exception ex) {
 ex.printStackTrace();
 System.exit(0);
}The java debug statements at the second exception:
Thread-1, WRITE: TLSv1 Handshake, length = 121
Thread-1, received EOFException: ignored
Thread-1, called closeInternal(false)
Thread-1, SEND TLSv1 ALERT: warning, description = close_notify
Plaintext before ENCRYPTION: len = 18
0000: 01 00 0F 78 84 EE 16 24 F6 99 B0 83 52 14 FF 86 ...x...$....R...
0010: 29 3C )<
Thread-1, WRITE: TLSv1 Alert, length = 18
Thread-1, called close()
Thread-1, called closeInternal(true)Again, any assistance is appreciated.

Multiple contexts are desired to establish a connection pool.The JNDI LDAP provider already does connection pooling so you don't need multiple initial contexts at all.

LONG and stream is closed exception

If I create 2 result sets from 2 different statements under the same connection, I get a stream already closed exception when I go to retrieve the results from the 2nd RS if the RS has a LONG column in it. That is, I fetch the results from RS1 OK and on the first next() call of RS2 I get the exception. Now RS1 does not even have a LONG column in it. If I reverse the order (fetch RS2 then RS1) it will work OK.
Any ideas on how to solve this since I will not be able to control the order as it will be depending on the application builder?

I had this (better: still have) problem, too. If a query contains a LONG (VARCHAR/RAW) row, it is important to process the result in correct order. Example: SELECT row1, longrow, row2 from .....; If you access row2 before longrow, the oracle driver collects row1 (datamode), longrow(stream-mode!!!), discards the stream because it switches back to datamode (thus loses the stream -> closed) and reads row2. Complicate? See also http://technet.oracle.com/doc/oracle8i_816/java.816/a81354/basic4.htm Section "Streaming Data Precautions". It's not nice, but it's that way officially. That's my knowledge so far - working on a workaround....

Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
or what's the problem,
Mahmoud Sabry IT System Engineer

this issue maybe will be fix by latest version, we still waiting for it
maybe your issue can be fix using this methods
https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
http://shawn.meunier.com/?p=1#comment-43

Error on content write: Socket closed

Since a week or so we are getting the following stack trace on our WebCenter Portal (11.1.1.6.3). There are several content presenters on it, and so far I've not found out yet where the problem originates from. Has anyone experienced the same, or perhaps any pointers?
<Aug 24, 2012 3:10:13 PM CEST> <Error> <oracle.webcenter.content.internal.http.HttpServiceImpl> <WCS-11001> <Error on content write: Socket closed
oracle.webcenter.content.internal.http.InternalServerErrorException: Aug 24, 2012 3:10:13 PM oracle.webcenter.content.internal.http.HttpServiceExceptionFactory getException
ALL: Error on content write: Socket closed
at oracle.webcenter.content.internal.http.HttpServiceExceptionFactory.getException(HttpServiceExceptionFactory.java:191)
at oracle.webcenter.content.internal.http.HttpServiceExceptionFactory.createInternalServerError(HttpServiceExceptionFactory.java:707)
at oracle.webcenter.content.internal.http.HttpServiceExceptionFactory.createInternalServerError(HttpServiceExceptionFactory.java:685)
at oracle.webcenter.content.internal.http.HttpServiceExceptionFactory.createInternalServerError(HttpServiceExceptionFactory.java:664)
at oracle.webcenter.content.internal.http.Entity.sendResponse(Entity.java:205)
at oracle.webcenter.content.internal.http.HttpServiceImpl.doGetOrHead(HttpServiceImpl.java:322)
at oracle.webcenter.content.internal.http.HttpServiceImpl.service(HttpServiceImpl.java:179)
at oracle.webcenter.content.http.GetHandlerServlet.service(GetHandlerServlet.java:225)
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:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:62)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.wcps.client.PersonalizationFilter.doFilter(PersonalizationFilter.java:75)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.webcenter.content.integration.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:168)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:62)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:179)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>

We have a content presenter which loads a video file from the content server. It looks like the socket is unexpectedly closed at some point if the video is paused or stopped for some reason.

Socket Closed error please help us finding a fix for the same

Hi everyone,
I have a web application deployed on Weblogic 10.3.4.0. In the application there is hyperlink to download a resouce (say an PDF document). Upon clicking the link, IE shows the Open/Save/Cancel dialog box. If the Open/Save/Cancel dialog box is not acted upon by the user within 1 min after it pops up, Weblogic is closing the socket. This causes IE to only download a part of the file say 784 KB or something. Whereas the entire file maybe 1MB in size. Please help in fixing this issue ASAP.
Thanks in Advance
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.teja.systemi.util.AroundData.copyStream(AroundData.java:311)
at com.teja.systemi.client.servlet.servant.Newdownloadsingle.producePageData(Newdownloadsingle.java:108)
at com.teja.systemi.client.servlet.servant.BaseViewController.serve(BaseViewController.java:542)
at com.teja.systemi.client.servlet.FrontController.doRequest(FrontController.java:226)
at com.teja.systemi.client.servlet.FrontController.doPost(FrontController.java:128)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
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: 910597 on Jan 27, 2012 2:15 AM

What do you mean by "moo" ?
Huh? You don't know about the moo? Are you livin' in a barn or sumthin'
Sorry, corny joke.
Seriously--if you haven't heard about the moo, then check out the MacBook forums. Nearly every third or fourth post is about the mooing problem.
My own MacBook moos, but it's not so bad that it makes me upset. I understand, though, that others have it much worse.
Black Macbook; Mini 1.5GHz (Late 2005); Mini 1.4GHz; PB G4 1GHz; PB Lombard; PB 2400; PMac G3; Blueberry iMac; iPod nano 4GB; and a talking Bill King bobblehead doll--Holy Toledo!

WebService Socket Timeout Exception before reaching timeout duration

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

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

Hello, Whenever I try to download Premier Pro CC I get an error message to close (CEPHtmlEngine, CEPHtmlEngine Helper). However, all my applications are closed except for Creative Cloud.

Hello, Whenever I try to download Premier Pro CC I get an error message to close (CEPHtmlEngine, CEPHtmlEngine Helper). However, all my applications are closed except for Creative Cloud.

Terminate the processes in task manager/ activity monitor.
Mylenium

The PersistenceManager has been closed Exception

Hi --
I'm gettting the following exception:
javax.jdo.JDOFatalUserException: The PersistenceManager has been closed.
 at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.checkClosed(PersistenceManagerImpl.java:2080)
 at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.isActive(PersistenceManagerImpl.java:481)
 at
com.solarmetric.kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java:840)
 at
net.nearlythere.utils.Money.jdoGetnet_nearlythere_utils_Money__amount(Money.java)
 at net.nearlythere.utils.Money.compareTo(Money.java:191)
 at
net.nearlythere.business.data.ServiceIntervalPricing.isPaying(ServiceIntervalPricing.java:248)
Now Money is a persistent class which looks like this (shortened greatly):
public class Money implements Comparable, Cloneable, Serializable
public static final Money ZERO = new Money(0.0);
private BigDecimal _amount;
public int compareTo(Money money)
return amount.compareTo(money.amount);
The code that throws the exception looks like:
 Money price = sip.getPrice();
 if(price.compareTo(Money.ZERO) > 0) {
I have reason to believe the price is persistent capable. My question
is: does jdo think the ZERO is persistent capable. Clearly, it is
simply a constant, but is jdo able to handle this?
Thanks,
Dan

Hi Patrick,
In my system.jdo file, "Money" only shows up in only place, here's the
portion of the jdo file in question:
<package name="net.nearlythere.utils">
 <class name="Money">
 </class>
</package>
It resides in a different package than all the other objects, in case
that matters...
Dan
Patrick Linskey wrote:
Dan,
What does your .jdo file look like for Money? In particular, are you
explicitly listing ZERO as a persistent field? If so, can you try explicitly
marking it as persistence-modifier="none":
<field name="MONEY" persistence-modifier="none"/>
This might be a bug in our default persistence assignment code.
-Patrick
On 6/26/02 1:48 PM, "Dan Finkelstein" <[email protected]> wrote:
Hi Patrick,
Here's some more info on this bug. With debug code, I have now
determined that kodo things that Money.ZERO is a persistent object using
the call JDOHelper.isPersistent(Money.ZERO). I've also verified that
"price" is a persistent object -- as well it should be.
It appears that kodo is throwing the PM has been closed exception
because Money.ZERO is thought of as persistent and not part of the
current PM.
Your help is most appreciated,
Dan
Patrick Linskey wrote:
This exception is probably not happening while accessing 'amount' in
Money.ZERO, but rather while accessing 'amount' in 'price'. Additionally,
the issue is not whether or not 'price' is a persistent instance; it's
whether or not the object's PM is still open. The fact that the PM is even
being used means that the object is associated with one.
To debug, use JDOHelper.getPersistenceManager(), JDOHelper.isPersistent(),
etc.
-Patrick
On 6/8/02 10:21 PM, "Dan Finkelstein" <[email protected]> wrote:
Hi --
I'm gettting the following exception:
javax.jdo.JDOFatalUserException: The PersistenceManager has been closed.
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.checkClosed(PersistenceM
an
agerImpl.java:2080)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.isActive(PersistenceMana
ge
rImpl.java:481)
at
com.solarmetric.kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java
:8
40)
at
net.nearlythere.utils.Money.jdoGetnet_nearlythere_utils_Money__amount(Money.
ja
va)
at net.nearlythere.utils.Money.compareTo(Money.java:191)
at
net.nearlythere.business.data.ServiceIntervalPricing.isPaying(ServiceInterva
lP
ricing.java:248)
Now Money is a persistent class which looks like this (shortened greatly):
public class Money implements Comparable, Cloneable, Serializable
public static final Money ZERO = new Money(0.0);
private BigDecimal _amount;
public int compareTo(Money money)
return amount.compareTo(money.amount);
The code that throws the exception looks like:
Money price = sip.getPrice();
if(price.compareTo(Money.ZERO) > 0) {
I have reason to believe the price is persistent capable. My question
is: does jdo think the ZERO is persistent capable. Clearly, it is
simply a constant, but is jdo able to handle this?
Thanks,
Dan

Socket Listener - Exception (Connection refused, reset)

Dear All,
We are developing a Socket Listener for an application. when we try to check the performance the below errors came.
Code
public static void main(String[] args) {
 ServerSocket ss = null;
 Socket s = null;
 try {
 ss = new ServerSocket(Integer.parseInt(property
 .getProperty("SERVER_PORT")), 1500 );
 while ((s = ss.accept()) != null) {
 Thread current = new Thread(new ServerSocketListener(s));
 current.setDaemon(true);
 // start the user's thread
 current.start();
 } catch (Exception exp) {
 exp.printStackTrace();
Exception 1
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(Unknown Source)
 at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
 at java.net.PlainSocketImpl.connect(Unknown Source)
 at java.net.SocksSocketImpl.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at srm.ServerSocketListener.run(ServerSocketListener.java:143)
 at java.lang.Thread.run(Unknown Source)
Exception 2
java.net.SocketException: Connection reset
Test
Invoking the Socket Server Listener with 1500 client (Java and .NET) requests.
Then the above exceptions occurred.
Help me
1) Maximum client a port can supports?
2) Is there any code or property change required?
3) any other way

 Thread current = new Thread(new ServerSocketListener(s));
java.net.ConnectException: Connection refused: connect Nothing is listening at the host:port you are trying to connect a new socket to.
 at srm.ServerSocketListener.run(ServerSocketListener.java:143)You are trying to create a new Socket inside the ServerSocketListener. Why? You already have a connected socket.
java.net.SocketException: Connection resetStack trace please. This usually means you have written to a connection that has already been closed by the other end, but there are other possibilities.
1) Maximum client a port can supports?Please restate your question in standard english.
2) Is there any code or property change required?Required for what?
3) any other wayAny other way to do what?

Socket closed exception

Similar Messages

Maybe you are looking for