July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBSER-48) Integrating/Extending Metadata with JBossMC Metadata repository

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBSER-48?page=all ] Clebert Suconic updated JBSER-48: --------------------------------- Fix Version/s: 1.1.0 Beta (was: 1.0.2 GA) > Integrating/Extending Metadata with JBossMC Metadata repository > --------------------------------------------------------------- > > Key: JBSER-48 > URL: http://jira.jboss.com/jira/browse/JBSER-48 > Project: JBoss Serialization > Issue Type: Task > Affects Versions: 1.0.0 RC 2 > Reporter: Clebert Suconic > Assigned To: Clebert Suconic > Fix For: 1.1.0 Beta > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-970) some management portlet ui encachements

by Boleslaw Dawidowicz (JIRA)

some management portlet ui encachements --------------------------------------- Key: JBPORTAL-970 URL: http://jira.jboss.com/jira/browse/JBPORTAL-970 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Priority: Optional add pagination and sort by columnt for portlet and instances tables alphabetical sorting for combo boxes content some other stuff to increase usuability -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Commented: (JGRP-217) unplugging of network cable makes jgroups behave weirdly

by David Forget (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-217?page=comments#action_12340221 ] David Forget commented on JGRP-217: ----------------------------------- This issue is also present when using UDP. The workaround is not valid and maybe priority of this issue should be increase. > unplugging of network cable makes jgroups behave weirdly > -------------------------------------------------------- > > Key: JGRP-217 > URL: http://jira.jboss.com/jira/browse/JGRP-217 > Project: JGroups > Issue Type: Bug > Affects Versions: 2.2.8, 2.2.9, 2.3 > Reporter: Manoranjan Sahu > Assigned To: Bela Ban > Fix For: 2.4 > > Attachments: logs.jar, mping.xml > > > Hi, > I am using jgroups 2.2.9 for communication in my cluster. > I was checking the behaviour of jgroups to network fluctuation. > for that I manually unplug the network cable and plug it back after some time. > But jgroups keeps sending suspected messages and never bring that into the cluster. > I have two machines in my cluster A(10.200.1.92) & B(10.200.1.74). > I unplug the cable in machine B. and plug it back . but B never joined the cluster. > Please find the attachment for the log files from both the machines. > I am using TCP based communication. I set up my protocol stack using . MPING,MERGE2,FD,VERIFY_SUSPECT,pbcast.NAKACK,pbcast.STABLE,VIEW_SYNC,pbcast.GMS. > The following are the confuguration in both the machines. > configuration setting in Machine-A > notificationbus.properties: > TCP(bind_addr=boca;recv_buf_size=200000;send_buf_size=100000;loopback=true; > start_port=7880): > MPING(timeout=4000;bind_to_all_interfaces=true;mcast_addr=228.8.8.8;mcast_port=7500; > ip_ttl=8;num_initial_members=4;num_ping_requests=1): > MERGE2(max_interval=10000;min_interval=5000): > FD(timeout=2000;max_tries=3): > VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): > pbcast.NAKACK(max_xmit_size=60000;gc_lag=50; > retransmit_timeout=100,200,300,600,1200,2400,4800): > pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false; > up_thread=false;max_bytes=0): > VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false): > pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true) > ------------------------------- > configuration setting in Machine-B > notificationbus.properties: > TCP(bind_addr=rizal;recv_buf_size=200000;send_buf_size=100000; > loopback=true;start_port=7880): > MPING(timeout=4000;bind_to_all_interfaces=true;mcast_addr=228.8.8.8; > mcast_port=7500;ip_ttl=8;num_initial_members=4;num_ping_requests=1): > MERGE2(max_interval=10000;min_interval=5000):FD(timeout=2000;max_tries=3): > VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): > pbcast.NAKACK(max_xmit_size=60000;gc_lag=50; > retransmit_timeout=100,200,300,600,1200,2400,4800): > pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false; > up_thread=false;max_bytes=0): > VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false): > pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true) > ---------------- -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBIDE-326) Integrate JBossCache IDE into build/bundle

by Marshall Culpepper (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-326?page=all ] Marshall Culpepper reopened JBIDE-326: -------------------------------------- > Integrate JBossCache IDE into build/bundle > ------------------------------------------ > > Key: JBIDE-326 > URL: http://jira.jboss.com/jira/browse/JBIDE-326 > Project: JBoss IDE > Issue Type: Task > Components: Build System (Releng) > Reporter: Marshall Culpepper > Assigned To: Marshall Culpepper > Fix For: 2.0.0.Beta1 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-326) Integrate JBossCache IDE into build/bundle

by Marshall Culpepper (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-326?page=all ] Marshall Culpepper updated JBIDE-326: ------------------------------------- Fix Version/s: 2.0.0.Beta1 (was: 2.0.0.GA) > Integrate JBossCache IDE into build/bundle > ------------------------------------------ > > Key: JBIDE-326 > URL: http://jira.jboss.com/jira/browse/JBIDE-326 > Project: JBoss IDE > Issue Type: Task > Components: Build System (Releng) > Reporter: Marshall Culpepper > Assigned To: Marshall Culpepper > Fix For: 2.0.0.Beta1 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-265) Multiplexer: additional_data is dropped in MuxChannel

by Bela Ban (JIRA)

Multiplexer: additional_data is dropped in MuxChannel ----------------------------------------------------- Key: JGRP-265 URL: http://jira.jboss.com/jira/browse/JGRP-265 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1, 2.3 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 HAPartition makes use of the "additional_data" feature to ensure the unique identity of each member of the partition. This breaks with the MUX if the Channel is connected before HAPartition gets a chance to set the additional_data. This could be a general problem with additional_data -- one service using a shared channel wants to make use of additional_data, but the channel is already connected, so all the IpAddress objects in the views around the cluster won't have the additional_data. This *may* not be a big deal, as logical addresses (JGRP-129) remove some of the need for additional data. If people use additional_data for some other reason than logical addresses, then it may be an issue. For the HAPartition use case, I created a temporary workaround by creating an org.jboss.ha subclass of JChannelFactory, and having the subclass ensure the additional_data is set before handing out a channel. This ensures that no matter what service starts the underlying channel, the additional_data HAPartition wants will be there. This will suffice until JGRP-129 is done, after which HAPartition won't need additional_data. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBAS-1486) Allow for deployments without an explicit suffix

by Scott M Stark (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1486?page=all ] Scott M Stark reassigned JBAS-1486: ----------------------------------- Assignee: Scott M Stark > Allow for deployments without an explicit suffix > ------------------------------------------------ > > Key: JBAS-1486 > URL: http://jira.jboss.com/jira/browse/JBAS-1486 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX, Deployment services > Affects Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.0.5.CR1 > > > A not uncommon request is to allow for deployments that do not have a qualifying suffix, for example, myejb/ instead of myejb.jar/, mywebapp instead of mywebapp.war > Most deployers require both a sepcific suffix and the correct deployment descriptor to exist in order to accept the deployment. We should look into supporting such deployments. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-526) extended exception handling for timer and command execution

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-526?page=all ] Tom Baeyens closed JBPM-526. ---------------------------- Resolution: Rejected this doesn't fit in the target scope of the jbpm scheduler and timer. the jbpm out-of-the-box timer and scheduler are targetted for java standard edition. and hence they got some limitations. if you need more features, you need to configure use the JMS based messaging and create a timer service based on the jboss scheduler or quartz. more out of the box support for these latter environments will be created in the near future. hopefully for the 3.2 release > extended exception handling for timer and command execution > ----------------------------------------------------------- > > Key: JBPM-526 > URL: http://jira.jboss.com/jira/browse/JBPM-526 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > it should be possible to configure a retry number on a given queue or on a given timer or asynchonous executed command. > also, a notification scheme should be implemented in case a timer or asynchronous command ends up in the error queue. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-712) Improved Documentation on ProcessInstance Lifecycle

by Ryan Campbell (JIRA)

Improved Documentation on ProcessInstance Lifecycle --------------------------------------------------- Key: JBPM-712 URL: http://jira.jboss.com/jira/browse/JBPM-712 Project: JBoss jBPM Issue Type: Feature Request Components: Documentation Affects Versions: jBPM 3.1.1 Reporter: Ryan Campbell Assigned To: Tom Baeyens Fix For: jBPM 3.2 Detailed design documentation on the lifecycle of a jBPM process. For instance: - When are things intialized, when are they saved to the database? - Can you control the flushing of the HibernateSession to improve performance - How many threads are created when using asynchronous processing? Is there a setting exposed to control this thread group? - Can you control how much logging jBPM does as this seems to be a high cost when processing large numbers of events? -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-109) Remove the need for OrderedList to improve performance

by Mark Little (JIRA)

Remove the need for OrderedList to improve performance ------------------------------------------------------ Key: JBTM-109 URL: http://jira.jboss.com/jira/browse/JBTM-109 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Priority: Minor -- 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, 11 months

1
0
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 July 2006