0 Replies Latest reply on Mar 4, 2004 11:44 PM by Dave Kohr

    how do you configure logging for a datasource?

    Dave Kohr Newbie

      I'm trying to upgrade my JBoss from 3.0.6 to 3.2.3, and having
      problems with a few (but not all) of our EJB's. I'm using the
      MS SQLSERVER2000 datasource, with JBoss and the database running
      on the same Windows 2000 host.

      I am beginning to think that something in the EJB implementation has
      changed, but the error messages at the default logging levels aren't
      giving me enough detail to figure out what (see below).

      So I'd like to know how to configure logging for a datasource, in
      particular how to increase the logging level for both the JDBC driver
      (we are using Opta2000.jar from TDS) and the JBoss parts of JDBC
      and EJB. I have already turned on debug mode in mssql-ds.xml,
      but that doesn't seem to have any effect. I'm using the default log4j.xml right now, I'm not sure which categories the JDBC and EJB stuff are in.

      The error messages I'm getting are just stacktraces from exceptions, like this one:

      2004-03-04 20:24:27,764 WARN [org.jboss.system.ServiceController] Problem starting service jboss.j2ee:jndiName=dataLayer/DBRestoreH,service=EJB
      at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.loadLoadGroups(JDBCEntityBridge.java:977)
      at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.resolveRelationships(JDBCEntityBridge.java:290)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.resolveRelationships(JDBCStoreManager.java:445)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:379)
      at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:152)
      at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:342)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      [lots of stuff deleted]

      Thanks for any advice you can offer,