July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-478) Create "deploy" Mojo for maven-jboss-as-control-plugin

by Andrew Lee Rubinger (JIRA)

Create "deploy" Mojo for maven-jboss-as-control-plugin ------------------------------------------------------ Key: JBBUILD-478 URL: http://jira.jboss.com/jira/browse/JBBUILD-478 Project: JBoss Build System Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger The JBoss AS Control Plugin currently has Mojos for "createConfiguration", "start", and "stop". We need to add a "deploy" Mojo which delegates to congruent functionality from jboss-test. Existing Mojos: http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk/maven-jboss-as-c... Root Checkout Location: http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk After the "deploy" Mojo is created, configuration to use it should be added to the "maven-jboss-as-control-example" project, following examples already in place in the POM. This is the self-documenting usage project which may also prove its validity. -- 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

12 years, 2 months

3
14
0 / 0

[JBoss JIRA] Created: (JBASMP-5) Rename folder structure of modules

by Andrew Lee Rubinger (JIRA)

Rename folder structure of modules ---------------------------------- Key: JBASMP-5 URL: http://jira.jboss.com/jira/browse/JBASMP-5 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Modules are currently namespaced with "maven-jboss-as-", which is unnecessary due to the groupId and folder structure. For instance: maven-jboss-as-build ...should become: build -- 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

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-8) Switch Log4J/Commons Logging in favor of AbstractMojo.getLog() where applicable

by Andrew Lee Rubinger (JIRA)

Switch Log4J/Commons Logging in favor of AbstractMojo.getLog() where applicable ------------------------------------------------------------------------------- Key: JBASMP-8 URL: https://jira.jboss.org/jira/browse/JBASMP-8 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 0.1.0 Replace all instances of non-Maven Logging code to AbstractMojo.getLog() within the Mojos themselves -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-4) Implement Deltas-only copying of configurations

by Andrew Lee Rubinger (JIRA)

Implement Deltas-only copying of configurations ----------------------------------------------- Key: JBASMP-4 URL: http://jira.jboss.com/jira/browse/JBASMP-4 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger >From Antony Stubbs: The other thing I noticed is that the JbossAsControlCreateConfigurationMojo doesn't seem to perform a delta copy as ALR has mentioned in places, but instead copies the entire directory every time and overwrites existing files. Is this a feature worth pursuing? It took quite a long time (at least 60 seconds) copying the config directory on every invoke for me - i.e. it appears worth it to me. -- 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

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBASMP-9) Change default overlayLocation to src/jbossas/resources

by Andrew Lee Rubinger (JIRA)

Change default overlayLocation to src/jbossas/resources ------------------------------------------------------- Key: JBASMP-9 URL: https://jira.jboss.org/jira/browse/JBASMP-9 Project: JBoss AS Maven Plugins Issue Type: Task Components: control-plugin Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger src/main/resources is for application/module resources; move the default for JBossAS Configuration files into their own namespace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-3) Review and Commit Patches by Antony Stubbs

by Andrew Lee Rubinger (JIRA)

Review and Commit Patches by Antony Stubbs ------------------------------------------ Key: JBASMP-3 URL: http://jira.jboss.com/jira/browse/JBASMP-3 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Community Contributor Antony Stubbs has provided patched (in linked issue). This task is to track their commits to a release. -- 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

12 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBASMP-6) Align current versions to all start at 0.1.0-SNAPSHOT

by Andrew Lee Rubinger (JIRA)

Align current versions to all start at 0.1.0-SNAPSHOT ----------------------------------------------------- Key: JBASMP-6 URL: http://jira.jboss.com/jira/browse/JBASMP-6 Project: JBoss AS Maven Plugins Issue Type: Task Components: build, common, control-example, control-plugin Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: 0.1.0 POMs should be set to same version, 0.1.0-SNAPSHOT, including the Aggregator POM -- 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

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-592) Pluggable policy for picking coordinator

by Bela Ban (JIRA)

Pluggable policy for picking coordinator ---------------------------------------- Key: JGRP-592 URL: http://jira.jboss.com/jira/browse/JGRP-592 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6 Make policy to pick coordinator pluggable. Pick new coordinator after existing coordinator crashes by calling this policy. Default policy is to pick the next in line. Other policies could pick the next in line from a set of pinned coordinator, so certain members can never become coordinators. -- 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

12 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JGRP-495) Memory leak in NAKACK

by Bela Ban (JIRA)

Memory leak in NAKACK --------------------- Key: JGRP-495 URL: http://jira.jboss.com/jira/browse/JGRP-495 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Priority: Blocker Fix For: 2.5 Probably due to the changes introduced in NAKACK/NakReceiverWindow (http://jira.jboss.com/jira/browse/JGRP-281). To reproduce, run perf.Test on 2 nodes with 1 million 1K messages each. JProfiler shows that we are leaking Map.Entry instances in NAKACK. They seem to accumulate in xmit_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

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-364) When using TCP_NIO, starting two nodes at the same time causes one of the nodes not to join group

by Matthew Todd (JIRA)

When using TCP_NIO, starting two nodes at the same time causes one of the nodes not to join group ------------------------------------------------------------------------------------------------- Key: JGRP-364 URL: http://jira.jboss.com/jira/browse/JGRP-364 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Environment: linux 2.6 kernel x86_64 running java 1.5.0_06 Reporter: Matthew Todd Assigned To: Bela Ban I am testing a jgroups tcp_nio configuration using the draw demo.If I start up my 3 nodes one by one then everything works fine. However if I start up node 1, then attempt to start node 2 and 3 in parallel then only node 2 will work. Node 3 will be isolated and not see the other nodes and logs the following message: org.jgroups.protocols.pbcast.ClientGmsImpl join WARNING: join(192.158.70.200:7802) sent to 192.158.70.200:7800 timed out, retrying I am starting the draw demo like this; java -cp jgroups-all.jar:commons-logging.jar:concurrent.jar:jmxri.jar org.jgroups.demos.Draw -props test.xml Here is the configuration for one of my nodes: <config> <TCP_NIO bind_addr="192.158.70.200" recv_buf_size="20000000" send_buf_size="640000" loopback="false" discard_incompatible_packets="true" max_bundle_size="64000" max_bundle_timeout="30" use_incoming_packet_handler="true" use_outgoing_packet_handler="true" down_thread="false" up_thread="false" enable_bundling="true" start_port="7800" end_port="7800" use_send_queues="false" sock_conn_timeout="300" skip_suspected_members="true" /> <MPING timeout="2000" num_initial_members="3" mcast_addr="229.6.7.8" bind_addr="192.158.70.200" down_thread="false" up_thread="false"/> <MERGE2 max_interval="100000" down_thread="false" up_thread="false" min_interval="20000"/> <FD_SOCK down_thread="false" up_thread="false"/> <VERIFY_SUSPECT timeout="1500" down_thread="false" up_thread="false"/> <pbcast.NAKACK max_xmit_size="60000" use_mcast_xmit="false" gc_lag="0" retransmit_timeout="300,600,1200,2400,4800" down_thread="true" up_thread="true" discard_delivered_msgs="true"/> <pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000" down_thread="false" up_thread="false" max_bytes="400000"/> <pbcast.GMS print_local_addr="true" join_timeout="3000" down_thread="true" up_thread="true" join_retry_timeout="2000" shun="true" view_bundling="true"/>  <pbcast.STATE_TRANSFER/>  </config> Node 2 and 3 have the same configuration except the port they bind to has been changed -- 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

12 years, 4 months

5
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008