Hermes Error Deserializing An Object

von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen

CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in weblogic.developer.interest.jms All PlacesOracle CommunityArchived ForumsArchived BEA Dev2Dev Forums (Read-only)WebLogic Server/Java EE Newsgroupsweblogic.developer.interest.jms This discussion https://groups.google.com/d/topic/weblogic.developer.interest.jms/m_sjlpSf3Rs is archived 6 Replies Latest reply on Aug 28, 2002 6:15 PM by 3004 JMS getObject() Error deserializing object for client 3004 Aug 27, 2002 3:38 PM I am using WL6.1 and having a problem deserializing an object for a client that doesn't have access to the https://community.oracle.com/thread/741760 corresponding implementation object in its CLASSPATH (it only deals with the interface). From previous posts, I read that upgrading to SP3 would fix this issue, but I am still having this problem on both Solaris and Windows using SP3. If I modify the client CLASSPATH to include the Server-side JAR file that contains the implementation class, I don't have the problem and I can successfully perform getObject() and deserialize the object. The following is the code for the client: public void onMessage(Message msg) { String msgText; if(msg instanceof ObjectMessage) { try { ObjectMessage objMsg = (ObjectMessage) msg; ActivityCreationEvent msgEvent = (ActivityCreationEvent) objMsg.getObject(); System.out.println("Got a creation event"); } catch(Exception ex) { System.out.println("Error getting JMS message:" + ex); ex.printStackTrace(); } } } the following is the code for the server: objMsg = tSess.createObjectMessage(null); ActivityCreationEvent createEvent=new ActivityCreationE

can be used to visually interact with JMS destinations (JMS Queues or JMS Topics). I find it convenient for ad hoc testing of JMS applications. I http://www.sjonsson.com/2015/03/jms-testing-with-hermesjms.html use it to monitor the status of JMS Queues, browse their contents, and to drop messages onto queues for testing purposes. When viewing a message in a JMS Queue, HermesJMS shows you the JMS headers and the value of the message payload, even if the payload is a serialization of a custom Java object. For example, in my current hermes error consulting engagement, we had a situation where we had a bad message stuck at the front of one of our JMS Queues (and due to invalid configuration our app kept processing that same message over and over, rather than proceeding onto the next message in the queue). Through the WebLogic Console we were able to see that there was a message hermes error deserializing in the queue that wasn't getting processed, but we couldn't see the actual content of the message that was causing it to get stuck. By connecting HermesJMS to the queue we could view the message payload and as a result identify and fix the issue. Browse Queue Contents The screenshot below shows an example of what browsing messages in a JMS Queue looks like: The table lists the JMS messages currently in the queue and the JMS headers for each message. Below the table is then a text rendering of the actual payload (typically a serialized Java object). In this example the payload is a Java class called HermesDemo with two properties, foo and bar (which I creatively concocted for this blog post :) 
 Drag Messages Between Queues Another handy feature of HermesJMS is that you can easily copy messages between queues. For example, if I click on the top message in the demo/Queue on my local machine I can drag it over to a queue in my testing environment (UAT): HermesJMS asks me to confirm the action and