subject:"\[flexcoders\] Re\: Can't connect to JMS with BlazeDS"

[flexcoders] Re: Can't connect to JMS with BlazeDS

2008-04-21 Thread meteatamel

Can you enable server side logging for JMSAdapter and let us know what
you are seeing? To enable server side logging, go to
services-config.xml and under logging section, make sure you have
debug level and under patterns, have Service.Message.JMS.

-Mete

--- In flexcoders@yahoogroups.com, Geoffrey [EMAIL PROTECTED] wrote:

 I'm trying to connect to our JMS service (Apache ActiveMQ), but am not
 having much luck.  Here are some config files.
 
 message-config.xml
 destination id=flex-jms-topic
   adapter ref=jms/
   properties
server
 allow-subtopicstrue/allow-subtopics
 subtopic-separator./subtopic-separator
/server
jms
 destination-typeTopic/destination-type
 message-typejavax.jms.TextMessage/message-type
 connection-factoryTopicConnectionFactory/connection-factory
 destination-jndi-nameGTBTopic/destination-jndi-name
 delivery-modeNON_PERSISTENT/delivery-mode
 message-priorityDEFAULT_PRIORITY/message-priority
 preserve-jms-headerstrue/preserve-jms-headers
 acknowledge-modeAUTO_ACKNOWLEDGE/acknowledge-mode
 max-producers1/max-producers
 initial-context-environment
  property
   nameContext.SECURITY_PRINCIPAL/name
   valueuserA/value
  /property
  property
   nameContext.SECURITY_CREDENTIALS/name
   valuepw123/value
  /property
  property
   nameContext.PROVIDER_URL/name
   valuetcp://localhost:61616/value
  /property
  property
   nameContext.INITIAL_CONTEXT_FACTORY/name
   valueorg.apache.activemq.jndi.
  ActiveMQInitialContextFactory/value
  /property
 /initial-context-environment
/jms
   /properties
 /destination
 
 
 I subscribe to this topic in my Application's creationComplete handler.
 // Subscribe to JMS topic
 __jmsTopicConsumer = new Consumer();
 __jmsTopicConsumer.destination = flex-jms-topic;
 __jmsTopicConsumer.subtopic = data.*;
 __jmsTopicConsumer.addEventListener(MessageEvent.MESSAGE,
 onJMSMessageResult);
 __jmsTopicConsumer.addEventListener(MessageFaultEvent.FAULT,
 onJMSMessageFault);
 __jmsTopicConsumer.subscribe();
 
 
 Here's my ActiveMQ configuration, which is mostly the default settings.
 activemq.xml
 beans xmlns=http://www.springframework.org/schema/beans;
xmlns:amq=http://activemq.org/config/1.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
 http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://activemq.org/config/1.0
 http://activemq.apache.org/schema/activemq-core.xsd
http://activemq.apache.org/camel/schema/spring
 http://activemq.apache.org/camel/schema/spring/camel-spring.xsd;
 
 bean

class=org.springframework.beans.factory.config.PropertyPlaceholderConfi\
 gurer/
   broker xmlns=http://activemq.org/config/1.0;
   brokerName=localhost
   dataDirectory=${activemq.base}/data
destinationPolicy
 policyMap
  policyEntries
policyEntry topic=FOO.
producerFlowControl=false
memoryLimit=1mb
dispatchPolicy
 strictOrderDispatchPolicy/
/dispatchPolicy
subscriptionRecoveryPolicy
 lastImageSubscriptionRecoveryPolicy/
/subscriptionRecoveryPolicy
   /policyEntry
  /policyEntries
 /policyMap
/destinationPolicy
transportConnectors
 transportConnector name=openwire
 uri=tcp://localhost:61616
 discoveryUri=multicast://default/
 transportConnector name=ssl
 uri=ssl://localhost:61617/
 transportConnector name=stomp
 uri=stomp://localhost:61613/
 transportConnector name=xmpp
 uri=xmpp://localhost:61222/
/transportConnectors
networkConnectors
 networkConnector name=default-nc
 uri=static://tcp://localhost:61616/
/networkConnectors
   /broker
   commandAgent config here
   jetty config here
 /beans
 
 
 I even configured a static topic.
 jndi.properties
 java.naming.factory.initial =
 org.apache.activemq.jndi.ActiveMQInitialContextFactory
 java.naming.provider.url = vm://localhost
 topic.MyTopic = FOO.MyTopic
 
 
 I know the static topic is created because I can go to the ActiveMQ web
 console and see the topic 'MyTopic' listed.
 
 Any help would be appreciated as I've been at this for a few days now.
 
 Thanks,
Geoff

[flexcoders] Re: Can't connect to JMS with BlazeDS

2008-04-21 Thread Geoffrey

This is all I see:

[BlazeDS] [Service.Message.JMS] JMS consumer for JMS destination
'MyTopic' is being removed from the JMS adapter due to the following
error: MyTopic
[BlazeDS] [Service.Message.JMS] JMS consumer for JMS destination
'MyTopic' is stopping.
[BlazeDS] [Service.Message.JMS] The corresponding MessageClient for
JMS consumer for JMS destination 'MyTopic' is being invalidated
[BlazeDS] [Service.Message] Warning: could not find MessageClient for
clientId in pushMessageToClients: 219F9B21-7B1A-57EA-730F-0051B4FBD6F1
for destination: flex-jms-topic
[BlazeDS] [Service.Message] Warning: could not find MessageClient for
clientId in pushMessageToClients: 219F9B21-7B1A-57EA-730F-0051B4FBD6F1
for destination: flex-jms-topic


--- In flexcoders@yahoogroups.com, meteatamel [EMAIL PROTECTED] wrote:

 Can you enable server side logging for JMSAdapter and let us know what
 you are seeing? To enable server side logging, go to
 services-config.xml and under logging section, make sure you have
 debug level and under patterns, have Service.Message.JMS.
 
 -Mete
 
 --- In flexcoders@yahoogroups.com, Geoffrey gtb104@ wrote:
 
  I'm trying to connect to our JMS service (Apache ActiveMQ), but am not
  having much luck.  Here are some config files.
  
  message-config.xml
  destination id=flex-jms-topic
adapter ref=jms/
properties
 server
  allow-subtopicstrue/allow-subtopics
  subtopic-separator./subtopic-separator
 /server
 jms
  destination-typeTopic/destination-type
  message-typejavax.jms.TextMessage/message-type
  connection-factoryTopicConnectionFactory/connection-factory
  destination-jndi-nameMyTopic/destination-jndi-name
  delivery-modeNON_PERSISTENT/delivery-mode
  message-priorityDEFAULT_PRIORITY/message-priority
  preserve-jms-headerstrue/preserve-jms-headers
  acknowledge-modeAUTO_ACKNOWLEDGE/acknowledge-mode
  max-producers1/max-producers
  initial-context-environment
   property
nameContext.SECURITY_PRINCIPAL/name
valueuserA/value
   /property
   property
nameContext.SECURITY_CREDENTIALS/name
valuepw123/value
   /property
   property
nameContext.PROVIDER_URL/name
valuetcp://localhost:61616/value
   /property
   property
nameContext.INITIAL_CONTEXT_FACTORY/name
valueorg.apache.activemq.jndi.
   ActiveMQInitialContextFactory/value
   /property
  /initial-context-environment
 /jms
/properties
  /destination
  
  
  I subscribe to this topic in my Application's creationComplete
handler.
  // Subscribe to JMS topic
  __jmsTopicConsumer = new Consumer();
  __jmsTopicConsumer.destination = flex-jms-topic;
  __jmsTopicConsumer.subtopic = data.*;
  __jmsTopicConsumer.addEventListener(MessageEvent.MESSAGE,
  onJMSMessageResult);
  __jmsTopicConsumer.addEventListener(MessageFaultEvent.FAULT,
  onJMSMessageFault);
  __jmsTopicConsumer.subscribe();
  
  
  Here's my ActiveMQ configuration, which is mostly the default
settings.
  activemq.xml
  beans xmlns=http://www.springframework.org/schema/beans;
 xmlns:amq=http://activemq.org/config/1.0;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://www.springframework.org/schema/beans
  http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
 http://activemq.org/config/1.0
  http://activemq.apache.org/schema/activemq-core.xsd
 http://activemq.apache.org/camel/schema/spring
  http://activemq.apache.org/camel/schema/spring/camel-spring.xsd;
  
  bean
 

class=org.springframework.beans.factory.config.PropertyPlaceholderConfi\
  gurer/
broker xmlns=http://activemq.org/config/1.0;
brokerName=localhost
dataDirectory=${activemq.base}/data
 destinationPolicy
  policyMap
   policyEntries
 policyEntry topic=FOO.
 producerFlowControl=false
 memoryLimit=1mb
 dispatchPolicy
  strictOrderDispatchPolicy/
 /dispatchPolicy
 subscriptionRecoveryPolicy
  lastImageSubscriptionRecoveryPolicy/
 /subscriptionRecoveryPolicy
/policyEntry
   /policyEntries
  /policyMap
 /destinationPolicy
 transportConnectors
  transportConnector name=openwire
  uri=tcp://localhost:61616
  discoveryUri=multicast://default/
  transportConnector name=ssl
  uri=ssl://localhost:61617/
  transportConnector name=stomp
  uri=stomp://localhost:61613/
  transportConnector name=xmpp
  uri=xmpp://localhost:61222/
 /transportConnectors
 networkConnectors
  networkConnector name=default-nc
  uri=static://tcp://localhost:61616/
 /networkConnectors
/broker
commandAgent config here
jetty config here
  /beans
  
  
  I even configured a static topic.
  jndi.properties
  java.naming.factory.initial =
  org.apache.activemq.jndi.ActiveMQInitialContextFactory

[flexcoders] Re: Can't connect to JMS with BlazeDS

[flexcoders] Re: Can't connect to JMS with BlazeDS

2 matches

Site Navigation

Mail list logo

Footer information