Doh, It looks like we have gone to far in reducing the excessive
exception reporting.
You could try turing up the logging in the log4j.xml file. It has
examples and good comments.
If you can't figure it out, post a bug report at sourceforge and I'll
take a look at it.
-dain
Brandon Knitter wrote:
> I'm tailing server.log, the only thing showing up during my request is:
>
>
> 2002-06-06 22:05:51,731 DEBUG
> [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using
> properties: {user=ejukebox, password=xxxxxxxxxx}
> 2002-06-06 22:05:51,823 DEBUG
>
>[org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQuery.PlaylistBean.findByPrimaryKey]
> Executing SQL: SELECT playlist_id FROM playlists WHERE playlist_id=?
> 2002-06-06 22:05:52,145 DEBUG
> [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.PlaylistBean] Executing
> SQL: SELECT user_id, name, user FROM playlists WHERE (playlist_id=?)
>
> Which looks about right for a prepared statement...any ideas? Is there a way to
> turn up vebosity?
>
>
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
