[ http://jira.jboss.com/jira/browse/JBAS-1626?page=comments#action_12316472 ] Adrian Brock commented on JBAS-1626: ------------------------------------
I disagreed with this interceptor when it was first written but let it pass because it is not enabled by default. It was put there by the guy (who now works on ActriveMQ) that wrote the buggy ILs that couldn't detect that a client crashed. We no longer use those ILs. It is a big security concern (to me) that one client can hijack another client's subscription. It is certainly not spec compliant. If you are telling me it does not work, I am more likely to delete it than fix it. There are no tests for this behaviour in the testsuite. So unless you can provide a fix yourself, I am going to close this as "Won't Fix" and remove the interceptor from the codebase. > ClientReconnectInterceptor doesn't work > --------------------------------------- > > Key: JBAS-1626 > URL: http://jira.jboss.com/jira/browse/JBAS-1626 > Project: JBoss Application Server > Type: Bug > Components: JMS service > Versions: JBossAS-4.0.1 SP1 > Environment: SuSE Linux Enterprise Server 8, JBoss-4.0.1SP1 > Reporter: jens.schanz > Priority: Minor > > > File: jbossmq-service.xml > <!-- > | The ClientReconnectInterceptor is used to allow a client to connect to > the server even > | if it's clientID is allready being used by another client. This > interceptor will disconnect > | the previously connected client to allow the new connection to succeed. > This is not enabled > | by default since the JMS spec states that the 2nd client connecting to > the server with the same > | id should get an exception. > --> > <mbean code="org.jboss.mq.server.jmx.InterceptorLoader" > name="jboss.mq:service=ClientReconnectInterceptor"> > <attribute > name="InterceptorClass">org.jboss.mq.server.ClientReconnectInterceptor</attribute> > <depends > optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager</depends> > </mbean> > I have uncommented this feature, because our application has a bug with > unregistering and disconnecting. Until this bug is solved I want to enable > this feature in JBoss, but it doesn't work. I allready get the message > "reconnect failed : javax.jms.InvalidClientIDException: This client id > 'system1' is already registered!". > Maybee it's a bug. Could someone please check this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
