[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2436) Look for eventual optimizations when scanning classes

[Richard Opalka (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBWS-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12499393#action_12499393 ] 

Richard Opalka commented on JBWS-2436:
--------------------------------------

Martin Vecera wrote:
---
I realized a strange thing in behaviour between EJB3 and POJO WS. Open both 
attached snapshots and I'll navigate you through them...

First, in both windows (snapshots), click at Thread Views, write '*http*' to 
Filter by name and press Enter. You can see around 25 thread called http-
jawa07%2F10.34.33.228.-8080-{number}. Search for a time period when they are 
not Waiting (orange colour). For EJB3 they are mainly running (green) and time 
to time they are blocked (red). The opposite is true for POJO.

You can see the same issue when you click on VM Telemetry Views, Threads tab 
and Scale to fit window (the button in the lower right corner). Many threads 
are blocked with POJO WS. It seems like they are synchronized somewhere.

Now click on CPU Views, Call tree tab, right click on the white space, select 
View settings and enable Hide calls with less than 0.2%. At the top right 
corner, select thread status to Blocked. Now you can go down the tree to see 
where the blocked threads spent their time. Switch to Hot Spots tab, the 
Thread Status should remain set to Blocked. With the POJO WS, the hot spot is 
java.lang.ClassLoader.loadClass being called from several different places in 
org.jboss.wsf and XML handling routines (see the snapshot)...


> Look for eventual optimizations when scanning classes
> -----------------------------------------------------
>
>                 Key: JBWS-2436
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2436
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-integration
>            Reporter: Alessio Soldano
>            Assignee: Richard Opalka
>            Priority: Critical
>             Fix For: jbossws-cxf-3.3, jbossws-metro-3.3, jbossws-native-3.3
>
>         Attachments: call_ejb3.jps, call_pojo.jps
>
>
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146807

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira