[英]Synchronized, clustered JMS application (Weblogic)
First of all: 首先:
output.jms.q
) and then waits about 20 seconds to get the message from another queue (lets say input.jms.q
) output.jms.q
),然后等待大约20秒从另一个队列获取消息(让我们说input.jms.q
)。 In my code, If I send the message from Managed-Server-1, it will try to get the response in Managed-Server-1. 在我的代码中,如果我从Managed-Server-1发送消息,它将尝试在Managed-Server-1中获得响应。 (Using the
InitialContext()
constructor). (使用
InitialContext()
构造函数)。 that makes 66% of the messages unreachable! 这使得66%的消息无法访问!
I am aware of the Forward Delay
option and I set it to like, 2 seconds. 我知道“
Forward Delay
选项,并将其设置为2秒。 When I was in the development, it worked like charm! 在开发过程中,它就像魅力一样! now, when I have a lot of clients testing it, It feels like the
Forward Delay
is not picking the right server. 现在,当我有很多客户端对其进行测试时,感觉“
Forward Delay
没有选择正确的服务器。
When I shut down 2 of my Managed Servers - It works amazingly fast. 当我关闭两台受管服务器时,它的运行速度非常快。 but I am using just one machine instead of 3.
但是我只用一台机器而不是3。
For each Managed server there is a JMS server, and one Distributed Queue. 对于每个受管服务器,都有一个JMS服务器和一个Distributed Queue。 I believe that for this thing, I only need one queue, that every JMS Server could connect to.
我相信对于这件事,我只需要一个队列,每个JMS Server都可以连接到该队列。 something like a shared queue instead of distributed.
类似于共享队列而不是分布式队列。
Is it possible? 可能吗?
The solution to my problem was using Distrubuted Topics. 解决我的问题的方法是使用分散主题。 Weblogic 10.3.5+ supports replicating the messages between the servers.
Weblogic 10.3.5+支持在服务器之间复制消息。 yeah, its pretty lame.. but that's what I found.
是的,它很la脚..但这就是我发现的。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.