"Chul Yoon" wrote :
| I assume I can just set the write timeout attribute for JBM in
remoting-bisocket-service.xml
|
| Something like this?:
|
|
| | 20
| |
|
That will set "writeTimeout" on the server side, which will affect (1) writing
responses to the client and (
I've just attached to JBREM-1120 two versions of jboss-remoting.jar with the
write timeout facility implemented:
* 2.2.3.SP1 preview (874 kb): writes "Remoting version: 2.2.3.SP1-preview:
8/19/2009 - 14:54" when loaded
* 2.5.2 preview (1.07 Mb): writes "JBossRemoting Version 2.5.2 (Flounder
"jlaemthonglang" wrote : does this bug affect JBM queue too? or topics only?
As far as I know, it should affect both. I'm sure someone from JBossMessaging
could be more definite.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244416#4244416
Reply to the pos
"waylandc" wrote : Any ETA on 2.2.2SP12?
Release 2.2.2.SP12 morphed into 2.2.3, which was released in May. The next
release, 2.2.3.SP1, should come out in early September, and I'll aim to get the
write timeout facility in that release.
View the original post :
http://www.jboss.org/index.html?
Any ETA on 2.2.2SP12?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238164#4238164
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238164
___
jboss-user mailing list
jboss-use
does this bug affect JBM queue too? or topics only?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234762#4234762
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234762
___
jbo
"timfox" wrote :
| Ron, do you have a JIRA and ETA for this?
|
JBREM-1120 "Add a socket write timeout facility".
I was hoping to get something into Remoting 2.5.1, which I just released, but
time didn't allow. I've scheduled JBREM-1120 for releases 2.2.2.SP12 and 2.5.2.
-Ron
View the
+1
I believe this is a serious issue and remoting should apply a fix as per the
AMQ fix.
Ron, do you have a JIRA and ETA for this?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223504#4223504
Reply to the post :
http://www.jboss.org/index.html?module=bb&o
Yes,This is a serious problem.
The JBM are not reliable in stressful conditions,We have to consider choosing
another mom production.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=457#457
Reply to the post :
http://www.jboss.org/index.html?module=bb&o
ActiveMQ's solution was above and beyond the TTL. This is a serious issue that
needs to be fixed by the JBOSS folks asap. No respectable messaging middle-ware
should ever be held hostage to a rogue client.
Unfortunately, we had to abandon our migration to JBM from ActiveMQ because of
this issue
Java does allow setting the keep-alive parameter programatically on a socket.
It appears from the Javadocs, however, that this value is binary (set to 2
hours or nothing).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221062#4221062
Reply to the post :
htt
Hi all
I faced the same problem,Can Remoting provide a method to resolve the problem
like AMQ.
http://issues.apache.org/activemq/browse/AMQ-1993
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220151#4220151
Reply to the post :
http://www.jboss.org/index.ht
I have a question.
On the server side, there is an org.jboss.remoting.Lease which, if it doesn't
receive pings from the client in a timely fashion, will declare that a
connection is broken and inform any registered listeners. Now JBossMessaging
registers a listener, so it should be informed
Hi guys,
First, a little background. JBossMessaging sends messages to a consumer by
calling
org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(),
which, in the case of the bisocket transport. results in a call to
org.jboss.remoting.Client.invoke(), which eventually leads
We are experiencing the exact same problem on Linux. This is very easy to
reproduce. Have two clients running against a server and pull the network cable
from one of the clients simulating a kernel death. A few seconds later, the
server puts out:
anonymous wrote : 13:07:15,064 WARN [SimpleConn
15 matches
Mail list logo