MQSeries.net :: View topic - Java Compute Node Transactions(Commit boundaries)

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Java Compute Node Transactions(Commit boundaries)

Java Compute Node Transactions(Commit boundaries)

« View previous topic :: View next topic »

Author

Message

tillywern

Posted: Tue Dec 23, 2008 11:41 am Post subject: Java Compute Node Transactions(Commit boundaries)

Centurion

Joined: 28 Jan 2003
Posts: 109
Location: Colorado

Ok so we are running 6.1.0.2 and working with Java compute nodes. We have implemented a connection to Oracle with the Class4JDBCDriver. Trouble is that when we start running transactions in, they don't ever seem to get committed.

We are not using XA so I don't need to discuss that.
Checked to ensure starting MQInput node Transaction was set to Automatic. Same with every other node in the flow including the MQOutput.

We know that the database has the data because running the same transaction in more than once generates a unique constraint violation. However, other applications looking at the tables can't see the data.

Is there something else I missed?

Last edited by tillywern on Tue Dec 23, 2008 12:09 pm; edited 1 time in total

mqjeff

Posted: Tue Dec 23, 2008 11:55 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

I know you're not using XA, but the doc for 6.1.0.3 specifically says that type4DatasourceClassName must reference the XA classname.

Also, have the DBA confirm if the transactions are committed...

tillywern

Posted: Tue Dec 23, 2008 12:05 pm Post subject:

Centurion

Joined: 28 Jan 2003
Posts: 109
Location: Colorado

Here are the properties that are set up. Based on what you said I think I am still ok. We tried to use the XA stuff as well but we haven't set up a single transaction coordinator so it failed with the MQBEGIN. We can easily see that in the logs. What we don't see in the logs is any output indicating any problem with committing message data to the database when we are running without XA. They all process just fine and get committed to MQ on the back side. So it looks like the commit takes place from an MQ perspective but the JDBC connection just doesn't seem to affected by it.

[wmqi@wbidev-vm VMBRK]$ mqsireportproperties VMBRK -c JDBCProviders -o OracleC -r

JDBCProviders
OracleC
connectionUrlFormat='jdbc:oracle:thin:[user]/[password]@[serverName]:[portNumber]:[connectionUrlFormatAttr1]'
connectionUrlFormatAttr1='DEVFH1'
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='DEVFH1'
databaseType='Oracle'
databaseVersion='default_Database_Version'
description='default_Description'
jarsURL='/opt/oracle/client/10.2.0/client_1/jdbc/lib'
portNumber='1521'
securityIdentity='dat_user'
serverName='myserver.mydomain.com'
type4DatasourceClassName='oracle.jdbc.xa.client.OracleXADataSource'
type4DriverClassName='oracle.jdbc.OracleDriver'

BIP8071I: Successful command completion.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Java Compute Node Transactions(Commit boundaries)

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP