This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
1. Add WebSphere. Start it. Result: WebSphere started, but it's state in IDE is 'stopped'. 2. Restart IDE. Result: WebSphere started, but it's state in IDE is 'stopped'. 3. Restart WebSphere outside of IDE. Result: WebSphere started, but it's state in IDE is 'stopped'. 4. Close IDE and remove .netbeans. Start IDE. Add WebSphere. Result: WebSphere started ant it's state in IDE is 'started'.
Created attachment 36616 [details] IDE's log
This issue is approximately 40% reproducible. I found no dependencies on environment. The general behavior is as following: when IDE is started it either is in "good" shape when everything works just fine, or in "bad" when the following scenarios are experienced: 1. If Refresh action is invoked against WebSphere node and it is running, an exception is thrown and the icon is blinking in NB notification area (Exception is attached): java.lang.ClassCastException: com.ibm.ws.management.application.j2ee.deploy.spi.factories.DeploymentFactoryImpl 2. If Web Application targeting WebSphere server is opened or created an exception is thrown and the application cannot be opened. This also could happen if user starts IDE and there are some projects to be opened during start up which are WebSphere-targeted. (The exceptions are attached)
Created attachment 36851 [details] Exception from scenario 1
Created attachment 36852 [details] Exceptions from scenario 2
Created attachment 36853 [details] Exceptions from scenario 2 on IDE start up
I couldn`t reproduce the issue at all. I`ve tried the same JDK, netbeans, websphere module, locale, websphere server. I close the issue as WORKSFORME. Please reopen it if you find 100% steps of reproduction. The first possible reason of such a behavior is the firewall. Please turn it off and try to reproduce the issue. The other possible reason is the broken userdir. Please delete it entirely and try to reproduce the issue again.
Verified with NB 5.5 build 200610171010 on WinXP