How can you run Mule 2.2.1 on a 64 bit Windows machine?

[hoffmandirt]

When I attempt to run Mule on a 64 bit Windows Server machine I get the following error:

WARNING - Unable to load the Wrapper's native library because none of the
          following files:
            wrapper-windows-x86-64.dll
            wrapper.dll
          could be located on the following java.library.path:
            C:\applications\web-service-proxy\%LD_LIBRARY_PATH%
            C:\applications\mule-standalone-2.2.1\lib\boot
          Please see the documentation for the wrapper.java.library.path
          configuration property.
          System signals will not be handled correctly.

This file doesn't exist in the Mule 2.2.1 zip file. Where do I get it? Is there another way to run Mule on a 64 bit Windows machine?

[Richard Swart]

Mule CE ship with community version of the Tanuki Wrapper. The Community version of Tanuki wrapper does not support windows 64 bit. http://wrapper.tanukisoftware.org/doc/english/download.jsp#downloadNote2

To run on windows 64 bit you will have to use Mule EE.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[hoffmandirt]

Giuseppe Pace wrote:

To run on windows 64 bit you will have to use Mule EE.

That's impractical considering most new Windows machines are 64 bit. I found a way around it after reading a little on the web site. Below is the contents of my bat file to execute Mule on a 64 bit machine. If I need to run it as a service, I believe I can use the Microsoft tool named srvinstw.exe.

cd "C:\applications\my-java-example"

java -cp "./;C:\applications\mule-standalone-2.2.1\lib\opt\*;C:\applications\mule-standalone-2.2.1\lib\mule\*;C:\applications\mule-standalone-2.2.1\lib\boot\*" org.mule.MuleServer -config mule-config.xml

Note that if you are not using Java 6, you will have to add each jar individually to the class path.

[Andrew Perepelytsya]

You would rather start a MuleBootstrap instead of messing with classpath.

And, to be fair, don't blame us, Tanuki decided to provide 64-bit in commercial version only ;)

Andrew

[hoffmandirt]

Andrew Perepelytsya wrote:

You would rather start a MuleBootstrap instead of messing with classpath.

The classpath instructions are in the Mule 2.x Getting Started guide under Starting Mule Directly. http://www.mulesoft.org/display/MULE2INTRO/Running+Mule. There is nothing mentioned about a MuleBootstrap and nothing comes up in the search results.  Can you explain what a MuleBootstrap is and how to create/start one?

Andrew Perepelytsya wrote:

And, to be fair, don't blame us, Tanuki decided to provide 64-bit in
commercial version only ;)

Mule is to blame and that comment makes Mule sound lazy. That's like opening a car wash that doesn't allow Chevrolets. It just doesn't make sense to not have 64 bit Windows support.  In my opinion, ditch Tanuki and find something else or develop your own wrappers and service installers for 64 bit Windows systems.

[Andrew Perepelytsya]

The classpath instructions are in the Mule 2.x Getting Started guide under
Starting Mule Directly.
http://www.mulesoft.org/display/MULE2INTRO/Running+Mule. There is nothing
mentioned about a MuleBootstrap and nothing comes up in the search results.
Can you explain what a MuleBootstrap is and how to create/start one?

Instructions still apply, if running as a java app. MuleBootstrap is doing extra startup magic, and is in fact what wrapper is calling (you'll see it if you open wrapper.conf).

 Mule is to blame and that comment makes Mule sound lazy. That's like opening

a car wash that doesn't allow Chevrolets. It just doesn't make sense to not
have 64 bit Windows support.  In my opinion, ditch Tanuki and find something
else or develop your own wrappers and service installers for 64 bit Windows
systems.

If the goal is to start some flame, then you found a wrong person. IIRC, 64-bit binary *was* available before, although not sure. You are always welcome to "find something else or develop your own wrappers and service installers for 64 bit Windows systems" for the benefit of the community, we're happy to provide guidance if needed.

Andrew