[JBoss Messaging] - Client connection timeout
by jbabad
Hi,
I've seen a few posts related to this and to JBREM-1069.
We're running a trial version of JBoss EAP 4.3 and the JBoss Remoting patch 2.2.2SP11-brew - which is supposed to contain that fix.
We're seeing this on the client side - in the remoting-bisocket-service.xml I've increased the timeout to 5s. The RemotingConnection is showing this value, but the ConnectionValidator is showing a timeout of 1s and a ping period of 1s. How do we change these values and the number of retries? We are seeing timeouts with the client thinking that the connection has disappeared. This triggers a client failover, which times out as, in fact, the cluster is still OK.
Thanks.
anonymous wrote :
| 2009-03-03 15:55:43,605 TRACE [org.jboss.jms.client.remoting.JMSRemotingConnection] (main) JMSRemotingConnection[bisocket://192.168.8.118:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=15000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&stopLeaseOnFailure=true&timeout=5000&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat&validatorPingPeriod=10000&validatorPingTimeout=5000] started
| 2009-03-03 15:55:43,605 TRACE [org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate] (main) Adding callback
| 2009-03-03 15:55:43,609 DEBUG [org.jboss.remoting.ConnectionValidator] (main) ConnectionValidator[null, pingPeriod=2000 ms] created
| 2009-03-03 15:55:43,609 TRACE [org.jboss.remoting.ConnectionValidator] (main) config timeout: null
| 2009-03-03 15:55:43,609 DEBUG [org.jboss.remoting.ConnectionValidator] (main) ConnectionValidator[null, pingPeriod=2000 ms] timeout: 1000
| 2009-03-03 15:55:43,609 DEBUG [org.jboss.remoting.ConnectionValidator] (main) ConnectionValidator[null, pingPeriod=2000 ms] ping retries: 1
| 2009-03-03 15:55:43,610 DEBUG [org.jboss.remoting.ConnectionValidator] (main) ConnectionValidator[null, pingPeriod=2000 ms] connection retries: null
| [/quote
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215194#4215194
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215194
17 years, 2 months
[Microcontainer] - Re: Attachments eligible for being passed to the deployers?
by alesj
"jaikiran" wrote :
| So would that mean, the attachment generated by a component deployer is of no pratical use to non-component deployers?
|
No, that's exactly what I'm trying to explain.
Component deployers should only consume attachments,
not create/generate them.
"jaikiran" wrote :
| So would this be a clean way of doing things in a component deployer:
|
|
| | public void deploy(DeploymentUnit unit) throws DeploymentException
| | {
| | logger.info("Deploying unit : " + unit);
| |
| | // Am i deploying a component?
| | if (unit.isComponent())
| | {
| | // yes, i am deploying a component
| | ...
| | // should my attachments be visible to non-component deployers?
| | if (shouldMyAttachmentsBeVisibleToAll())
| | {
| | // should be visible to all, so add to parent
| | unit.getParent().addAttachment(something,someotherthing);
| | }
| | else
| | {
| | // only to component deployers
| | unit.addAttachment(something,someotherthing);
| | }
| |
| | }
| |
| | }
|
|
The moment you're hacking with getParent::addAtachment you know
there is something wrong with how you're doing it.
I know we have something like that in our JPA deployers. :-(
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215187#4215187
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215187
17 years, 2 months