[jboss-user] [JBoss Portal] - WSRP: SAP EP versus JBoss

[walfreund]

Hi folks,

upon trying to connect JBoss and SAP EP over WSRP I'm struggling on both sides of the WSRP-world - neither SAP as consumer (an issue with consumer agent string) nor SAP as producer likes to talk WSRP.
My latest exception is about cookie headers, wow. It seems like the cookie information length is simply too much... ? 

Did anyone stumble across something like this before or can explain this issue to me?


  | 2008-03-17 23:50:28,477 DEBUG [org.jboss.ws.core.client.RemotingConnectionImpl] Get locator for: [addr=http://sapdemoce04:50000/irj/servlet/prt/soap/AutoGenProducer1_0?style=doc_lit,props={javax.xml.rpc.service.endpoint.address=http://sapdemoce04:50000/irj/servlet/prt/soap/AutoGenProducer1_0?style=doc_lit}]
  | 2008-03-17 23:50:28,478 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.HTTPClientInvoker at 1655aac connecting
  | 2008-03-17 23:50:28,478 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.HTTPClientInvoker at 1655aac connected
  | 2008-03-17 23:50:28,478 DEBUG [org.jboss.ws.core.client.RemotingConnectionImpl] Remoting metadata: {HEADER={SOAPAction="urn:oasis:names:tc:wsrp:v1:getServiceDescription", Content-Type=text/xml; charset=UTF-8}, NoThrowOnError=true}
  | 2008-03-17 23:50:28,478 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Setting request header with SOAPAction : "urn:oasis:names:tc:wsrp:v1:getServiceDescription"
  | 2008-03-17 23:50:28,478 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Setting request header with Content-Type : text/xml; charset=UTF-8
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.soap.SOAPMessageUnMarshaller] getMimeHeaders from: {Set-Cookie=[JSESSIONID=(J2EE5390400)ID0043229050DB10711443334707187519End; Version=1; Path=/, saplb_*=(J2EE5390400)5390450; Version=1; Path=/], ResponseCodeMessage=OK, Date=[Tue, 25 Mar 2008 13:44:26 GMT], Content-Type=[text/xml], Server=[SAP J2EE Engine/7.00], HEADER={SOAPAction="urn:oasis:names:tc:wsrp:v1:getServiceDescription", Content-Type=text/xml; charset=UTF-8}, Transfer-Encoding=[chunked], NoThrowOnError=true, ResponseCode=200}
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.portal.faces.loader.FacesClassLoader] Want to load org.jboss.ws.core.soap.EnvelopeBuilderDOM will delegate
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage: [contentType=text/xml]
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.http.HTTPClientInvoker at 1655aac from registry
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.jaxrpc.handler.MessageContextJAXRPC] Begin response processing
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl] Enter: handleResponse
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl] Exit: handleResponse with status: true
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.jaxrpc.SOAP11BindingJAXRPC] unbindResponseMessage: {urn:oasis:names:tc:wsrp:v1:intf}getServiceDescription
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue: org.jboss.ws.core.soap.SOAPBodyElementDoc
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl] Enter: handleResponse
  | 2008-03-17 23:50:28,483 WARN  [org.jboss.ws.core.jaxrpc.handler.HandlerWrapper] RuntimeException in handler method, transition to DOES_NOT_EXIST
  | 2008-03-17 23:50:28,483 DEBUG [org.jboss.ws.core.jaxrpc.handler.HandlerWrapper] destroy: org.jboss.portal.wsrp.handler.RequestHeaderClientHandler at 1478e10
  | 2008-03-17 23:50:28,483 ERROR [org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl] RuntimeException in response handler
  | java.lang.IllegalArgumentException: Too many cookie headers!
  | Cookie headers:
  | 	0:	JSESSIONID=(J2EE5390400)ID0043229050DB10711443334707187519End; Version=1; Path=/
  | 	1:	saplb_*=(J2EE5390400)5390450; Version=1; Path=/
  | 
  | 	at org.jboss.portal.wsrp.handler.RequestHeaderClientHandler.handleResponse(RequestHeaderClientHandler.java:125)
  | 	at org.jboss.ws.core.jaxrpc.handler.HandlerWrapper.handleResponse(HandlerWrapper.java:142)
  | 	at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleResponseInternal(HandlerChainBaseImpl.java:364)
  | 	at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleResponse(HandlerChainBaseImpl.java:329)
  | 	at org.jboss.ws.core.jaxrpc.client.CallImpl.callResponseHandlerChain(CallImpl.java:567)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:374)
  | 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:517)
  | 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
  | 	at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:151)
  | 	at $Proxy279.getServiceDescription(Unknown Source)
  | 	at org.jbo
  | .... 4.000.000 lines of error code more ...
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138720#4138720

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138720