Hide Forgot
Description of problem: Within an ejb, if you make a lookup on a remote queue. the operation goes well, but after the context is closed, the following error gets displayed: Channel end notification received, closing channel Channel ID b8e969d6 (outbound) of Remoting connection 4970f4db to DEVPC016970/10.23.132.245:5301 How reproducible: Very Steps to Reproduce: 0. download https://github.com/myannou/jbossRefApp/ 1. execute Case01043891.closeChannel() in the minibankref1 support application. The reproducer doe the following - Client -> EJB (on a cluster of 2 nodes) -> looks up a remote queue (on another cluster of 2 nodes) The 2 clusters are running on the same machine. I have the reproducer set up that demonstrates this. Actual results: Error seen when Expected results: No error to be reported for a normal situation Additional info: It looks to be that the org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.handleEnd method: 261 public void handleEnd(final Channel channel) { 262 log.errorf("Channel end notification received, closing channel %s", channel); 263 try { 264 channel.close(); 265 } catch (IOException ignore) { 266 } 267 } reports an error when handling the end Note this was addressed by https://bugzilla.redhat.com/show_bug.cgi?id=900323 The fix there was to say that this error is OK by adding text in the jms quickstart - this is a bodge. An error is not OK for an expected situation. The fix is to reduce the severity of the message to something more appropriate. 262 log.debugf("Channel end notification received, closing channel %s", channel);
OK this need to be in EAP 6.3.0.CP01 then.
Shouldn't this be listed as a known issue in the docs?
Shaun, you are right. Filed https://bugzilla.redhat.com/show_bug.cgi?id=1126440
Verified in EAP 6.3.1.CR1 / jboss-remote-naming 1.0.9.Final-redhat-1