I want to let you know that since the release of Caucho Resin 4.0, Atmosphere applications can be deploy on Resin and will be supported natively. Resin 4.0 implements Servlet 3.0.
That’s really good. Another web server that is supported.
What about the Websocket’s Caucho implementation… nah ! There implementation is too buggy right now. I suppose the code it using a early release of the Websocket specs, and never updated it. Anyway, Websocket application won’t work on Resin 4.0 
We posted a thread on there forum here : http://forum.caucho.com/showthread.php?t=10680
but still didn’t received news from them. So until they fix it, I suggest that you try your Websocket application on another web server like Glassfish.
You can follow me on Twitter
Just a little note that we try to add Websphere native support for Atmosphere. We work really hard to find an API that could allow us to do that, but is simply impossible.
We were able to get in touch with the dev team of Websphere and the dev team of WebSphere Application Server Feature Pack for Web 2.0. They have demo that used bayeux for comet application or JMS to simulate asynchronous connections, but it’s not a complete asynchronous solution.
Even with the addon WebSphere Application Server Feature Pack for Web 2.0, you can’t suspend and resume a connection. Websphere server doesn’t support that. It’s not supported in WAS 7.0, but in 8.0 alpha there should be Servlet 3.0 support.
Until IBM do something about that, or wait for WAS 8.0, you will still be able to deploy Atmosphere application on WAS but it will use BlockingIO (one blocking thread by connection).
If that is not enough for you, I suggest Glassfish as alternative. Of course, we will continue to monitor the situation. Maybe the community call could be enough to wakeup them 
You can follow me on Twitter
Just a little note that we try to add Websphere native support for Atmosphere. We work really hard to find an API that could allow us to do that, but is simply impossible.
We were able to get in touch with the dev team of Websphere and the dev team of WebSphere Application Server Feature Pack for Web 2.0. They have demo that used bayeux for comet application or JMS to simulate asynchronous connections, but it’s not a complete asynchronous solution.
Even with the addon WebSphere Application Server Feature Pack for Web 2.0, you can’t suspend and resume a connection. Websphere server doesn’t support that. It’s not supported in WAS 7.0, but in 8.0 alpha there should be Servlet 3.0 support.
Until IBM do something about that, or wait for WAS 8.0, you will still be able to deploy Atmosphere application on WAS but it will use BlockingIO (one blocking thread by connection).
If that is not enough for you, I suggest Glassfish as alternative. Of course, we will continue to monitor the situation. Maybe the community call could be enough to wakeup them
You can follow me on Twitter
Just to let you know that Grizzly Deployer was adopted by another framework : Atmosphere.
Since Atmosphere-0.6, Grizzly Deployer is in the module : spade-server
To launch Atmosphere application you could use Grizzly Deployer or use Atmosphere-Spade-Server (that used Grizzly Deployer under the hood).
You can browse the changes on github : http://github.com/Atmosphere/atmosphere/tree/master/extras/spade-server
I did the commit under the name “Unknown” It was my first git commit.
You can follow me on Twitter
