September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla edited comment on WFLY-7131 at 9/16/16 3:51 PM: ----------------------------------------------------------------- InitialContext is created with parameters - jmsuser, password, and BEEERequisitions.JndiProviderUrl=http-remoting://<ip-address>:<port> 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): InitialContext is created with 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 > Wildfly 10.0.Final Messaging System issue > ----------------------------------------- > > Key: WFLY-7131 > URL: https://issues.jboss.org/browse/WFLY-7131 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Preeta Kuruvilla > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla updated WFLY-7131: ----------------------------------- Attachment: standalone-full-WL-8.2.xml standalone-full-WL-10.0.Final.xml I have attached the standalone-full.xml for Wildfly 8.2 (which was working fine) as well as standalone-full.xml for Wildfly 10.0.Final (which is having this JMS related issue) for your reference > Wildfly 10.0.Final Messaging System issue > ----------------------------------------- > > Key: WFLY-7131 > URL: https://issues.jboss.org/browse/WFLY-7131 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Preeta Kuruvilla > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla updated WFLY-7131: ----------------------------------- Affects Version/s: 10.0.0.Final (was: 8.2.0.Final) > Wildfly 10.0.Final Messaging System issue > ----------------------------------------- > > Key: WFLY-7131 > URL: https://issues.jboss.org/browse/WFLY-7131 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla updated WFLY-7131: ----------------------------------- Summary: Wildfly 10.0.Final Messaging System issue (was: Wildfly 10 Messaging System issue) > Wildfly 10.0.Final 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla edited comment on WFLY-7131 at 9/16/16 3:33 PM: ----------------------------------------------------------------- InitialContext is created with 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 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 > 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue

by Preeta Kuruvilla (JIRA)

[ 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-338: ------------------------------------ Description: Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such. Analysis (and eventually design) document is at: https://developer.jboss.org/docs/DOC-55491 was:Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such. > Auto-promotion of slave HC to master > ------------------------------------ > > Key: WFCORE-338 > URL: https://issues.jboss.org/browse/WFCORE-338 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such. > Analysis (and eventually design) document is at: https://developer.jboss.org/docs/DOC-55491 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-338: --------------------------------------- Assignee: Brian Stansberry (was: Ken Wills) > Auto-promotion of slave HC to master > ------------------------------------ > > Key: WFCORE-338 > URL: https://issues.jboss.org/browse/WFCORE-338 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla commented on WFLY-7131: ---------------------------------------- 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla updated WFLY-7131: ----------------------------------- Attachment: standalone-full.xml The standalone-full.xml for Wildfly 10.0.0.Final is attached. > 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)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016