2:33 p.m.
[
https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin....
]
Preeta Kuruvilla edited comment on WFLY-7131 at 9/16/16 3:32 PM:
-----------------------------------------------------------------
The above is used to create the InitialContext along with the other parameters - jmsuser,
password, and
BEEERequisitions.JndiProviderUrl=http-remoting://10.76.80.29:6080
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting
in the queues. This is not consistent as sometimes messages are getting processed.
Thanks,
Preeta
was (Author: kpreeta12):
The client class that does the lookup for the JMS jndi does using the below
BEEERequisitions.JmsQueueFactory=jms/RemoteConnectionFactory
BEEERequisitions.JmsQueue=jms/queue/BEEERequisitionsQueue
BEEEAuthorizations.JmsQueueFactory=jms/RemoteConnectionFactory
BEEEAuthorizations.JmsQueue=jms/queue/BEEEAuthorizationsQueue
BEEEInbound.JmsQueueFactory=jms/RemoteConnectionFactory
BEEEInbound.JmsQueue=jms/queue/BEEEInboundQueue
ISEEOutbound.JmsQueueFactory=jms/RemoteConnectionFactory
ISEEOutbound.JmsQueue=jms/queue/ISEEOutboundQueue
The above is used to create the InitialContext along with the other parameters - jmsuser,
password, and
BEEERequisitions.JndiProviderUrl=http-remoting://10.76.80.29:6080
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Let me know if you need any more info.
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting
received in the queues. This is not consistent as once in a while messages are getting
processed.
Thanks,
Preeta
Wildfly 10 Messaging System issue
---------------------------------
Key: WFLY-7131
URL: https://issues.jboss.org/browse/WFLY-7131
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 8.2.0.Final
Reporter: Preeta Kuruvilla
Assignee: Jeff Mesnil
Priority: Blocker
Attachments: standalone-full.xml
Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS
message broker.
The HornetQ code base was donated to the Apache ActiveMQ community late last year and now
resides as a sub project under the ActiveMQ umbrella named 'Artemis’.
http://activemq.apache.org/artemis.
http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from
Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we
configured the messaging subsystem in standalone-full.xml:-
Let me know if this is good. Also I am attaching the entire standalone-full.xml with this
case.
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
<server name="default">
<security enabled="false"/>
<statistics enabled="true"/>
<security-setting name="#">
<role name="guest"
delete-non-durable-queue="true" create-non-durable-queue="true"
consume="true" send="true"/>
<role name="jmsrole"
delete-non-durable-queue="true" create-non-durable-queue="true"
consume="true" send="true"/>
</security-setting>
<address-setting name="#"
message-counter-history-day-limit="10" page-size-bytes="2097152"
max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue"
dead-letter-address="jms.queue.DLQ"/>
<http-connector name="http-connector"
endpoint="http-acceptor" socket-binding="remote-http"/>
<http-connector name="http-connector-throughput"
endpoint="http-acceptor-throughput" socket-binding="http"/>
<in-vm-connector name="in-vm"
server-id="0"/>
<http-acceptor name="http-acceptor"
http-listener="default"/>
<http-acceptor name="http-acceptor-throughput"
http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver"
value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm"
server-id="0"/>
<jms-queue name="testQueue" entries="queue/test
jboss/exported/jms/queue/test"/>
<jms-queue name="ISEEOutboundQueue"
entries="/ISEEOutboundQueue
java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
<jms-queue name="ISEEInboundQueue"
entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
<jms-queue name="BEEEAuthorizationsQueue"
entries="/BEEEAuthorizationsQueue
java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
<jms-queue name="BEEERequisitionsQueue"
entries="/BEEERequisitionsQueue
java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
<jms-queue name="BEEEInboundQueue"
entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
<jms-topic name="testTopic" entries="topic/test
java:jboss/exported/jms/topic/test"/>
<connection-factory name="InVmConnectionFactory"
entries="java:/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="RemoteConnectionFactory"
entries="java:jboss/exported/jms/RemoteConnectionFactory
/RemoteConnectionFactory" connectors="http-connector"/>
<pooled-connection-factory name="activemq-ra"
transaction="xa" entries="java:/JmsXA
java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
</server>
</subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)