July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1496) Views can overtake one another the wrong view is installed

by David Hotham (JIRA)

David Hotham created JGRP-1496: ---------------------------------- Summary: Views can overtake one another the wrong view is installed Key: JGRP-1496 URL: https://issues.jboss.org/browse/JGRP-1496 Project: JGroups Issue Type: Feature Request Reporter: David Hotham Assignee: Bela Ban As noted in JGRP-1495; but since I'm now claiming two bugs I should have two tickets... - View 1 arrives on Thread Incoming-1. Let's say this thread gets to GMS.installView, and then pauses just after the debug trace at line 600 ("installing view") - View 2 arrives on Thread Incoming-2. It's a newer view, and is fully installed and notified to everyone. - Thread Incoming-1 picks up, and completes the installation of View 1 Now everyone has View 1, but the correct view should be View 2. -- 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, 10 months

2
7
0 / 0

[JBoss JIRA] (JBJCA-863) Add support for maximum-free-thread scheduler in DWM

by Stefano Maestri (JIRA)

Stefano Maestri created JBJCA-863: ------------------------------------- Summary: Add support for maximum-free-thread scheduler in DWM Key: JBJCA-863 URL: https://issues.jboss.org/browse/JBJCA-863 Project: IronJacamar Issue Type: Task Reporter: Stefano Maestri Assignee: Stefano Maestri -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] (JGRP-1433) RELAY2: multi-site clustering

by Bela Ban (JIRA)

Bela Ban created JGRP-1433: ------------------------------ Summary: RELAY2: multi-site clustering Key: JGRP-1433 URL: https://issues.jboss.org/browse/JGRP-1433 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 Successor to RELAY. The biggest differences are: - Multicast messages are not relayed by default (has to be enabled in the protocol config, or per message (via flag)) - Multiple sites can be connected, e.g. in a tree structure - There is no virtual view; every site gets the view for its local cluster. The application can fetch -- 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, 10 months

1
6
0 / 0

[JBoss JIRA] (JGRP-1487) X509Token Authentication vulnerable to replay attacks

by sreenivas chinimilli (JIRA)

sreenivas chinimilli created JGRP-1487: ------------------------------------------ Summary: X509Token Authentication vulnerable to replay attacks Key: JGRP-1487 URL: https://issues.jboss.org/browse/JGRP-1487 Project: JGroups Issue Type: Bug Affects Versions: 3.0.9 Reporter: sreenivas chinimilli Assignee: Bela Ban In the implementation of X509Token Authentication The auth_value is enrypted with the certificate within the keystore and during verification encrypted auth value is decrypted with the private key compared against the orignial auth value. This implementation is prone to replay attacks, that is any user with out having any knowledge of the auth value can join the group by replaying the enrypted auth value captured in earlier sessions. -- 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, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format

by Paul Gier (JIRA)

Migrate existing Nexus Audit information to standard XML format --------------------------------------------------------------- Key: JBBUILD-670 URL: https://issues.jboss.org/browse/JBBUILD-670 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: John Casey Fix For: Build Support 2011 We currently have audit information (username, timestamp) stored in .json files in the repository. Nexus uses an XML format to store this information, and recent versions of Nexus allow easy way to view this information in the Nexus UI. The existing audit information should be migrated to the standard Nexus XML format. These XML files are located in the directory "sonatype-work/nexus/proxy/attributes". For each file in each Maven repository hosted by Nexus, there is a file with the same name in this attributes directory. For example, "sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar" is actually an XML file containing the attributes for the named jar file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
9
0 / 0

[JBoss JIRA] Created: (JBBUILD-523) Issues with custom packaging in maven

by Paul Gier (JIRA)

Issues with custom packaging in maven ------------------------------------- Key: JBBUILD-523 URL: https://jira.jboss.org/jira/browse/JBBUILD-523 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2009 Steve ran into some issues when using custom packaging for the jdocbook plugin. - Transitive dependency resolution does not work - Two dependencies with the same packaging but different artifact handlers cannot both be resolved, because no info about the handler is encoded into the repo - The plugin containing the custom packaging needs to programmatically register the artifact handler in addition to specifiying it in the components.xml this has to be done by: (1) retrieve the handler using @parameter expression="${component.org.apache.maven.artifact.handler.ArtifactHandler#jdocbook-style}" (2) manually register it using project.getArtifact().setArtifactHandler( artifactHandler ); -- 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

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] (AS7-5065) WEB-INF/classes always created as ResourceRoot

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5065: ----------------------------------- Summary: WEB-INF/classes always created as ResourceRoot Key: AS7-5065 URL: https://issues.jboss.org/browse/AS7-5065 Project: Application Server 7 Issue Type: Feature Request Components: OSGi, Web Reporter: Thomas Diesler Assignee: Thomas Diesler WEB-INF/class is created as ResourceRoot even if it daoes not exist -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] (AS7-3585) Allign deployment phases with OSGi terminology

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3585: ----------------------------------- Summary: Allign deployment phases with OSGi terminology Key: AS7-3585 URL: https://issues.jboss.org/browse/AS7-3585 Project: Application Server 7 Issue Type: Task Components: OSGi, Server Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 In OSGi we have * INSTALLED * RESOLVED * ACTIVE * UNINSTALLED It'd be useful to talk about modules and osgi bundles in the same jagon - i.e If a deployment is INSTALLED it has valid metadata If a deployment is RESOLVED it has Module/ClassLoader associated If a deployment is ACTIVE it can perform its normal operation If a deployment is UNINSTALLED it can be removed from the system The task here is mainly to rename/revisit the deployment phases -- 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, 10 months

1
12
0 / 0

[JBoss JIRA] (AS7-5066) Allow REST deployments as OSGi bundles

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5066: ----------------------------------- Summary: Allow REST deployments as OSGi bundles Key: AS7-5066 URL: https://issues.jboss.org/browse/AS7-5066 Project: Application Server 7 Issue Type: Sub-task Components: OSGi, Web Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (AS7-1326) Cannot redeploy OSGi bundle that is wired to webapp

by Thomas Diesler (JIRA)

Cannot redeploy OSGi bundle that is wired to webapp --------------------------------------------------- Key: AS7-1326 URL: https://issues.jboss.org/browse/AS7-1326 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Final Reporter: Thomas Diesler Assignee: Thomas Diesler {code} 09:12:12,719 ERROR [org.jboss.msc.service] (MSC service thread 1-1) MSC00002: Invocation of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@2789a406" failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.jboss-osgi-example-jbossas-bundle"."0.0.0" is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2194) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) at org.jboss.as.osgi.service.ModuleLoaderIntegration.addModule(ModuleLoaderIntegration.java:122) at org.jboss.osgi.framework.internal.ModuleManagerPlugin.createHostModule(ModuleManagerPlugin.java:340) at org.jboss.osgi.framework.internal.ModuleManagerPlugin.addModule(ModuleManagerPlugin.java:225) at org.jboss.osgi.framework.internal.ResolverPlugin.addModules(ResolverPlugin.java:248) at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:226) at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:161) at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210) at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:146) at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:121) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
9
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 2012