Bug 793456 (JBEPP-539) - Can't create any WSRP consumer - ClassCastException
Summary: Can't create any WSRP consumer - ClassCastException
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-539
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.0.ER01,5.1.0.ER02
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER03
Assignee: claprun@redhat.com
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-07 15:15 UTC by Michal Vanco
Modified: 2013-04-30 23:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
EPP5.1.0.ER02, ER01
Last Closed: 2010-10-19 19:16:33 UTC
Type: Bug


Attachments (Terms of Use)
wsrp-consumer-2.0.0-Beta01_patched.jar (171.42 KB, application/x-java-archive)
2010-10-07 18:24 UTC, Thomas Heute
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-539 0 None Closed Can't create any WSRP consumer - ClassCastException 2012-03-01 01:55:21 UTC

Description Michal Vanco 2010-10-07 15:15:23 UTC
Steps to Reproduce:  - import WSRP Configuration portlet
 - add WSRP configuration portlet on page
 - create or refresh any consumer
project_key: JBEPP

It is not possible to create any WSRP consumer.

Log: 
[WSRPConsumer] Consumer with id 'test' started
16:59:47,318 ERROR [CommonClient] Exception caught while (preparing for) performing the invocation: 
java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.String
	at org.jboss.ws.core.client.HTTPRemotingConnection.createRemotingMetaData(HTTPRemotingConnection.java:325)
	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:176)
	at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:360)
	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:231)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:171)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:157)
	at $Proxy230.getServiceDescription(Unknown Source)
	at org.gatein.wsrp.services.v1.V1ServiceDescriptionService.getServiceDescription(V1ServiceDescriptionService.java:96)
	at org.gatein.wsrp.consumer.ProducerInfo.getUnmanagedServiceDescription(ProducerInfo.java:832)

Important: it works properly with GateIn - today I checked with portal trunk + wsrp trunk.
There is full log from hudson job: http://hudson.qa.jboss.com/hudson/view/EPP5/job/epp5_wsrp2_ui_tests_epp5_vs_epp5/5/console

Comment 1 Thomas Heute 2010-10-07 18:24:30 UTC
I attached a patch to let you continue, just replace the existing one.
Note that I found a new issue (would need a jira). If i try to activate a consumer before refreshing it, I get a stacktrace.

Here is the sources of the patch:

Index: consumer/src/main/java/org/gatein/wsrp/services/ServiceWrapper.java
===================================================================
--- consumer/src/main/java/org/gatein/wsrp/services/ServiceWrapper.java	(revision 4591)
+++ consumer/src/main/java/org/gatein/wsrp/services/ServiceWrapper.java	(working copy)
@@ -109,7 +109,7 @@
       // better interoperability as Oracle's producer doesn't support it, for example.
       // See https://jira.jboss.org/jira/browse/JBWS-2884 and
       // http://community.jboss.org/wiki/JBossWS-NativeUserGuide#Chunked_encoding_setup
-      requestContext.put(JBOSS_WS_STUBEXT_PROPERTY_CHUNKED_ENCODING_SIZE, 0);
+      requestContext.put(JBOSS_WS_STUBEXT_PROPERTY_CHUNKED_ENCODING_SIZE, "0");
 
       // Add client side handler via JAX-WS API
       Binding binding = bindingProvider.getBinding();


Comment 2 Thomas Heute 2010-10-07 18:24:30 UTC
Attachment: Added: wsrp-consumer-2.0.0-Beta01_patched.jar


Comment 3 Michal Vanco 2010-10-08 11:42:00 UTC
Thanks for patch Thomas - it works fine with it.
But I wasn't able to reproduce issue you mentioned (activate and refresh). Can you describe it please?

Comment 4 Thomas Heute 2010-10-09 08:19:11 UTC
I tried again and it's not clear, if i play with activate/desacivate/refresh buttons randomly for selfv1 and selfv2 I get some stacktraces

Comment 5 Thomas Heute 2010-10-19 19:16:33 UTC
Shouls be fixed by r4609 (Need upgrade of WSRP component post-Beta01)

Comment 6 Scott Mumford 2010-11-08 09:56:23 UTC
Release Notes Docs Status: Added: Not Required



Note You need to log in before you can comment on or make changes to this bug.