Saturday, 15 August 2015

java - JBoss EAP6 Connection to external HornetQ Implementation doesn't work, but does with JBoss 7.1.1 -



java - JBoss EAP6 Connection to external HornetQ Implementation doesn't work, but does with JBoss 7.1.1 -

i trialing jboss eap6.

however have scheme solution has been implementated using jboss 7.1.1. , external hornetq 2.1.14 implementation. works jboss 7.1.1, eap 6 doesn't connect hornetq.

i running localhost. case doesn't work, or missing , configuration wrong?

hornetq configuration:

hornetq-beans.xml

<?xml version="1.0" encoding="utf-8"?> <deployment xmlns="urn:jboss:bean-deployer:2.0"> <bean name="naming" class="org.jnp.server.namingbeanimpl"/> <!-- jndi server. disable if don't want jndi --> <bean name="jndiserver" class="org.jnp.server.main"> <property name="naminginfo"> <inject bean="naming"/> </property> <property name="port">${jnp.port:1099}</property> <property name="bindaddress">${jnp.host:localhost}</property> <property name="rmiport">${jnp.rmiport:1098}</property> <property name="rmibindaddress">${jnp.host:localhost}</property> </bean> <!-- mbean server --> <bean name="mbeanserver" class="javax.management.mbeanserver"> <constructor factoryclass="java.lang.management.managementfactory" factorymethod="getplatformmbeanserver"/> </bean> <!-- core configuration --> <bean name="configuration" class="org.hornetq.core.config.impl.fileconfiguration"> </bean> <!-- security manager --> <bean name="hornetqsecuritymanager" class="org.hornetq.spi.core.security.hornetqsecuritymanagerimpl"> <start ignored="true"/> <stop ignored="true"/> </bean> <!-- core server --> <bean name="hornetqserver" class="org.hornetq.core.server.impl.hornetqserverimpl"> <constructor> <parameter> <inject bean="configuration"/> </parameter> <parameter> <inject bean="mbeanserver"/> </parameter> <parameter> <inject bean="hornetqsecuritymanager"/> </parameter> </constructor> <start ignored="true"/> <stop ignored="true"/> </bean> <!-- jms server --> <bean name="jmsservermanager" class="org.hornetq.jms.server.impl.jmsservermanagerimpl"> <constructor> <parameter> <inject bean="hornetqserver"/> </parameter> </constructor> </bean> </deployment>

hornetq-configuration.xml

<configuration xmlns="urn:hornetq" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:schemalocation="urn:hornetq /schema/hornetq-configuration.xsd"> <clustered>true</clustered> <paging-directory>${data.dir:../data}/node-a/paging</paging-directory> <bindings-directory>${data.dir:../data}/node-a/bindings</bindings-directory> <journal-directory>${data.dir:../data}/node-a/journal</journal-directory> <journal-min-files>10</journal-min-files> <large-messages-directory>${data.dir:../data}/node-a/large-messages</large-messages-directory> <connectors> <connector name="netty"> <factory-class>org.hornetq.core.remoting.impl.netty.nettyconnectorfactory</factory-class> <param key="host" value="${hornetq.remoting.netty.host:localhost}"/> <param key="port" value="${hornetq.remoting.netty.port:5445}"/> </connector> <connector name="netty-throughput"> <factory-class>org.hornetq.core.remoting.impl.netty.nettyconnectorfactory</factory-class> <param key="host" value="${hornetq.remoting.netty.host:localhost}"/> <param key="port" value="${hornetq.remoting.netty.batch.port:5455}"/> <param key="batch-delay" value="50"/> </connector> </connectors> <acceptors> <acceptor name="netty"> <factory-class>org.hornetq.core.remoting.impl.netty.nettyacceptorfactory</factory-class> <param key="host" value="${hornetq.remoting.netty.host:localhost}"/> <param key="port" value="${hornetq.remoting.netty.port:5445}"/> </acceptor> <acceptor name="netty-throughput"> <factory-class>org.hornetq.core.remoting.impl.netty.nettyacceptorfactory</factory-class> <param key="host" value="${hornetq.remoting.netty.host:localhost}"/> <param key="port" value="${hornetq.remoting.netty.batch.port:5455}"/> <param key="batch-delay" value="50"/> <param key="direct-deliver" value="false"/> </acceptor> </acceptors> <broadcast-groups> <broadcast-group name="bg-group1"> <group-address>231.7.7.7</group-address> <group-port>9876</group-port> <broadcast-period>5000</broadcast-period> <connector-ref>netty</connector-ref> </broadcast-group> </broadcast-groups> <discovery-groups> <discovery-group name="dg-group1"> <group-address>231.7.7.7</group-address> <group-port>9876</group-port> <refresh-timeout>10000</refresh-timeout> </discovery-group> </discovery-groups> <cluster-connections> <cluster-connection name="my-cluster"> <address>jms</address> <connector-ref>netty</connector-ref> <retry-interval>500</retry-interval> <forward-when-no-consumers>true</forward-when-no-consumers> <max-hops>1</max-hops> <discovery-group-ref discovery-group-name="dg-group1"/> </cluster-connection> </cluster-connections> <security-settings> <security-setting match="#"> <permission type="createnondurablequeue" roles="guest"/> <permission type="deletenondurablequeue" roles="guest"/> <permission type="consume" roles="guest"/> <permission type="send" roles="guest"/> </security-setting> </security-settings> <address-settings> <!--default grab all--> <address-setting match="#"> <dead-letter-address>jms.queue.dlq</dead-letter-address> <expiry-address>jms.queue.expiryqueue</expiry-address> <redelivery-delay>0</redelivery-delay> <max-size-bytes>10485760</max-size-bytes> <message-counter-history-day-limit>10</message-counter-history-day-limit> <address-full-policy>block</address-full-policy> <redistribution-delay>1000</redistribution-delay> </address-setting> </address-settings> </configuration>

jboss eap 6 configuration

standalone-ha.xml

key parts of file below:

<extensions> <extension module="org.jboss.as.clustering.infinispan"/> <extension module="org.jboss.as.clustering.jgroups"/> <extension module="org.jboss.as.configadmin"/> <extension module="org.jboss.as.connector"/> <extension module="org.jboss.as.deployment-scanner"/> <extension module="org.jboss.as.ee"/> <extension module="org.jboss.as.ejb3"/> <extension module="org.jboss.as.jaxrs"/> <extension module="org.jboss.as.jdr"/> <extension module="org.jboss.as.jmx"/> <extension module="org.jboss.as.jpa"/> <extension module="org.jboss.as.logging"/> <extension module="org.jboss.as.mail"/> <extension module="org.jboss.as.modcluster"/> <extension module="org.jboss.as.naming"/> <extension module="org.jboss.as.osgi"/> <extension module="org.jboss.as.pojo"/> <extension module="org.jboss.as.remoting"/> <extension module="org.jboss.as.sar"/> <extension module="org.jboss.as.security"/> <extension module="org.jboss.as.threads"/> <extension module="org.jboss.as.transactions"/> <extension module="org.jboss.as.web"/> <extension module="org.jboss.as.webservices"/> <extension module="org.jboss.as.weld"/> <extension module="org.jboss.snowdrop"/> </extensions> <interfaces> <interface name="management"> <inet-address value="${jboss.bind.address.management:127.0.0.1}"/> </interface> <interface name="public"> <inet-address value="${jboss.bind.address:127.0.0.1}"/> </interface> <interface name="unsecure"> <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/> </interface> </interfaces> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/> <socket-binding name="ajp" port="8009"/> <socket-binding name="http" port="8080"/> <socket-binding name="https" port="8443"/> <socket-binding name="jgroups-diagnostics" port="0" multicast-address="224.0.75.75" multicast-port="7500"/> <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/> <socket-binding name="jgroups-tcp" port="7600"/> <socket-binding name="jgroups-tcp-fd" port="57600"/> <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/> <socket-binding name="jgroups-udp-fd" port="54200"/> <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="23364"/> <socket-binding name="osgi-http" interface="management" port="8090"/> <socket-binding name="remoting" port="4447"/> <socket-binding name="txn-recovery-environment" port="4712"/> <socket-binding name="txn-status-manager" port="4713"/> <outbound-socket-binding name="mail-smtp"> <remote-destination host="localhost" port="25"/> </outbound-socket-binding> </socket-binding-group>

that won't compatible.. newer library can't talk older server.

up hornetq 2.2, wouldn't back upwards different versions @ on protocol, , started taking care of compatibility after 2.2... you're trying accomplish won't work.

java spring jboss jms hornetq

No comments:

Post a Comment