Monitoring Weblogic 12c

[CommunityUser]

Hello!

I am Trying to monitor a Java application under WebLogic 12c server.

After all configurations, I can only see metrics related to the Memory, jvm, jmx and some exceptions.

On the main dashboard, there is no transactions being monitored.

Looking at the Agent logs, I have noticed lots of connection erros such as described below

[AD Thread-Metric Reporter0] 26 Aug 2013 12:43:02,666 ERROR MetricSender - Fatal transport error: Connection refused
[AD Thread-Metric Reporter0] 26 Aug 2013 12:43:02,666 WARN MetricHandler - Problem registering metrics: Fatal transport error: Connection refused.

and lots of these other ones described below

[AD Thread Pool-Global0] 26 Aug 2013 12:45:15,688 INFO ClassMetaData - Exception java.lang.ArrayIndexOutOfBoundsException: 16302 caught trying to parse class file for la.foton.brb.banklink.pmt.dto.ParametroPMTService_f9ib1c_ParametroPMTServiceRemoteImpl_WLSkel from Cla
ssLoader weblogic.utils.classloaders.GenericClassLoader@6253e921 finder: weblogic.utils.classloaders.CodeGenClassFinder@51b5a913 annotation: brb-banklink-ear@
[AD Thread Pool-Global0] 26 Aug 2013 12:45:15,688 ERROR ClassMetaData - java.lang.ArrayIndexOutOfBoundsException: 16302
[AD Thread Pool-Global0] 26 Aug 2013 12:45:15,689 WARN BCIFixer - Error matching class [la.foton.brb.banklink.pmt.dto.ParametroPMTService_f9ib1c_ParametroPMTServiceRemoteImpl_WLSkel] [null]. Blacklisting the class
[AD Thread Pool-Global0] 26 Aug 2013 12:45:15,689 WARN BCIFixer - Error matching class [la.foton.brb.banklink.pmt.dto.ParametroPMTService_f9ib1c_ParametroPMTServiceRemoteImpl_WLSkel] [null]. Blacklisting the class
[AD Thread Pool-Global0] 26 Aug 2013 12:45:15,690 WARN BCIFixer - Error matching class [la.foton.brb.banklink.pmt.dto.ParametroPMTService_f9ib1c_ParametroPMTServiceRemoteImpl_WLSkel] [null]. Blacklisting the class

A zip containing all logs under agent logs folder follows attached.

Thanks.

[Arun_Dasetty · Accepted solution]

Hi,

Thanks for writing in. Please find the analysis of the logs and plan of action:
1) We do see the following errors in agent.logs logged repetively, we see such issue due to network issues between agent and controller machine, please make sure that controller http://hib340210:8090/ is running fine and there is not network issues from agent/server machine to connect controller:
======================
[AD Thread Pool-Global1] 26 Aug 2013 13:04:36,708  WARN ConfigurationChannel - Invalid response for configuration request from controller/could not connect to controller. Msg : null
[AD Thread Pool-Global1] 26 Aug 2013 13:04:36,708  WARN ConfigurationChannel - Number of tries [3] exceeded maximum allowed [3]. Disabling agent.
=========================

2) we request you to restart agent once you resolved network issues if any at the agent side

3) We see the following servlet, EJB interceptors applied in BCI.log:
==================
Applying method interceptor entry.ejb.WLS.Identifier at weblogic/rmi/internal/BasicServerRef.invoke ((Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V) id:9
Applying method interceptor entry.Servlet at weblogic/management/servlet/FileDistributionServlet.doGet ((Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) id:14
====================

we request to enabled Servelt auto discovery and EJB auto discovery entry points at Controller UI under configure => instrumentation -> transaction detection (select app/tier) and enabled servlet and EJB auto discovery checkboxes if not enabled and generate load on the above listed servlets and EJBs and check whether you see any data in BT grid and app dashboard in Controller UI.

4) also we see that you have enabled find-entry-points node property, we request you to disable the property and try the following:
- we see 32 possible Business transactiosn listed in Business-transaction.log and we request you to define POJO and EJB custom rules for the possible entry points listed in BT.log , we listed few selected entry points on which you can try to configure custom rules :
===================
[pool-5-thread-50] 26 Aug 2013 14:44:12,098  INFO - 24.    EJB    la.foton.brb.banklink.cliente.ejb.LimitePreAprovadoService_yiboac_NoIntfViewImpl        carrega
[pool-5-thread-50] 26 Aug 2013 14:44:12,098  INFO - 25.    EJB    la.foton.brb.banklink.cliente.ejb.LimitePreAprovadoService_yiboac_NoIntfViewImpl        __WL_invoke
..
[SIAScheduler_Worker-1] 26 Aug 2013 15:01:11,953  INFO - 25.    POJO    com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor        invoke
[SIAScheduler_Worker-1] 26 Aug 2013 15:01:11,953  INFO - 27.    POJO    com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation        proceed
===================

refer docs: http://docs.appdynamics.com/display/PRO13S/Configure+Transaction+Detection

5) Regarding the error on blacklisting class we see such errors

Could you please try adding this JVM option to the startup script?
-XX:-UseSplitVerifier

or let us know if adding and incresing the value for -Xss to jvm opts makes any difference here in logs,

we see such errors during retransformation of the classes

Let us know if that information helps, Do write back to us for further assistance.

Thanks,

Arun

[CommunityUser]

Hi Arun.

I have made the changes, and now it started to monitor my transactions as it should.

Thanks a lot for your help.