JDBC MySQL driver problem

[Former Member]

Hi guys,

I'm working on XI but I have a question you might know the answer...I've been at the XI forum and they suggested that you guys may know the answer to my problem.

I'm having trouble with the JDBC MYSQL driver...I have already gone through the "How To Install and Configure External Drivers for JDBC & JMS Adapters" and placed the .jar and zipped the aii.af.jmsproviderlib.sda and ran the deploy. I have already created the driver at the VA->server->JDBC Connector.

But I'm having the following error:

Receiver Adapter v1027 for Party '', Service 'GV_LEGACY_BS_SQLSERVER':

Configured at 18:10:58 2005-11-16

Processing Error: Accessing database connection 'jdbc:mysql://localhost:3306/gvxi_ex02' 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:284)

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

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

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

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

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

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.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:440)

at com.sap.engine.frame.core.thread.Task.run(Task.java:60)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)

• 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:

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

Do you have any ideas...?

[gregorw]

Hello Gonçalo,

perhaps you can't connecto to MySQL because it does not have transactions. Have a look at this toppic: /thread/41500 .

Regards

Gregor

[detlev_beutner]

Hi Gonçalo,

are you sure about your mySQL server awaiting connections on port 3306 on your localhost?!

From the stack trace, this minimum requirement doesn't seem to be fulfilled...

Hope it helps

Detlev