Forum Discussion

Kiyoshi_Egawa's avatar
11 months ago
Solved

SAP_HANA_SystemDatabaseAvailability Test DataSource Script failed

I have a wrong Java environment ?

The script failed, elapsed time: 21 seconds - Unable to load Snippet - lm.emit
java.lang.Exception: Unable to load Snippet - lm.emit
    at java.base/jdk.internal.reflect.GeneratedConstructorAccessor103.newInstance(Unknown Source)
    at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
    at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
    at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
    at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
    at Script1.get(Script1.groovy:70)
    at Script1.load(Script1.groovy:19)
    at Script1$load$0.callCurrent(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:157)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
    at Script1.load(Script1.groovy:15)
    at Script1$load.call(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
    at Script1$load.call(Unknown Source)
    at Script7.run(Script7.groovy:6)

  • The release notes related to that DataSource (https://www.logicmonitor.com/release-notes/v-183-release-notes) does have a note that perhaps is related?

    Some collectors were observed to have CPU spikes when scripts created a new GroovyShell object, so we updated the snippet loader to remove the creation of this object in order to improve the performance.

    To ensure monitoring is not disrupted when updating, verify that all Collectors are version EA 32.100 or greater, or use LogicMonitor_Collector_Snippets DataSource to update the snippet loader.

7 Replies

  • The release notes related to that DataSource (https://www.logicmonitor.com/release-notes/v-183-release-notes) does have a note that perhaps is related?

    Some collectors were observed to have CPU spikes when scripts created a new GroovyShell object, so we updated the snippet loader to remove the creation of this object in order to improve the performance.

    To ensure monitoring is not disrupted when updating, verify that all Collectors are version EA 32.100 or greater, or use LogicMonitor_Collector_Snippets DataSource to update the snippet loader.

  • Did you try to install Java? You don't need to install Java, the collector will do it. I'd talk to support, but they will probably have you reinstall the collector.

  • Did Mike’s answer resolve the issue? What did the OP say? It’s been 3 hours since Mike posted his answer. The OP needs to be given a chance to mark this as the correct answer. 3 hours is not long enough. Has the OP tested Mike’s solution?

  • mray's avatar
    mray
    Icon for LM Conqueror rankLM Conqueror

    Fair point. I would say that Mike’s response is the best answer in terms of preliminary troubleshooting. Make sure the DataSources and Collector are all up-to-date. If this does not resolve the issue, then a Support ticket/chat is best. 

    OP should be able to mark any other response as ‘best answer’ and override my action.

  • EA34.200 has worked fine but SAP_HANA_Troubshooter said no jdbc connection strings. Cloud you please let me know how to set it ?

    Thanks,

    Kiyoshi