Hi Folks; I'm still following up on the various 26B's we started seeing after upgrading to 5.1.1 + Solaris patches + java.
Per prior advice, we've backed java down to the one shipped in Solaris. 1. POSSIBLE BUG but WORKAROUND FOUND - somewhat coincidentally, we got our first large scale batch of SunRay 3's in, and deployed. In one install with >40 sunrays, a single sunray 3 replaced a sunray 2. That site also has a few users with the old 'Sun Branded' smart cards. We have now confirmed that 'Sun Branded' cards do not work in any of the 3 series sunray. Those cards work perfectly in any of the SunRay 2's (same sun ray servers, etc). From the SunRay Server side, the cards are identified as 'unknown.unknown'. When these cards are inserted into a SunRay 3, the OSD is 26, hence what we saw. Tested cards in Sunray 3 and 3+, same result. a. Oracle guys: do you know if this was deliberate, or might a firmware fix correct? Didn't like the sun logo on the cards, so made them stop working? ;) b. Current workaround is to re-issue cards to replace old Sun branded cards (I believe they may have been PayFlex). 2. utauthd crash. Hasn't happened since. Hoping it was related to java version, which was adjusted to be 1.6.0_13 included with SRSS distribution. 3. Floating 26B's over working uttsc session. We are getting not zero reports of this still. But since this is no longer confused with the 26B's in item #1 above, the occurrence of this symptom is extremely low and we are not spending any major time. If we come across easy to diag situation, we'll certainly investigate and report in. Thanks, Devin
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
