Does anybody have any information on what this error means?
I'm upgrading an application from Weblogic 8.1/Java 1.4 to Weblogic 10.3 / Java 6. We have a Swing client that communicates with the Weblogic server. This error is appearing when trying to start the Swing client. I've traced it through to see that the swing client is successfully connecting to the server and that the server is performing the correct action. However, when the server is sending the response back to the client, I get the error below on the client side (there is no error on the server side).
I've checked classpaths and made sure that the client and the server are using the same JRE and all that good stuff -- although I'm hoping that it's something like that that I just missed. I've looked around and can't find any (useful) information on this error.
Piscis Babelis est parvus, flavus, et hiridicus, et est probabiliter insolitissima raritas in toto mundo.
This is a bit brute force, but have you tried mixing and matching more JDK and Weblogic versions? I'm thinking 1.5_17 with Weblogic 10.3 in particular. Also, what version of the JDK 6 are you using exactly?
As an update, I still haven't tried any 1.5 version (I've been entertaining other suggestions), but I did discover that the problem seems to stem from the fact that I'm sending multiple objects as a response.
You can see different tests as I experiment with what works and what doesn't, and you can also see that this is (mostly) pre-generic source code. Note the call to lcColl.isEmpty(); if I only put one VO in the list, it works. If there's more than one, it fails.
Also, I can see the error being thrown on the server side if I run the server through a debugger and trap for javax.rmi.MarshalExceptions.
I'm still not any further to solving this, as I would really, really like to return more than one of these VOs, but maybe this extra information will help someone say "Here's what the problem is..."
What does an actual ResponseVO and a LicensedComponentVO look like? I'm going out on a limb here but I'm wondering if some member variable/setting in there is causing problems when there are multiples of them (really going out on a limb here).