We're running WAS 184.108.40.206 under RAD 7.5.3, but in the past we have run WAS 6 under that same RAD. The performance downgrade from 6 to 7 is DRAMATIC.
First, there seems to be NO hot code feature anymore for debugging. Every time I change ANYTHING, regardless of whether the class was loaded or the interface of the class changed, the server needs to republish and restart. WAS6 allowed changes WHILE DEBUGGING THAT CLASS as long as you didn't add variables or change the method signatures, and would slide the instruction pointer to the top of the method upon rebuild. Very useful. WAS7 seems to have NO such capacity, and it doesn't even matter if that particular class hasn't even been loaded yet!
Second, and even more debilitating, is that almost every publish takes 5-10 minutes (sometimes more) regardless of how small the change.
This is unacceptably slow. I've seen some stuff online blaming annotation scanning. I added 'metadata-complete="true"' to my webapp node, and that helped a little, but not much. Further, the new app we're starting probably will need annotations, so I can't really get away with that.
I can't believe IBM just spiked their new release like this. I mean, IBM has always released BloatWare, but this is ridiculous. There must be some setting or something that is crippling this. Anyone have ideas?
I've got 3.5GB RAM. Note that WAS itself runs okay...it's the PUBLISH that is killing us.
Joined: Mar 12, 2009
I should also note that the publish times out fairly often. But a second publish usually succeeds.
In order to reduce publishes, i've been looking at using the plugin jRebel to do the hot deployments and it seems to be working. This is especially useful since RAD doesn't support hot deployments. JRebel supports most of the changes that I do on a daily basis, but there are still some changes that require publish such as Hibernate Config or J2EE bean changes, but most other code changes seem to work. The only negative is that the plugin is a bit expensive.
I'm looking into other things to reduce publish times, but I don't have anything definitive answers at this time.