« Making del.icio.us work for me | Main | Values »

HELP: Developing with WebSphere

Listen to this articleListen to this article

I have to know. Is it just me or is the compile, deploy, debug cycle with WAS just so ridiculously long and slow that it's practically impossible to do anything productive with it? Does anyone ACTUALLY use WAS for development? If so, how do you manage? If not, what do you use instead and how do you then make sure that it still runs in WAS when it can take 10 minutes just to re-deploy an application? Is there some secret to determining why WAS silently rolls back transactions, for no apparent reason (WLTC0033W and WLTC0032W), before control has even returned to the container and with no exceptions; doesn't seem to be able set transaction isolation levels on SQL Server but instead creates extra connections with the correct isolation level (READ_COMMITTED) leaving the original one handed back from the DataSource as the default (REPEATABLE_READ); and mysteriously times-out waiting for Oracle connections from a pool of 10 even it only ever seems to need at most 3 when the maximum pool size is set to 100!

Comments

I'm using it in a current project, thru RAD 6 (another abomination in itself) and yes, it is slow as you say and even more. Redeploying is basically impossible, we restart it for every change; also, running it in debug mode is about 40% slower and hotspot class reloading does not work. I manage with *a lot* of patience and much cursing.

I hope to never experience the JDBC problems you mention as we're on DB2...

Are you using Eclipse or Websphere Studio? The developers I've worked with could only get real work done in an IDE.

It was a couple of years ago, but I remember running in Jetty locally, have WAS only on integrationservers. We got pretty proficient using jacl for our redeployment. But in general it was a miserable experience, WAS was riddled with bugs that were only fixed upgrading to the next major release.

WAS(6.0) is terribly slow but I could just update my class files in the deployed location and the EAR restarts by itself. I think JACL can also partially update a EAR without downtime.

Does anyone have solved the problem of the silently rolling back transaction ?
I have exactly the same problem.

Thank's

Post a comment