You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Frank Trietsch (JIRA)" <ji...@apache.org> on 2006/11/09 21:56:02 UTC
[jira] Created: (SM-742) JdbcAuditor fails on JBoss
JdbcAuditor fails on JBoss
--------------------------
Key: SM-742
URL: https://issues.apache.org/activemq/browse/SM-742
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.1
Environment: JBoss 4.0.4.GA, SM 3.x (all Versions affected)
Reporter: Frank Trietsch
Priority: Minor
The JdbcAuditor handles JDBC connections in a way which does not work correctly inside JBoss, not dependent on the kind of datasource being used. This is due to explicit calls to Connection.commit().
a) Transactional datasources
When using transactional datasources inside a transactional context, all subsequent calls to DataSource.getConnection() create a managed connection. Explicit calls to commit() are not allowed on them.
b) Non-transactional datasources
In JBoss, non-tx datasources are created with autocommit by default. So calls to commit() are not allowed to them either.
Using non-tx datasources and changing the JdbcAuditor to call setAutoCommit(false) on all connections worked for me. Would be great if you can apply that to the original code.
Cheers,
Frank
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (SM-742) JdbcAuditor fails on JBoss
Posted by delkant <ro...@t-systems.es>.
Hi guys,
I hope you can help me.
After use (start the service with a JMX-console ) the jdbcAuditor on
servicemix-3.2.1 standalone version, i'm now trying to find the way to get
this service enable on Jboss 4.0.5-GA plus jboss-deployer-3.2.1.sar. My try
was to put (manually) the servicemix-audit.jar in to the lib directory
inside the jboss-deployer.sar. There is no error in the jboss log, but i
have not results at all after test the examples (also succefully deployed,
like the wsdl-fist-sa).
I'm trying to save data in a mysql db by creating and copy my binding-sm.xml
in the jboss deploy directory, this file has a very simple content:
<sm:container id="jbi" useMBeanServer="false" createMBeanServer="false">
<sm:activationSpecs>
<Empty config to test >
</sm:activationSpecs>
</sm:container>
and
<audit:jdbcAuditor container="#jbi" autoStart="true">
<audit:dataSource>
<bean class="com.mysql.jdbc.jdbc2.optional.MysqlDataSource">
<property name="databaseName" value="servicemixDB" />
<property name="user" value="user" />
<property name="password" value="secret" />
</bean>
</audit:dataSource>
</audit:jdbcAuditor>
but i have not results!!, no errors, just nothing.., do i have to do a
special configuration or put the jar in another place?
Where i can find documentation about how to have the JdbcAuditor working on
Jboss+servicemix?
(My born languaje is the spanish, sory for the errors)
Thank you,
delkant.
JIRA jira@apache.org wrote:
>
> JdbcAuditor fails on JBoss
> --------------------------
>
> Key: SM-742
> URL: https://issues.apache.org/activemq/browse/SM-742
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.1
> Environment: JBoss 4.0.4.GA, SM 3.x (all Versions affected)
> Reporter: Frank Trietsch
> Priority: Minor
>
>
> The JdbcAuditor handles JDBC connections in a way which does not work
> correctly inside JBoss, not dependent on the kind of datasource being
> used. This is due to explicit calls to Connection.commit().
>
> a) Transactional datasources
> When using transactional datasources inside a transactional context, all
> subsequent calls to DataSource.getConnection() create a managed
> connection. Explicit calls to commit() are not allowed on them.
>
> b) Non-transactional datasources
> In JBoss, non-tx datasources are created with autocommit by default. So
> calls to commit() are not allowed to them either.
>
> Using non-tx datasources and changing the JdbcAuditor to call
> setAutoCommit(false) on all connections worked for me. Would be great if
> you can apply that to the original code.
>
> Cheers,
>
> Frank
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> https://issues.apache.org/activemq/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
>
--
View this message in context: http://www.nabble.com/-jira--Created%3A-%28SM-742%29-JdbcAuditor-fails-on-JBoss-tp7266082p19861202.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Resolved: (SM-742) JdbcAuditor fails on JBoss
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-742?page=all ]
Guillaume Nodet resolved SM-742.
--------------------------------
Fix Version/s: 3.1
Resolution: Fixed
Assignee: Guillaume Nodet
Author: gnodet
Date: Thu Dec 28 13:22:26 2006
New Revision: 490828
URL: http://svn.apache.org/viewvc?view=rev&rev=490828
Log:
SM-742: Need to explicitely set autoCommit to false
Modified:
incubator/servicemix/trunk/core/servicemix-audit/src/main/java/org/apache/servicemix/jbi/audit/jdbc/JdbcAuditor.java
incubator/servicemix/trunk/core/servicemix-services/src/main/java/org/apache/servicemix/jdbc/adapter/DefaultJDBCAdapter.java
incubator/servicemix/trunk/core/servicemix-services/src/main/java/org/apache/servicemix/store/jdbc/JdbcStore.java
> JdbcAuditor fails on JBoss
> --------------------------
>
> Key: SM-742
> URL: https://issues.apache.org/activemq/browse/SM-742
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.1
> Environment: JBoss 4.0.4.GA, SM 3.x (all Versions affected)
> Reporter: Frank Trietsch
> Assigned To: Guillaume Nodet
> Priority: Minor
> Fix For: 3.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> The JdbcAuditor handles JDBC connections in a way which does not work correctly inside JBoss, not dependent on the kind of datasource being used. This is due to explicit calls to Connection.commit().
> a) Transactional datasources
> When using transactional datasources inside a transactional context, all subsequent calls to DataSource.getConnection() create a managed connection. Explicit calls to commit() are not allowed on them.
> b) Non-transactional datasources
> In JBoss, non-tx datasources are created with autocommit by default. So calls to commit() are not allowed to them either.
> Using non-tx datasources and changing the JdbcAuditor to call setAutoCommit(false) on all connections worked for me. Would be great if you can apply that to the original code.
> Cheers,
> Frank
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira