March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3667) Upgrade to JSF 2.1.6

by Ove Ranheim (JIRA)

Ove Ranheim created AS7-3667: -------------------------------- Summary: Upgrade to JSF 2.1.6 Key: AS7-3667 URL: https://issues.jboss.org/browse/AS7-3667 Project: Application Server 7 Issue Type: Library Upgrade Components: Build System, JSF Affects Versions: 7.1.0.CR1b Reporter: Ove Ranheim Assignee: Paul Gier Fix For: 7.1.0.Final Upgrade JSF from 2.1.5 to 2.1.6. Release notes: http://java.net/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10985 -- 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, 1 month

5
10
0 / 0

[JBoss JIRA] (AS7-4023) AS7 TS: Intermittent failures "No EJB receiver available" - JBossAppXMLSecurityTestCase, SimpleApplicationClientTestCase

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-4023?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka moved JBQA-5984 to AS7-4023: ----------------------------------------- Project: Application Server 7 (was: JBoss QA) Key: AS7-4023 (was: JBQA-5984) Workflow: GIT Pull Request workflow (was: jira) Component/s: EJB Test Suite (was: JBoss AS Test Suite) > AS7 TS: Intermittent failures "No EJB receiver available" - JBossAppXMLSecurityTestCase, SimpleApplicationClientTestCase > ------------------------------------------------------------------------------------------------------------------------ > > Key: AS7-4023 > URL: https://issues.jboss.org/browse/AS7-4023 > Project: Application Server 7 > Issue Type: Bug > Components: EJB, Test Suite > Reporter: Ondrej Zizka > Priority: Minor > Labels: intermittent > > org.jboss.as.test.integration.ejb.security.jbossappxml.JBossAppXMLSecurityTestCase.testEJBRunAs > No EJB receiver available for handling [appName:myapp,modulename:jboss-app-xml-sec,distinctname:] combination > org.jboss.as.test.integration.ee.appclient.basic.SimpleApplicationClientTestCase.simpleAppClientTest > No EJB receiver available for handling [appName:simple-app-client-test,modulename:ejb,distinctname:] combination > https://hudson.qa.jboss.com/hudson/job/AS7-TS-valid-mvn-all-ipv6/36/testR... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4526) JBossMQ UIL2 Read/Write Tasks should not be doing initialization

by Adrian Brock (JIRA)

JBossMQ UIL2 Read/Write Tasks should not be doing initialization ---------------------------------------------------------------- Key: JBAS-4526 URL: http://jira.jboss.com/jira/browse/JBAS-4526 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.1.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1 The JBossMQ UIL2 Read/Write tasks both do their stream initialization when each thread starts. This code needs changing such that the streams are allocated before started the threads. Only if all resources can be succesfully allocated should we start the threads. -- 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

14 years, 1 month

3
5
0 / 0

[JBoss JIRA] (AS7-4003) add a command to echo DMR requests for commands and operations

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-4003: -------------------------------------- Summary: add a command to echo DMR requests for commands and operations Key: AS7-4003 URL: https://issues.jboss.org/browse/AS7-4003 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.1.Final For debugging and other reasons it might be useful to see the DMR requests for user commands and operations. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-3996) CLI: deployment crashes console with --header={rollout id=XXX} parameter

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3996: ------------------------------------- Summary: CLI: deployment crashes console with --header={rollout id=XXX} parameter Key: AS7-3996 URL: https://issues.jboss.org/browse/AS7-3996 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Alexey Loubyansky 1) connect to a domain using CLI 2) create a rollout-plan 3) deploy /tmp/RolloutPlanTestCase.war --all-server-groups --headers={rollout id=testPlan} [domain@localhost:9999 /] deploy /tmp/RolloutPlanTestCase.war --all-server-groups --headers={rollout id=testPlan} java.lang.NullPointerException at org.jboss.as.cli.operation.impl.ParsedRolloutPlanHeader.addTo(ParsedRolloutPlanHeader.java:277) at org.jboss.as.cli.ArgumentValueConverter$5.fromNonDMRString(ArgumentValueConverter.java:157) at org.jboss.as.cli.ArgumentValueConverter$DMRWithFallbackConverter.fromString(ArgumentValueConverter.java:50) at org.jboss.as.cli.handlers.BaseOperationCommand.addHeaders(BaseOperationCommand.java:214) at org.jboss.as.cli.handlers.DeployHandler.execute(DeployHandler.java:559) at org.jboss.as.cli.handlers.DeployHandler.doHandle(DeployHandler.java:365) at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:84) at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:458) at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:469) at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1022) at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:191) at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.modules.Module.run(Module.java:260) at org.jboss.modules.Main.main(Main.java:291) -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] (AS7-3898) Improve the processing time of a request with a large number of parameters on JBossAS7.1.

by Toshio Oya (JIRA)

Toshio Oya created AS7-3898: ------------------------------- Summary: Improve the processing time of a request with a large number of parameters on JBossAS7.1. Key: AS7-3898 URL: https://issues.jboss.org/browse/AS7-3898 Project: Application Server 7 Issue Type: Enhancement Components: Web Affects Versions: 7.1.0.Final Reporter: Toshio Oya Assignee: Remy Maucherat Attachments: modified-7.1.0.Final.zip JBAS-9472 which is reported as an enhancement request for JBossAS 5.1.0.GA, is reproduced on JBossAS 7.1.0.Final. So, we have created a patch for JBossAS 7.1.0.Final. We want to incorporate this patch in JBoss AS 7.x. Please see JBAS-9472. -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] (JBRULES-3407) Error generating invokers using a declaration having a primitive type

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3407: ------------------------------------ Summary: Error generating invokers using a declaration having a primitive type Key: JBRULES-3407 URL: https://issues.jboss.org/browse/JBRULES-3407 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When the value type of a declaration is primitive, the invokers created via mvel templating using that declaration cannot be compiled because they try to do an invalid cast from an Object to a primitive type, generating an error as it follows: java.lang.AssertionError: Unable to generate rule invoker. : [Accumulate: input=[AND [[Pattern: id=null; objectType=MyObj]] ]] org/drools/Rule_foo_3191b39fd6ce40eaac55301df07acc19AccumulateExpression0Invoker.java (19:754) : Cannot cast from Object to long -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] (JBRULES-3408) excludeUninitializedPlanningEntity should support specific uninitialized planning variables too

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3408: ----------------------------------------- Summary: excludeUninitializedPlanningEntity should support specific uninitialized planning variables too Key: JBRULES-3408 URL: https://issues.jboss.org/browse/JBRULES-3408 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet partial initialization (only 1 variable, not all of them) can be needed in some optimization algorithms. See section in the manual. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4008) Don't enable remote access to JMX by default in domain mode

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4008: ------------------------------------- Summary: Don't enable remote access to JMX by default in domain mode Key: AS7-4008 URL: https://issues.jboss.org/browse/AS7-4008 Project: Application Server 7 Issue Type: Task Components: JMX Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.1.Final In domain mode this is exposed using the remoting subsystem connector which is the same connector as is secured by the application users not the management users so by default we should not enable remote JMX access over this connection. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-4001) Bad reference to XSL transformation files in module jboss-as-testsuite-benchmark and jboss-as-testsuite-stress

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-4001?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-4001: ------------------------------ Fix Version/s: 7.1.1.Final > Bad reference to XSL transformation files in module jboss-as-testsuite-benchmark and jboss-as-testsuite-stress > -------------------------------------------------------------------------------------------------------------- > > Key: AS7-4001 > URL: https://issues.jboss.org/browse/AS7-4001 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > Priority: Critical > Fix For: 7.1.1.Final > > > Transformation procedure is invoked, but it seems like bad configuration path or not correctly done clean-up in previous step. I caught this problem via warning: > {code} > [INFO] --- xml-maven-plugin:1.0:transform (ts.config-as.ip) @ jboss-as-testsuite-stress --- > [WARNING] The directory /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/target/jbossas/standalone/configuration, which is a base directory of a ValidationSet or TransformationSet, does not exist. > [WARNING] No files found for transformation by stylesheet /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/../integration/src/test/xslt/changeIPAddresses.xsl > [WARNING] The directory /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/target/jbossas/standalone/configuration, which is a base directory of a ValidationSet or TransformationSet, does not exist. > [WARNING] No files found for transformation by stylesheet /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/../integration/src/test/xslt/addJmsDestinations.xsl > {code} > Further investigation says /build/target/... isn't copied to these modules at all. > You can see this problem [there|https://hudson.qa.jboss.com/hudson/job/AS7-TS-linux-ipv6-experiment...]. -- 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, 1 month

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 March 2012