[ https://jira.jboss.org/jira/browse/GTNWSRP-12?page=com.atlassian.jira.plu... ] Ron Sigal commented on GTNWSRP-12: ---------------------------------- I'm not really sure what the problem is, but if the goal is to 1. supply a timeout value to the Remoting client invoker, and 2. remove the timeout parameter from the InvokerLocator, then the solution is to pass the timeout parameter to the Client constructor in the configuration map instead of in the InvokerLocator. For example, in http://anonsvn.jboss.org/repos/jbossws/legacy/tags/jbossws-2.0.0.GA/jboss..., change targetAddress = addURLParameter(targetAddress, "timeout", timeout.toString()); // line 146 to clientConfig.put("timeout", timeout.toString()); Then, client = new Client(locator, "jbossws", clientConfig); // line 235 passes the timeout parameter to the client invoker without putting it in the InvokerLocator. Hope that helps. If not, let me know. -Ron -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/GTNWSRP-12?page=com.atlassian.jira.plu... ] Chris Laprun resolved GTNWSRP-12. --------------------------------- Resolution: Done Applied a work-around for now but this issue still needs to be resolved properly at the JBoss WS level. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira