Is it possible to configure multiple external activemq for wildfly? I have two external activemq that runs on different port and url, can I configure them for one wildfly?
Related
I am new to Apache Ignite. I have an application for which I am trying to utilize Apache Ignite for a distributed cache.
I currently have 3 servers to process to serve the incoming requests and if one server is down, one of the other two servers would need to handle the request.
I have configured the "REPLICATED Cache" in the Cache Configuration and have configured the IP Address for the servers in use using "TcpDiscoveryVmIpFinder".
The topology snapshot always shows me one client and one server when all three servers are up, and killing one server disconnects the client node even if the other two servers are still up.
I am having the same issue when using multicast node discovery. One server is identified and the other two servers do not join the topology even though they have the same multicast group configuration.
I have a Google Cloud Container Engine cluster with 2 Pods, master and slave. Each of them runs RabbitMQ instance, that supposed to be joined into one cluster.
Ports exposed from Dockers aren't available from other machine, but could be accessed only through a Service. That's not a problem, I could establish a service for each instance (one-to-one, service-to-pod), and point each Pod to opposite service IP.
The problem that RabbitMQ uses more that one port for communications. That means that service IP should open all this ports from underlying Pod. But I cannot specify list of shared port for a Service, and if I create a new service for each port each of them will have own IP.
Is there any way to expose list of ports from same Docker/Pod on same internal IP address using Container Engine cluster? maybe some special routing configuration?
Your question is similar to this question, and unfortunately has the same response: Kubernetes / Google Container Engine does not currently have a way to expose a range of ports for a service at the current time. There is an open issue in GitHub to address this use case.
Are you aware of a mod_proxy, mod_proxy_balancer, mod_proxy_http configuration of Apache 2.2 that would allow HTTP requests to be replicated? That is: each matched request is sent to an existing balancer AND replicated to an another worker node.
Goal:
Take production HTTP traffic coming into Apache 2.2, retain normal production load-balanced routing AND replicate that same traffic to one more [test] worker fronting a new back-end database required to be performance and load tested under production operations.
Background info:
Multi-tier system.
(a) Custom applications
(b) Redirector/Proxy [Apache 2.2 using mod_proxy, mod_proxy_balancer, mod_proxy_http]
(c) Workers [application server nodes: Tomcat 7.0.56 over Java 1.7.0_67 over 64-bit Linux kernels]
(d) Database [Oracle 11.2]
End-users driving custom applications generate HTTP requests funneled to the redirector. The redirector forwards application requests on a round-robin basis to a pool of worker nodes. Workers directly access backend database. HTTP responses funnel back through the redirector to the end-user workstation.
No, it is not currently possible. But you can save the traffic and replay it with a relatively new module called mod_firehose. But it is not an all in one tool.
I'm trying to understand the topology of Worklight. Specifically how does a WL Server handles its applications.
If I understood correctly, a WL Server has a <httpEndpoint>. This means that a set of WL Applications will have their context root on that port. Right?
This means, If I want to put /worklightconsole on a custom port, I'll need a network installation instead of a standalone so that I can have a cluster of WL instances and each one will bind to a different port.
Did I understood this matter correctly? Then I can use a reverse proxy to needle my requests to the correct instance of WL Server.
Right?
Thanks in advance!
http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.1.0/com.ibm.worklight.installconfig.doc/admin/c_typical_topology_of_an_ibm_wor.html
Yes the httpEndpoint entry defines the http and https port and the WL applications have their context root on these ports.
If you have different Liberty Servers with the same WL runtime, be sure that the you share the same database and same schema.
After that you can use a Web Proxy to load balance the requests between the different Liberty servers.
Is it possible to use activemq brokerservice without port number. I am using activemq as embeded to write my app logs to DB. But I am in trouble with open ports while side by side deploying to the weblogic
If you only need in VM client connections you can use ActiveMQ's VM Transport and not add any other network based transports.