APM Java agent websphere startup issues

Elastic Observability APM
1

APM Java agent websphere startup failure

I have the same issue as the above thread. I know WebSphere isn't officially supported only WebSphere Liberty but if this issue is something I could work around that would be great.

To add to the above discussion check this from the native_stdout.log :

 2019-01-04 15:45:10.319 [apm-server-healthcheck] INFO co.elastic.apm.agent.report.ApmServerHealthChecker - Elastic APM server is available: {"ok":{"build_date":"2018-11-29T22:56:26Z","build_sha":"ea0bf4863f638b35ecb6ced94f02015bab8bcb47","version":"6.5.2"}}
2019-01-04 15:45:10.374 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - Starting Elastic APM 1.2.0 as bbtools_solr_sandbox on Java 1.7.0 (IBM Corporation) Windows Server 2012 R2 6.3
[1/4/19 15:45:16:064 CET] 00000001 ProviderTrack I com.ibm.ffdc.osgi.ProviderTracker AddingService FFDC1007I: FFDC Provider Installed: com.ibm.ffdc.util.provider.FfdcOnDirProvider@58719931
[1/4/19 15:45:16:346 CET] 00000001 Ffdc          I com.ibm.ffdc.util.provider.FfdcOnDirProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WEBSPH~1\APPSER~1\profiles\bbtools_solr\logs\ffdc\ffdc.6144037256924974509.txt com.ibm.ws.util.ImplFactory.loadImplFromClass 345
[1/4/19 15:45:16:354 CET] 00000001 Ffdc          I com.ibm.ffdc.util.provider.FfdcOnDirProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WEBSPH~1\APPSER~1\profiles\bbtools_solr\logs\ffdc\ffdc.8545878984471733618.txt com.ibm.ws.util.PlatformHelperFactory.getPlatformHelper 74
org.eclipse.core.runtime.CoreException: Plug-in "com.ibm.ws.runtime" was unable to instantiate class "com.ibm.ws.runtime.WsServer".

And then after all the class not found errors for org.omg.CORBA.ORB I get this:

2019-01-04 15:45:16.374 [Thread-7] WARN co.elastic.apm.agent.impl.ElasticApmTracer - Suppressed exception while calling stop()
java.security.AccessControlException: Access denied ("java.lang.RuntimePermission" "modifyThread")
	at java.security.AccessController.throwACE(AccessController.java:125)
	at java.security.AccessController.checkPermission(AccessController.java:198)
	at java.lang.SecurityManager.checkPermission(SecurityManager.java:563)
	at java.util.concurrent.ThreadPoolExecutor.checkShutdownAccess(ThreadPoolExecutor.java:745)
	at java.util.concurrent.ThreadPoolExecutor.shutdown(ThreadPoolExecutor.java:1402)
	at java.util.concurrent.ScheduledThreadPoolExecutor.shutdown(ScheduledThreadPoolExecutor.java:771)
	at co.elastic.apm.agent.shaded.stagemonitor.configuration.ConfigurationRegistry.close(ConfigurationRegistry.java:444)
	at co.elastic.apm.agent.impl.ElasticApmTracer.stop(ElasticApmTracer.java:321)
	at co.elastic.apm.agent.bci.ElasticApmAgent$1.run(ElasticApmAgent.java:95)

Any input/ideas?

2

Hi!
Thanks for trying out our agent and providing your input.

Regarding the latter error- we have an issue for supporting SecurityManagers in general. It seems that we will still require users to edit the policy file to grant the agent jar with the right permissions.
In any case, the first error will probably won't let your WebSphere start up so I am afraid I have no good advice at this stage...

3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.