Legacy-XI-MySQL

[Former Member]

Hi Friends

I have a problem in JDBC Receiver adapter while connecting to MySQL. The Adapter Monitoring in RWB shows me the error.

<b>Receiver Adapter v1109 for Party '', Service 'ORACLE_SERVER_BS':

Configured at 12:35:34 2006-01-10

Processing Error: Accessing database connection 'jdbc:mysql://172.25.5.127:3306/MYSQL' failed: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:

• BEGIN NESTED EXCEPTION **

java.net.SocketException

MESSAGE: java.net.ConnectException: Connection refused: connect

STACKTRACE:

java.net.SocketException: java.net.ConnectException: Connection refused: connect

at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)

at com.mysql.jdbc.MysqlIO.(MysqlIO.java:283)

at com.mysql.jdbc.Connection.createNewIO(Connection.java:2541)

at com.mysql.jdbc.Connection.(Connection.java:1474)

at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:264)

at java.sql.DriverManager.getConnection(DriverManager.java:512)

at java.sql.DriverManager.getConnection(DriverManager.java:171)

at com.sap.aii.adapter.jdbc.XI2JDBC.connectDB(XI2JDBC.java:637)

at com.sap.aii.adapter.jdbc.XI2JDBC.init(XI2JDBC.java:595)

at com.sap.aii.adapter.jdbc.AdminAdapter.addAdapter(AdminAdapter.java:99)

at com.sap.aii.adapter.jdbc.AdminAdapter.addAdapter(AdminAdapter.java:73)

at com.sap.aii.adapter.jdbc.AdminAdapter.channelAdded(AdminAdapter.java:171)

at com.sap.aii.af.service.cpa.impl.callback.CallbackManager.performChannelCallback(CallbackManager.java:217)

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endDocument(DirectoryDataSAXHandler.java:1136)

at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endDocument(SAXDocHandler.java:236)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:126)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:136)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:209)

at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:270)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:331)

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:54)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:713)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:595)

at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.process(CacheRefresh.java:104)

at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.doGet(CacheRefresh.java:53)

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:385)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

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)

• END NESTED EXCEPTION **

Last packet sent to the server was 0 ms ago.

Addtional information: JDBC driver 'com.mysql.jdbc.Driver' loaded successfully, additional driver information:

Available JDBC drivers:

oracle.jdbc.driver.OracleDriver, 1.0 JDBC compliant

com.mysql.jdbc.Driver, 3.1 NOT JDBC compliant

sun.jdbc.odbc.JdbcOdbcDriver, 2.1 JDBC compliant</b>

What could be the reason for this. This scenario was working fine some days before but now it gives an error. Can anyone please help me.

Thanks in Advance.

[former_member91687 · Accepted solution]

Hi Raju,

You can check the following thread.

Cheers,

Chandra

[Former Member · Accepted solution]

Hi,

Do you have a firewall configured in your place , let me know if you can ping your server.

I am not sure but one of the reason may be a firewall issue.

And Also

Make sure the port is correct as well as the host as to what you are trying to connect to.

Please check,

Anirban.

[former_member184154 · Accepted solution]

Almost everything was suggested already.

Basically:

1- go to the Mysql box and check port 3306 is the real one being used (also try "telnet <mysqlhost> 3306" from your PC, should go to black screen)

2- go to the XI box (either telnet, WTS, pcanywhere, etc) and try "telnet <mysqlhost> 3306", should go to black screen

If port 3306 is correct but you can't telnet from XI box, then check your firewall allows incoming connections on 3306 for mysql box.

[Former Member]

Hi Raju,

Please go through these blogs. You will find them useful

/people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter

/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures

/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30

regards,

Prashanth