May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3766) Port the webservice deployer

by Scott M Stark (JIRA)

Port the webservice deployer ---------------------------- Key: JBAS-3766 URL: http://jira.jboss.com/jira/browse/JBAS-3766 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott M Stark Assigned To: Thomas Diesler Fix For: JBossAS-5.0.0.Beta The old jmx/interceptor based jbossws deployer is now complete broken: *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} jboss.ws:service=DeployerInterceptorEJB21 -> jboss.ejb:service=EJBDeployer{Create:** NOT FOUND **} -> jboss.ejb:service=EJBDeployer{Start:** NOT FOUND **} jboss.ws:service=DeployerInterceptorEJB3 -> jboss.ejb3:service=EJB3Deployer{Create:** NOT FOUND **} -> jboss.ejb3:service=EJB3Deployer{Start:** NOT FOUND **} jboss.ws:service=DeployerInterceptorNestedJSE -> jboss.ws:service=WebServiceDeployerJSE{Start:Configured} -> jboss.ws:service=WebServiceDeployerJSE{Create:Configured} jboss.ws:service=WebServiceDeployerJSE -> jboss.web:service=WebServer{Start:** NOT FOUND **} -> jboss.web:service=WebServer{Create:** NOT FOUND **} *** CONTEXTS IN ERROR: Name -> Error jboss.web:service=WebServer -> ** NOT FOUND ** jboss.ejb3:service=EJB3Deployer -> ** NOT FOUND ** jboss.ejb:service=EJBDeployer -> ** NOT FOUND ** It needs to be ported to a deployer that augments the metadata passed to other deployers. This means no unapckaing of wars to modify the war descriptors. -- 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

18 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (BPEL-200) Redeployment of a changed PAR (with modified .bpel) requires App Server Restart

by Burr Sutter (JIRA)

Redeployment of a changed PAR (with modified .bpel) requires App Server Restart ------------------------------------------------------------------------------- Key: BPEL-200 URL: http://jira.jboss.com/jira/browse/BPEL-200 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 1 Environment: JBoss 4.0.4.GA with EJB3 using beta JEMS installer Reporter: Burr Sutter Assigned To: Alejandro Guizar Simply modifying the .bpel script, running pack-definition and deploy-definition do not reload/restart the process (even though all process instances have terminated). The only thing I've found that refreshes the BPEL engine properly is to restart the App Server. -- 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

18 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-394) Performance enhancements

by Bela Ban (JIRA)

Performance enhancements ------------------------ Key: JGRP-394 URL: http://jira.jboss.com/jira/browse/JGRP-394 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 - NAKACK.handleMessage(): NakReceiver.add() --> Retransmitter.add() --> TimeScheduler.add() is quite costly; we also iterate through a linear list when removing a message from the Retransmitter ! -- 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

18 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JGRP-461) Add highest_deliverable to NakreceiverWindow

by Bela Ban (JIRA)

Add highest_deliverable to NakreceiverWindow -------------------------------------------- Key: JGRP-461 URL: http://jira.jboss.com/jira/browse/JGRP-461 Project: JGroups Issue Type: Sub-task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Currently, we use highest_delivered (= removed) seqno, highest_deliverable would purge more messages faster, if we have a slow receiver (slow to call receive()) -- 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

18 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-281) Investigate whether sent messages need to be buffered in NAKACK

by Bela Ban (JIRA)

Investigate whether sent messages need to be buffered in NAKACK --------------------------------------------------------------- Key: JGRP-281 URL: http://jira.jboss.com/jira/browse/JGRP-281 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1, 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 NAKACK buffers sent messages in sent-table and received messages in received-table. We might be able to discard sent-table entirely because received-table will contain a message sent by oneself ! Once we have loopback in place by default, we can be sure that any message sent by P will be in P's received-table. -- 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

18 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (JGRP-487) Rewrite Retransmitter

by Bela Ban (JIRA)

Rewrite Retransmitter --------------------- Key: JGRP-487 URL: http://jira.jboss.com/jira/browse/JGRP-487 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 Attachments: Retransmitter.java The old Retransmitter is (a) too complex and (b) uses a linear list of Entries as retransmission list, which has a cost proportional to the number of messages in the retransmit buffer. We should switch to using simple scheduled futures with the TimeScheduler for retransmissions and cancel the futures when a message has been acked. The new Retransmitter.java is attached -- 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

18 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-462) NAKACK: remove bundling for retransmitted messages

by Bela Ban (JIRA)

NAKACK: remove bundling for retransmitted messages -------------------------------------------------- Key: JGRP-462 URL: http://jira.jboss.com/jira/browse/JGRP-462 Project: JGroups Issue Type: Task Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, all retransmitted messages are sent in batches (governed by max_xmit_size). This is redundant, as TP also provides bundling. A quick change of code showed that individual retransmissions is as fast as batched retransmission. This functionality can therefore be removed -- 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

18 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-510) NAKACK: adjust retransmission times based on statistics

by Bela Ban (JIRA)

NAKACK: adjust retransmission times based on statistics ------------------------------------------------------- Key: JGRP-510 URL: http://jira.jboss.com/jira/browse/JGRP-510 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6 NAKACK can maintain a rolling average of the time it takes for a missing message to get retransmitted (time between sending the XMIT-REQ and reception of the missing message). This can be done per sender. The retransmit_timeout values can be based on the rolling average, e.g. make this completely dynamic: instead of a set of retransmit timeouts we only define a retransmit_timeout, e.g. 30ms. If a message is not able to get retransmitted the first time, we simply double that value (exponential backoff), until a max limit is reached. When we discover that the rolling timeout is less than 30ms (e.g. 4ms), then we lower the retransmission timeout, e.g. to 4 ms (plus possibly a safety time, say 2ms), to a total of 6ms. This will make message retransmission faster, since we don't have to wait for 30ms to ask for retransmission. OTOH, if the rolling average increases, we can also increase our retransmission timeout, to avoid overloading the network with spurious retransmission requests. RESULT: message retransmission is more dynamic: - Retransmit timeout is *per sender* - On low retransmission ack times, we ask for retransmission sooner, therefore increasing message rates - On high retransmission ack times, we throttle retransmission timeouts (and use exponential backoff), therefore reducing traffic -- 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

18 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-678) Remove spring dependency

by Geoffrey De Smet (JIRA)

Remove spring dependency ------------------------ Key: JBRULES-678 URL: http://jira.jboss.com/jira/browse/JBRULES-678 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Once the configuration xml is extracted this should be a peice of cake -- 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

18 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-642) Extract solver configuration

by Geoffrey De Smet (JIRA)

Extract solver configuration ---------------------------- Key: JBRULES-642 URL: http://jira.jboss.com/jira/browse/JBRULES-642 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Mark Proctor Priority: Critical Preferable into an xml file. Should help to make the integration tests easier to do. -- 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

18 years, 11 months

3
4
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 May 2007