0 Replies Latest reply on Mar 10, 2010 10:52 AM by BenDarkBlue

    BlazeDS/Flex cannot serialize client message

    BenDarkBlue

      We've had a BlazeDS instance running online for many months now, and the other day we came across an error that we have never seen before.

       

      [RPC Fault faultString="Error deserializing client message." faultCode="Client.Packet.Encoding" faultDetail="null"]

           at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[C:\autobuild\galaga\frameworks\ projects\rpc\src\mx\rpc\AbstractInvoker.as:290]

           at mx.rpc::Responder/fault()[C:\autobuild\galaga\frameworks\projects\rpc\src\mx\rpc\Responde r.as:58]

           at mx.rpc::AsyncRequest/fault()[C:\autobuild\galaga\frameworks\projects\rpc\src\mx\rpc\Async Request.as:103]

           at NetConnectionMessageResponder/statusHandler()[C:\autobuild\galaga\frameworks\projects\rpc \src\mx\messaging\channels\NetConnectionChannel.as:576]

           at mx.messaging::MessageResponder/status()[C:\autobuild\galaga\frameworks\projects\rpc\src\m x\messaging\MessageResponder.as:222]

       

      This would happen any time a call was sent to Blaze from Flex. Restarting the Tomcat server fixed the issue, but now we're concerned with it happening again. Any ideas as to what may have caused this?