IBM Support

IT07544: HUNG THREADS ON SERVER STARTUP SEEN AFTER APPLYING THE PRELOAD PROPERTY ON MEDIATION FLOWS

Direct link to fix

bpm.8570.cf2017.06.delta.repository

 

APAR status

  • Closed as program error.

Error description

  • The server becomes unresponsive after start up and the
SystemOut.log reports multiple threads are hung with a similar
stack to the following:

WSVR0605W: Thread "server.startup : 2" (0000007f) has been
active for 642780 milliseconds and may be hung. There is/are 1
thread(s) in total in the server that may be hung.
at java.net.URLEncoder.encode(URLEncoder.java:206)
at
com.ibm.ws.sibx.scax.mediation.engine.utils.TableValueUtils.toke
nizeTableValues(TableValueUtils.java:137)
at
com.ibm.ws.sibx.scax.mediation.engine.utils.PropertySetter.resol
veProperties(PropertySetter.java:716)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.resolve
Properties(ESBFlowAnalyzer.java:326)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.analyze
JavaMediationPrimitive(ESBFlowAnalyzer.java:232)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.analyze
Node(ESBFlowAnalyzer.java:218)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.recurse
toNextNode(ESBFlowAnalyzer.java:204)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.analyze
JavaMediationPrimitive(ESBFlowAnalyzer.java:271)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.analyze
Node(ESBFlowAnalyzer.java:218)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.recurse
toNextNode(ESBFlowAnalyzer.java:204)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.analyze
JavaMediationPrimitive(ESBFlowAnalyzer.java:267)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.analyze
Node(ESBFlowAnalyzer.java:218)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.recurse
toNextNode(ESBFlowAnalyzer.java:204)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.analyze
JavaMediationPrimitive(ESBFlowAnalyzer.java:267)
at
com.ibm.ws.sibx.scax.mediation.component.ESBFlowAnalyzer.analyze
Node(ESBFlowAnalyzer.java:218)
...

Local fix

  • 



Problem summary


    

  • ****************************************************************
USERS AFFECTED:
Users of Business Process Manager v8.5 who are making use of the
preload WebSphere environment variable to load mediation flows
at application startup.

****************************************************************
PROBLEM DESCRIPTION:
When the mediation flow is first built (during preload) all of
the flow's nodes need to be analysed so that any promoted
properties can be resolved. The process by which this occurs was
found to have some inefficiencies that lead to excessive looping
and ultimately resulted in the preload taking a long time.

    



Problem conclusion


    

  • The code has been optimized to reduce the time taken to analyse
the flow's nodes which has subsequently reduced the time
required for the application server to start up.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IT07544
    • 

  • Reported component name
    WESB IN BPM
    • 

  • Reported component ID
    AIMCMFC00
    • 

  • Reported release
    855
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2015-03-06
    • 

  • Closed date
    2015-03-25
    • 

  • Last modified date
    2015-03-25
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    

  • Fixed component name
    WESB IN BPM
    • 

  • Fixed component ID
    AIMCMFC00
    • 



Applicable component levels


    

  • R855  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC2KE9","label":"Mediation"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Edition":"","Line of Business":{"code":"","label":""}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            25 March 2015
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback