I have to set up a Hornetq Core-Bridge to a Hornetq 2.1.X Server, but I would like to use a more updated version on my side of the architecture (2.2.X). Is it compatible?
I haven't found info about it on documentation (as always btw, regarding to hornetq).
Obs: The 2.1.X Server is running on a JBoss AS, and mine is on stand-alone mode.
Until hornetq 2.2.2, hornetq didn't have version compatibility support. That means that you would need all your servers on the same version. (same as you would need for your clients).
After hornetQ 2.2.2 we offer version compatibility, however the client has to be older than the server. We don't test a 2.2.5 talking to a 2.2.2 server.
So, if the core-bridge is installed in a 2.2.2 talking to a 2.2.5, you would be fine.
a 2.2.5 talking to a 2.2.2.. probably not
A 2.1.X talking to 2.2.x.. definitely not.
Related
I am using neo4j-connector-apache-spark_2.11-4.0.2_for_spark_2.4.jar this connector with spark version 2.4.4, scala 2.11.12 and neo4j 3.3.x
Throwing this org.neo4j.driver.exceptions.ClientException: The server does not support any of the protocol versions supported by this driver. Ensure that you are using driver and server versions that are compatible with one another, while trying to read data from neo4j.
TL;DR
This error means that the underlying Neo4j driver is either very old (unlikely) or too recent (most likely) for the target Neo4j server.
You should either downgrade the Neo4j driver (and hope it is still compatible with the Spark connector) or upgrade the 3.3 server to 4.4 or 5.x (since 3.3 has reached EOL in 2019).
Long version
Neo4j drivers negotiate a Bolt protocol version with the server after establishing a connection. Drivers have a limited range of versions they can offer, so older protocol versions are excluded from newer driver releases. The server also offers a range of protocol versions it can support. The server then selects a version from the overlap of all these versions.
Since Neo4j server 3.3 has reached end of life in 2019 (see https://neo4j.com/developer/kb/neo4j-supported-versions/), the associated Bolt protocol version (1, according to the docs) has not been included in any recent drivers' negotiated version range.
Because of this, there is no overlap so no protocol version can be picked up and this error happens, reported back by the Java driver as a ClientException.
My organization's development environment is quite old and still uses JBoss 4.0.5 GA as a Development Application server. We would like to switch to modern servers such as wildlfly. What are the steps to be taken for the same? are there any resources available online for this? which version of Wildfly should we migrate to considering our application uses primarily JAVA EE8 API?
I have done everything possible from my end.
OS Linux data is coming from server.
but data of wildfly (i.e heap thread etc.) is not coming.
does anyone have template of wildfly 20?
There are several solutions widely available on the internet
Zabbix-JBoss-Agent
Zabbix_wildfly_eap_jboss_monitoring
WildFly (formerly JBoss) is a Java application and can be monitored with JMX agent
I would strongly recommend upgrading to a newer version of Zabbix, as version 4.0 will become unsupported on October 31, 2021.
JMSToolBox is a tool for browsing queues in a jms provider.
But it's not possible to configure it for browsing in JBoss EAP 6.3 (HornetQ 2.3).
Anyone tried this and can provide the right configuration?
Thanks in advance,
Mario
Update 2017-02-28:
With the help of the JTB author everything works now.
There was a problem in the version of JTB i used. This was fixed with JTB 3.8. The problem was that the bundled hornetq clients (version 2.4.x) had a problem with connecting to older versioned hornetq servers (version 2.3.x). This seemd to be a known bug.
The user/role used for the connection has to have the permission "manage".
#titou10: Thank you very much for your help!
I'm the author of JMSToolbox.
JTB should work with HornetQ. At least it does on my test workstation.
Did you follow the instructions to setup JMSToolBox for HornetQ?
What exact problem do you encounter?
Is communication by JMS between JBoss 5.x and JBoss 6.x possible?
Or do you need same version on both sides because of class version compatibility reasons?
JBoss 5 and 6 use different JMS implementations (JBoss Messaging and HornetQ, respectively), so I suspect that they're not interoperable. However, since HornetQ is based on the Jboss Messaging codebase, it's possible that the HornetQ broker in JBoss 6 can be made interopable, but it's not going to be easy.
I suggest trawling the HornetQ documentation to see if it's even possible.