December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6214) Use of ServerGroupProfileWriteAttributeHandler got dropped

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6214: ------------------------------------- Summary: Use of ServerGroupProfileWriteAttributeHandler got dropped Key: AS7-6214 URL: https://issues.jboss.org/browse/AS7-6214 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 In the switch of the core model to ResourceDefinition during 7.2 development, use of ServerGroupProfileWriteAttributeHandler got dropped. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3346) Batch execution code has not been finished and is missing tests

by Marco Rietveld (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3346?page=com.atlassian.jira.plug... ] Marco Rietveld deleted JBRULES-3346: ------------------------------------ > Batch execution code has not been finished and is missing tests > --------------------------------------------------------------- > > Key: JBRULES-3346 > URL: https://issues.jboss.org/browse/JBRULES-3346 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Marco Rietveld > Assignee: Marco Rietveld > Priority: Minor > > See [here|https://github.com/droolsjbpm/drools/blob/622d359886bf687a8397214f16...] for an example. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-714) Release PicketBox 4.0.15.Final

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-714?page=com.atlassian.jira.plug... ] Stefan Guilhen closed SECURITY-714. ----------------------------------- Resolution: Done PicketBox 4.0.15.Final has been released. > Release PicketBox 4.0.15.Final > ------------------------------ > > Key: SECURITY-714 > URL: https://issues.jboss.org/browse/SECURITY-714 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBossSX, Security SPI > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6213) WARs and EARs should not get registered in the OSGi environment

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6213: ----------------------------------- Summary: WARs and EARs should not get registered in the OSGi environment Key: AS7-6213 URL: https://issues.jboss.org/browse/AS7-6213 Project: Application Server 7 Issue Type: Feature Request 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ] Thomas Diesler edited comment on AS7-6202 at 12/18/12 3:02 PM: --------------------------------------------------------------- The reason is that the FrameworkBootstrapService cannot start because of this missing dependency {code} builder.addDependency(JBOSS_BINDING_NAME.append("osgi-http"), SocketBinding.class, service.httpServerPortBinding); {code} the DC should have {code} <socket-binding name="osgi-http" interface="management" port="8090"/> {code} The PR makes the dependency optional was (Author: thomas.diesler): The reason is that the FrameworkBootstrapService cannot start because of this missing dependency {code} builder.addDependency(JBOSS_BINDING_NAME.append("osgi-http"), SocketBinding.class, service.httpServerPortBinding); {code} the DC should have {code} <socket-binding name="osgi-http" interface="management" port="8090"/> {code} > Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi > --------------------------------------------------------------- > > Key: AS7-6202 > URL: https://issues.jboss.org/browse/AS7-6202 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Kabir Khan > Assignee: Thomas Diesler > Fix For: 7.1.4.Final (EAP) > > Attachments: domain.xml, host.xml > > > I noticed this when working on the mixed-domain tests. The attached domain.xml and host.xml contain adjustments for the older slave to work (replacing the MERGE3 jgroups protocol with MERGE2, since 7.1.x does not have that version), and makes all its servers auto-start="false". > To reproduce, start up a DC built from master using those files. Then start up a slave HC built from 7.1.2.Final or 7.1.3.Final using a command like: > ./build/target/jboss-as-7.1.3.Final/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999 > Now in CLI: > {code} > [domain@localhost:9999 /] /deployment=test.war:add(content=[{"url" => "file:/Users/kabir/sourcecontrol/jboss-as7/git/jboss-as/testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war"}] > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@localhost:9999 /] /deployment=test.war:remove [domain@localhost:9999 /] /server-group=main-server-group/deployment=test.war:add(enabled=true) > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", > "rolled-back" => true, > "server-groups" => {"main-server-group" => {"host" => {"kabirs-macbook-pro.local" => {"server-one" => {"response" => { > "outcome" => "failed", > "result" => undefined, > "failure-description" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]}, > "rolled-back" => true > }}}}}} > } > {code} > The console log for the slave shows > {code} > [Server:server-one] 17:21:22,201 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war" > [Server:server-one] 17:21:22,556 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /test > [Server:server-one] 17:21:22,771 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]} > [Server:server-one] 17:21:22,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test.war in 42ms > {code} > The deployment is very simple, and just contains an html file: > {code} > $unzip -l testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war > Archive: testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war > Length Date Time Name > -------- ---- ---- ---- > 210 12-17-12 16:34 index.html > -------- ------- > 210 1 file > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6202: -------------------------------- Fix Version/s: 7.1.4.Final (EAP) (was: 7.2.0.Alpha1) > Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi > --------------------------------------------------------------- > > Key: AS7-6202 > URL: https://issues.jboss.org/browse/AS7-6202 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Kabir Khan > Assignee: Thomas Diesler > Fix For: 7.1.4.Final (EAP) > > Attachments: domain.xml, host.xml > > > I noticed this when working on the mixed-domain tests. The attached domain.xml and host.xml contain adjustments for the older slave to work (replacing the MERGE3 jgroups protocol with MERGE2, since 7.1.x does not have that version), and makes all its servers auto-start="false". > To reproduce, start up a DC built from master using those files. Then start up a slave HC built from 7.1.2.Final or 7.1.3.Final using a command like: > ./build/target/jboss-as-7.1.3.Final/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999 > Now in CLI: > {code} > [domain@localhost:9999 /] /deployment=test.war:add(content=[{"url" => "file:/Users/kabir/sourcecontrol/jboss-as7/git/jboss-as/testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war"}] > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@localhost:9999 /] /deployment=test.war:remove [domain@localhost:9999 /] /server-group=main-server-group/deployment=test.war:add(enabled=true) > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", > "rolled-back" => true, > "server-groups" => {"main-server-group" => {"host" => {"kabirs-macbook-pro.local" => {"server-one" => {"response" => { > "outcome" => "failed", > "result" => undefined, > "failure-description" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]}, > "rolled-back" => true > }}}}}} > } > {code} > The console log for the slave shows > {code} > [Server:server-one] 17:21:22,201 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war" > [Server:server-one] 17:21:22,556 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /test > [Server:server-one] 17:21:22,771 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]} > [Server:server-one] 17:21:22,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test.war in 42ms > {code} > The deployment is very simple, and just contains an html file: > {code} > $unzip -l testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war > Archive: testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war > Length Date Time Name > -------- ---- ---- ---- > 210 12-17-12 16:34 index.html > -------- ------- > 210 1 file > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on AS7-6202: ------------------------------------- The reason is that the FrameworkBootstrapService cannot start because of this missing dependency {code} builder.addDependency(JBOSS_BINDING_NAME.append("osgi-http"), SocketBinding.class, service.httpServerPortBinding); {code} the DC should have {code} <socket-binding name="osgi-http" interface="management" port="8090"/> {code} > Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi > --------------------------------------------------------------- > > Key: AS7-6202 > URL: https://issues.jboss.org/browse/AS7-6202 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Kabir Khan > Assignee: Thomas Diesler > Fix For: 7.2.0.Alpha1 > > Attachments: domain.xml, host.xml > > > I noticed this when working on the mixed-domain tests. The attached domain.xml and host.xml contain adjustments for the older slave to work (replacing the MERGE3 jgroups protocol with MERGE2, since 7.1.x does not have that version), and makes all its servers auto-start="false". > To reproduce, start up a DC built from master using those files. Then start up a slave HC built from 7.1.2.Final or 7.1.3.Final using a command like: > ./build/target/jboss-as-7.1.3.Final/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999 > Now in CLI: > {code} > [domain@localhost:9999 /] /deployment=test.war:add(content=[{"url" => "file:/Users/kabir/sourcecontrol/jboss-as7/git/jboss-as/testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war"}] > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@localhost:9999 /] /deployment=test.war:remove [domain@localhost:9999 /] /server-group=main-server-group/deployment=test.war:add(enabled=true) > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", > "rolled-back" => true, > "server-groups" => {"main-server-group" => {"host" => {"kabirs-macbook-pro.local" => {"server-one" => {"response" => { > "outcome" => "failed", > "result" => undefined, > "failure-description" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]}, > "rolled-back" => true > }}}}}} > } > {code} > The console log for the slave shows > {code} > [Server:server-one] 17:21:22,201 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war" > [Server:server-one] 17:21:22,556 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /test > [Server:server-one] 17:21:22,771 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]} > [Server:server-one] 17:21:22,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test.war in 42ms > {code} > The deployment is very simple, and just contains an html file: > {code} > $unzip -l testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war > Archive: testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war > Length Date Time Name > -------- ---- ---- ---- > 210 12-17-12 16:34 index.html > -------- ------- > 210 1 file > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-714) Release PicketBox 4.0.15.Final

by Stefan Guilhen (JIRA)

Stefan Guilhen created SECURITY-714: --------------------------------------- Summary: Release PicketBox 4.0.15.Final Key: SECURITY-714 URL: https://issues.jboss.org/browse/SECURITY-714 Project: PicketBox Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Reporter: Stefan Guilhen Assignee: Stefan Guilhen -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6212) Invalid expression support for some transaction subsystem attributes

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6212: ------------------------------------- Summary: Invalid expression support for some transaction subsystem attributes Key: AS7-6212 URL: https://issues.jboss.org/browse/AS7-6212 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Transactions Affects Versions: 7.1.3.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 The transaction subsystem specifies that expressions are allowed for attributes USEHORNETQSTORE and JTS. This can't work because the xml schema uses an empty element to indicate these are "true". That kind of xml grammar cannot support expressions. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5135) Expression support for transaction subsystem attributes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5135?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5135: ---------------------------------- Fix Version/s: 7.2.0.Alpha1 7.1.3.Final (EAP) > Expression support for transaction subsystem attributes > ------------------------------------------------------- > > Key: AS7-5135 > URL: https://issues.jboss.org/browse/AS7-5135 > Project: Application Server 7 > Issue Type: Enhancement > Components: Transactions > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tomaz Cerar > Assignee: Stefano Maestri > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > most attributes in transaction subsystem should support expressions especial node-identifier. > review all attributes and enable expressions on all that make sense. -- 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, 6 months

1
0
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 December 2012