Association ARTIM timer expired in State: Sta5

239 views
Skip to first unread message

BOB

unread,
Aug 8, 2014, 3:54:24 PM8/8/14
to dcm...@googlegroups.com
I've recently begin getting this issue where I never had it before.
I'm wondering what if anything could have changed on my side that would cause this?

By 'my' side I mean:
I send the Association Request, but I no longer receive Association Accepts or Rejects.
It's as if the client has never received the message.

I one such example (Using WireShark) I see that the A-ASSOCIATE-RQ has been sent by tcp/ip and acknowledge but then i see a RST come back from the client.
I other examples I simply the an ARTIM timeout message.  Wireshark log on the recipient side shows the A-ASSOCIATE-RQ received but it doesn't appear to be getting 'up' the stack.

None of this was happening before and now I seem to be plagued with this issue of 'disappearing'  association request.

Was there a java update that broke something?
Was there a tcp/ip security update that broke something?

Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.6.0_27]
at java.net.SocketInputStream.read(SocketInputStream.java:129) ~[na:1.6.0_27]
at org.dcm4che2.net.PDUDecoder.readFully(PDUDecoder.java:101) ~[dcm4che-net-2.0.24.jar:2.0.24]
at org.dcm4che2.net.PDUDecoder.nextPDU(PDUDecoder.java:155) ~[dcm4che-net-2.0.24.jar:2.0.24]
at org.dcm4che2.net.Association.run(Association.java:850) ~[dcm4che-net-2.0.24.jar:2.0.24]

Reply all
Reply to author
Forward
0 new messages