"Error establishing socket" error on JDBC Receiver Channel.

Dear All,
Scenario: Soap to JDBC.
I m getting error on JDBC Receiver Channel. messages are processed succesfully on ABAP Stack and receiver channel is on below error:
ERROR : Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://156.5.202.194:3312;DatabaseName=ODW': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
Note: i already tested another interface with this same IP and it was fine with different port.
jdbc:microsoft:sqlserver://IP:PORT;DatabaseName=Name
Regards,
Manikandan

and it was fine with different port
socket exception is (always) related to port....did you check with the network team about this new Port?

Similar Messages

Getting "Error Establishing Socket " error while running the application

Hi,
Can Any one help me as I getting the following error while inserting data into database for after some rows and will insert for some rows then again some error . I googled but but didnt get any proper solution.
Soultion what I got it is
1) turn off windows firewall.
2) change server TCP/IP settings.
3) It will give probelm with windows XP SP 2
I tried all but didnt able to solve that.
I am using Java 1.5, MSSQL server 2000,and eclipse 3.2,windows XP SP2
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at com.aztecsoft.quality.DatabaseConnectionQLTYSRV.getCon(DatabaseConnectionQLTYSRV.java:25)
at com.aztecsoft.quality.DatabaseQuery.getDaytoCountRow(DatabaseQuery.java:147)
at com.aztecsoft.quality.ProjectTrackerUtil.getNetworkDays(ProjectTrackerUtil.java:73)
at com.aztecsoft.quality.ProjectPlan.calODurationinDays(ProjectPlan.java:81)
at com.aztecsoft.quality.ProjectPlan.projectSummary(ProjectPlan.java:25)
at com.aztecsoft.quality.ProjectPlan.main(ProjectPlan.java:126)
Thanks in advance.

Hi this is gopi,Hyd.Is your Problem "Getting "Error Establishing Socket " error while running the application" solved if so can you reply me i am waiting for this answer

'Error establishing socket' due to too many TCP sockets

Hallo
I have an app running on Win 2000, SP 3, JRE 1.2, connecting with a MSSQL 2000 DB using MS JDBC drivers and constantly writing updates to this DB. It starts off fine and continues for quite some time before encountering the following exception:
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing socket.
Checking the output from netstat while the application is running revealed a huge number of sockets which are aparently used by the application since closing the application causes all these connections to be closed. I assumed that this may be the cause of the exception.
The application only connects with the database once and statements and resultsets are closed after use.
The same application running at other sites with more-or-less the same environment does not cause as many open sockets.
Can anybody tell why so manu sockets are created and not closed ? Any suggestions will be much appreciated.
Regards
Dawie

As an update, I was using connection pooling, and removed it. Now I create a connection per request and explicitly close the connection when done. This accomplished two things, reduced the number of stale connections, and also "throttled" down the process somewhat (not by much as in testing I found the average response times slowed by only a couple milliseconds).
I did do a netstat on the application server when I started receiving all the errors and found, like dawiemoller did, there was a VERY large number of stale connections to the SQL 2000 server. I wasn't able to telnet into the SQL server and port, as expected. Restarting the Java app on the application server cleared up all the stale connections.
After I removed the connection pooling, I've yet to receive the "error establishing socket" error, however after checking netstat again, I did find that there are still a lot of stale connections, just not nearly as many.
If this is a Microsoft bug, why would the stale connections go away after restarting the Java Application? Microsoft IIS is also running on the same server with database access to the SQL 2000 server and it isn't having any trouble. Could it be just a combination of this "bug" and using Microsoft's JDBC driver (SP1) to SQL 2000? Would switching to another vendors JDBC driver avoid this problem?
Scott Reynolds

Intermittent error establishing socket on SQL Server 2000

I have a suite of 130 JUnit tests. Recently, they started to give me intermittent "error establishing socket" errors when trying to connect to a local instance of SQL Server 2000 via JDBC.
Each test creates one or more connections. I've used wrappers to prove that I'm closing all of the connections, statements, prepared statements and result sets. The first 70 or 80 tests succeed. After that every test gets the "error establishing socket" exception. Sometimes (but not always) SQL Server continues to refuse connections when I re-run the suite. When that happens I have to let it sit for 30 seconds or so (or restart the server) before it will accept connections.
I've tested this with both Microsoft's and WebLogic's JDBC drivers with the same results. There's nothing in the SQL Server logs when this happens. There's nothing in the Windows event logs, either.
If I sleep for 5 seconds between each test the problem goes away.
I installed the latest service pack (SP3a) for SQL Server 2000 with no change in behavior.
All of this leads me to believe that something is wrong with SQL Server. Has anyone else run into this problem? Any ideas?

I am not overly familiar with the SQL Server network architecture, but there are scenarios that could explain your intermittent failures.
When you connect to a database one of two things can happen, you can start your own process on the server that acts as communication to from the server locally, or you are put in a queue for a static (shared) process that does the same thing.
Assuming that most databases are initially setup with singular processes per connection, and you have established a connection then you disconnect from the database you do not automatically or instantly kill your process running on the server. There are two primary reasons for this as far as I know. First, the database puts more priority on doing something then doing nothing. Cleaning up and removing your process would be considered doing nothing, accepting incoming connections would be considered doing something. Second, the process may have to stay around to ensure all commit or rollback is completed properly (not always true in every database).
So, I would expect that there is a connection limit (perhaps between 50-80) that you are exceeding because you are firing these connections rapidly and even though you close the connection in your remote program, the database simply doesn't keep up. Most databases will "cleanup" reasonably quickly if they have the resources to do so, so if you were to put a 30 second delay between every connection it would probably work just fine. It would probably work fine if you put a 30 second delay between after every 20 connections too. It's a bit of balancing act.
There would be a couple of ways to alleviate this constraint. Putting in delays can demonstrate that this is in fact a work load problem (constrained by total count of connections), but doesn't really help in production instances. You can change the maximum number of connections allowed by the database, however this threshold may be caused by hardware resource (memory) limitations as much as it is a parameter in the database. You may have to add memory to accommodate this many connections. You may have to constrain how much memory each connection gets (again controlled by database parameters). You may have to accept this as a resource constraint and write your code accordingly. This often manifests itself by taking advantage of transaction managers (or transaction manager logic) that will queue up requests until database resources are available.
Again, I'm not a SQL Server expert, but I'm reasonably certain that most of what I said applies if not specifically at least generally.
Good Luck.

JDBC Communication channel : Error establishing socket

Dear friends,
Im using JDBC comm channel. JDBC driver has been insatlled for SQL Server 2000 (SP3) .
However for the JDBC comm. channel i get an error
"SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.'
following parameters are used :
JDBC driver: com.microsoft.jdbc.sqlserver.SQLServerDriver
DB connection :
jdbc:microsoft:sqlserver://<ip address>:1433;databaseName=<dbname>
i looked up some blogs in SDN, & tried some other options,
eg: com.microsoft.sqlserver.jdbc.SQLServerDriver
DB name:
jdbc:microsoft:sqlserver://<ip address>:1433;DatabaseName=<dbname>
However still get the same error
Can somebody help ?

Hi
The following should fix your problem
I had this problem using SQLServer 2000 Driver for JDBC and finally solved it. Here's what I did:
1. Make sure that SQL Server is set to mixed authentication. To do this, open enterprise manager, right click on server/properties; go to security tab and select SQL Server and Windows Authentication. Apparently, the driver from Microsoft cannot handle windows integrated authentication.
2. Keeping the server properties dialog up, go to the general tab and push the network configuration button. Enable TCP/IP (it is disabled by default). If you wish, press properties to change the default port (1433).
3. Add an SQL Server login account (NOT a WINDOWS account (see 1)). You can also use your sa account, but I don't recommend it.
4. Use the login setup in step 3.
Some final notes:
(1) I've seen ads for third party drivers that can use Windows integrated authentication. Try one if you need this feature.
(2) One responder suggested telneting to port 1433 to verify TCP connectivity. The connection is refused on my machine even though I can connect through the driver. And this is how it should be; otherwise there'd be a security risk.
Courtesy:XI installation Configuration of J2EE engine problem
Regards
krishna
Note:Reward points if helpful

Error in JDBC Adapter-"Error establishing socket"

Hi,
I am getting an error in the seander JDBC adapter. PFB the error:
Error during database connection to the database URL 'jdbc:microsoft:sqlserver://Server Name;DatabaseName=DB Name;SelectMethod=cursor' using the JDBC driver 'com.microsoft.jdbc.sqlserver.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://Server Name;DatabaseName=DB Name;SelectMethod=cursor': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.'
Can any one hlep me to resolve the error.
Thanks,
RK

Hi,
Also check whether you have given database connection parameters in the following format:
JDBC Driver:
com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection: jdbc:microsoft:sqlserver://<HOSTNAME>:1433;DatabaseName=<xxxx>;SelectMethod=cursor
I think the deployment is done, because you have not got "SAPClassNotFoundException" error.(If the deployment is not done, the driver file cant be located so this will be thrown...)
Thanks & Regards,
Senthil.

Error Establishing Socket jdbc

hello guys i have the problem of error establishing socket in tomacat 4.0.1 and i am using sqlserver 2000.My Application works well for n number of users but then application server hangs giving the "error establishing socket".
i am closing all the statements and i am calling connection object in init() and closing it in destoy(). And I am not using connection pooling.
please specify the changes needed to work with SQL server connection with jdbc
do help me guys its urgent for me
tell me as soon as possible.

hello guys i have the problem of error establishing
socket in tomacat 4.0.1 and i am using sqlserver
2000.My Application works well for n number of users
but then application server hangs giving the "error
establishing socket".
i am closing all the statements and i am calling
connection object in init() and closing it in
destoy(). And I am not using connection pooling.
please specify the changes needed to work with SQL
server connection with jdbc
do help me guys its urgent for me
tell me as soon as possible. sql server and windows are terrible under load. i know this from
personal experience ahving spent a great deal of time fixing an ASP site
that used ADO to access SQL Server 2000. what happens eventually with
windows and sql server is that when the server gets really busy the os
does not prioritize itself very well and you can run out of sockets
temporarily because even though you have programmtically released them
the operating system is still holding on to them.
part of the solution i used was to use pooled connections. i suggest the
same for you.

SQL Server 2000 Driver for JDBC - Error establishing sockets

Hi there
I am using Microsoft SQL Server 2000 Driver for JDBC to connect to SQL Sever 2000. It is just a test application to see if it would connect to the datacase successfully. But I got the following errors. I already set up the classpath and installed all SQL Server 2000 Driver for JDBC sp 3. Dont know why it still failed...can anyone help me out of this? Thanks.
When i am using simple JDBC-ODBC bridge Driver it's working fine.
For this Server Pack3 , i have checked every thing like--
TCP / IP Poart is Enable.
I am working in client machine, my MSSQLServer 2000 Placed in server Machine.
when i am giving Telnet ServerIP 1433 it's giving following response.
connecting to ServerIP ....... could not open connection to the host , on port 1433:connection Failed
My Sample Code is :--
String user="sa";
String password="imcindia";
Connection con1 = null;
CallableStatement cstmt = null;
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
con1=DriverManager.getConnection("jdbc:microsoft:sqlserver://ServerName:1433;DatabaseName=dmo1o2d",user,password);
Statement st=con1.createStatement();
st.execute("use dm0102d");
st.execute("setuser 'dm01012'");
cstmt = con1.prepareCall("{?=Call dms_ex_create_folder('ABC','18753','NB21','u')}");
cstmt.execute();
Here are Error Code :
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
 at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
 at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
 at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
 at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
 at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
 at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
 at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
 at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
 at java.sql.DriverManager.getConnection(Unknown Source)
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Connection refused: connect
 at java.sql.DriverManager.getConnection(Unknown Source)
 at TestConnection1.main(TestConnection1.java:24)
one can help me to over come this problm,
Thanks in advance.
venkat

hey i also have this problem i have been looking for solution for this problem for along time i tried every possible solution i tried every service pack for the SQL but it didn't connect to the port!!!
it's a network problem ur java code is correct dont worry about it.
finally i had to install MySQL and it's work fine now but if u insist on usning SQL u have to use the JDBC-ODBC Bridge it will work by :
first add data source database , follow these steps
1- go to Administrative tools
2-Data Sources(ODBC)
3-System DNS tab and add then choose SQL SERVER the last option then finish
4-write the name; Note: this name is the one that u will write in ur URL for example if u write Hello the URL will be "jdbc:odbc:Hello"
5- choose the server, its recommended to write "." or (local)
6-change the database to its an important step to choose the database that u want to use, choose northwind if u want to use it
finish
second
adding this code:
import java.sql.*;
class JdbcTest1 {
public static void main (String[] args) {
try {
// Step 1: Load the JDBC driver.
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
// Step 2: Establish the connection to the database.
String url = "jdbc:odbc:Hello";
Connection conn = DriverManager.getConnection(url,"user1","password");
} catch (Exception e) {
System.err.println("Got an exception! ");
System.err.println(e.getMessage());
it will work without any problems

Error establishing socket (Microsoft SQL Server 2000 Driver for JDBC)

I tray connect to MS-SQL2000 using JDeveloper and retrieve an error: "[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.[Microsoft][SQLServer 2000 Driver for JDBC]PC160832\NCI_DBA_01"
I followed the steps:
1 - Install the JDBC Driver for MS-SQL2000
2 - Create a new AddJavaLibPath :"AddJavaLibPath C:/Program files/Microsoft SQL Server 2000 Driver for JDBC/lib"
3 - Specify Default Project Libraries: "msbase.jar, msutil.jar and mssqlserver.jar"
4 - Create a new connection: "Java class name: com.microsoft.jdbc.sqlserver.SQLServerDriver" "URL: jdbc:microsoft:sqlserver://PC160832\NCI_DBA_01:1433;SelectMethod=cursor"
5 - Retrieve the error: "[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.[Microsoft][SQLServer 2000 Driver for JDBC]PC160832\NCI_DBA_01"

Were you able to resolve this? If so could you tell me how. I have the same problem.
Thanks!!!

JDBC Error Establishing Socket

Hi, I've a problem with my JDBC connection to the SQL Server Database in my Java file. I got a "Error Establishing Socket" problem when I tried to access a database in another server. Can someone tell me what are the possible causes?

firewall... server not running... etc etc

Error establishing socket. Address already in use

Running CFMX 6.1 on Win2k3, I just recently started getting
these errors from connections to one of our SQLServer database
servers (2000, enterprise):
quote:
Error Executing Database Query.[Macromedia][SQLServer JDBC
Driver]Error establishing socket. Address already in use: connect
Any ideas what might cause this?

ok. well, if you think that was useless, you might as well
not read on... this isnt a coldfusion error. it only appears that
way because you are using cfml. this is a most probably an SQL
issue. i say most probably, because there are many reasons this
could be happening. try doing things in these steps as they are in
degrees of harshness.
1. check the server event log, see if you have an entry like
this
'You are running a version of Microsoft SQL Server 2000 or
Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that
has known security vulnerabilities when used in conjunction with
the Microsoft Windows Server 2003 family. To reduce your computer's
vulnerability to certain virus attacks, the TCP/IP and UDP network
ports of Microsoft SQL Server 2000, MSDE, or both have been
disabled. To enable these ports, you must install a patch, or the
most recent service pack for Microsoft SQL Server 2000 or MSDE from
[L=http://www.microsoft.com/sql/downloads/default.asp]http://www.microsoft.com/sql/downlo ads/default.asp[/L]
[L=http://www.microsoft.com/sql/downloads/default.asp'</[/L]]http://www.microsoft.com/sql/downloads/default.asp'</[/L][/L]
install sp4
[L=http://www.microsoft.com/sql/downloads/2000/sp4.mspx]http://www.microsoft.com/sql/down loads/2000/sp4.mspx[/L]
2. change your database server name to its IP (if that doesnt
work, you might as well change it back)
3. make sure you are authenticating with an SQL account.
windows integrated authentication does not work well ... in your
SQL enterprise manager, set it to mixed authentication in the
security tab, select SQL server and windows authentication. the
microsoft driver seems to not handle the windows authentication
properly. i wouldnt use the the SA account, create another one just
for this purpose.
4. under the general tab in your enterprise manager click
network configuration. enable TCP/IP which is not enabled by
default
5. Install SQL Server 2000 sp3 or sp4
and here are some other useless articles you might want to
read...
Know bug in SQL Server preventing it from listening on port
1433
[L=http://support.microsoft.com/default.aspx?scid=kb;en-us;306865]http://support.microsoft .com/default.aspx?scid=kb;en-us;306865[/L]
[L=http://support.microsoft.com/default.aspx?scid=kb;en-us;329329]http://support.microsoft .com/default.aspx?scid=kb;en-us;329329[/L]
info on clustered SQL servers
[L=http://support.microsoft.com/default.aspx?scid=kb;en-us;815431]http://support.microsoft .com/default.aspx?scid=kb;en-us;815431[/L]

How do i fix "Error establishing socket" !!!

I get the following error:
SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
I have included the driver jar files in the classpath. How can i fix this?
Thank u all for your time

No.. That's not the real answer.Which one?
If it can't create the socket then something is interferring with the socket creation.
I'm getting the same problem trying to connect to an
MSSQLServer box from JDBC.
I believe that my connect string is fine, as I use
jdbc on many databases - SWLServer being the only one
I can't connect to. Both machines are using TCP/IP,
and the server is accepting TCP/IP connections on port
1433. My connect URL is:
jdbc:microsoft:sqlserver://DBHOST:1433
This works on an NT box. This doesn't work on my
linux box.
I've attempted to use the IP address of the database
in the connect string, but that only produces a
different error from the driver "INVALID URL"
The only way I have been able to get this to work is
by bypassing JDBC and using the JDBC/ODBC bridge,
which STINKS. There must be a better answer.
Nope, don't think so. You said it doesn't work on linux. Are you claiming that you have a MS SQL Server ODBC driver for linux? If so you need to share it with the world.
Can you ping the SQL server box from your linux box? Can you telnet to the 1433 port (that tells you if it is open from the linux box.)
Presumably the SQL Server was NOT installed with NT authorization. Rather it was installed with Database authorization.

Error establishing socket

I have an applet which Dynamically builds and updates a JTree. I have signed this applet with a Thawte Certificate and I runs great on our intranet. When I try to access the applet from the Internet I get an error:
java.SQL.SQLException: [MERANT][SQLServer JDBC Driver]: Error establishing socket
I am using Merant's type 4 JDBC driver. Any suggestions????

Make sure the port is open for the applet to talk. Look into the permissions or Browser Settings.

AttachToDocument - Error establishing socket.

I'm encountering a problem where the calls to attachToDocument are generating SQLExceptions (CWS in Java for 4.5WS). It's a strange error that I am unfamiliar with. Please advise on how to fix this. Here is the complete stack trace:
java.sql.SQLException: Pool connect failed : weblogic.common.ResourceException:
0:Could not create pool connection. The DBMS driver exception was: [BEA][SQLServ
er JDBC Driver]Error establishing socket. Too many open files - with nested exce
ption:
[weblogic.common.ResourceException: Could not create pool connection. The DBMS d
river exception was: [BEA][SQLServer JDBC Driver]Error establishing socket. Too
many open files]
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(
JDBCUtil.java:160)
at weblogic.jdbc.pool.Driver.connect(Driver.java:155)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:444)
at weblogic.jdbc.jts.Driver.connect(Driver.java:138)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:298)
at com.ml.mlim.enterprise.common.util.MCServiceLocator.getDBConn(MCServi
ceLocator.java:183)
at com.ml.mlim.marketing.estudio.cws.DocumentProvider.connect(Unknown So
urce)
at com.ml.mlim.marketing.estudio.cws.DocumentProvider.getConnection(Unkn
own Source)
at com.ml.mlim.marketing.estudio.cws.DocumentProvider.initialize(Unknown
Source)
at com.plumtree.remote.crawler.NativeDocumentProvider.Initialize(NativeD
ocumentProvider.java:47)
at com.plumtree.remote.crawler.xp.XPDocumentProvider.Initialize(XPDocume
ntProvider.java:62)
at com.plumtree.remote.crawler.soap.DocumentProviderSoapBindingImpl.Init
ialize(DocumentProviderSoapBindingImpl.java:73)
at com.plumtree.remote.crawler.soap.DocumentProviderSoapBindingSkeleton.
Initialize(DocumentProviderSoapBindingSkeleton.java:150)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.j
ava:402)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider
.java:309)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:
333)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:481
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:323)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:85
4)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:387)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6310)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3622)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

This is happening because you are running out of file descriptors. You can see how many file descriptors you have open by using the following command:
lsof -p<process id of your JVM>
Cause: you might have a file descriptor leak. The oracle OCI driver is known to have this type of issue! You must find out what is causing this leak. Or if you are not closing your connections. Use the lsof command to monitor your file descriptors and try to isolate the leak.
Fix: Increase the number of file descriptor to 4096 if you still run out you must restart the process to rest them to 0. If you have a leak you must address it if not it could be a case of you application just needing more desciptors.
Email me if you want to talk more:
[email protected]

Error Establishing Socket with SQL Server 2000

I have a java application that uses JDBC to connect to a source of data.
The application has been installed on many platforms using many different data sources, but one combination has beaten me.
I am using Windows Server 2003 and SQL Server 2000 Enterprise, when the application starts up it fails to connect to the database with the following message:
[Microsoft][SQL Server 2000 Driver for JDBC] Error Establishing Socket
I have looked at a lot of forums and tried many things but nothing has fixed the problem for me:
To summarise:
The URL I am using is jdbc:microsoft:sqlserver://locahost:1433
I have also tried using the name of the machine and it's actual IP address
I have checked that TCP/IP is enabled and using the correct port (1433)
Both SQL Server and Windows authentication are enabled and I can connect using both method from ODBC
I can connect to it and use it with c#.net, vb.net and ODBC from the same machine
I have installed the latest SQL Server 2000 service pack
The application works with SQL Server 2000 Developer on Windows XP
If anyone has any other suggestions, I would love to hear from you.

If you printed out the SQL state and error code that would be a bit more info:
catch (SQLException e)
    e.printStackTrace();
    System.err.println("SQL state: " + e.getSQLState());
    System.err.println("SQL error: " + e.getErrorCode());
}Maybe that will give you more detail as to exactly why this is happening.
The only other thought I had was security. Maybe there's a permission to access the port that would have to be granted explicitly as part of M$'s new emphasis on security. You did say it was Windoze Server 2003. Maybe that's the difference between all the other installs and this one.
No joy from me, sorry. - MOD

"Error establishing socket" error on JDBC Receiver Channel.

Similar Messages

Maybe you are looking for