"mohitanchlia" wrote :
| Is there a way to change the timeout and make it applicable only for
certain EJBs. The change timeout= is a global change but what I really want
is to apply it to only certain EJB invocations.
|
Well, one thing you could try would be to create multiple EJB3 Con
Is there a way to change the timeout and make it applicable only for certain
EJBs. The change timeout= is a global change but what I really want is to
apply it to only certain EJB invocations.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200810#4200810
"mohitanchlia" wrote :
| So new release of Jboss remoting doesn't do retries? Is it then just 1 try
then?
|
Yes, that's right.
"mohitanchlia" wrote :
| Does the new document reflect all the new features. It looked pretty much
the same.
|
In general, there won't be any new features
Thanks. So new release of Jboss remoting doesn't do retries? Is it then just 1
try then? Does the new document reflect all the new features. It looked pretty
much the same.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199387#4199387
Reply to the post :
ht
anonymous wrote :
| anonymous wrote :
| | I don't follow. What's the outcome?
| |
|
| It worked just fine. It reduced the number of times it was trying to get
the Socket (client invoker) to the server.
|
Great!
"mohitanchlia" wrote :
| I have another question though, In c
anonymous wrote : I don't follow. What's the outcome?
It worked just fine. It reduced the number of times it was trying to get the
Socket (client invoker) to the server. I have another question though, In
clustered environment when is the pool created on client side? Because until
client gets f
"mohitanchlia" wrote :
| I made the change to EJB deployer only but for some reason it didn't work
because I had a typo.
|
I don't follow. What's the outcome?
"mohitanchlia" wrote :
| Upgrading the jboss remoting might be a problem with Jboss support group.
In order to continue to ge
I made the change to EJB deployer only but for some reason it didn't work
because I had a typo.
Upgrading the jboss remoting might be a problem with Jboss support group. In
order to continue to get their support they require us to use that comes in
their distribution.
In any case why numberOf
"mohitanchlia" wrote :
| I don't understand why would it keep trying to connect to remote host even
after numberOfRetries is set to 1.
|
You're using a relatively old version of Remoting, 2.2.2.SP2 or earlier. We're
up to 2.2.2.SP10 now, and the parameter "numberOfRetries" no longer exist
