Hello All, thanks for helping... I stopped and started with jconsole and i stopped only the route, not the whole context, but it was actually just for testing purposes.
"Storing" is a little bit too much said, i guess. These Objects are only for a short period time on the queue. They are the "Command Messages" for a batch. When the Batch is over, there shouldn't be any messages on the queue. I'm defining workloadchunks in form of a java-object (WLChunk as you can see, it is the class that is not found after route stop/start). in a camel-route. I put a lot of those on a queue, from which my route (that i stopped and started) distributes on the WebSphere cluster. Actually starting stopping was just for some sort of testing purposes, i have another (quartz-triggered) route that observers all that with that BrowsableEndpoint-Interface... Right i don't have too much test-data and i just wanted to control the processing of the queue. I think you can say: See how it works just for test. But i got little disturbed with the fact, that i couldn't start/stop my route as i wished. Not that this is big problem, but i wanted to know why it doesn't work. (because maybe i get this problem eventually) So you say it is preferable to use jms.Textmessages instead of jms.Objectmessages? Thanx, Martin Claus Ibsen-2 wrote: > > Hi > > Are you sure you want to store serialized objects on the WebSphereMQ ? > > You could maybe consider storing text instead? For example you can > marshal to/from objects using XML, JSon etc. > With XML you can use JAXB etc. > -- View this message in context: http://old.nabble.com/Serialzable-Classnotfoundexception-after-route-stop-start-tp28878193p28888778.html Sent from the Camel - Users mailing list archive at Nabble.com.
