Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

ClassCastException deserializing message

Not applicable
After upgrading from LCDS 2.5 to 2.6, I see the following exception. This used to work. Anyone care to guess what is going on here? Thanks in advance.






Sep 9, 2008 10:23:57 AM org.apache.catalina.core.ApplicationContext log

INFO: [*** MAKANA SERVER LOG ***] 10:23:57.125 Exception when invoking service: data-service

with message: Flex Message (flex.data.messages.DataMessageExt)

operation = page_items

id = null

clientId = FEF26AD2-45B0-6CD6-9EAE-477EBAC634C6

correlationId =

destination = stateAssignmentVO

messageId = FB76030B-C9E6-48E0-30CA-477F4C9660F2

timestamp = 1220970237109

timeToLive = 0

body = {id=1D5D0AC1-F24D-CEC5-075E-477F4A05821D, prop=stateAssignments, parent=positionVO}

hdr(sync) = false

hdr(DSids) =

[

D8915707-2D6E-5CC5-D9D8-477F4A058567,

9C3403F2-CFD1-5A88-9537-477F4A155E75,

7BA1851F-4A95-9919-3E8B-477F4A15DA0D

]

hdr(DSId) = A8C8B167-80F6-37FD-E5F9-D63CBAAD6A90

hdr(DSEndpoint) = my-amf

Exception: java.lang.ClassCastException: java.lang.String cannot be cast to java.util.Map

at flex.data.SequenceManager.toItemIdentities(SequenceManager.java:3930)

at flex.data.SequenceManager.getDSidsHeader(SequenceManager.java:1088)

at flex.data.SequenceManager.getPageFromSequence(SequenceManager.java:1042)

at flex.data.DataService.serviceMessage(DataService.java:458)

at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1495)

at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:882)

at flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:121)

at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158)

at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:44)

at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:67)

at flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:146)

at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:278)

at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:315)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)



2 Replies
Not applicable
Can you provide more details like the destination configuration/objects description and what operation are you doing?
Not applicable
We have established that this is a bug in LCDS 2.6. The operation involves creating a complex object graph: LCDS has trouble tracking which object needed creating. I have been adviced by Adobe that the following bug report tracks this issue:



https://bugs.adobe.com/jira/browse/LCDS-388



(The above URL does not seem to be publicly accessible. Or at least, I don't have access to it.)



I am currently trying to get a hotfix for this problem.