We are seeing a classloader issue when we start WAS 184.108.40.206 from RSA 220.127.116.11 each time any of us does a publish of our application. We never see the error if we do a normal WAS startup.
We have run some traces and it looks as if the classloader tree has about 6 parents when WAS starts correctly, i.e. not doing a publish or republish, but has no parents when doing a publish, and we believe that this is the source of the exception.
Is there a way that we can specify the boot command or classpath for publish mode?
Pinned topic How could we fix a WAS startup classloading issue?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-07T14:03:38Z at 2012-12-07T14:03:38Z by SystemAdmin
Re: How could we fix a WAS startup classloading issue?2012-12-07T13:59:27ZThis is the accepted answer. This is the accepted answer.Hi,
you may have not unpublished your applications from another workspace.
Then you either deleted the projects of that other workspace but kept the workspace OR did a project clean without build OR deleted the complete workspace directory including the project.
You should start WAS, open the admin console and uninstall the applications with errors from there.
You can avoid this problem by either unpublishing the application from WAS before closing RAD
OR creating one profile for each workspace.
Re: How could we fix a WAS startup classloading issue?2012-12-07T14:03:38ZThis is the accepted answer. This is the accepted answer.The post was misconceived. Am going to mark it closed. We may post the actual problem at a later date, when we have more information.