spring-jms

问题 I have developed project using Spring JMS to receive the message from Queue. and it is deployed Websphere application Server (WAS 7.5) clustered environment. it is working fine once it is deployed in server.Later i have update my logger information and deployed in to server. it seems server not picking the latest code base. Even though i have stop/start the cluster. Please refer below config xml. <bean id="connectionFactory" class="com.ibm.mq.jms.MQQueueConnectionFactory"> <property name=

问题 What is the equivalent of destination-type from jms:listener-container in JavaConfig? I have checked in the API these two following classes without results. DefaultMessageListenerContainer MessageListenerAdapter I am trying to create consumers for a topic , many tutorials in the web use destination-type="topic" According with the 23.6 JMS Namespace Support section, there is the Table 23.2. Attributes of the JMS element table. Where for the destination-type attribute says: The JMS destination

问题 I have the following flow: 1) message-driven-channel-adapter -> 1.1) output-channel connected to -> service-activator -> outbound-channel-adapter (for sending response) 1.2) error-channel connected to -> exception-type-router 1.2.1) message is sent to different queues depending on the exception type using outbound-channel-adapter MessageDrivenChannelAdapter uses DefaultMessageListenrContainer and OutboundAdapter uses JMSTemplate Have used same cachingconnectionfactory for inbound and outbound

问题 I have WildFly 10.1.0.Final, this have Artemis 1.1.0 Whats the correct way of configure jndi.properties?: java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory java.naming.provider.url=http-remoting://127.0.0.1:8080 jboss.naming.client.ejb.context=false This worket with WildFly 9.0.0.Final that have HornetQ: java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory java.naming.provider.url=http-remoting://127.0.0.1:8080 jboss.naming

问题 Update It was my mistake I forget the ssl debugging running, it is super fast now and working like magic I have a Spring Boot application that connects to IBM MQ using spring JMS. I realized that the jmsTemplate is super slow compared to not using Spring at all. I am sure I have something not configured correctly. Hope Someone can help. I create a connection factory using IBM MQ 8 jar files. @Bean public ConnectionFactory connectionFactory() { properties.getCipherSpec()); MQConnectionFactory

问题 Two separate processes are communicating via JMS over MQ. The writer sets a string property: new MessageAction() { public void actOn(Message message) throws JMSException { logger.debug("Setting message property (GmmThreadId, CASHFLOW-1234)"); message.setStringProperty("GmmThreadId", "CASHFLOW-1234"); } }); This MessageAction is executed, as shown in the logs: Setting message property (GmmThreadId, CASHFLOW-1234) The reader uses a message selector to obtain this message. (using Spring's

问题 Like the title says.. I have read this valuable How to add multiple JMS MessageListners in a single MessageListenerContainer for Spring Java Config link The author of that post is working through messageListenerContainer.setMessageListener(new TaskFinished()); BTW: I use @Autowired private ConsumerListener consumerListener; defaultMessageListenerContainer.setMessageListener(consumerListener); I am not using the new operator. OK, the restriction of the setMessageListener method is: the class

问题 I have an requirement in my application to send files from one application to another over HTTP/FTP protocol. I found following link which tells that the same can be done using Active MQ with supoort of Blob messages: activemq.apache.org/blob-messages.html I configured ActiveMq 5.8 on my windows machine, included required dependency for ActiveMQ lib in my pom.xml and i am able to send the simple javax.jms.TextMessage and javax.jms.MapMessage with org.springframework.jms.core.JmsTemplate But

问题 I am setting up a JMS subscriber listener as follows with the goal of achieving a pool of 5 threads listening to topATopic, however, what I see at runtime is multiple consumers processing the same record (recordCount*#of consumers). I am assuming I am doing something wrong considering I am new to spring. <bean id="messageListener" class="com.abc.app.mdp.Receiver"> <property name="bean" ref="bean" /> </bean> <jms:listener-container container-type="default" connection-factory="connectionFactory

问题 Our system will not shutdown when a "Stop" command is issued from the Tomcat Manager. I have determined that it is related to ActiveMQ/Spring. I have even figured out how to get it to shutdown, however my solution is a hack (at least I hope this isn't the "correct" way to do it). I would like to know the proper way to shutdown ActiveMQ so that I can remove my hack. I inherited this component and I have no information about why certain architectural decisions were made, after a lot of digging