Hello,
We instrumented dynaTrace Agents on JVMs running the Cognos application; everything from the dynaTrace side is fine ...no errors ...agent is up and running etc. However the cognos application cannot start. On perusing the logs for some reason DT is interfering with the startup.
Has anyone faced this issue with cognos?
Regards,
George
Answer by Richard M. ·
Hi Sreerag,
Thanks for responding on this, we have moved on and decided not to add cognos on to dynatrace. The path we were using is a symbolic link that is pointing to the lib64/dtagent.dll file.
Thanks
Richard
Answer by Sreerag M. ·
Richard,
We have the Cognos instrumented with DT agent.
You may need to check the path (C:\Dynatrace\dtagent.dll) to dll is correct. (are you sure that there is no lib/lib64 folder)
-Sreerag
Answer by Richard M. ·
Hi,
I am also busy with a Cognos Application instrumentation and I have added the Parameter as indicated by Gerald in the bootstrap_win64.xml config file as per below, however the application starts up but it does not connect to dynatrace neither do I see any logs genereated in the logs folder for the dynatrace agent nor anything in the cognos application logs relating to dynatrace.
Is there something wrong with the way I added it to the xml file?
<process name="catalina">
<start>
<spawn sync="0" wait_time="5">
<path quoteAsParam="true">${java_home}/bin/java.exe</path>
<param condName="${ip_protocol}" condValue="IPv6">-Djava.net.preferIPv6Addresses=true</param>
<param>-agentpath:"C:\Dynatrace\dtagent.dll"=name=Cognos,server=server1:9982</param>
<param>-Xrs</param>
<param>-Xmx${dispatcherMaxMemory}m</param>
<param>-Xms${dispatcherMaxMemory}m</param>
<param condName="${java_vendor}" condValue="IBM">-Xgcpolicy:gencon</param>
<param condName="${java_vendor}" condValue="Sun">-XX:MaxNewSize=${dispatcherMaxMemoryBy2}m</param>
<param condName="${java_vendor}" condValue="Sun">-XX:NewSize=${dispatcherMaxMemoryBy4}m</param>
<param condName="${java_vendor}" condValue="Sun">-XX:MaxPermSize=128m</param>
<!-- uncomment these for debug -->
<!--
<param>-Xdebug</param>
<param>-Xnoagent</param>
<param>-Xrunjdwp:transport=dt_socket,address=9091,server=y,suspend=n</param>
<param>-Djava.compiler=NONE</param>
-->
<!-- end debug params -->
<param>"-cp"</param>
<param>"${install_path}/tomcat/bin/bootstrap.jar;${java_home}/lib/tools.jar"</param>
<param>"-Dcom.ibm.cognos.disp.useDaemonThreads=true"</param>
<param>"-Dcatalina.base=${install_path}/tomcat"</param>
<param>"-Dcatalina.home=${install_path}/tomcat"</param>
<param>"-Djava.io.tmpdir=${temp}"</param>
<param>"-Djava.endorsed.dirs=${java_home}/lib/endorsed;${java_home}/jre/lib/endorsed;${install_path}/tomcat/lib/endorsed"</param>
<param>org.apache.catalina.startup.Bootstrap</param>
<param>start</param>
</spawn>
</start>
Thanks
Richard
Answer by Mark P. ·
Thank you Gerald! That is working. I am not seeing purepaths in dynaTrace. However, I see that one of the long running transactions is taking 32 seconds and it points to a socket read. When I drill down to the database, it shows queries to the content store but nothing to the datamart. All the queries to the content store are taking milleseconds and there are no queries that add up to 32 secs. Is there a special sensore that we need to place to capture the queries to the datamart?
Thanks,
Mark
Answer by Mark P. ·
Where did you place the startup command for dynaTrace? We are running Cognos on Windows and have tried placing the startup cmd in the Catalina.bat in teh Tomcat directory as well as the CogConfig.bat file.
Thanks,
Mark
Answer by Mike S. ·
George,
Any update? Were you able to instrument successfully?
We are about to start instrumenting Cognos over at Comerica Bank and i'm trying to gather any information beforehand that might prove useful.
Thanks,
Mike
Hi Mike,
Yes, after removing the JMX MBean sensor and the JMS entry Point sensors, the Cognos app was able to come up and we were successful in the profiling exercise. I noticed that Cognos uses Mx4J (instead of JMX) and I'm guessing that's the reason for the problem.
Regards,
George
Answer by Ted F. ·
Yes. In my case, we had to unplace the JMX MBean Sensor from the Agent Group Sensor Placement screen. We actually also unplaced the JMS and JMS Receive Entry Point sensors, but my guess is we only had to do the JMX MBean Sensor.
Of course, I can't guarantee that what you are seeing and what I saw are the same things, but the log for Cognos showed a linkage error on an MBean in my case.
Hope that helps!
thanks,
ted
JANUARY 15, 3:00 PM GMT / 10:00 AM ET