Job1: That exception means that the connection from the Java Desktop Client is getting improperly directed to a Twist that does not know about the Weblogic session id: 1029. This can happen if a twist is restarted and connected clients are not.
The issue was that our Core servers are on Red Hat Enterprise Linux 5.
Our Unix team had applied a particular kernel patch that did something to how network traffic was handled. As a result, our Java web client kept trying to communicate with various twist servers (we had 2 Slice bundles in our environment).
At the time, there was no solution other than to remove the patch. Technically, the patch couldn't be removed, what our Unix admins did was set the GRUB loader to boot to the previous kernel version. Support had told us that the issue was also present on the earlier releases of RHEL 6.
However, this issue was resolved in a later HPSA patch/hotfix. We didn't have the issue on 9.14 (I don't recall if a roll-up hotfix was necessary with 9.14).