Have a look at:
http://wiki.jboss.org/wiki/Wiki.jsp?page=IGetIOExceptionPingTimeoutHowDoIFixIt
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954313#3954313
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954313
Usin
please help
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954180#3954180
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954180
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done q
Hi,
We have the same pb as you with Jboss 3.2.2 :
org.jboss.mq.SpyJMSException:Connection Failed
Please do you know if this pb is solve in a newer Jboss release.
Thanks,
Patricia
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867040#3867040
Reply to the po
Yes I know what was wrong...
Our scenario was 200,000 Hashtables created more or less at the same time, and of
course we wanted those to be pushed on to the queue as
fast as possible.
In this particular case you will always get very high load on the server, no matter
what server you have. A lit
The algorithm is pseudo code. It is implemented a lot more efficiently in the real
code.
Of course java:/ConnectionFactory is faster, there is no serialization.
The ping is minimal (a few bytes once every minute) and couldn't possibly cause
a bottleneck. If your server can't handle two small net
In Adrians description of ping "algorithm" I guess the wait method is the problem, a
separate thread waiting for 60s?.
Maybe the ping should move out in the JMS main thread so the ping would be forced to
happen during heavy load!?
/Goran
View the original post :
http://www.jboss.org/inde
We had a lot of problems with the "ping" or more correct "no ping" during
heavy load. When the processor is near 100% it seems like the ping task has lower
priority than every thing else.
For us the following solution gave us amazing performance in our last
project, with a lot of JMS queues:
We
Thank you the reply , greatly appricaited.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834396#3834396
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834396
---
T
Guys, your feedback though appreciated is useless.
If you want help resolving this problem, I need specifics.
The ping is just a simple network packet that the client sends to the server saying
"are you still there?"
The alogrithm is:
| while (notclosed)
| {
| sendping();
| wait(pingp
We are deleveloping our codes on windows platform and deployed them on Linux box. Just
an add, a servlet receives incoming xml and send it to QueueA on which MyMDB consumes
it. The sqlserver reside from other box while mysql and jboss reside on same box. I
also assumed that the server (linux) is
Just as an add - I see that several are using windows and point the finger there. We
are running on several platforms. However I am getting the above error during testing
on a Linux platform, running JBoss 3.2.3, and Sun's 1.4.2-b28 jvm.
View the original post :
http://www.jboss.org/index.html?
I am getting the same exception. We have built a large application around message
queues, and send lots of messages - one to start a document to be processed and
another for each stage of processing. So for each document, there are 5 or 6 messages.
After a few thousand documents, we get the exce
The error says the server is not responding to pings.
Unless this is due to a network failure, it would have to be unresponsive for 60
seconds (the default PingPeriod).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834114#3834114
Reply to the post :
http://w
13 matches
Mail list logo
