Home » Language IDEs » ServerTools (WTP) » Probleme using Websphere in WTP
| Probleme using Websphere in WTP [message #165276] |
Wed, 29 March 2006 05:12  |
Eclipse User |
|
|
|
Originally posted by: laurent.piroelle.westcast-systems.com
Hello,
I'm trying to use Websphere in WTP but I don't achieve to start it.
When I launch it, it takes long time, writes nothing in the console, and
after long time, I've got this error message "Timeout waiting for IBM
WebSphere 6 to start. Server did not start after 300000s."
Any idea of what it could be ?
I'm using the latest version of eclipse all-in-one WTP with a trial
version of WebSphere 6.
Program arguments for starting WebSphere are (cell and node values are
good) :
com.ibm.ws.runtime.WsServer
" D:/users/lpiroelle/AppServeurs/WebSphere/profiles/default/co nfig "
"varnaNode02Cell" "myNode" "server1"
and JVM arguments (I'm using IBM jvm furnished with WebSphere) :
" -Duser.install.root=D:/users/lpiroelle/AppServeurs/WebSphere /profiles/default "
" -Dserver.root=D:/users/lpiroelle/AppServeurs/WebSphere/profi les/default "
"-Dwas.install.root=D:/users/lpiroelle/AppServeurs/WebSphere "
" -Dcom.ibm.itp.location=D:/users/lpiroelle/AppServeurs/WebSph ere/bin "
" -Dws.ext.dirs=D:/users/lpiroelle/AppServeurs/WebSphere/java/ lib;D:/users/lpiroelle/AppServeurs/WebSphere/profiles/defaul t/classes;D:/users/lpiroelle/AppServeurs/WebSphere/classes;D :/users/lpiroelle/AppServeurs/WebSphere/lib;D:/users/lpiroel le/AppServeurs/WebSphere/installedChannels;D:/users/lpiroell e/AppServeurs/WebSphere/lib/ext;D:/users/lpiroelle/AppServeu rs/WebSphere/web/help;D:/users/lpiroelle/AppServeurs/WebSphe re/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime "
-Xbootclasspath/p:D:/users/lpiroelle/AppServeurs/WebSphere/j ava/jre/lib/ext/ibmorb.jar;D:/users/lpiroelle/AppServeurs/We bSphere/java/jre/lib/ext/ibmext.jar
-Xms50m -Xmx256m
" -Dcom.ibm.CORBA.ConfigURL=file:D:/users/lpiroelle/AppServeur s/WebSphere/profiles/default/properties/sas.client.props "
" -Dcom.ibm.SOAP.ConfigURL=file:D:/users/lpiroelle/AppServeurs /WebSphere/profiles/default/properties/soap.client.props "
" -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManage r "
"-Djava.util.logging.configureByServer=true"
"-Dibm.websphere.preload.classes=true"
" -Djava.library.path=D:/users/lpiroelle/AppServeurs/WebSphere /java/bin;D:/users/lpiroelle/AppServeurs/WebSphere/bin;D:/us ers/lpiroelle/AppServeurs/WebSphere/java/bin;D:/users/lpiroe lle/AppServeurs/WebSphere/java/jre/bin "
Thanks for answering
|
|
|
| Re: Probleme using Websphere in WTP [message #165427 is a reply to message #165276] |
Thu, 30 March 2006 15:44  |
| Eclipse User |
|
|
|
Laurent,
Does it start OK when you start WebSphere from its own start options?
Is it WebSphere 6.0?
This sounds a little like an experience that many others have had with
RAD6 and WAS6 since they were first released back at the end of 2004,
and it's still not fixed. The two of them do not play well together,
but are quite contented when you keep them in separate playpens.
Does this long time to start occur when you have stopped the server
previously? The problem I encountered in late 2004 with RAD6 and WAS6
was particularly bad with a restart, sometimes it took 45 minutes or
more to restart the WebSphere Server from within RAD6, whereas you could
do it in 30 seconds by killing the java process that the WTE ran in.
If your experience of lengthy start times occurs after stopping the
server, try killing the java process (NOT the javaw process!!!) from the
task manager after you issue the stop command, and before you issue the
start command, and see if that helps. Be careful to choose the right
java process, though!!! Usually it is rather large in memory, like well
over 100MB in size, so that may help you to distinguish it, in the task
manager's window, from other java things you may have running.
Messy and crude, I know, but mostly it works OK and avoids a reboot,
which is the only alternative.
Chris
|
|
|
| Re: Probleme using Websphere in WTP [message #165480 is a reply to message #165427] |
Fri, 31 March 2006 02:43 |
| Eclipse User |
|
|
|
Originally posted by: laurent.piroelle.westcast-systems.com
Chris,
Thanks for your answer.
I can easily start WAS6 (trial) in a standalone context but I've never
achieved to start it with WTP. When I run it, I've got another javaw
process (not java, it's defined in WTP server properties), even if it
takes 140Mb of memory, it doesn't make anything and WTP sends me the
timeout message after 6 minutes but the process is still running and the
server status in WTP is still "starting...".
I've just seen one important thing : the server is really started even
if I've got an error message, I can access it.
Thanks
Laurent
Chris Gage a écrit :
> Laurent,
>
> Does it start OK when you start WebSphere from its own start options?
>
> Is it WebSphere 6.0?
>
> This sounds a little like an experience that many others have had with
> RAD6 and WAS6 since they were first released back at the end of 2004,
> and it's still not fixed. The two of them do not play well together,
> but are quite contented when you keep them in separate playpens.
>
> Does this long time to start occur when you have stopped the server
> previously? The problem I encountered in late 2004 with RAD6 and WAS6
> was particularly bad with a restart, sometimes it took 45 minutes or
> more to restart the WebSphere Server from within RAD6, whereas you could
> do it in 30 seconds by killing the java process that the WTE ran in.
>
> If your experience of lengthy start times occurs after stopping the
> server, try killing the java process (NOT the javaw process!!!) from the
> task manager after you issue the stop command, and before you issue the
> start command, and see if that helps. Be careful to choose the right
> java process, though!!! Usually it is rather large in memory, like well
> over 100MB in size, so that may help you to distinguish it, in the task
> manager's window, from other java things you may have running.
>
> Messy and crude, I know, but mostly it works OK and avoids a reboot,
> which is the only alternative.
>
> Chris
|
|
| |
| Re: Probleme using Websphere in WTP [message #165861 is a reply to message #165846] |
Tue, 04 April 2006 12:13 |
| Eclipse User |
|
|
|
Originally posted by: laurent.piroelle.westcast-systems.com
Hi Wolfgang,
I use the IBM JVM to run WebSphere and has done many searches before
posting here and still haven't found what I'm looking for.
Thanks for your help.
Laurent
Wolfgang Knauf a écrit :
> Hi Laurent,
>
> There are some posts in this newsgroup about WebSphere server. I think
> you have to use the integrated IBM JDK to start the server, not some Sun
> or other runtime. Do you do this already ?
>
> Hope this helps
>
> Wolfgang
>
> Laurent Piroelle wrote:
>> Chris,
>>
>> Thanks for your answer.
>>
>> I can easily start WAS6 (trial) in a standalone context but I've never
>> achieved to start it with WTP. When I run it, I've got another javaw
>> process (not java, it's defined in WTP server properties), even if it
>> takes 140Mb of memory, it doesn't make anything and WTP sends me the
>> timeout message after 6 minutes but the process is still running and
>> the server status in WTP is still "starting...".
>>
>> I've just seen one important thing : the server is really started even
>> if I've got an error message, I can access it.
>>
>> Thanks
>>
>> Laurent
>>
|
|
|
| Re: Probleme using Websphere in WTP [message #165869 is a reply to message #165861] |
Tue, 04 April 2006 12:24 |
| Eclipse User |
|
|
|
Originally posted by: wknauf_NO_._INSIDE_hg-online.de
Hi Laurent,
Do the websphere log files provide you with any information ?
Best regards
Wolfgang
Laurent Piroelle wrote:
> Hi Wolfgang,
>
> I use the IBM JVM to run WebSphere and has done many searches before
> posting here and still haven't found what I'm looking for.
>
> Thanks for your help.
>
> Laurent
>
|
|
|
Goto Forum:
Current Time: Fri Nov 07 23:36:32 EST 2025
Powered by FUDForum. Page generated in 0.07493 seconds |
Home