ECLIPSE - slow deployment with WAS 6.0
in [Java Programming]
|
From: pramodr on 25 Jan 2010 04:46 Hi group, I am in the process of migrating one of the projects to WTP 1.5.4 (Eclipse 3.2) coupled with WAS 6.0. The development now happens with RAD 6.0. I found few problems - the foremost being the slow deployment and publishing of Eclipse. In RAD, I found that it is quite instantaneous publish (or is it just copying just the modified content ?) after saving jsp's which is not the case in Eclipse which takes quite a long time which is not at all acceptable. Can somebody give me a clue what is happening behind the scenes in both the cases and what to look for with some links ? regards Pramod R
From: Arved Sandstrom on 25 Jan 2010 05:26 pramodr wrote: > Hi group, > > I am in the process of migrating one of the projects to WTP 1.5.4 > (Eclipse 3.2) coupled with WAS 6.0. The development now happens with > RAD 6.0. I found few problems - the foremost being the slow deployment > and publishing of Eclipse. In RAD, I found that it is quite > instantaneous publish (or is it just copying just the modified > content ?) after saving jsp's which is not the case in Eclipse which > takes quite a long time which is not at all acceptable. Can somebody > give me a clue what is happening behind the scenes in both the cases > and what to look for with some links ? > > regards > Pramod R I haven't used Eclipse 3.2, which is about 4 years old, in some time, but I haven't used that version of WAS (which is about 6 years old) in some time either. Being forced to use another ancient J2EE 1.4 server on some other projects though, I feel your pain (even though for us we can at least use the latest Eclipse versions with no problems, as well as the latest JDKs). Speaking of which, what version of the JDK do you use? Also, when you say slow, and "long time", how bad is it? Having said that, if I were faced with the same situation, I think the first thing I'd do is review how much memory is assigned. The WAS documentation will certainly have some guidelines. Also, try doing the operations on the command line, leaving Eclipse completely out of the equation, and see what happens. AHS
From: pramodr on 25 Jan 2010 06:00 On Jan 25, 3:26 pm, Arved Sandstrom <dces...(a)hotmail.com> wrote: > pramodr wrote: > > Hi group, > > > I am in the process of migrating one of the projects to WTP 1.5.4 > > (Eclipse 3.2) coupled with WAS 6.0. The development now happens with > > RAD 6.0. I found few problems - the foremost being the slow deployment > > and publishing of Eclipse. In RAD, I found that it is quite > > instantaneous publish (or is it just copying just the modified > > content ?) after saving jsp's which is not the case in Eclipse which > > takes quite a long time which is not at all acceptable. Can somebody > > give me a clue what is happening behind the scenes in both the cases > > and what to look for with some links ? > > > regards > > Pramod R > > I haven't used Eclipse 3.2, which is about 4 years old, in some time, > but I haven't used that version of WAS (which is about 6 years old) in > some time either. Being forced to use another ancient J2EE 1.4 server on > some other projects though, I feel your pain (even though for us we can > at least use the latest Eclipse versions with no problems, as well as > the latest JDKs). > > Speaking of which, what version of the JDK do you use? Also, when you > say slow, and "long time", how bad is it? > > Having said that, if I were faced with the same situation, I think the > first thing I'd do is review how much memory is assigned. The WAS > documentation will certainly have some guidelines. > > Also, try doing the operations on the command line, leaving Eclipse > completely out of the equation, and see what happens. > > AHS Thanks AHS, In fact I tried J2RE 1.4.2 IBM Windows 32 build cn142-20040926 that is bundled with RAD. When I say slow, I mean it takes 2-3 minutes for each publish. I shall try out your suggestions. I heard somewhere that there was a deployment bug in WTP 1.5, which does a full deployment instead of an incremental one. Let me try out a later version and try that too. regards - Pramod
From: Lew on 25 Jan 2010 10:06 pramodr wrote: > In fact I tried J2RE 1.4.2 IBM Windows 32 build cn142-20040926 that is Any particular reason you use such an obsolescent Java version? -- Lew
From: Mike Schilling on 26 Jan 2010 18:22
Lew wrote: > pramodr wrote: >> In fact I tried J2RE 1.4.2 IBM Windows 32 build cn142-20040926 that >> is > > Any particular reason you use such an obsolescent Java version? Because he's using WAS 6.0, which doesn't support JDK 1.5. As I've explained in the past, those of us whose software has to run in containers are constrained by the conservatism of the container vendors, who feel no obligation to move to the latest version of Java, and further constrained by the conservatism of our customers, who feel no obligation to move to the latest version of the container. |