This content has been marked as final.
Show 2 replies
-
1. Re: JBM 1.4.0sp3 cp04 bisocket parameters does not effect
ron_sigal Dec 2, 2008 12:28 AM (in response to lanceliao1)Yes, I noticed that recently; see https://jira.jboss.org/jira/browse/JBREM-1069. It will get fixed in the next Remoting releases.
However, as far as I can see, it should affect only "validatorPingPeriod", which gets set in the metadata map, overriding the org.jboss.remoting.Client's configuration map. But "validatorPingTimeout" should get its value from the Client's configuration map, which includes the parameters set in remoting-bisocket-service.xml.
However, maybe I'm missing something.
-Ron -
2. Re: JBM 1.4.0sp3 cp04 bisocket parameters does not effect
lanceliao1 Dec 2, 2008 1:56 AM (in response to lanceliao1)I think there are some subtle mechanism.
JMSRemotingConnection public void start()Map config = new HashMap(); config.put(Client.ENABLE_LEASE, String.valueOf(clientPing)); if (serverLocator.getParameters().containsKey(MicroSocketClientInvoker.MAX_POOL_SIZE_FLAG)) { throw new IllegalArgumentException("Invalid remoting configuration - do not specify clientMaxPoolSize" + " use " + JBM_MAX_POOL_SIZE_KEY +" instead"); } if (!serverLocator.getProtocol().equals("http") & !serverLocator.getProtocol().equals("https")) { String val = (String)serverLocator.getParameters().get(JBM_MAX_POOL_SIZE_KEY); if (val == null) { log.warn(JBM_MAX_POOL_SIZE_KEY + " not specified - defaulting to 200"); val = "200"; } config.put(MicroSocketClientInvoker.MAX_POOL_SIZE_FLAG, val); } client = new Client(serverLocator, config); client.setSubsystem("JMS");
The method only set a few parameters of remoting,the Map config used as configuration of Client.
The ConnectionValidator only use this map to set parameters,so it does not work.