what's wrong with this my-ds.xml?

[m.ardito]

the file is in the <jboss>/server/default/deploy dir

and is named my-ds.xml

====================================

<?xml version="1.0" encoding="UTF-8"?>
<datasources>
    <local-tx-datasource>
        <jndi-name>MyDS</jndi-name>
        <connection-url>jdbc:mysql://192.168.3.8:3306/phpscheduleit_test</connection-url>
        <driver-class>com.mysql.jdbc.Driver</driver-class>
        <user-name>phpScheduleIt</user-name>
        <password>xxxxxxxxx</password>
    </local-tx-datasource>
</datasources>

====================================

in <jboss>/server/default/lib i have

mysql-connector-java-5.1.13-bin.jar

from the shell i can connect to with the mysql client and the same parameters, so, why it is always DOWN?

<grrrr... :-) >

Marco

[rareddy]

Marco,

That looks right. Using SquirreL, can make connection to MySQL using the URL "jdbc:mysql://192.168.3.8:3306/phpscheduleit_test"?

Ramesh..

[m.ardito]

yes, i can, using same user/pass, see attachments.

in every way I try, it seems my teiid datasource to be quite strange...

and shows no data, just schemas/structures as tables

but i just followed the quickstart examples...

from the jboss screenshot, you can see the myds is DOWN (edit: it is in state UNKNOWN, not DOWN, but jboss shows the same "red x" icon as if it waqs DOWN, end despite the UNKNOWN status it is really working, i can use it in a VDB and i can connect to the mysql tables through the odbc intercace in msaccess...)

M

[rareddy]

Marco,

The data source is a artifact of JBoss AS, that Teiid uses as source connection for its use. In my experience, when you specify the following xml in the "xxx-ds.xml" file

<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>

it checks to make sure correctly if the connection is valid connection or not.

The switch between your "IP" and "localhost" can be possible if you were on LAN vs home network, it really depends upon how Derby resolves the hostname at the startup. JBoss AS always starts on "localhost" or "127.0.0.1" if you did not specify the IP with "run.sh -b <ip>" option.

Hope this helps.

Ramesh..