Tuesday, December 27, 2011

configure/Enable JDBC profiler

Hi Everyone,

Today we will discuss about one of diagnostic module which help us in diagnosing issues JDBC profiler is one of them.

I have come across the issue of increasing inactive session issues on Database level with weblogic server, we have found on DB level that all inactive connections are from weblogic server.
It gives SQL query as select * from dual. ( we have weblogic server in host level cluster mode with Oracle RAC 11g)

We have discussed with oracle support for the same, they suggest us to enable JDBC profiler in weblogic Node1 and Node2.

Following are the steps to configure/Enable JDBC profiler :


Step 1: Click on Diagnostics-->Diagnostic Modules

Step 2: Click on new and provide name of the module. for e.g ProfilerModule

Step 3: Once Module-0 is created. Click on it. It'll lead you to configuration tab of ProfilerModule.

Step 4: Click on Collected Matrics tab. Check Enabled check box. Here you've to define sampling period. In our case it should be 10 mins.(This value is specified in milliseconds). and click on new to create a new matrics.

Step 5: Choose server location Server Runtime and click next.

Step 6: Select mbean type as
weblogic.management.runtime.JDBCConnectionPoolRuntimeMBean and click next.

Step 7: Move all available collected attributes into chosen field by clicking on >> and click next.

Step 8: Move available instance to the chosen field.an click on finish.

Step 9: Click on targets tab. and deploy this diagnostic module to the specified server.

After configuring/ enabling JDBC profiler, we get logs in weblogic console under 
Diagnostics > log files > Managed_server log.

To Disable the profiler we just need to change Weblogic Server Targets to none or delete Diagnostic module which we have created.

I hope it will helps you in troubleshooting issues, we can create modules for different MBeans.

Enjoy working with Middleware Technologies.

Regards,
Ajinkya Vichare

ajinkya-vichare.blogspot.com

2 comments:

  1. Hi Ajinkya, today I find the same issue, what do you find after enabling the jdbc diagnostic? a WLS or JDBC issue? or a wrong configuration?
    Thank and Regards
    Steve

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete