Thanks, James. Yes, I'm also inclined to think it's a class loader issue. But then, how come it doesn't happen all the time? What may cause it to load another version of the class only some of the times? Does ActiveMQ do anything... um, unconventional with class-loading?
Thanks, Naaman James.Strachan wrote: > > If you get a ClassCastException yet the object seems to be of the > correct class name, then it looks like a class loader issue (multiple > versions of the same class on the classpath). Otherwise if it was a > serialization issue, you wouldn't get an object you can inspect. > -- View this message in context: http://www.nabble.com/ClassCastException-on-MessageObject%27s-object-tf3671759s2354.html#a10264576 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
