Tom,
FINE logging gives you too many messages that you need to parse to get to
the actual SQL. In CMP we added a special sublogger to log generated SQL
only (both, the users and our SQEs were asking for it).
Adam,
I don't see a reason for p6spy not to work with glassfish. Can you try and
let us know (blog?) how well does it work? If you encounter any issues that
you think are glassfish bugs, file the corresponding issue. Glassfish
connection pooling wraps the actual database connections, but it shouldn't
cause any problems.
Thanks,
-marina
Tom Ware wrote:
> Hi Adam,
>
> Alot of this information can be made visible when using the persistence
> API just by increasing the logging level.
>
> When using the Java Persistence API, you can just provide the
> "toplink.logging.level" property in your persistence unit and set the
> value to FINE and you should be able to see all the SQL including the
> binding variables. I am not sure if that will completely satisfy your
> requirement, but perhaps it will help.
>
> -Tom
>
> Adam Bien wrote:
>
>> In the past a used p6spy to log all SQL statements to a file for
>> debugging purposes. P6spy even writes the value of binding variables
>> (the ? in prepared statements)
>> Is it possible to do the same with glassfish? -> this would be a great
>> feature and help to monitor caching behavior and monitoring,
>>
>> cheers,
>>
>> adam bien
>>
>>