1

I'm exploring the Azure platform, but I'm experiencing issues.

Actually, there's something I don't get...

I understand the difference between a web role and a worker role. But how to specifically create a web role for a Java app ?

Because when developping a java app for azure in eclipse, we have to copy/paste a java server (i picked up tomcat7) + jdk. I assume it's only to run the java app inside the emulator.

But, when deploying the app to azure as a webrole.....Does it upload only the war package + xml configuration files (cscfg and others) or does it also uploads the server and jdk ? I tried to build the project with "Cloud" parameter instead of "Emulator" parameter and it created a huge cspkg file of 150Mb... I seriously can't upload 150Mb each time I have to update the app...

Why don't just allow to upload a .war file ? And if we have to upload the server distribution, then how is the failover and session replication set up ??

I probably miss something...

Thanks for your answers

Edit :

Actually, from what I've read from the web, java applications are not natively handled by Azure, so you have to provide your own applications server (tomcat, glassfish etc..) inside the package, and the startup script will run the server with your app inside. You have to upload the jre + the server binaries + your application code everytime you want to redeploy a new package.

There's no built-in support for session replication or anything. If you want session to be "sharable" across multiples instances, you have to use the Table Storage service to store session infos.

Note : With eclipse, the lastest plugin allows you to set sticky session, but I don't know anything more about it

Hence, a java app is not deployed as a webrole but as a worker role where you add your own server.

Webroles are only for .NET and PHP applications.

Correct me if I'm wrong.

will
  • 53
  • 7
  • You don't need to include Java or Tomcat with your deployment package. You can store them in blob storage and, in a startup script, copy them to local storage and start tomcat. The copy from blob storage to local vm storage is extremely fast. I'm working on a demo app that does the same thing, and the package size dropped from about 160MB to 70MB when moving the JRE and Tomcat to blob storage. I'll update this post in a few weeks, when the code is available, but there's plenty of material out there that show how to do this as well. – David Makogon Feb 06 '12 at 01:02

2 Answers2

1

You are right. In general you can also run java/Tomcat in web role but in web role there must be at least one site inside IIS (do not bound port 80 to this site as IIS and Tomcat can't share TCP port).

You should try with Azure VM Role. In this scenario you create virtual macine locally with all system requirements (JRE, Tomcat,...). The you upload this virtual image to Azure as template for your VM Roles. Now you can upload only your application files.

You can also speed up upload / deployment process with starup task that downloads and unpacks your JRE and Tomcat from Blob storage. Azure Bootstrapper can help you.

Matej
  • 7,517
  • 2
  • 36
  • 45
  • I disagree - you do NOT need a VM role to run Java. You simply need to start Tomcat, Jetty, etc. If you go with a VM Role, you now have to manage OS upgrades as well, and there's absolutely no advantage doing this. Also: the OP was concerned with uploading a 170MB package. Using a VM role, this would now mean pushing an entire VM up, much larger than the deployment package. – David Makogon Feb 06 '12 at 00:59
1

Thanks for your answers guys.

This brings another question : what happens "under the hood" when you deploy a new version of a java package ?

Let's imagine tomcat released a major security fix, you need to use a new version of tomcat either by embedding it into the cspkg (heavyyyyy), or, as you (David) suggested, by storing in blob (light !!) and, of course, the java code with few updates. You deploy this package on already running instances.

What happens to them ? Do they reboot with the new package ? Does it spawn new instances and kill the current running ? Does it kill the running applications server in each instance and run the new one inside the new package ? What happens to the (non-persistant) local storage (if used as cheap cache) ? What happens to in-use sessions (if they are not stored in blob but only in-memory) ?

Is there any benchmark/comparative-table of different java servers inside Azure ? (memory footprint, concurrent connections, etc..

My questions might seem weird but I'm currently working with Google App Engine (and willing to move to Azure) and the only action I have to do to deploy/update an app is to click the Deploy button in eclipse. So currently, things are still quite confusing. But actually, the fact you have to upload your own jre and your own applications server adds a lot of freedom. It brings a piece of IaaS inside the PaaS.

will
  • 53
  • 7