I/o Error While Closing Socket Connection
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in WebLogic Server - General All PlacesFusion MiddlewareWebLogicWebLogic Server - General This discussion is archived 10 Replies Latest reply on Aug 14, 2009 11:16 AM by Barossa Node Manager does not restart WebLogic servers when computer starts doublev Jul 17, 2009 9:08 AM Hello all, I'm testing the new WebLogic server release along with new Forms and Reports. I don't have much experience with WebLogic (using Oracle Internet Application 10g) so bare with me for a moment. I'm using Node Manager to start admin servers and all other managed servers. I also installed the Node Manager as a Windows service and configured startup parameters to include -Xrs/-Xnohup as stated in documentation and everything seems to work fine up until I restart the server. Node Manager service starts and according to it's log, it does read startup.properties of each server but it does not start them. Am I missing something here? I was left in an impression that Node Manager should restart the server in case of system restart if the server was running when computer was restarted. Even though I don't have much experience with WebLogic, I'm not a newbie. I've managed to migrate (for testing purposes only) complete business application (more than 1000 forms and reports) from iAS 10g to new version in two days. Application works just fine and I'm only having problems with starting servers when computer starts using Node Manager. Testing environment: Windows 2008 Standard 32bit RAM: 2GB HDD: 140GB CPU: 2xXeon 7717Views Tags: no
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up I/O ERROR: SOCKET ERRORS up vote 1 down vote favorite We have J2EE Web application deployed on JBOSS 4.0.2 server. From last few days The application suddenly stops. we are getting following errors https://community.oracle.com/thread/932295 in log. java.net.SocketException: Software caused connection abort: recv failed Due to above socket errors application is not able to connect database. Restarting jboss application also does not help. To resolve socket error we have to restart production machine. After restarting production machine it works perfectly. What could be reason for above socket errors? java sockets java-ee share|improve this question edited Mar 17 '11 at 11:47 Bobby 8,33433062 asked Mar 17 '11 at 5:07 Maulin 112 Looks like a http://stackoverflow.com/questions/5335089/i-o-error-socket-errors problem on DB side. Did you check errors in DB logs? –Benoit Thiery Mar 17 '11 at 11:35 Is it due to closed DB connection? Looks like you have a firewall issue. –adarshr Mar 17 '11 at 11:38 We are using Windows 2003 64 bit Server. Using Jboss 4.0.2 as application Server, JDK Version 1.6.18 64 bit and apache 2.2.15 as webserver. There are other application instances which are connected to the same database and working fine. To test this DB connection issue, we deployed a jsp in another ear but under the same application server instance which successfully connects to the database server. Please let us know for any additional information required. Looking for a response and a resolution to this ASAP. –Maulin Mar 18 '11 at 14:56 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote That error essentially means somebody tried to read or write from a closed socket (it's Windows speak for "connection reset"). There are a lot of reasons that can happen though, and it's impossible to say exactly why your application is doing it. Some things you might try checking: if you have multiple threads reading and writing to the same socket, make sure one of them isn't closing it try turning off Nagle's algorithm; I've seen this error happen because someone closed the socket before the OS finished writing to it
JMX / WLST / WLDF Proxy Plugin http://middlewaremagic.com/weblogic/?p=2887 / Web Servers Knowledge Sharing Miscellaneous 31 Aug/10 Common NodeManager Issues in WebLogic by Jay SenSharma under NodeManager BufferEmailPrintHi, Jay SenSharma Actual Post Location: http://middlewaremagic.com/weblogic/?page_id=241 Many times we face a very common issue while configuring a Domain which has some remote Managed Servers asssigned i/o error to a Machine. The issue we might face is "NodeManager is Inactive", "SSLException", "Hostname Verification failed", "domain salt not found"…etc =========Issue-1).While Starting the Nodemanager if you see the following Exception …