Re: [jira] Created: (SM-742) JdbcAuditor fails on JBoss

[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.