August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5296) Deployment of secure or signed war file and verifying the integrity of signed war file by digital certificate during the deployment by jboss application server.

by Shashidhar Puttashamaiah (JIRA)

Shashidhar Puttashamaiah created AS7-5296: --------------------------------------------- Summary: Deployment of secure or signed war file and verifying the integrity of signed war file by digital certificate during the deployment by jboss application server. Key: AS7-5296 URL: https://issues.jboss.org/browse/AS7-5296 Project: Application Server 7 Issue Type: Feature Request Components: Security Affects Versions: 7.1.2.Final (EAP) Reporter: Shashidhar Puttashamaiah Assignee: Anil Saldhana -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3563) Planner: Benchmark report should also show percentage versus worst dataset (and an average of that percentage)

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3563: ----------------------------------------- Summary: Planner: Benchmark report should also show percentage versus worst dataset (and an average of that percentage) Key: JBRULES-3563 URL: https://issues.jboss.org/browse/JBRULES-3563 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Managers like to know much better a result it in relative terms. This often boils down to comparing the results of the construction heuristic with the results of 1 or more full-fledged configuration (construction heuristic + metaheuristic). So for each dataset for each solver configuration, we can calculate a percentage: ((- Worst solver's score) - (- this solver's score)) / (- Worst solver's score). For the Worst's solver's score this will be 0%. If the worst solvers score is 0, then it should be NaN or empty. Then, for each solver configuration, we can calculate an "average percentage". Note that is is calculated based on the percentages, not the average of the scores! If any datasets have NaN or empty, that result should be discarded (which means the entire column gets discarded). Classes to look into: - SingleBenchmark should have the betterThanWorstScorePercentage. TODO: find a better name then that :) - SolverBenchmark should have the averageBetterThanWorstScorePercentage TODO: find a better name then that :) - PlannerStatistic should output a graph of it. Copy paste from writeBestScoreSummaryChart. (add it after the WinningScoreDifference code) - index.html.ftl should write the numbers in the report (add it after WinningScoreDifference) -- 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

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5060) CLONE - add-user.sh/add-user.bat should provide a scriptable mode

by Brad Maxwell (JIRA)

Brad Maxwell created AS7-5060: --------------------------------- Summary: CLONE - add-user.sh/add-user.bat should provide a scriptable mode Key: AS7-5060 URL: https://issues.jboss.org/browse/AS7-5060 Project: Application Server 7 Issue Type: Feature Request Components: Security Affects Versions: 7.1.1.Final Reporter: Brad Maxwell Assignee: Anil Saldhana Currently the vault.sh / vault.bat script can only be run in interactive mode. We tried scripting vault.sh by redirecting stdin, but that fails due to it using the Java Console class. This RFE is to add a non-interactive mode, e.g. be able to invoke the vault script with all parameters passed on the command line. We realise this would expose passwords in plain text, but it is the intention to be able to run this on a private machine and copy the result to the actual deployment box. -- 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

11 years, 9 months

6
10
0 / 0

[JBoss JIRA] (AS7-5295) Changing the TX settings prevents server :reload

by Heiko Braun (JIRA)

Heiko Braun created AS7-5295: -------------------------------- Summary: Changing the TX settings prevents server :reload Key: AS7-5295 URL: https://issues.jboss.org/browse/AS7-5295 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Priority: Blocker Fix For: 7.1.3.Final (EAP) When changing the "enable-statitics" attribute on a standalone server tx subsystem, I am forced to reload (dmr header). however when executing the :reload op the server nukes and terminates the java process: {noformat} 13:31:13,012 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("parallel-extension-add") failed - address: ([]): java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.transactions at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:156) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:191) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.server.ServerService.boot(ServerService.java:300) [jboss-as-server-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.server.ServerService.boot(ServerService.java:275) [jboss-as-server-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33] Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: duplicate transformer add at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) [classes.jar:1.6.0_33] at java.util.concurrent.FutureTask.get(FutureTask.java:83) [classes.jar:1.6.0_33] at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] ... 9 more Caused by: java.lang.IllegalStateException: duplicate transformer add at org.jboss.as.controller.registry.OperationTransformerRegistry.registerTransformer(OperationTransformerRegistry.java:151) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:191) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.registry.GlobalTransformerRegistry$SubRegistry.registerTransformer(GlobalTransformerRegistry.java:303) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:195) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:115) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.transform.TransformerRegistry$TransformersSubRegistrationImpl.registerOperationTransformer(TransformerRegistry.java:255) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.txn.subsystem.TransactionExtension.registerTransformers(TransactionExtension.java:142) at org.jboss.as.txn.subsystem.TransactionExtension.initialize(TransactionExtension.java:115) at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:99) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_33] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] 13:31:13,018 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. 13:31:13,025 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.3.Final-SNAPSHOT "Steropes" stopped in 4ms {noformat} happens on the most current 7.1.3 build (branch "7.1-next") -- 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

11 years, 9 months

2
1
0 / 0

[JBoss JIRA] (AS7-5241) Look for jboss-cli.xml in current directory.

by Stan Silvert (JIRA)

Stan Silvert created AS7-5241: --------------------------------- Summary: Look for jboss-cli.xml in current directory. Key: AS7-5241 URL: https://issues.jboss.org/browse/AS7-5241 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.2.Final (EAP) Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 7.2.0.Alpha1 The jboss-cli.xml file provides configuration for running CLI. By default, CLI looks for this file first using the system property "jboss.cli.config", where the value is the fully-qualified path and file name. Next, it tries to find a file named "jboss-cli.xml" in the JBOSS_HOME/bin directory. 99% of the time, this is the way the file is found. When using the jboss-cli-client.jar, we are running on a machine where AS7 is probably not installed. Therefore, there is no JBOSS_HOME. So, CLI should also look in the current directory for jboss-cli.xml. -- 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

11 years, 9 months

1
2
0 / 0

[JBoss JIRA] (AS7-5270) CLI command for executing the deployment scanner

by Ben Schofield (JIRA)

Ben Schofield created AS7-5270: ---------------------------------- Summary: CLI command for executing the deployment scanner Key: AS7-5270 URL: https://issues.jboss.org/browse/AS7-5270 Project: Application Server 7 Issue Type: Feature Request Components: CLI Reporter: Ben Schofield Assignee: Alexey Loubyansky Priority: Minor provide a CLI command that will run the deployment scanner even if the deployment scanner is turned off. -- 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

11 years, 9 months

3
2
0 / 0

[JBoss JIRA] (AS7-2949) DMR Browser

by Max Rydahl Andersen (Created) (JIRA)

DMR Browser ----------- Key: AS7-2949 URL: https://issues.jboss.org/browse/AS7-2949 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Max Rydahl Andersen Assignee: Heiko Braun I know the CLI exist to browse and perform operations in the management API and its definitely awesome, but it has some severe limitations. 1) It requires you to have AS7 installed 2) I can't access it within a browser 3) It requires upfront DMR knowledge to get to the information 4) I cannot link to it for sharing information to my peers (this could be partially handled by command line but then we are back to 1 & 2) Similar the current admin console is not sufficient for all cases since it does not allow you to see parts of the DMR model that the admin console does not have UI support for yet. Thus I suggest we get a way to browse the DMR model to provide a way to read and understand the model by simply browsing it *then* users can use that info to start getting more into the CLI approach. And even when you got the CLI approach handled, just being able to click through and browse the content would be a tremendous help. The console could even be able to generate/show the paths and proper syntax to perform operations via the CLI. And the CLI could be able to open a webbrowser for a certain segment for more interactive browsing. Similar tools like JBoss Tools could link to this DMR browser for nice navigation. next steps could be to also support doing CLI-like operations in the browser but that is not the urgent need. -- 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

11 years, 9 months

2
3
0 / 0

[JBoss JIRA] (AS7-3736) javax.el.BeanELResolver.properties keeps references to undeployed classes (Class Loader leak)

by Philippe Guinot (JIRA)

Philippe Guinot created AS7-3736: ------------------------------------ Summary: javax.el.BeanELResolver.properties keeps references to undeployed classes (Class Loader leak) Key: AS7-3736 URL: https://issues.jboss.org/browse/AS7-3736 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.1.0.CR1b Environment: Seam 2.2.2 application Reporter: Philippe Guinot Assignee: David Lloyd This is another Class Loader leak memory issue. When class are loaded into the properties map, they don't get unloaded at undeploy. This cause the whole application's class loader not being garbage collected and so will result in OutOfMemoryError: PermGen space after a few deployments. The solution would be to call the purgeBeanClasses method at undeploy with each of the class loader of all sub-modules of the application. For the moment, the work around I've done was to change {code}private static final ConcurrentHashMap<Class, BeanProperties> properties = new ConcurrentHashMap<Class, BeanProperties>(CACHE_SIZE); {code}to{code} private static final Map<Class<?>, SoftReference<BeanProperties>> properties = Collections.synchronizedMap(new WeakHashMap<Class<?>, SoftReference<BeanProperties>>(CACHE_SIZE)); {code} But I'm not really sure if that's a good idea to replace the ConcurrentHashMap with a SynchronizedMap and I had to change {code}properties.putIfAbsent(baseClass, bps);{code} By{code} synchronized(properties) { if (!properties.containsKey(baseClass)) properties.put(baseClass, new SoftReference<BeanProperties>(bps)); } {code} -- 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

11 years, 9 months

5
7
0 / 0

[JBoss JIRA] (AS7-5294) unable to get console after JBOSS AS7 install

by Hema Damacharla (JIRA)

Hema Damacharla created AS7-5294: ------------------------------------ Summary: unable to get console after JBOSS AS7 install Key: AS7-5294 URL: https://issues.jboss.org/browse/AS7-5294 Project: Application Server 7 Issue Type: Enhancement Reporter: Hema Damacharla HI i have installed JBOSSAS7 in linux in standalone, after starting the server i am unable to get the console using http://localhost:8080/ -- 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

11 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9232) Store config file comments in the model

by Brian Stansberry (JIRA)

Store config file comments in the model --------------------------------------- Key: JBAS-9232 URL: https://issues.jboss.org/browse/JBAS-9232 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.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012