RHQ Agent and 32-bit vs. 64-bit wrapper.dll

[rherrick]

I found this issue in RHQ 4.0.0.B02 and just updated to RHQ 4.0.0.B03 and nothing changed, so I figured I'd ask here.

I'm running on 64-bit Windows 7 with 64-bit JVM 1.6.  On start-up of the RHQ agent, I get this message:

STATUS | wrapper  | 2011/02/25 16:22:04 | RHQ Agent [rhqagent-DEVMOB0G8VK1] installed.

STATUS | wrapper  | 2011/02/25 16:22:14 | --> Wrapper Started as Service

STATUS | wrapper  | 2011/02/25 16:22:14 | Launching a JVM...

INFO   | jvm 1    | 2011/02/25 16:22:14 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org

INFO   | jvm 1    | 2011/02/25 16:22:14 |

INFO   | jvm 1    | 2011/02/25 16:22:14 |

INFO   | jvm 1    | 2011/02/25 16:22:14 | WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.

INFO   | jvm 1    | 2011/02/25 16:22:14 |           The file is located on the path at the following location but

INFO   | jvm 1    | 2011/02/25 16:22:14 |           could not be loaded:

INFO   | jvm 1    | 2011/02/25 16:22:14 |             C:\Servers\rhq-agent-4.0.0.B03\bin\wrapper\windows-x86_32\wrapper.dll

INFO   | jvm 1    | 2011/02/25 16:22:14 |           Please verify that the file is readable by the current user

INFO   | jvm 1    | 2011/02/25 16:22:14 |           and that the file has not been corrupted in any way.

INFO   | jvm 1    | 2011/02/25 16:22:14 |           One common cause of this problem is running a 32-bit version

INFO   | jvm 1    | 2011/02/25 16:22:14 |           of the Wrapper with a 64-bit version of Java, or vica versa.

INFO   | jvm 1    | 2011/02/25 16:22:14 |           This is a 64-bit JVM.

INFO   | jvm 1    | 2011/02/25 16:22:14 |           System signals will not be handled correctly.

INFO   | jvm 1    | 2011/02/25 16:22:14 |

INFO   | jvm 1    | 2011/02/25 16:22:15 | RHQ 4.0.0.B03 [7d43d73] (Thu Feb 17 10:11:05 CST 2011)

I tried to use a 64-bit wrapper, but there's no community version for that. I tried the standard version, but got a grip about not having a license key. Fair enough, I suppose, but the question then is whether the agent would work properly with the 32-bit wrapper given this message.

The reason I ask is that I'm having some issues with discovered services and I'm trying to determine if this might be part of the cause. Thanks!    

[mazz]

Yeah, unfortunately, looks like you are on one of the very few platforms that the JSW guys don't support with their community release.

That error message indicates that you can't start the agent via the Java Service Wrapper. But if you start the agent manually (say, on a command line via rhq-agent.bat), the agent should work normally. The JSW is only used/needed to start the agent as a background service. Once the agent is started, the agent works the same regardless of how it was started.

[kmacedovarela]

I am having the same problem on a Windows server 2008...

I am using Jon 3.1.0, and 64-bit JVM ... Same error..

The user that is excuting has permissions and the file is located in the path..

I can run the agent manually, but i cant start it as a service.

Does anyone have any ideia?

INFO   | jvm 1    | 2012/07/30 17:40:09 | WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.

INFO   | jvm 1    | 2012/07/30 17:40:09 |           The file is located on the path at the following location but

INFO   | jvm 1    | 2012/07/30 17:40:09 |           could not be loaded:

INFO   | jvm 1    | 2012/07/30 17:40:09 |             c:\rhq-agent\bin\wrapper\windows-x86_32\wrapper.dll

INFO   | jvm 1    | 2012/07/30 17:40:09 |           Please verify that the file is readable by the current user

INFO   | jvm 1    | 2012/07/30 17:40:09 |           and that the file has not been corrupted in any way.

INFO   | jvm 1    | 2012/07/30 17:40:09 |           One common cause of this problem is running a 32-bit version

INFO   | jvm 1    | 2012/07/30 17:40:09 |           of the Wrapper with a 64-bit version of Java, or vica versa.

INFO   | jvm 1    | 2012/07/30 17:40:09 |           This is a 64-bit JVM.

INFO   | jvm 1    | 2012/07/30 17:40:09 |           System signals will not be handled correctly.

[gilksd]

Have a look at the logs in rhq-agent\logs

The wrapper issue won't stop you running the RHQ agent as a service.