WL7.0 ignores connection properties

Question

I'm trying to use the Sybase XA driver with WL7.0 and can't seem to get all
of the connection properties passed on to the driver. Specifically, I need
to have the CHARSET=iso_1 set in order to connect to the server. The
properties string looks like this:
DriverName="com.sybase.jdbc2.jdbc.SybXADataSource"
Properties="url=jdbc:sybase:Tds:sfohp7:5055;
NetworkProtocol=Tds;
DatabaseName=theDatabaseName;
dataSourceName=jtaXAPool;
user=theuser;
CHARSET=iso_1;
PortNumber=5055;
password=welcome;
ServerName=ipaddress"
I have a test program which uses the XA driver and can successfully connect
when given the CHARSET property, and which fails without. This would seem to
verify that the XA driver will respect this property. However, specifying
this property in the above connect string for WL7.0 has no effect, causing
the following exception:
<Jun 10, 2002 12:52:33 PM EDT> <Error> <JDBC> <001060> <Cannot startup
connection pool "jtaXAPool" weblogic.common.ResourceException:
weblogic.common.ResourceException: java.sql.SQLException: JZ006: Caught
IOException: java.io.IOException: JZ0I6: An error occured converting UNICODE
to the charset used by the server. Error message:
java.io.CharConversionException: java.io.UnsupportedEncodingException:
hp-roman8
The same CHARSET property passed to the non-XA sybase driver DOES remedy
this problem. I can't figure out why Weblogic would pick and choose which
properties to send to the driver, but I can't explain why my sample program
can connect fine using the same connection string. Any suggestions would be
greatly appreciated.
-Aaron

Answer 1

Fei,
Attached is my test program (hopefully, it will attach correctly...if not
here is the snippet of connection code). This came from a Sybase rep while
we were trying to validate the DTM/XA configuration was correct on the
server. The relevant connection code reads:
<-------snip------------>
com.sybase.jdbcx.SybDataSource sds = new
com.sybase.jdbc2.jdbc.SybXADataSource();
sds.setServerName(SERVERHOST);
sds.setPortNumber(SERVERPORT);
Properties props = new Properties();
props.put("user", USER);
props.put("password", PASSWORD);
props.put("CHARSET", "iso_1");
sds.setConnectionProperties(props);
//... etc... and connection properties also go here.
// -- this is equivalent to getting the
// XADataSource back from JNDI, a la
// XADataSource sds = (XADataSource) ctx.lookup(...);
// downcast to expose the getXAConnection method
// let's use a couple different xa connections to make things
// more complicated
xaconn1 = ((XADataSource)sds).getXAConnection();
<------snip-------------->
If I remove the props.put("CHARSET", "iso_1") from my test program, it fails
with the UnsupportedEncodingException as expected. However, adding this
CHARSET to the Properties in the connection pool does not seem to fix the
same issue within Weblogic.
Thanks for taking a look..
-Aaron
"Fei Luo" <[email protected]> wrote in message
news:[email protected]...
>
Aaron,
Could you please attach your test program that works? Thanks.
"Aaron" <[email protected]> wrote:
I'm trying to use the Sybase XA driver with WL7.0 and can't seem to get
all
of the connection properties passed on to the driver. Specifically, I
need
to have the CHARSET=iso_1 set in order to connect to the server. The
properties string looks like this:
DriverName="com.sybase.jdbc2.jdbc.SybXADataSource"
Properties="url=jdbc:sybase:Tds:sfohp7:5055;
NetworkProtocol=Tds;
DatabaseName=theDatabaseName;
dataSourceName=jtaXAPool;
user=theuser;
CHARSET=iso_1;
PortNumber=5055;
password=welcome;
ServerName=ipaddress"
I have a test program which uses the XA driver and can successfullyconnect
when given the CHARSET property, and which fails without. This would seem
to
verify that the XA driver will respect this property. However, specifying
this property in the above connect string for WL7.0 has no effect,causing
the following exception:
<Jun 10, 2002 12:52:33 PM EDT> <Error> <JDBC> <001060> <Cannot startup
connection pool "jtaXAPool" weblogic.common.ResourceException:
weblogic.common.ResourceException: java.sql.SQLException: JZ006: Caught
IOException: java.io.IOException: JZ0I6: An error occured convertingUNICODE
to the charset used by the server. Error message:
java.io.CharConversionException: java.io.UnsupportedEncodingException:
hp-roman8
The same CHARSET property passed to the non-XA sybase driver DOES remedy
this problem. I can't figure out why Weblogic would pick and choose which
properties to send to the driver, but I can't explain why my sampleprogram
can connect fine using the same connection string. Any suggestions would
be
greatly appreciated.
-Aaron
[SimpleDtmTest.java]