[Remoting] - Re: Socket Read Timeout on stressing calls for validating pr
by ron.sigal@jboss.com
Hi Vinay,
"vink" wrote :
| Issue 1:
| On providing invokerDestructionDelay=10000, my system run out of threads. I mean my client side. Every call results in the creation of new thread, it seems old invoker thread is not getting reused.
|
Well, I don't think this is a Remoting problem, because the socket transport doesn't create new threads on the client side. My conjecture is that there is some other problem, and setting "invokerDestructionDelay=10000" is just reducing the consumption of Remoting resources enough to allow this other problem to show up. What kind of threads are you seeing on the client side?
"vink" wrote :
| The best use case for SLSB is to open a socket for a request & close it after finish.
|
Actually, that is the default behavior, but it's expensive to recreate sockets. The "invokerDestructionDelay" parameter is meant to prevent the closing of existing sockets when they are likely to be reused in the near future. By the way, if a socket is in the TIME_WAIT state, then it *has* been closed.
"vink" wrote :
| n the meanwhile, I tried overnight tests on my system with invokerDestructionDelay=10000, & I face this exception on server. I cannot understand what it means, but it is linked with socket; so I thought it may be worth to share;
|
| Caused by: javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: could not execute query
|
This problem is somewhere between hibernate and your database. Definitely not a Remoting issue.
-Ron
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201580#4201580
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201580
17 years, 6 months
[Management, JMX/JBoss] - jboss monitoring
by priyapg
how jboss details can be retreived from mbeans?the parameters are Monitor information (JVM usage,Listen port,activation time etc),Web Application Details(Web Application name,context root,reponse type etc),JDBC Connection Pool details(JDBC pool,pool size,connections currently in use,connections destroyed etc),EJB Details (EJB Name,Module,Type etc).Please help it's urgent............
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201571#4201571
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201571
17 years, 6 months
[JBossWS] - How do I determine which version of JBossWS is being used?
by nogamejoe
Hi,
I am reviewing JBoss Portal and JBossWS support. I currently installed JBossWS 3.05 into JBoss Portal 2.6.7 which is using JBoss AS 4.2.3. I am testing portlets. So far my portlet examples work. However they had also worked prior to installing JBossWS 3.0.5.
How do I find out what version of the WS Stack my JBoss Portal environment is executing with, upon startup. I checked the boot.log, and found no mention of JBossWS 3.0.5. I tried following the install instructions (JBossWS 3.0.5 native GA) which instructed that I navigate to http://localhost:8080/jbossws. The page is displayed, however, if I do the same within the old environment, the same page is displayed - without any version specification made regarding JBossWS.
So after all the above, the basic question at hand is:
How do I determine which specific version my JBoss Portal environment is executing with?
If you need any more information to help with this request, please let me know.
Thank you
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201552#4201552
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201552
17 years, 6 months