What's wrong with jboss3.2.1?

[yjyang]

I used the jboss3.0.6 ago,But today I changed it to jboss3.2.1. I don't know what's wrong with jboss3.2.1.And I run the program which is well on jboss3.0.6,but it occurs error on jboss3.2.1.
Who can tell me what i should do? Thanks

Now is a simple program.But when i deploy it ,it error:
); - nested throwable:(org.jboss.resource.JBossResourceException: Could not cre
ate connection; - nested throwable: (java.sql.SQLException: ERROR: Option 'xact
isolevel' is not recognized
)))
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:68)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBCEnt
ityBridge.java:119)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBC
StoreManager.java:438)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManage
r.java:372)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManag
er.java:170)
at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:339)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)

[jonlee]

If you are using Postgresql as the back-end database, it means there is an incompatibility between the back-end database and the JDBC driver. I can't remember which way it went but it is either that the new drivers don't match the old back-end interface or vice-versa. I think the newer drivers are incompatible with the older Postgresql interface, hence doesn't support the isolevel option in the connection establishment.

[yjyang]

Thanks.
But why the driver has not any errors when i use the jboss3.0.6?
And can you give me an example for configuration?

Thanks.

[jonlee]

I think the pools are more exacting in the connection process to better handle events such as the database or network connection bouncing - and the isolevels were not introduced until the either 7.2 or 7.3. In any event, we use Postgresql 7.3 in Cygwin and Linux with pg73jdbc3.jar without any issues.

The postgres-ds.xml in docs/jca/examples is an operational definition. I give an ECperf 1.1 definition below.

<?xml version="1.0" encoding="UTF-8"?>

<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->

<!-- $Id: postgres-ds.xml,v 1.1 2002/07/22 22:57:24 d_jencks Exp $ -->
<!-- ==================================================================== -->
<!-- Datasource config for Postgres -->
<!-- ==================================================================== -->



<local-tx-datasource>
<jndi-name>CorpDataSource</jndi-name>
<connection-url>jdbc:postgresql://localhost:5432/ecperf</connection-url>
<driver-class>org.postgresql.Driver</driver-class>
<user-name>x</user-name>
y
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</local-tx-datasource>

[yjyang]

Thanks jonlee.

I have understood what you said.

Thanks.