aspose file tools*
The moose likes Websphere and the fly likes WebSphere 3.5 - Strange Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WebSphere 3.5 - Strange" Watch "WebSphere 3.5 - Strange" New topic
Author

WebSphere 3.5 - Strange

Kavita Saluja
Greenhorn

Joined: Jun 05, 2001
Posts: 19
I am working on Websphere3.5 on Solaris 2.7. The problem is that in our developement environment we have to deploy the bean more than one time ( after new changes ), sometimes what happens is that during deployment time ( we take the deployed jar from VAJ3.5) it gives an error like invalid zip file or some other error, Now if we rename the same jar file and then deploy it then theres no problem. Is it that WAS3.5 holds on the reference to the bean even after removing it (though this problem occurs rarely, but my point is that is it a bug in WAS)
The second and very important question is that we always have to restart the server if theres a slight change in our class file. We have a directory structure outside the installation directory of WebSphere on Solaris. Websphere is installed on /opt/WebSphere/AppServer while the directories for the application are in /xyz/application name/ . The directory structure is such that all the core files are in one directory and all the utility files are in other directory. So if theres a slight change in the class file, we have to restart the server. Is that so in WebSphere3.5.4, i mean do we always have to restart the server, if thats so then i m very disappointed, coz its not viable to start the server again and again especially in our developement environments since there are so many frequent changes as its a very big project.
I hope I will get a solution.
Thanks and Regards
Kavita
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Originally posted by Kavita Saluja:

The second and very important question is that we always have to restart the server if theres a slight change in our class file. We have a directory structure outside the installation directory of WebSphere on Solaris. Websphere is installed on /opt/WebSphere/AppServer while the directories for the application are in /xyz/application name/ . The directory structure is such that all the core files are in one directory and all the utility files are in other directory. So if theres a slight change in the class file, we have to restart the server. Is that so in WebSphere3.5.4, i mean do we always have to restart the server, if thats so then i m very disappointed, coz its not viable to start the server again and again especially in our developement environments since there are so many frequent changes as its a very big project.
Thanks and Regards
Kavita

If the directories you are referring to are those used by the EJB server (you didn't state if they are used by the EJB's or Servlets) then the answer is yes, you must restart the server. That is because Websphere 3.5.X does not feature "hot deploy" of EJB's. That is a feature of WebSphere 4.0.X.
On the other hand, if these are classes used by the servlet engine, then you can easily set it up so that the server will automatically pick up changes. Just make sure you have both directories on the web application classpath, and that you have enabled servlet reloading (refer to the documentation).
Kyle

------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Kavita Saluja
Greenhorn

Joined: Jun 05, 2001
Posts: 19
Thanks Kyle
Well the utility files I am referring to are the DAO's and the VO's and the specific Event clases. Since they are being used by the SessionBean (DAO's and VO's) then I guess we have to just restart the
server.
I am curious about the jar files question, why is it that if we just rename the same jar file then it gets deployed but otherwise it gives problems.
I will be very greatful if you can also answer one other question. For
using Admin Console remotely, we are doing it from NT to NT and Solaris to Solaris but it gives an error if we try to start the Admin Console from NT for Solaris. Is there any special thing that we have to do except for starting the AdminApplication.
Thanks and Regards
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Originally posted by Kavita Saluja:
Thanks Kyle
Well the utility files I am referring to are the DAO's and the VO's and the specific Event clases. Since they are being used by the SessionBean (DAO's and VO's) then I guess we have to just restart the
server.
I am curious about the jar files question, why is it that if we just rename the same jar file then it gets deployed but otherwise it gives problems.

I don't know about this one, sorry. These "happen sometime" errors are the tough ones. I've not seen anything like this in my experience, but it doesn't mean it doesn't happen.
I will be very greatful if you can also answer one other question. For
using Admin Console remotely, we are doing it from NT to NT and Solaris to Solaris but it gives an error if we try to start the Admin Console from NT for Solaris. Is there any special thing that we have to do except for starting the AdminApplication.
Thanks and Regards

The only thing I can think of is that the admin console is VERY sensitive to matching exactly on the patch level between console and server. Are you absolutely sure that the console and the server are running exactly the same patch level (e.g. 3.5.4 or 3.5.3?)
Kyle

------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
Kavita Saluja
Greenhorn

Joined: Jun 05, 2001
Posts: 19
Thanks Kyle
We are planning to move to WebSphere 4.0.1 in a month or so. I hope the server restart problem
will be resolved with that.
Thanks once again for your help
Sak Jtwoee
Greenhorn

Joined: Oct 08, 2003
Posts: 6
how to create Jar files for stateless session bean using jndi in ibm websphere3.5.4 .
very much thanks for reading this question. and please mail me with steps in WAS 3.5.4
 
 
subject: WebSphere 3.5 - Strange