[jbosstools-dev] Re: Interesting Occurance... any suggestions?

[max.andersen at redhat.com]

Set a breakpoint at system.out.println and see when it gets called

/max (sent from my phone)


On 09/12/2008, at 23.40, Rob Stryker <rob.stryker at redhat.com> wrote:

> So I'm testing JBoss 5.0 support for GA since I missed the boat for  
> CR1, and the following weird behavior is happening. Obviously the  
> way I'm testing is the way I always do. I've got my eclipse  
> development environment up, then I run the runtime workbench, and  
> from there create a JBoss 5.0 server and go nuts.
>
> So I've got eclipse-dev -> eclipse-runtime -> jboss 5.0
>
> The interesting thing is... eclipse-dev's console view, I see output  
> OBVIOUSLY generated from jboss 5.0. Now to be clear, I also see  
> output in eclipse-runtime's console view. Specifically, the  
> runtime's console view is showing INFO and WARN statements, but  
> eclipse-dev's console view is showing DEBUG statements. (Nothing is  
> showing on the actual terminal window I loaded eclipse-dev  
> with ;) )   A sample is below:
>
> eclipse-dev's console view:
> 17:09:14,333 DEBUG [TimedSocketFactory] createSocket, hostAddr:  
> localhost/127.0.0.1, port: 1099, localAddr: null, localPort: 0,  
> timeout: 0
> 17:09:42,412 DEBUG [TimedSocketFactory] createSocket, hostAddr:  
> localhost/127.0.0.1, port: 1099, localAddr: null, localPort: 0,  
> timeout: 0
> he17:09:48,547 DEBUG [SecurityAssociation] Using ThreadLocal: false
> 17:09:48,566 DEBUG [TimedSocketFactory] createSocket, hostAddr:  
> localhost/127.0.0.1, port: 1099, localAddr: null, localPort: 0,  
> timeout: 0
>
> eclipse-runtime's console view:
> 17:09:42,859 INFO  [ServerPeer] JBoss Messaging 1.4.1.GA server [0]  
> started
> 17:09:43,377 INFO  [QueueService] Queue[/queue/DLQ] started,  
> fullSize=200000, pageSize=2000, downCacheSize=2000
> 17:09:43,389 WARN  [ConnectionFactoryJNDIMapper] supportsFailover  
> attribute is true on connection factory:  
> jboss.messaging.connectionfactory:service=ClusteredConnectionFactory  
> but post office is non clustered. So connection factory will *not*  
> support failover
> 17:09:43,389 WARN  [ConnectionFactoryJNDIMapper]  
> supportsLoadBalancing attribute is true on connection factory:  
> jboss.messaging.connectionfactory:service=ClusteredConnectionFactory  
> but post office is non clustered. So connection factory will *not*  
> support load balancing
> 17:09:43,455 INFO  [ConnectionFactory] Connector bisocket:// 
> localhost:4457 has leasing enabled, lease period 10000 milliseconds
> 17:09:43,455 INFO  [ConnectionFactory]  
> org.jboss.jms.server.connectionfactory.ConnectionFactory at 4e2899d0  
> started
> 17:09:43,458 INFO  [ConnectionFactory] Connector bisocket:// 
> localhost:4457 has leasing enabled, lease period 10000 milliseconds
>
> The part that's most confusing to me is that a) how could jboss even  
> POSSIBLY send output to eclipse-dev's console ( AKA eclipse- 
> runtime's system.out)?  When it sends output to jboss's system.out  
> it appears (or always has before) in eclipse-runtime's console view.
>
> What makes it even slightly weirder is I haven't written any code to  
> listen to JBoss' console output yet and add it to my Server Log View  
> or anything like that, and I even did a search throughout my code  
> for System.out which turned up pretty fruitless.
>
> Any ideas are much appreciated ;)
>
> - Rob Stryker
>