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.
Build21: Deploy the stock sample with SAML-HoldOfKey profile. The following exceptions are in the ide output window. Tried again; it was OK. Saw the exception on solaris and on windows.
Created attachment 34718 [details] exceptions
Created attachment 34719 [details] snapshot
I am not sure why this is a P3? The first exception from the solaris output(Invalid session ID) is a harmless one and laready fixed to be removed in next AM build. But the FATAl exception seems like a serious one. Peter, can u pls check when this error occurs if the deployment succeeds in other words are the changes pushed to the ideRepo? If it is, then I agree both are harmless exceptions and the priority can be lowered to P3. If they are not harmless then this priority should stay as P2 since this is a stopper issue with a workaround of redeployment. So, increasing priority and assigning it to Peter.
Redeployment was OK and stocksample worked, so put it as p3.
I didn't see the FATAL EXCEPTION in the attachment until Vidhya pointed out to me. This looks to be the same issue as 86096. Note that this bug happens when there is already a successfully connection to an instance of am server whether local or remote. If you try to connect to a different instance for the first time, you'll get this exception and it is truely FATAL. Howerver, for some reason, subsequent connections will succeed. Malla has a new amclientsdk.jar that he thinks has the fix for this problem. I am going to test it out and see if it fixes this issue.
Well, the new amclientsdk.jar didn't fix the problem. Since there is already a bug filed against the am team in bugster, 6476524, I closed this bug with wontfix.