How to Intercep a client close on the server side

[jay.howell]

JBM 1.4.0 sp3 CP04

If I want a notification on the server side that a connection has been closed(either called close on the connection or closed due to network error), how do you get a server notification.

I've tried to use the aspects, but the connection advised doesn't get called when the connection is shut down due to error.

My last option is to do runtime weaving and use an aroundinvoke around handleConnectionException in the SimpleConnectionManager

Since the flow calls close and closing on the and does not call the connectionAdvised, it seems like this is a bug. Shouldn't the connectionAdvised get called in the event of a client failure. I would think that on the server side methods for closing and close should be called for the connectionAdvised. It seems like a bug, but I can also see it the other way... The code fix for the bug would be to wrap the endpoint in the connectionAdvised and call that in the SimpleConnection in cleanupForSessionID instead of calling the endpoint directly.

Jay:)

[timfox]

My initial reaction would be this is not functionality that we have ever claimed is supported in JBM 1.x.

But if you want to add the new feature then go for it :) If it's tested properly and has no nasty side effects we can get it in the next CP.

[jay.howell]

Yeah that was my reaction to... We never said we supported that feature. Which was why I was hesitant to raise it as a jira until speaking with you. I'll raise it as a feature reqeust and add it in to the next cp. I don't think there are going to be any side effects from it, but I'll test well to make sure.

Thanks a bunch. Jay:)

[slimamar]

Hi Jay,

>> My last option is to do runtime weaving and use an aroundinvoke around
>> handleConnectionException in the SimpleConnectionManager

We are very interested by this feature.
If you have a solution, can you tell us how to do this.

Thanks in advance.

Slimane.

JBM 1.4.1.GA
JBAS 5.0.0.GA

[jay.howell]

This was added to the 1.4 branch for the following jira https://jira.jboss.org/jira/browse/JBMESSAGING-1620

You might try 1.4.4. It should be fixed in that version. If you want to port the change back to 1.4.1 GA, you can, it's a really easy fix.

http://fisheye.jboss.org/browse/Messaging/branches/Branch_1_4/src/main/org/jboss/jms/server/connectionmanager/SimpleConnectionManager.java?r1=6192&r2=6709

Jay:)

[slimamar]

Thank you !