jdbc adapter...driver error...

[Former Member]

Hi guys,

I'm having a tiny little trouble with the JDBC adapter.

I'm trying to create a FILE-XI-JDBC scenario and the db is supported by MySQL-server.

I've 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. Everything went ok but when I go to the adapter monitoring i get the error:

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

Configured at 16:32:35 2005-11-16

Processing Error: Accessing database connection 'jdbc:mysql://localhost:3306;DatabaseName=gvxi_ex02' failed: java.sql.SQLException: No suitable driver

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

any ideas? Not jdbc compliant...?

[Former Member]

ok guys...my mistake....

but now I'm having the most common 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

I've searched the web, it's a common error, but so common I couldn't find the answer...ANYone???

[Former Member]

Hi Goncalo,

Check your connection string. Try this format:

jdbc:microsoft:sqlserver://<host>:<port>

(notice the microsoft)

bregards,

cedric

[Former Member]

Cedric,

That connection string is meant only for microsoft sql servers, I'm using MySQL...

But thanks for the tip, i'm completely lost with this problem....

Anyone?

[Former Member]

yes indeed. MySQL & SQLServer always confuse me

Did you try using the driver to connect to the DB from another app? (e.g. some simple Java app).

[Former Member]

I was able to connect to the database from another app, this must be a badly SAP config...

From any other app I can connect, query it, insert values...

Do i need to create any connection on the xi server?...or opening any port, maybe the port MySQL uses, 3306? I've looked to the XI server and I don't think it's needed....

Like I said I've uploaded the connector to the SDM, has anyone tried to use a MySQL database?

Can anyone answer it....?

[Former Member]

Hi Goncalo,

Last try :

Ports 33xx are used in SAP for defining "SAP System Gateway Central Instance Ports".

E.g. sapgw06 = tcp/ip port 3306 (= your port for MySQL)

This might lead to confusion on the WAS. Maybe the range 33xx is a reserved range. Just guessing here.

Try posting your question on the WAS forum.

[Former Member]

Hi Goncalo

Couple of suggestions, hope it helps.

Try passing ip instead of localhost.

If you are on WinXP try disabling the firewall settings.

Also check the if the following thread helps,

cheers

sameer

PS: Do award points if the answers were helpful.