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.
Related
We are using Wildfly 10 and we want to use Red Hat AMQ 7 (standalone) remotely. I checked few documentation and found that ActiveMQ Artemis is also inbuilt in Wildfly 10, and I also configured it successfully to send and receive messages.
But as per our requirement, we want to use a remote AMQ broker so that it can be used as a centralized server and will be best suited in our enterprise requirement. Even I also want to understand the exact difference in using the ActiveMQ Artemis embedded in Wildfly and a remote Red Hat AMQ 7 instance, but I could not find enough information about it. If anyone is having any idea about it, please explain it.
I think there are three approaches to implement remote Red Hat AMQ.
Use the embedded ActiveMQ Artemis as a standalone server. I mean if we will install this Wildfly 10 in a separate server and if we can use that only for integration purpose and use the embedded ActiveMQ Artemis to connect with our Java application running on separate servers.
Install Red Hat AMQ 7.x as separate broker and connect it from the java application deployed on Wildfly 10. I checked Red Hat documentation and one point bothered me about this implementation as Red Hat claims "Currently AMQ 7.2 is only supported as a stand-alone broker. It has not be certified with EAP 7.0 or earlier. It is planned to be tested both as the internal broker of EAP 7.1 and as an external broker with EAP.". This is my preferred approach but I am not getting any documentation to implement it even Red Hat also not did it yet.
Install Apache ActiveMQ Artemis 2.x and integrate it from the application deployed in Wildfly 10.
I tried to get this information but as of now there is not much information available on internet for Artemis. It will be a great help if someone can explain the differences with pros and cons in above approaches.
Regard's
Ram
Configuring Apache's mod_jk (used just as a proxy, not as loadbalancer) is supported with JBoss 5.x Community Server?
Instead of using mod_jk, mod_cluster is a better option for JBoss. It also has support for sticky session and session replication. Mod_cluster works both with Wildfly/JBoss AS since version 5 and with Tomcat 6+. If you are looking only for mod_jk, JBoss documentation can help. Mod_cluster doc and info: http://modcluster.io
We are migrating from old Fuse Source ESB to JBoss Fuse ESB 6.2 version, so we look for better deployment strategies using the newer version of JBoss Fuse ESB 6.2 with Disaster recovery (multi data center deployments) & with in same data center - a Master/Slave (Primary/Secondary) nodes with automatic fail over options.How to achieve this in newer version?
Based on your requirements, I believe Fuse Fabric will work well. You can read more here
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Getting_Started/files/Deploy-Scalable.html
What is the question exactly? What is your architecture?
DR for what, Fabric, A-MQ, Camel containers...
I've blogged on the topic here that might be a good start.
We would like to use mutual-authentication to secure a communication between a Java program running on Redhat JBoss 6 and a Java service running on Redhat JBoss 5.1.2. In other words, mutual-authentication where JBoss is both the client and the server. Is this possible? Some people say that JBoss Application Server can only handle the handshake if JBoss is at the role of the server only. Is this true? Thanks.
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.