Has anyone seen the following error:
[Flex] Attempt to subscribe to out of range sequence: 4 clientId:
4AE7.....
I'm getting a boatload of these (w/ different seq numbers and client
IDs) when there are multiple browsers connected to my server and I start
recycling the browsers.
I'm using LCDS 2.5.1, one RTMP channel with many destinations, and the
hibernate assembler.
It acts like something isn't being cleaned up when a previous client
disconnects.
Often times after a handful of these come out I get the following error:
20:53:43,877 ERROR [LazyInitializationException] could not initialize
proxy - the owning Session was closed
org.hibernate.LazyInitializationException: could not initialize proxy -
the owning Session was closed
at
org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyIniti\
alizer.java:60)
at
org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLa\
zyInitializer.java:111)
at
flex.data.assemblers.HibernatePropertyProxy.getHibernateProxyValue(Hiber\
natePropertyProxy.java:60)
at
flex.data.assemblers.HibernatePropertyProxy.getAlias(HibernatePropertyPr\
oxy.java:67)
at
flex.messaging.io.amf.Amf3Output.writePropertyProxy(Amf3Output.java:533)
at
flex.messaging.io.amf.Amf3Output.writeCustomObject(Amf3Output.java:518)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:193)
at
flex.messaging.io.amf.Amf3Output.writeObjectProperty(Amf3Output.java:243\
)
at
flex.messaging.io.amf.Amf3Output.writePropertyProxy(Amf3Output.java:549)
at
flex.messaging.io.amf.Amf3Output.writeCustomObject(Amf3Output.java:518)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:193)
at
flex.messaging.io.amf.Amf3Output.writeObjectArray(Amf3Output.java:800)
at
flex.messaging.io.amf.Amf3Output.writeAMFArray(Amf3Output.java:431)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:179)
at
flex.messaging.io.amf.Amf3Output.writeObjectProperty(Amf3Output.java:243\
)
at
flex.messaging.io.amf.Amf3Output.writePropertyProxy(Amf3Output.java:549)
at
flex.messaging.io.amf.Amf3Output.writeCustomObject(Amf3Output.java:518)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:193)
at flex.messaging.io.amf.Amf0Output.writeObject(Amf0Output.java:181)
at
flex.messaging.io.tcchunk.TCCommand.getCommandResponse(TCCommand.java:42\
0)
at
flex.messaging.endpoints.rtmp.AbstractRTMPServer.dispatchMessage(Abstrac\
tRTMPServer.java:1013)
at
flex.messaging.endpoints.rtmp.NIORTMPConnection$RTMPReader.run(NIORTMPCo\
nnection.java:435)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker\
.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker\
.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:619)
I understand Hibernate lazy initialization problems but I'm not
explicitly accessing a relationship that isn't loaded. Could these two
errors be related with some kind of cleanup/termination situation?
Any thoughts?
Thanks.
