WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  WAS8 Profiling Problem

    Posted Mon December 30, 2013 11:06 AM
    Hi All,

    we are using RSA V8.0.4 and WAS v 8.00.7. and Agent Controller V8.3.4.

    While profiling, the request is not getting processed. or getting ArrayIndexOutOfBounds exception.

    If the server is started in regular mode, the request is getting proessed and getting the results.


    I checked a similar  java.lang.ArrayIndexOutOfBoundsException issue in the below URL, but this does not help www-01.ibm.com/support/docview.wss?uid=s....

    Any clues to solve this issue? Thanks in advance.


  • 2.  WAS8 Profiling Problem

    Posted Mon December 30, 2013 12:02 PM
    Hi Raj,

      can you put the complet error? have you applied any fixpack (8.0.4.1 or 8.0.4.2) to RSA?
     
      Thanks in advanced
     
    Regards


  • 3.  WAS8 Profiling Problem

    Posted Mon December 30, 2013 12:11 PM
    No, i have not applied any fix pack.

    Following is the trace. removed some app specific class names.

                                     java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:527)
     at ...................................
     at ...................................
     at ...................................
     at ...................................
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
     at java.lang.reflect.Method.invoke(Method.java:611)
     at org.apache.axis2.jaxws.server.dispatcher.JavaDispatcher.invokeTargetOperation(JavaDispatcher.java:120)
     at org.apache.axis2.jaxws.server.dispatcher.JavaBeanDispatcher.invoke(JavaBeanDispatcher.java:118)
     at org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:111)
     at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:161)
     at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:208)
     at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
     at com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis2Servlet.java:1532)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
     at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136)
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:79)
     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:960)
     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1064)
     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3763)
     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:976)
     at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:277)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
     at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
     at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
     at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
     at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
     at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1700)
    Caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 3
     at  ...................................
     at  ...................................


  • 4.  WAS8 Profiling Problem

    Posted Mon December 30, 2013 12:34 PM
    raj,


      You are getting the exception in your class NOT in product (WAS) class.

      Have you enabled traces? the application seems a Webservice.

       Integration layer
    com.ibm.ws.websvcs.*=all
        
    Policyset component
    com.ibm.ws.policyset.*=all

    WS-Security component
    com.ibm.ws.wssecurity.*=all

    WS-Addressing component
    com.ibm.ws.wsaddressing.*=all    

    WS-Transactions component
    com.ibm.ws.wstx.*=all

    JAX-WS run-time
    org.apache.axis2.jaxws.*=all

    Axis2 run-time (including JAX-WS)
    org.apache.axis2.*=all   

    regards


  • 5.  WAS8 Profiling Problem

    Posted Mon December 30, 2013 12:45 PM
    Hi Gabriel, yes this is a webservice.

    Definitely this is not a Applicaiton problem, as the problem happens only while profiling, otherwise the app runs fine.



  • 6.  WAS8 Profiling Problem

    Posted Mon December 30, 2013 02:08 PM
    Ok, in that case have you enable traces?
     
     the options are or enable traces a look into or open a PMR


  • 7.  WAS8 Profiling Problem

    Posted Tue December 31, 2013 07:46 AM
    Hi Gabriel,

    Thanks a lot for your suggestions.

    I checked what is happening. TPTP profiling instrumentation adds lot of properties into objects starting with "sm_bAlreadyInvoked". In our code we do reflection on properties. This causes problems.

    I tried adding these classes in the filters to exclude from profiling, it does not work.

    Finally i excluded the properties, when doing reflection on these objects. Now Profiling works fine.