HTTP server invokers should not put null URL path in metadata map ----------------------------------------------------------------- Key: JBREM-853 URL: http://jira.jboss.com/jira/browse/JBREM-853 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.Beta1 (Pinto) org.jboss.remoting.transport.servlet.ServletServerInvoker calls javax.servlet.http.HttpServletRequest.getPathTranslated() and puts the result in the invocation's requestPayload with key "Path". If the path of the URL is null, then a null value goes in the map, and using Map.putAll() can result in a NullPointerException. This phenomenon was observed in the execution of org.jboss.test.remoting.transport.servlet.ssl.SSLServletClientAddressTestClient when the contents of the requestPayload map are added to the callback Client configuration map. The callback transport is "socket", and a call to Map.putAll() occurs in org.jboss.remoting.transport.socket.MicroSocketClientInvoker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira