]
Kevin Conner commented on JBESB-694:
------------------------------------
Kurt has already addressed the STDOUT issue, it will disappear once he upgrades the
version of scout.
ERROR [ClosedInterceptor] ClosedInterceptor.ClientConsumerDelegate
------------------------------------------------------------------
Key: JBESB-694
URL:
http://jira.jboss.com/jira/browse/JBESB-694
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 2
Reporter: Burr Sutter
Assigned To: Kevin Conner
Priority: Minor
Fix For: 4.2
The following messages are shown on the AS console (AS 4.2 + Messaging + WS 2.0 updates +
ESB):
15:38:28,078 INFO [STDOUT] 1
15:38:28,093 ERROR [ClosedInterceptor] ClosedInterceptor.ClientConsumerDelegate[
20]: method receive() did not go through, the interceptor is IN_CLOSE
This happens upon undeployment of a .esb archive. You can simply just delete it from the
deploy directory to see the message. Or in helloworld use 'ant deploy' and then
'ant undeploy'
Note: the STDOUT 1 also appears when you simply update/touch the jboss-esb.xml. I
didn't go digging for the class that must be using a System.out.println(1).
Now, I do like the fact that you see some activity on the console when a .esb. is
undeployed as that is "user friendly" or if we perform a hot redeployment,
however, these 2 messages are not that useful in their content.
I've been seeing the "1" now for a couple of months.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: