Enterprises are inherently complex, comprising of hundreds of applications with completely different semantics. Some of these applications are custom built, where as some are acquired from third parties and some even can be a combination of both and they can be operating in different system environments.
WSO2 VMware Images helps you to try our products inside your virtualized environments without having to go through the trouble of installation and configuration. Download an image and get your hands on cutting edge, lightweight SOA middleware right away!
WSO2 Governance Registry is a product from WSO2 that facilitates you to govern the SOA platform of your organization by helping you store and manage SOA meta data. The product is free and open source with Apache licence and you can download it from http://wso2.org/projects/governance-registry
There was an issue in the
There was an issue in the 1.5.1 startup bat files for windows. They don't load the vm options properly. It was fixed in trunk.
You can get the latest .bat files from https://wso2.org/svn/browse/wso2/trunk/mashup/java/modules/distribution/bin/ and replace ones in your installation.
If you like, you can also get the latest nightly build from http://builder.wso2.org/browse/MASHUP-NIGHTLY/latest/artifact
Tyrell
Not working
I changed the .bat file and it didn't seems to affect the memory usage of the Java process. I might not be looking at the right place though but in the process manager it says that the java.exe process uses about 162 000 KB. I tried my service anyways and still ended up with a java heap space fault.
My .vmoptions contain the following
-Xms512m
-Xmx512m
-XX:PermSize=64m
-XX:MaxPermSize=64m
Any idea about what should I do? Try to run it in a linux environnement maybe?
Thank you in advance
edit : The nightly build crash when I try to start it, it seems to have something to do with the wrapper.
solution 1 ---------- You
solution 1
----------
You need to change at least 2 bat files.
- wso2mashup.bat
- startup.bat
Then instead of starting the windows service, try starting the server using the startup.bat
If you need the windows service here's a potential solution.
Solution 2
----------
in your mashup server installations /conf folder, there's a file named 'wrapper.conf'. Uncomment lines 58 and 61 and give the memory values you require there.
The wrapper will initialize the VM using these values when the service is restarted.
Tyrell
It's working! Thanks a lot
Solution 2 worked for me.
Thank you for you continuous support!