cancel
Showing results for 
Search instead for 
Did you mean: 

Strange JDBC Error

Former Member
0 Kudos

Hi Gurus,

We are observing the strange issue for our JDBC connection to one of our end DB system

The design is for matmas, 1 idoc can be send to 1 or more of the 4 DB systems.

while sending the master data, 1 of the DB system shows below error:

'JDBC:microsoft:sqlserver://<host>;DatabaseName=<db>': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket..

Out of 22 messages to be sent to this system, 16 were successfully processed.

others failed with error above

note that telnet to port 1433 was always working fine.

when the failed messages are resent it fails again.

note that PI is cluster environment. there is a firewall between the PI and db and ports are already opened.

regards,

Anirudh.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Anirudh,

This error basically means JDBC driver found the socket which was dead while it was trying to write through it.

The reasons for this could be either network broke the socket between the driver and the DBMS, or the DBMS had a failure which required it to terminate the connection abruptly.

Please check the DBMS error logs to see if there are any messages about killing a session.

One more thing you might want to look at are any timeout settings on network hardware/software between your DBMS and XI system where JDBC adapter is running.

Also, may be the DBMS has an idle connection timeout, and is closing connections because of time-out.

DBMS error log would probably help in his case. If you are not able to analyze DBMS logs, then contact DB administrator or DB vendors who supplied JDBC driver to you.

Regds,

Pinangshuk.

Former Member
0 Kudos

Hi All,

This issue was resolved by deplying the latest version of JDBC driver as per SAP's recommendation

regards,

Anirudh

abhijitbolakhe
Advisor
Advisor
0 Kudos

Hi

This may be due to JDBC service problem.

Go to Visual Admin> server> JDBC adapter service. Right click on that STOP and then START the service.

Regards

Abhijit

Former Member
0 Kudos

it seems that this is happening due to error at the time of opening port,

check your firewall logs , trace.check maximum parallel connection allowed.

Edited by: NetWeaver Expert on Sep 14, 2009 9:00 AM

Former Member
0 Kudos

Hi,

We have got firewall checked and DB is working fine.

We have now started getting this error for other JDBC systems also.

Regards,

Anirudh

Former Member
0 Kudos

Did you checked is there any problem with the database during that time of message processing?

Rajesh

Former Member
0 Kudos

hi,

this is production database and there were no issues during this time.

regards,

Anirudh