I have an app that runs on 8.2.1. The app connects to a third party application using their API. Among config attributes, the API needs two KeyStore objects to setup the connection. One for the SSL chain for the server cert, and one for the client certificate that the server requires to authenticate the connection coming from my WildFly instance.… Show more
I am running into HornetQ issue HQ222116 because I configured Unicast with Replication for my cluster. I need Unicast in my network, and I'd like to avoid the shared-storage journals. Unfortunately I am stuck with 8.2.1 for a few more months. That said, has anyone successfully updated just the HornetQ/Artemis module in WildFly 8.2.1?
Hello, I tried to setup a live/backend(HA) wildfly servers on AWS using S3_PING for a couple of days and no success. And S3 bucket has two files from both live and backup server for addresses when servers are up. I am able to test S3 with awscli on both machines(seems for me the S3 bucket configured fine). But live server always got "channel is… Show more
I just implemented a tcp/tcpping/replication/unicast cluster, and all my nodes start up with that same message: unable to start broadcast group bg-group1: java.lang.IllegalStateException: channel is closed My application seems to work fine, but I wish I could get rid of it. I'm seeing this in 8.2.1, which unfortunately is the latest supported…
I have two WildFly clusters (8.2.1, sorry, cannot be helped right now) on one subnet. Each cluster uses a different -u multicast address, yet there is still cross-talk. What else need to be made unique so the cross-talk will stop?
I am troubleshooting a multicast problem on my cluster, but while that is ongoing I also want to try to switch to unicast for my 3-node cluster. What is involved in reconfiguring an existing cluster from multicast to unicast?