Loading native library failed message when starting Remote Agent

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

When starting a Remote Agent with DEBUG logging enabled, the following appears in the atlassian-bamboo-agent.log:

INFO   | jvm 1    | 2017/03/02 23:54:11 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2017/03/02 23:54:11 | Load native library.  One or more attempts may fail if platform specific libraries do not exist.
INFO   | jvm 1    | 2017/03/02 23:54:11 | Loading native library failed: wrapper-windows-x86-64.dll  Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-64 in java.library.path
INFO   | jvm 1    | 2017/03/02 23:54:11 | Loaded native library: wrapper.dll
INFO   | jvm 1    | 2017/03/02 23:54:11 | Calling native initialization method.

Cause

This message appears with the DEBUG logging enabled but doesn't indicate a problem. The platform specific library isn't shipped so the regular wrapper is used instead.

https://sourceforge.net/p/wrapper/mailman/message/21733694/

When the WrapperManager class in the JVM is initialized, it attempts to load the wrapper.dll using two names. The first is a platform specific name that works when running the Wrapper using delta-pack naming. The second is the regular wrapper.dll file.

 

Resolution

No action is necessary – the Remote Agent wrapper starts successfully.

 

Last modified on Nov 30, 2017

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.