.NET proxy web service "uncompressInt" exception "Unexpected type found (O)"
search cancel

.NET proxy web service "uncompressInt" exception "Unexpected type found (O)"

book

Article ID: 393108

calendar_today

Updated On:

Products

Gen Gen - Run Time Distributed

Issue/Introduction

Referencing the Gen .NET proxy samples on this doc. page: .NET Proxy > Executing the Sample Applications

Testing the "Web Service Sample" using SoapUI produces the following error with associated prior entries in the CMIDEBUG trace file immediately after the incoming message from the Gen server:

CFBDynamicMessage::SetConn(): TRANSIENT connection encountered
TCPIPDynamicCoopFlow::DoFlow(): Transient Connection detected
CFBDynamicMessage::SetMessage(): entered (buffersize:16777215)
CFBDynamicMessage::parseForCommError(): entered
CFBDynamicMessage::parseForCommError(): exiting
CFBDynamicMessage::parseCFBHeader(): entered
CFBDynamicMessage::parseCFBHeader(): exiting
CFBDynamicMessage::parseUA(): entered
CFBDynamicMessage::parseForServerError(): entered
CFBDynamicMessage::parseForServerError(): exiting
CFBDynamicMessage::parseUA(): exiting
CFBDynamicMessage::parseExitState(): entered
CFBDynamicMessage::parseExitState(): exiting
CFBDynamicMessage::decryptMessage(): entered
CFBDynamicMessage::decryptMessage(): Data buffer not encrypted
CFBDynamicMessage::decryptMessage(): exiting
CFBDynamicMessage::parseViewArea(): entered
GenException::TraceDump(): GenException created: 
GenException: [Function: CFBDynamicMessage::uncompressInt]Unexpected type found (O)

Environment

Gen 8.6 .NET Proxy

Cause

The uncompressInt "type(O)" exception indicates Gen was expecting an Integer to be returned from the server, but it received a One character view (type O) instead.
Therefore it appears there is a view mismatch between the Gen server and the SoapUI client i.e. a view mismatch between the export views sent back from the server and what the SoapUI client is expecting.

Resolution

There was a procedural problem with the promotion of code changes which caused the view mismatch. Correctly promoting the full set of code changes resolved the problem.