February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3741) AS 7.01CR1B (jbosss-as-cmp) does not compile using eclipse

by shay Matasaro (JIRA)

shay Matasaro created AS7-3741: ---------------------------------- Summary: AS 7.01CR1B (jbosss-as-cmp) does not compile using eclipse Key: AS7-3741 URL: https://issues.jboss.org/browse/AS7-3741 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.1.0.CR1b Environment: Ubuntu 64 , Eclispe Indigo clean install , latest M2E Reporter: shay Matasaro Assignee: Paul Gier AS-CMP fails to compile due to missing simbols , the reason for that is that a maven JAVACC plugin that auto-generates some files , does not add the new sources directory to the build path. Also it looks like JBOSS is suing 2 different version of JAVACC 2.5 and 2.6 Installing the javacc m2e connector does not help due to the version mismatch as well as the connector not being mature enough. possible solutions are : 1) rewrite the javacc maven plug-in 2) fix the javacc m2e connector 3) add the required folder to the build path. option 3 seems to be the easiest and the best short term fix. I have tested the fix and will try to merge it into the code base(this is my first time revising jboss) Shay -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] (AS7-3844) Add ability to disable / enable deployments

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-3844: -------------------------------- Summary: Add ability to disable / enable deployments Key: AS7-3844 URL: https://issues.jboss.org/browse/AS7-3844 Project: Application Server 7 Issue Type: Feature Request Components: CLI, Domain Management Affects Versions: 7.1.0.Final Reporter: Tomaz Cerar Assignee: Tomaz Cerar Currently we cannot enable / disable deployment trough cli. admin console fakes it by undeploying and deploying with enabled=false flag. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] (AS7-2887) Disallow deployment of @Clustered EJBs if the type is not valid

by David Lloyd (Created) (JIRA)

Disallow deployment of @Clustered EJBs if the type is not valid --------------------------------------------------------------- Key: AS7-2887 URL: https://issues.jboss.org/browse/AS7-2887 Project: Application Server 7 Issue Type: Task Components: Clustering, EJB Reporter: David Lloyd Priority: Blocker Fix For: 7.1.0.CR1 @Clustered can be applied as follows: * Entity EJB - Give a "feature unsupported" error, refuse to deploy * Stateful Session EJB - Allow * Stateless Session EJB - Allow (has no effect though) * Singleton EJB - Give a "feature unsupported" error, refuse to deploy * MDB - Give a "feature unsupported" error, refuse to deploy Note that "feature unsupported" should be worded such that the feature may become available in future releases. -- 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, 4 months

6
7
0 / 0

[JBoss JIRA] (AS7-3190) Poor error message when attempting to undeploy something that isn't deployed

by Brian Stansberry (Created) (JIRA)

Poor error message when attempting to undeploy something that isn't deployed ---------------------------------------------------------------------------- Key: AS7-3190 URL: https://issues.jboss.org/browse/AS7-3190 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.CR1b, 7.0.2.Final Reporter: Brian Stansberry Fix For: 7.1.0.Final I see messages like the following in the testsuite logs after some problem results in a failed deployment. I *believe* this happens when Arquillian attempts to undeploy at the end of the test; the "undeploy" is invalid because the "deploy" was rolled back. In this situation having the "undeploy" fail is fine (it is in fact an error); the problem is the error is completely confusing. 04:44:08,190 ERROR [org.jboss.as.controller.management-operation] (management-handler-threads - 7) JBAS014612: Operation ("undeploy") failed - address: ([("deployment" => "testTimerServiceSimple.war")]): java.util.NoSuchElementException: No child 'runtime-name' exists at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.dmr.ModelNode.require(ModelNode.java:812) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.server.deployment.DeploymentUndeployHandler.execute(DeploymentUndeployHandler.java:58) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:84) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:432) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:121) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:98) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$3$1.doExecute(AbstractMessageHandler.java:268) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:424) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] -- 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, 4 months

6
8
0 / 0

[JBoss JIRA] Created: (JBAS-7994) Clean up quartz messages in AS startup log

by Paul Gier (JIRA)

Clean up quartz messages in AS startup log ------------------------------------------ Key: JBAS-7994 URL: https://jira.jboss.org/jira/browse/JBAS-7994 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Gier Assignee: Paul Gier Fix For: 6.0.0.CR1 The recent updates to quartz have added more noise to the console log. These messages should be written only to the log file and not the console. -- 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

14 years, 4 months

3
4
0 / 0

[JBoss JIRA] (AS7-3847) Non-standard format of IPv6 address(-es) in LOG files

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3847?page=com.atlassian.jira.plugin.s... ] Pavel Janousek moved JBPAPP-8164 to AS7-3847: --------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3847 (was: JBPAPP-8164) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.0.Final (was: EAP 6.0.0 DR 13) Security: (was: JBoss Internal) Docs QE Status: (was: NEW) > Non-standard format of IPv6 address(-es) in LOG files > ----------------------------------------------------- > > Key: AS7-3847 > URL: https://issues.jboss.org/browse/AS7-3847 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.0.Final > Reporter: Pavel Janousek > Priority: Critical > > There are several places where some IPv6 address related info is logged. The format of a such info is formally correct, but used format is against [RFC-5952|http://tools.ietf.org/html/rfc5952] - this RFC has status of +Proposed standard+ and I don't know any software product which doesn't follow it (at least by-default). > I think in enterprise product we should not violate this RFC. > I'm mentioning about LOG messages like: > {code} > 15:14:15,985 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:9999 > > 15:14:15,990 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost6.localdomain6/0:0:0:0:0:0:0:1%1:4447 > {code} > In both lines IPv6 address should be stretched to "::1" string. > More "funny" and obfuscated version of the same LOG content is LOG line like this: > {code} > 15:14:14,363 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A1%251-8080 > {code} > But both version of the issue is almost unreadable by human. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3846) Distributed cache attributes don't show up in read-resource-description

by Stan Silvert (JIRA)

Stan Silvert created AS7-3846: --------------------------------- Summary: Distributed cache attributes don't show up in read-resource-description Key: AS7-3846 URL: https://issues.jboss.org/browse/AS7-3846 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Stan Silvert Assignee: Richard Achmatowicz /profile=default/subsystem=infinispan/cache-container=fasfd/distributed-cache=*/:read-resource-description(operations=false,inherited=false,recursive=false,proxies=false) The attributes owners, virtual-nodes, and l1-lifespan don't show up. This keeps help text from working in the console and CLI GUI. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3839) WebSecurityJBossSimpleRoleMappingTestCase fails during testsuite execution

by Jan Lanik (JIRA)

Jan Lanik created AS7-3839: ------------------------------ Summary: WebSecurityJBossSimpleRoleMappingTestCase fails during testsuite execution Key: AS7-3839 URL: https://issues.jboss.org/browse/AS7-3839 Project: Application Server 7 Issue Type: Bug Components: Test Suite Environment: commit 4620414e3c56a171c6cd6952ddad26d88c86f355 Reporter: Jan Lanik Assignee: Peter Skopek Run testsuite as follows: $ ./integration-tests.sh clean install -Dts.basic Usually, the run fails with following error: Results : Failed tests: testPasswordBasedUnsuccessfulAuth(org.jboss.as.test.integration.web.security.WebSecurityJBossSimpleRoleMappingTestCase): expected:<403> but was:<200> testPrincipalMappingOnRole(org.jboss.as.test.integration.web.security.WebSecurityJBossSimpleRoleMappingTestCase): expected:<200> but was:<403> I'll add surefire reports and server log. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] (JBRULES-3385) Rule not fired depending on the class loading order

by Manuel Reinaldo Falagan (JIRA)

Manuel Reinaldo Falagan created JBRULES-3385: ------------------------------------------------ Summary: Rule not fired depending on the class loading order Key: JBRULES-3385 URL: https://issues.jboss.org/browse/JBRULES-3385 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.3.0.Final, 5.2.0.Final Environment: SLES11 SP1 with java 1.6.0_14-b08 (32bit and 64bit) or XP with jdk1.6.0_22 (32 or 64 bit) Reporter: Manuel Reinaldo Falagan Assignee: Mark Proctor Priority: Blocker A very simple example "FailTest" triggers a rule only 15 times when it should trigger it 16 times. The same example with almost any change to the class model or to the order in loading the classes or the input data or the version of java it works. The Class FailTest contains only a main method calling the main method of the Class HelloWorldExample. Running directly the main method in the class HelloWorldExample does work. Any change fixes the problem in the example but it moves the error to other part. We have set a test testing more than 2000 million cases of rules/inputs and no matter how we write the rules or the code, we end up finding a case that fails, making the software not usable, as it is not predictable were it is going to fail. The case has been uner study for more than a year and we have tried AIX, Linux and XP with DROOLS 5.1, 5.2, 5.3 and the trial of Enterprise edition. The example provided has only been tested to fail for DROOLS 5.3.0 final and Enterprise edition for SLES11 SP1 with the SUN virtual machine (not the IBM one) and for XP but there is no combination for which DROOLS work for the 2000 million cases. The example provided is a 7kb example self-contained ( ftp://mpf:mpf@ftp.eumetsat.int/DROOLS_ERROR.zip ) -- 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, 4 months

1
11
0 / 0

[JBoss JIRA] (AS7-3793) Provide remoting subsystem for appclients

by Richard Opalka (JIRA)

Richard Opalka created AS7-3793: ----------------------------------- Summary: Provide remoting subsystem for appclients Key: AS7-3793 URL: https://issues.jboss.org/browse/AS7-3793 Project: Application Server 7 Issue Type: Feature Request Components: Application Client Reporter: Richard Opalka Assignee: Stuart Douglas Fix For: 7.1.1.Final -- 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, 4 months

2
5
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 February 2012