handling of deployment failed the validation on the domain controller
---------------------------------------------------------------------
Key: JBAS-8336
URL: https://jira.jboss.org/browse/JBAS-8336
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Alexey Loubyansky
Fix For: 7.0.0.M1
A deployment can fail validation on the domain controller. In this event, the deployment is not added to the domain and an error is thrown from the deployer API, so this does not impact the server.
--
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
Algorithms for generating server names
--------------------------------------
Key: JBAS-8412
URL: https://jira.jboss.org/browse/JBAS-8412
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.M1
Right now we're identifying servers by the static "name" attribute value in the host.xml server element. We need pluggable algorithms for other mechanisms to come up with a name, particularly for cloud use cases.
--
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
KnowledgeAgent should load knowledge bases directly from Resource (bypassing the ChangeSet)
-------------------------------------------------------------------------------------------
Key: JBRULES-2124
URL: https://jira.jboss.org/jira/browse/JBRULES-2124
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-api, drools-core
Affects Versions: 5.0.1.FINAL
Reporter: Jürgen Schiewe
Assignee: Mark Proctor
We develop Drools based applications and use Guvnor as a a repository. Hard-coding the hostname where Guvnor runs is not an option for us because the names are different in each installation and we do not want to modify all the changeset.xml files for each deployment.
Instead we would pass one (or more) Resources to the KnowledgeAgent and let it do the monitoring. This would allow us to build URLs dynamically from our system environment configuration.
--
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
Use ByteMan / Metronome to inject faults for testing
----------------------------------------------------
Key: JGRP-1001
URL: https://jira.jboss.org/jira/browse/JGRP-1001
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
Use ByteMan (jboss.org/byteman) to simulate issues that can happen at runtime: do this in unit tests.
For example: crash of merge leader after initial round (who frees the locks ?) (same for FLUSH)
--
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
Fix build warning for missing pom on ws-commons policy
------------------------------------------------------
Key: JBAS-8422
URL: https://jira.jboss.org/browse/JBAS-8422
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.M4
Reporter: Paul Gier
Priority: Minor
The AS 6 trunk build currently gives a warning about the pom missing from ws-commons:policy
[WARNING] The POM for ws-commons:policy:jar:1.0 is missing, no dependency information available
This is caused by a missing POM file in central
http://repo2.maven.org/maven2/ws-commons/policy/1.0/
ws-commons:policy is now called project Neethi. Possible a recent version of Neethi can be used to replace the old policy jar.
http://repo2.maven.org/maven2/org/apache/neethi/neethi/
--
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
parameter element missing value in profile.xml
----------------------------------------------
Key: JBAS-7856
URL: https://jira.jboss.org/jira/browse/JBAS-7856
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.1.0.GA
Environment: Windows,X86
Reporter: thamizhelango natarajan
<bean name="AttachmentStore" class="org.jboss.system.server.profileservice.repository.AbstractAttachmentStore">
<constructor><parameter class="java.io.File"><inject bean="BootstrapProfileFactory" property="attachmentStoreRoot" /></parameter></constructor>
The parameter element missing class attribute
--
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
Discovery protocol based on Rackspace
-------------------------------------
Key: JGRP-1226
URL: https://jira.jboss.org/browse/JGRP-1226
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.0
Similar to S3_PING (Amazon), create a discovery protocol (extending FILE_PING) which uses Rackspace's distributed store
--
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
TCLFilter fails to get correct URLs from classloader in AS-5
--------------------------------------------------------------
Key: JBLOGGING-30
URL: https://jira.jboss.org/jira/browse/JBLOGGING-30
Project: JBoss Logging
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jboss-logging-log4j
Affects Versions: 2.1.0.GA-jboss-logging
Reporter: jaikiran pai
Assignee: jaikiran pai
As explained in JBAS-6532, the TCLFilter doesn't work in AS-5 because it never attempts to use the URLClassLoader while retrieving the Classloader URLs. A patch is attached to that JIRA (details of the patch are in the forum thread) which needs to be applied in jboss-logging-log4j component to get this working.
--
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
Release drools binaries with debug information
----------------------------------------------
Key: JBRULES-443
URL: http://jira.jboss.com/jira/browse/JBRULES-443
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: All
Reporter: Juergen none
Assigned To: Mark Proctor
Priority: Trivial
Would it be possible to supply a debug-build of the binaries in addition to the existing downloads (where at least the drools jar files are without debug-info)?
--
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