[ https://jira.jboss.org/jira/browse/JBWS-2849?page=com.atlassian.jira.plug... ] Heiko Braun commented on JBWS-2849: ----------------------------------- Within riftsaw,we experience this exception in some situations: Caused by: java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.lang.Integer at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:66) at org.jboss.ws.core.client.transport.NettyClient.invokeInternal(NettyClient.java:189) Here's the corresponding JBossWS code: public Object read(InputStream inputStream, Map<String, Object> metadata) throws IOException { if (log.isTraceEnabled()) log.trace("Read input stream with metadata=" + metadata); try { Integer resCode = (Integer)metadata.get(NettyClient.RESPONSE_CODE); if (resCode == null) { log.warn("No HTTP resonse code, assuming: SC_OK"); resCode = HttpServletResponse.SC_OK; } [...] } It's not clear to me how the ClassCastException might occur. But it seems to be a JBossWS problem. -- 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/JBWS-2849?page=com.atlassian.jira.plug... ] Heiko Braun commented on JBWS-2849: ----------------------------------- It's actually a bug in the WSResponseHandler#messageReceived(ChannelHandlerContext ctx, MessageEvent e) implementation: [...] HttpResponse response = (HttpResponse)e.getMessage(); Map<String, Object> responseHeaders = result.getResponseHeaders(); responseHeaders.put(NettyClient.PROTOCOL, response.getProtocolVersion()); responseHeaders.put(NettyClient.RESPONSE_CODE, response.getStatus().getCode()); responseHeaders.put(NettyClient.RESPONSE_CODE_MESSAGE, response.getStatus().getReasonPhrase()); for (String headerName : response.getHeaderNames()) { responseHeaders.put(headerName, response.getHeaders(headerName)); } Iterating over the header names and calling 'response.getHeaders(headerName)' will replace the map entry with a List<String> object corresponding to the header name. -- 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/JBWS-2849?page=com.atlassian.jira.plug... ] Heiko Braun commented on JBWS-2849: ----------------------------------- "ResponseCode" doesn't seem to be an official HTTP Header. So it must be the ESB adding it. However, since anyone can add arbitrary HTTP headers, the implementation should make sure it doesn't replace the Map keys. Same thing happens to NettyClient.RESPONSE_CODE_MESSAGE. -- 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