In flex-enterprise-services.xml, enable logging and the debug
level and check your server console for errors.
Another thing that might be helpful is ensure that you can
reach the destinations via jndi.
You can do this by using a jsp page. If the page runs without
stack traces, then you know that your jndi and jms factory and
destination are configured correctly. Be sure to update
flex-message-service.xml with those jndi names.
jndiTest.jsp
<%@ page import="javax.naming.*,javax.util.*" %>
<%
Properties p = new Properties();
// as configured in your destination's
initial-context-environment in flex-message-service.xml
p.setProperty("java.naming.factory.initial","com.sonicsw.jndi.mfcontext.MFContextFactory");
p.setProperty("com.sonicsw.jndi.mfcontext.domain","Domain1");
p.setProperty("java.naming.provider.url","tcp://jmsserver:2506");
p.setProperty("java.naming.security.principle","jms_user");
p.setProperty("java.naming.security.credentials","jms_pass");
Context ctx = new InitialContext(p);
ctx.lookup("MessagingTopic"); // this maps to
connection-factory on the destination in flex-message-service.xml
ctx.lookup("GlobalEvents"); // this maps to
destination-jndi-name on the destination in
flex-message-service.xml
%>
/* If you get an exception running with the above try,
generally application servers make resource available to the
application at java:comp/env/<resource-name>. In the app.xml,
you've specified GlobalEvents as the resource name. I don't see
MessageTopic specified in app.xml, which may be an issue. Once you
have these lookup calls running, you should go back and update
flex-message-service.xml with these jndi names.
ctx.lookup("java:comp/env/GlobalEvents");
ctx.lookup("java:comp/env/MessageTopic");
*/