November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-725) Reduce the amount of INFO logging

by Dimitris Andreadis (JIRA)

Reduce the amount of INFO logging --------------------------------- Key: JBCACHE-725 URL: http://jira.jboss.com/jira/browse/JBCACHE-725 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.4.0 Reporter: Dimitris Andreadis Assigned To: Manik Surtani I've posted this to jboss-dev, and didn't get a reply, so: No big deal, but you guys really need to reduce the amount of INFO logging that goes to the console. This is from HEAD but Branch_4_x is not any better. Those should really be DEBUG level: http://docs.jboss.org/process-guide/en/html/logging.html (and why JGroups need to do that STDOUT printout anyway?) 14:40:24,374 INFO [TreeCache] setting cluster properties from xml to: UDP(down_ thread=false;enable_bundling=true;ip_ttl=2;loopback=false;max_bundle_siz e=64000; max_bundle_timeout=30;mcast_addr=230.1.2.7;mcast_port=45577;mcast_recv_b uf_size= 25000000;mcast_send_buf_size=640000;ucast_recv_buf_size=20000000;ucast_s end_buf_ size=640000;up_thread=false;use_incoming_packet_handler=true;use_outgoin g_packet _handler=false):PING(down_thread=false;num_initial_members=3;timeout=200 0;up_thr ead=false):MERGE2(down_thread=false;max_interval=100000;min_interval=200 00;up_th read=false):FD(down_thread=false;max_tries=5;shun=true;timeout=2500;up_t hread=fa lse):VERIFY_SUSPECT(down_thread=false;timeout=1500;up_thread=false):pbca st.NAKAC K(discard_delivered_msgs=true;down_thread=false;gc_lag=50;max_xmit_size= 60000;re transmit_timeout=100,200,300,600,1200,2400,4800;up_thread=false;use_mcas t_xmit=f alse):UNICAST(down_thread=false;timeout=300,600,1200,2400,3600;up_thread =false): pbcast.STABLE(desired_avg_gossip=50000;down_thread=false;max_bytes=21000 00;stabi lity_delay=1000;up_thread=false):pbcast.GMS(down_thread=false;join_retry _timeout =2000;join_timeout=3000;print_local_addr=true;shun=true;up_thread=false) :FC(down _thread=false;max_credits=10000000;min_threshold=0.20;up_thread=false):F RAG2(dow n_thread=false;frag_size=60000;up_thread=false):pbcast.STATE_TRANSFER(do wn_threa d=false;up_thread=false) 14:40:24,434 INFO [BuddyManager] Using buddy communication timeout of 2000 mill is 14:40:24,454 INFO [TreeCache] Not using an EvictionPolicy 14:40:24,504 INFO [InterceptorChainFactory] interceptor chain is: class org.jboss.cache.interceptors.CallInterceptor class org.jboss.cache.interceptors.PessimisticLockInterceptor class org.jboss.cache.interceptors.DataGravitatorInterceptor class org.jboss.cache.interceptors.UnlockInterceptor class org.jboss.cache.interceptors.ReplicationInterceptor class org.jboss.cache.interceptors.TxInterceptor class org.jboss.cache.interceptors.CacheMgmtInterceptor 14:40:24,524 INFO [TreeCache] cache mode is REPL_ASYNC 14:40:24,815 WARN [JChannel] option GET_STATE_EVENTS has been deprecated (it is always true now); this option is ignored 14:40:25,035 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.0.20:3384 ------------------------------------------------------- 14:40:27,088 INFO [TreeCache] viewAccepted() for Tomcat-Cluster: [192.168.0.20: 3384|0] [192.168.0.20:3384] 14:40:27,088 INFO [TreeCache] processNewView(): [192.168.0.20:3384|0] [192.168. 0.20:3384] 14:40:27,138 INFO [TreeCache] processNewView(): [192.168.0.20:3384|0] [192.168. 0.20:3384] 14:40:27,138 INFO [TreeCache] TreeCache local address is 192.168.0.20:3384 14:40:27,138 INFO [BuddyManager] Instance 192.168.0.20:3384 broadcasting member ship in buddy pool default to recipients null 14:40:27,138 WARN [NextMemberBuddyLocator] Expected to look for 1 buddies but c ould only find 0 suitable candidates - trying with colocated buddies as well. 14:40:27,138 WARN [NextMemberBuddyLocator] Expected to look for 1 buddies but c ould only find 0 suitable candidates - trying again, ignoring buddy pool hints. 14:40:27,138 WARN [NextMemberBuddyLocator] Expected to look for 1 buddies but c ould only find 0 suitable candidates - trying with colocated buddies as well. 14:40:27,138 WARN [NextMemberBuddyLocator] Expected to look for 1 buddies but c ould only find 0 suitable candidates! 14:40:27,168 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty ... 14:40:34,609 INFO [TreeCache] setting cluster properties from xml to: UDP(ip_mc ast=true;ip_ttl=64;loopback=false;mcast_addr=228.1.2.3;mcast_port=45551; mcast_re cv_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;u cast_sen d_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout= 2000;up_ thread=false):MERGE2(max_interval=20000;min_interval=10000):FD(down_thre ad=false ;shun=true;up_thread=false):VERIFY_SUSPECT(down_thread=false;timeout=150 0;up_thr ead=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192; retransm it_timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false ;timeout =600,1200,2400):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false ;up_thre ad=false):FRAG(down_thread=false;frag_size=8192;up_thread=false):pbcast. GMS(join _retry_timeout=2000;join_timeout=5000;print_local_addr=true;shun=true):p bcast.ST ATE_TRANSFER(down_thread=false;up_thread=false) 14:40:34,639 INFO [TreeCache] setEvictionPolicyConfig(): [config: null] 14:40:34,639 WARN [TreeCache] No transaction manager lookup class has been defi ned. Transactions cannot be used 14:40:34,669 WARN [TreeCache] Using deprecated configuration element 'EvictionP olicyProvider'. This is only provided for 1.2.x backward compatibility and may disappear in future releases. 14:40:34,709 INFO [InterceptorChainFactory] interceptor chain is: class org.jboss.cache.interceptors.CallInterceptor class org.jboss.cache.interceptors.EvictionInterceptor class org.jboss.cache.interceptors.PessimisticLockInterceptor class org.jboss.cache.interceptors.ActivationInterceptor class org.jboss.cache.interceptors.UnlockInterceptor class org.jboss.cache.interceptors.ReplicationInterceptor class org.jboss.cache.interceptors.PassivationInterceptor class org.jboss.cache.interceptors.TxInterceptor class org.jboss.cache.interceptors.CacheMgmtInterceptor 14:40:34,759 INFO [TreeCache] cache mode is REPL_ASYNC 14:40:34,779 WARN [JChannel] option GET_STATE_EVENTS has been deprecated (it is always true now); this option is ignored 14:40:34,799 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.0.20:3391 ------------------------------------------------------- 14:40:36,822 INFO [TreeCache] viewAccepted() for SFSB-Cache: [192.168.0.20:3391 |0] [192.168.0.20:3391] 14:40:36,822 INFO [TreeCache] processNewView(): [192.168.0.20:3391|0] [192.168. 0.20:3391] 14:40:36,842 INFO [TreeCache] processNewView(): [192.168.0.20:3391|0] [192.168. 0.20:3391] 14:40:36,852 INFO [TreeCache] TreeCache local address is 192.168.0.20:3391 14:40:36,852 INFO [TreeCache] transferred state is null (may be first member in cluster) 14:40:36,852 INFO [TreeCache] State could not be retrieved (we are the first me mber in group) 14:40:36,862 INFO [CacheLoaderManager] preloading transient state from cache lo ader org.jboss.cache.loader.FileCacheLoader@17d8769 14:40:36,872 INFO [CacheLoaderManager] preloading transient state from cache lo ader was successful (in 10 milliseconds) 14:40:36,872 INFO [RegionManager] Starting eviction timer 14:40:37,002 INFO [TreeCache] setting cluster properties from xml to: UDP(ip_mc ast=true;ip_ttl=2;loopback=false;mcast_addr=228.1.2.3;mcast_port=43333;m cast_rec v_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;uc ast_send _buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=2 000;up_t hread=false):MERGE2(max_interval=20000;min_interval=10000):FD(down_threa d=true;s hun=true;up_thread=true):VERIFY_SUSPECT(down_thread=false;timeout=1500;u p_thread =false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;ret ransmit_ timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false;mi n_thresh old=10;timeout=600,1200,2400;window_size=100):pbcast.STABLE(desired_avg_ gossip=2 0000;down_thread=false;up_thread=false):FRAG(down_thread=false;frag_size =8192;up _thread=false):pbcast.GMS(join_retry_timeout=2000;join_timeout=5000;prin t_local_ addr=true;shun=true):pbcast.STATE_TRANSFER(down_thread=false;up_thread=f alse) 14:40:37,022 INFO [TreeCache] setEvictionPolicyConfig(): [config: null] 14:40:37,032 WARN [TreeCache] Using deprecated configuration element 'EvictionP olicyProvider'. This is only provided for 1.2.x backward compatibility and may disappear in future releases. 14:40:37,032 INFO [InterceptorChainFactory] interceptor chain is: class org.jboss.cache.interceptors.CallInterceptor class org.jboss.cache.interceptors.EvictionInterceptor class org.jboss.cache.interceptors.PessimisticLockInterceptor class org.jboss.cache.interceptors.UnlockInterceptor class org.jboss.cache.interceptors.ReplicationInterceptor class org.jboss.cache.interceptors.TxInterceptor class org.jboss.cache.interceptors.CacheMgmtInterceptor 14:40:37,102 INFO [TreeCache] cache mode is REPL_SYNC 14:40:37,122 ERROR [UNICAST] window_size is deprecated and will be ignored 14:40:37,122 ERROR [UNICAST] min_threshold is deprecated and will be ignored 14:40:37,122 WARN [JChannel] option GET_STATE_EVENTS has been deprecated (it is always true now); this option is ignored 14:40:37,142 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.0.20:3394 ------------------------------------------------------- 14:40:39,185 INFO [TreeCache] viewAccepted() for EJB3-entity-cache: [192.168.0. 20:3394|0] [192.168.0.20:3394] 14:40:39,185 INFO [TreeCache] processNewView(): [192.168.0.20:3394|0] [192.168. 0.20:3394] 14:40:39,185 INFO [TreeCache] processNewView(): [192.168.0.20:3394|0] [192.168. 0.20:3394] 14:40:39,185 INFO [TreeCache] TreeCache local address is 192.168.0.20:3394 14:40:39,185 INFO [TreeCache] transferred state is null (may be first member in cluster) 14:40:39,185 INFO [TreeCache] State could not be retrieved (we are the first me mber in group) 14:40:39,185 INFO [RegionManager] Starting eviction timer -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-586) Modify Messaging's Labs landing page so it's easy to go to the source code (SVN repository)

by Ovidiu Feodorov (JIRA)

Modify Messaging's Labs landing page so it's easy to go to the source code (SVN repository) ------------------------------------------------------------------------------------------- Key: JBMESSAGING-586 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-586 Project: JBoss Messaging Issue Type: Task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Trivial Fix For: 1.2.0.Alpha2 -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
9
0 / 0

[JBoss JIRA] Created: (JGRP-366) Show whether a member left gracefully or ungracefully (crash)

by Bela Ban (JIRA)

Show whether a member left gracefully or ungracefully (crash) ------------------------------------------------------------- Key: JGRP-366 URL: http://jira.jboss.com/jira/browse/JGRP-366 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Priority: Optional Fix For: 2.6 Could be a simple tag in the View for each crashed member (default is graceful leave). Possibly API change, tbd -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-569) Typographical error in the documentation.

by Ramakrishnan Subramanian (JIRA)

Typographical error in the documentation. ----------------------------------------- Key: JBRULES-569 URL: http://jira.jboss.com/jira/browse/JBRULES-569 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Ramakrishnan Subramanian Assigned To: Mark Proctor Priority: Trivial Typographical error in this URL: http://labs.jboss.com/file-access/default/members/jbossrules/freezone/doc... Under section 1.6.4. WorkingMemory ..."however this is a weak reference, so it should eventually me garbage collected anyway. ". It should be "however this is a weak reference, so it should eventually be garbage collected anyway. " Under section 1.6.4.2. Assertion. ..."however, no rules are executedl you call "fireAllRules()" should be "however, no rules are executed until you call "fireAllRules()" -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-525) better documentation for globals

by Mark Proctor (JIRA)

better documentation for globals -------------------------------- Key: JBRULES-525 URL: http://jira.jboss.com/jira/browse/JBRULES-525 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 documentations for globals needs padding out some more, maybe with a few use case examples. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-485) Add "collect" conditional element

by Edson Tirelli (JIRA)

Add "collect" conditional element --------------------------------- Key: JBRULES-485 URL: http://jira.jboss.com/jira/browse/JBRULES-485 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 3.1-m1 Add "collect" conditional element. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-488) Create documentation for "collect" conditional element

by Edson Tirelli (JIRA)

Create documentation for "collect" conditional element ------------------------------------------------------ Key: JBRULES-488 URL: http://jira.jboss.com/jira/browse/JBRULES-488 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 3.1-m1 Add documentation for "collect" conditional element. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-480) update documentation with 'accumulate' information

by Edson Tirelli (JIRA)

update documentation with 'accumulate' information -------------------------------------------------- Key: JBRULES-480 URL: http://jira.jboss.com/jira/browse/JBRULES-480 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assigned To: Edson Tirelli -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
4
0 / 0

[JBoss JIRA] Created: (JBAOP-278) Make AbstractAnnotationMetaData use correct classloader for loading annotation class

by Kabir Khan (JIRA)

Make AbstractAnnotationMetaData use correct classloader for loading annotation class ------------------------------------------------------------------------------------ Key: JBAOP-278 URL: http://jira.jboss.com/jira/browse/JBAOP-278 Project: JBoss AOP Issue Type: Sub-task Reporter: Kabir Khan -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-99) Make AbstractAnnotationMetaData use correct classloader for loading annotation class

by Kabir Khan (JIRA)

Make AbstractAnnotationMetaData use correct classloader for loading annotation class ------------------------------------------------------------------------------------ Key: JBMICROCONT-99 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-99 Project: JBoss MicroContainer Issue Type: Task Reporter: Kabir Khan It currently uses the TCL, but this might not always be correct? -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

4
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006