Mantis Bugtracker
  

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0005291 [Resin] minor always 11-27-12 14:18 09-08-14 17:14
Reporter ferg View Status public  
Assigned To ferg
Priority normal Resolution no change required  
Status closed   Product Version 4.0.32
Summary 0005291: jms message destination not set
Description (rep by Daniel Ziegelbein)

FYI, I got this working?kind of.

After getting past the JNDI issue (just had to set the JNDI name of the ClusterTopic and JmsConnectionFactory), I had a problem where EclipseLink would throw an exception upon receipt of a cache coordination message because the message's destination was null.

To make it work, I had to use a Message Driven Bean, inject an instance of ClusterTopic in that bean and explicitly set the message destination in the onMessage method of the MDB (setting it to the injected ClusterTopic instance). It doesn't seem right that the message destination is null, but if this is a legitimate work-around then I'm fine with it.

Can anyone shed more light on this? Is this a legitimate work-around?

Additional Information
Attached Files

- Relationships

There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
11-27-12 14:18 ferg New Issue
09-08-14 17:14 ferg Assigned To  => ferg
09-08-14 17:14 ferg Status new => closed
09-08-14 17:14 ferg Resolution open => no change required


Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed.
24 unique queries executed.
Powered by Mantis Bugtracker