wood burning stoves 2.0*
The moose likes Websphere and the fly likes Restarting Websphere Server after replacing jar in AppServer/lib Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Restarting Websphere Server after replacing jar in AppServer/lib" Watch "Restarting Websphere Server after replacing jar in AppServer/lib" New topic
Author

Restarting Websphere Server after replacing jar in AppServer/lib

manik prasad
Greenhorn

Joined: Oct 20, 2009
Posts: 3
While using Websphere 6.1, I needed to replace commons-collections.jar with commons-collections-3.2.jar in AppServer/lib location due to error of version conflict (org/apache/commons/collections/SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set. ) This server is on Linux machine and shares database server as well. Do I need to restart entire server or just restarting AppServer will take newer version of commons-collections-3.2.jar

Please help.

Thanks in advance.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18110
    
    8

What's this "entire server" you're asking about?
manik prasad
Greenhorn

Joined: Oct 20, 2009
Posts: 3
entire server means ....the server machine
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18110
    
    8

I thought it might mean that. If you want the Websphere application server to use a different classpath, then it's only necessary to restart the Websphere application server.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Restarting Websphere Server after replacing jar in AppServer/lib
 
Similar Threads
NoSuchMethodError
Fix Pack not working in WAS 3.5.3
MyFaces Tomahawk 1.1.7 Examples cannot be run using myfaces-core-1.2.5 lib
java.io.IOException: Error parsing - jsf-core.taglib.xml
bad major version at offset=6