October 2012 - jboss-jira - Jboss List Archives

[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

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-682) http://repository.jboss.org/maven2/ serving HTTP 403 to hosts outside RedHat VPN

by Marek Schmidt (JIRA)

http://repository.jboss.org/maven2/ serving HTTP 403 to hosts outside RedHat VPN -------------------------------------------------------------------------------- Key: JBBUILD-682 URL: https://issues.jboss.org/browse/JBBUILD-682 Project: JBoss Build System Issue Type: Bug Reporter: Marek Schmidt Assignee: Paul Gier Priority: Critical The legacy maven repository http://repository.jboss.org/maven2/ is serving HTTP 403 to hosts outside RedHat VPN, causing lots of builds to fail. e.g. http://community.jboss.org/message/606819?tstart=0 with error: Access denied to: http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

11
23
0 / 0

[JBoss JIRA] Created: (JBBUILD-666) upload hsqldb 2.0.1-rc3 to our nexus

by Strong Liu (JIRA)

upload hsqldb 2.0.1-rc3 to our nexus ------------------------------------ Key: JBBUILD-666 URL: https://issues.jboss.org/browse/JBBUILD-666 Project: JBoss Build System Issue Type: Task Components: Sonatype Reporter: Strong Liu Assignee: Paul Gier since hsqldb 2.0.0 has some problems, we need 2.0.1-rc3 to run the test now, only 2.0.0 is available on the nexus (maven-central) so, would you please upload this one http://sourceforge.net/projects/hsqldb/files/alpha_beta/hsqldb-2.0.1-rc3.... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-8134) Common mechanism for all secure socket definitions

by Brian Stansberry (JIRA)

Common mechanism for all secure socket definitions -------------------------------------------------- Key: JBAS-8134 URL: https://jira.jboss.org/browse/JBAS-8134 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> The JAASSecurityDomain in my opinion should >> handle all secure socket definitions. Mod-cluster currently does >> not support JAASSecurityDomains. I won't comment either way on whether JAASSecurityDomain is how we'll do this, but I definitely agree that a common mechanism should be used for all secure socket definitions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

6
12
0 / 0

[JBoss JIRA] Created: (JGRP-1326) Gossip Router dropping message for node that is in its routing table list

by vivek v (JIRA)

Gossip Router dropping message for node that is in its routing table list ------------------------------------------------------------------------- Key: JGRP-1326 URL: https://issues.jboss.org/browse/JGRP-1326 Project: JGroups Issue Type: Bug Affects Versions: 2.10 Environment: Linux, Windows Reporter: vivek v Assignee: Bela Ban We are using Tunnel protocol with two Gossip Routers. For some reason we start seeing lots of suspect messages in all the nodes - there are 7 nodes in the group. Six of the nodes (including the coordinator) was suspecting node A (manager_172.27.75.11) and node A was suspecting the coordinator, but no new view was being created. After turning on the trace on both gossip routers (GR1 and GR2) I see following for every message that's sent to Node A (manager_172.27.75.11), {noformat} 2011-05-20 15:56:21,186 TRACE [gossip-handlers-6] GossipRouter - cannot find manager_172.27.75.11:4576 in the routing table, routing table= 172.27.75.11_group: probe_172.27.75.13:4576, collector_172.27.75.12:4576, probe_172.27.75.15:4576, manager_172.27.75.11:4576, probe_172.27.75.16:4576, probe_172.27.75.14:4576 {noformat} Now, the issue is the routing table does indeed shows that there is "manager_172.27.75.11" - so why is the GR dropping messages for that node. I suspect that somehow the Gossip Router has got some old entry which has not been cleaned up - different UUID with same logical address. I tried going through the GossipRouter.java code, but couldn't find how would this be possible. As I understand a node randomly chooses a GR if there are multiple of them for its communication. Each GR would keep a separate list of physical addresses for each node - so is it possible somehow it uses physical address instead of UUID for cleaning/retrieving the node list? This seems to be creating big issue and the only work around is to restart the Gossip Routers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
13
0 / 0

[JBoss JIRA] (AS7-5574) Switch to standard Java debug options -agentlib

by Cheng Fang (JIRA)

Cheng Fang created AS7-5574: ------------------------------- Summary: Switch to standard Java debug options -agentlib Key: AS7-5574 URL: https://issues.jboss.org/browse/AS7-5574 Project: Application Server 7 Issue Type: Feature Request Components: Documentation, Scripts Affects Versions: 7.2.0.Alpha1 Reporter: Cheng Fang Assignee: Brian Stansberry AS7 currently has the Java debug options -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n This uses non-standard options, which may be removed in future JDK, and may not work with other vendors' JDK. How about switching to use the standard options, to make it easier to maintain and port? -agentlib:jdwp=transport=dt_socket,address=localhost:8787,server=y,suspend=n -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] (AS7-5059) Deprecate no-arg OperationContext.completeStep() variant

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5059: ------------------------------------- Summary: Deprecate no-arg OperationContext.completeStep() variant Key: AS7-5059 URL: https://issues.jboss.org/browse/AS7-5059 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Deprecate OperationContext.completeStep() in favor of OperationContext.completeStep(RollbackHandler) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
5
0 / 0

[JBoss JIRA] (AS7-5697) Verify that optional imports work as expected

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5697: ----------------------------------- Summary: Verify that optional imports work as expected Key: AS7-5697 URL: https://issues.jboss.org/browse/AS7-5697 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] (AS7-5637) Broken footer layout

by Heiko Braun (JIRA)

Heiko Braun created AS7-5637: -------------------------------- Summary: Broken footer layout Key: AS7-5637 URL: https://issues.jboss.org/browse/AS7-5637 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 See JBPAPP-10016 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
3
0 / 0

[JBoss JIRA] (AS7-5447) The footer linkes (rhs) overlay each other

by Heiko Braun (JIRA)

Heiko Braun created AS7-5447: -------------------------------- Summary: The footer linkes (rhs) overlay each other Key: AS7-5447 URL: https://issues.jboss.org/browse/AS7-5447 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
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 October 2012