unable to use legacy mode bootstrap

Details

  • User impact:
    Medium
  • Similar Issues:
    None

Description

Using these instructions: http://corp.wiki.mulesource.com/display/MULEDEV/Mule+Standalone+Legacy+Mode+Testing
I get the following error when trying to start mule standalone in legacy mode:

mule-enterprise-standalone-3.1.1-SNAPSHOT $ ./bin/mule -config ./examples/echo/src/main/app/mule-config.xml
MULE_HOME is set to /Users/dzapata/mule-enterprise-standalone-3.1.1-SNAPSHOT
Running in console (foreground) mode by default, use Ctrl-C to exit...
MULE_HOME is set to /Users/dzapata/mule-enterprise-standalone-3.1.1-SNAPSHOT
Running Mule Enterprise Edition...
Removed stale pid file: /Users/dzapata/mule-enterprise-standalone-3.1.1-SNAPSHOT/bin/./.mule_ee.pid
--> Wrapper Started as Console
Java Service Wrapper Standard Edition 32-bit 3.5.4
Copyright (C) 1999-2010 Tanuki Software, Ltd. All Rights Reserved.
http://wrapper.tanukisoftware.com

License Error:
The License Key, 201010160006, was found but failed to be validated.
Please verify that the wrapper.license.* properties match exactly and have
not been modified. Also verify that the following property values match
those specified when generating the license:
wrapper.java.mainclass=org.mule.module.boot.MuleBootstrap

The Java Service Wrapper requires a License Key to activate the
software. License Keys can be purchased on the Java Service Wrapper
web site:
http://wrapper.tanukisoftware.com/purchase

You can also immediately obtain a one-month Free trial license:
http://wrapper.tanukisoftware.com/trial

License Keys can be generated for any of the following HostIds.
HostId(s):
109addb44d1e (en1)
109add613e1b (en0)

Optional host name for license: Daniel-Zapatas-MacBook-Pro.local

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dirk Olmes added a comment -

Do your instructions include to use a 2.2.x wrapper license? It looks like the class name is hardcoded in the Tanuki license and so the new license does not work.

Show
Dirk Olmes added a comment - Do your instructions include to use a 2.2.x wrapper license? It looks like the class name is hardcoded in the Tanuki license and so the new license does not work.
Hide
Permalink
Daniel Feist added a comment -

This is exactly what Dirk said, i've updated the test steps on wiki.

Show
Daniel Feist added a comment - This is exactly what Dirk said, i've updated the test steps on wiki.
Hide
Permalink
Daniel Zapata added a comment -

I don't think this is an acceptable solution for customers. If they download Mule 3.1.x and want to use the legacy bootstrapper, they need to download Mule 2.2.x and copy over some config from there? We should at least provide the old license info commented out in the configuration file to make this obvious to the user.

Show
Daniel Zapata added a comment - I don't think this is an acceptable solution for customers. If they download Mule 3.1.x and want to use the legacy bootstrapper, they need to download Mule 2.2.x and copy over some config from there? We should at least provide the old license info commented out in the configuration file to make this obvious to the user.
Hide
Permalink
Andrew Perepelytsya added a comment -

How about dropping support for it altogether? It was a stop-gap measure for people who couldn't upgrade fast and never meant as a product feature

Show
Andrew Perepelytsya added a comment - How about dropping support for it altogether? It was a stop-gap measure for people who couldn't upgrade fast and never meant as a product feature
Hide
Permalink
Daniel Feist added a comment -

So lets plan on dropping it for 3.2? For now i think adding license commented out is best approach. Anyone know where this is documented publicly?

Show
Daniel Feist added a comment - So lets plan on dropping it for 3.2? For now i think adding license commented out is best approach. Anyone know where this is documented publicly?
Hide
Permalink
Daniel Feist added a comment -

I added some simple doc and commented out properties to the wrapper.conf to ease enabling legacy mode.

EE 3.1.x: r18739

Show
Daniel Feist added a comment - I added some simple doc and commented out properties to the wrapper.conf to ease enabling legacy mode. EE 3.1.x: r18739

People

  • Assignee:
    Daniel Feist
    Reporter:
    Daniel Zapata
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: