By looking at the datasource it is almost impossible to determine what is causing the slowness at this moment, Because first we need to determine what kind of calls are causing the slowness. I will suggest the following :
1). Enable the Garbage Collection log on your JBoss EAP
2). As soon as you notice a slowness please collect 5-6 thread dumps collected during that time.
3). It is also best to collect the CPU utilization matrix of that time like running the "top" command during the time of slowness.
Thank You Jay SenSharma for responding so quickly .
I thought like we need to modify the connection pool size min and max , idle and blockout time in millis values..,
But you have mentioned some more points.
Can you please explain me how to enable those 1.Garbage Collection log 2,3 .points u mentioned.
by d way , i'm running the server from eclipse.
You can refer to the following article in order to know how to collect the thread dumps
The thread dump & CPU investigation can be done is general as mentioned in :
In order to collect the Garbage collection logs you can add the following JAVA_OPTS in your EAP6 standalone.conf file.
JAVA_OPTS="$JAVA_OPTS -Xloggc:/PATH/TO/GCLogs.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps"
See the following article for more details on this:
Analyzing Garbage Collection Log