January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3207) Make the management-client-content module conform to ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Make the management-client-content module conform to ANDIAMO-2 -------------------------------------------------------------- Key: AS7-3207 URL: https://issues.jboss.org/browse/AS7-3207 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Final I added this module but did not create the i18n Logger or Messages class for it. Fix that. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-2508) Upgrade to a GA release of JBoss Negotiation

by Darran Lofthouse (Created) (JIRA)

Upgrade to a GA release of JBoss Negotiation -------------------------------------------- Key: AS7-2508 URL: https://issues.jboss.org/browse/AS7-2508 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.0.CR1 JBoss Negotiation needs tagging and AS7 updating to the GA version. -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3103) "A and not(B after A)" type rules don't fire when session clock has negative values (pre Unix epoch)

by Richard Calmbach (JIRA)

"A and not(B after A)" type rules don't fire when session clock has negative values (pre Unix epoch) ---------------------------------------------------------------------------------------------------- Key: JBRULES-3103 URL: https://issues.jboss.org/browse/JBRULES-3103 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-core (fusion) Affects Versions: 5.2.0.Final Reporter: Richard Calmbach Assignee: Mark Proctor See JBRULES-3100 for the gory details. The implementation described there causes two bugs, so THIS IS NOT A DUPLICATE of JBRULES-3100. Rather, the bugs are related, and because it is possible to fix one without the other, it makes sense to track both bugs explicitly, so that the developers can ensure that both bugs get fixed. The summary of this issue also conveys to users that this particular bug has already been reported. So, *this* bug prevents rules of the form $a: A() not(B(this after $a)) or "A and not(B after A)" in pseudocode, from firing when they should if the session clock has a negative value, say during a simulation or if the system clock is turned back pre Unix epoch. This is confirmed for the pseudo clock, and I believe the real-time clock is equally affected. The root of the problem is that "A and not(B after A)" type rules get a duration of Long.MAX_VALUE assigned. When that gets added to a non-positive current time, it results in a very large positive number for the trigger time, which will never be reached by the session clock, preventing the rule from ever firing. The fix is probably to add the activation for such a rule to the agenda immediately, rather than schedule it for adding. This would yield the same behavior as when you compare the timestamps explicitly. For now, comparing timestamps explicitly instead of using "after" is a workaround for this bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
4
0 / 0

[JBoss JIRA] (JBRULES-3333) org.drools.eclipse.builder.DroolsBuilder assumes all XLS files are decision tables and attempts to compile them, leading to the error "No RuleTable cells in spreadsheet."

by Swaroop Oggu (Created) (JIRA)

org.drools.eclipse.builder.DroolsBuilder assumes all XLS files are decision tables and attempts to compile them, leading to the error "No RuleTable cells in spreadsheet." --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3333 URL: https://issues.jboss.org/browse/JBRULES-3333 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Swaroop Oggu Assignee: Mark Proctor When using *.XLS (templates in this case)in drools 5.2.0 final and Eclipse 3.7.1 indigo , they are being considered as decision tables and hence leading to the error "No RuleTable cells in spreadsheet." -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-672) HostController status

by Brian Stansberry (Assigned) (JIRA)

[ https://issues.jboss.org/browse/AS7-672?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry reassigned AS7-672: ------------------------------------ Assignee: Kabir Khan Kabir, before doing anything on this, check in case it's already done; maybe was long ago. :-) > HostController status > --------------------- > > Key: AS7-672 > URL: https://issues.jboss.org/browse/AS7-672 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 7.1.0.Final > > > Analogous to a server's status, but for a HostController. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-2943) Make managed servers (domain mode) store deployments in their own content repository

by Kabir Khan (Created) (JIRA)

Make managed servers (domain mode) store deployments in their own content repository ------------------------------------------------------------------------------------- Key: AS7-2943 URL: https://issues.jboss.org/browse/AS7-2943 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Brian Stansberry Priority: Blocker Fix For: 7.1.0.Final AS7-341 implements the removal of the deployed content in the domain DeploymentRemoveHandler. However, since the managed servers use their HC's content repository, if one of the servers failed removing the deployment from their model, the content is wrongly removed from the HC repository since the error is not reported back. Having each server maintain their own repo avoids this problem -- 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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (AS7-3085) Deployment breaks when data source is being recycled

by Heiko Braun (Created) (JIRA)

Deployment breaks when data source is being recycled ---------------------------------------------------- Key: AS7-3085 URL: https://issues.jboss.org/browse/AS7-3085 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.Final Deploy the jboss-as-login.war example. It depends on the "ExampleDS" datasource. Access the web application. Disable and enable the datasource. Try the web app again: {noformat} 13:11:26,599 INFO [org.jboss.as.controller] (HttpManagementService-threads - 4) JBAS014774: Service status report JBAS014776: Newly corrected services: service jboss.naming.context.java.jboss.datasources.ExampleDS (no longer required) {noformat} This error prevails as long as the deployment is not disabled and re-eanbled again -- 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

14 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1981) Can't change the profile of an existing server group

by Misty Stanley-Jones (JIRA)

Can't change the profile of an existing server group ---------------------------------------------------- Key: AS7-1981 URL: https://issues.jboss.org/browse/AS7-1981 Project: Application Server 7 Issue Type: Bug Components: CLI, Console Affects Versions: Open To Community Environment: Fedora 15, Git pull 6e719b8 Reporter: Misty Stanley-Jones Assignee: Alexey Loubyansky There is no way to change the profile of an existing server group. There is no way to edit it in the Management Console, and if you try to do it in the CLI you get an error that it is read-only. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] (AS7-2505) Deployment order for MDBs and RAs is not working for a packaged EAR

by Abhi S (Created) (JIRA)

Deployment order for MDBs and RAs is not working for a packaged EAR ------------------------------------------------------------------- Key: AS7-2505 URL: https://issues.jboss.org/browse/AS7-2505 Project: Application Server 7 Issue Type: Bug Components: Deployment, EJB, JCA Affects Versions: 7.1.0.Alpha1, 7.0.2.Final Environment: Windows 7 64-bit Reporter: Abhi S Assignee: Thomas Diesler Priority: Critical If an application is packaged with MDBs and RAs (resource adapters) such that the order of deployment of these modules needs to be deterministic, the application fails to load. In other words, there is no way to define the order in which MDBs and RAs must be loaded in an application. This is a strict requirement by JEE 6, and without this support, JBoss 7 cannot be fully JEE 6 compliant. Theoretically, following are 3 different ways to accomplish the above objective: # Set <initialize-in-order> to true; see http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325, but I tested it using a sample application, and this definitely does not work for MDBs and RAs. # Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on an RA. Adding this configuration MUST ensure that the application loader loads the RA before trying to load the MDB. # Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the same as #2. None of the above work in the nightly build of AS7.1. -- 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

14 years, 2 months

11
20
0 / 0

[JBoss JIRA] (JBJCA-723) Add WrappedConnection::getXAResource

by Jesper Pedersen (Created) (JIRA)

Add WrappedConnection::getXAResource ------------------------------------ Key: JBJCA-723 URL: https://issues.jboss.org/browse/JBJCA-723 Project: IronJacamar Issue Type: Task Components: JDBC Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.7.Final, 1.1.0.Alpha5 -- 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

14 years, 2 months

2
1
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 January 2012