April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6664: ---------------------------------------------- pkremens(a)redhat.com made a comment on [bug 915317|https://bugzilla.redhat.com/show_bug.cgi?id=915317] Verified on EAP 6.1.0 ER4 > Unable to turn on/off logging handlers using enable()/disable() in CLI > ---------------------------------------------------------------------- > > Key: AS7-6664 > URL: https://issues.jboss.org/browse/AS7-6664 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Logging > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Peter Kremens reports: > I am unable to use enable/disable operation in logging handlers. > > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Calling disable() won't affect enabled attribute > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable() > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Must use write-attribute instead > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => false, > ... > } > } > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6664: ---------------------------------------------- pkremens(a)redhat.com changed the Status of [bug 915317|https://bugzilla.redhat.com/show_bug.cgi?id=915317] from ON_QA to VERIFIED > Unable to turn on/off logging handlers using enable()/disable() in CLI > ---------------------------------------------------------------------- > > Key: AS7-6664 > URL: https://issues.jboss.org/browse/AS7-6664 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Logging > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Peter Kremens reports: > I am unable to use enable/disable operation in logging handlers. > > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Calling disable() won't affect enabled attribute > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable() > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Must use write-attribute instead > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => false, > ... > } > } > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5855) CLONE - vault script generates identical shared keys when adding multiple passwords in one session

by Geoffrey Bays (JIRA)

[ https://issues.jboss.org/browse/AS7-5855?page=com.atlassian.jira.plugin.s... ] Geoffrey Bays commented on AS7-5855: ------------------------------------ I am aware of this bug, and have used two interactive sessions to generate two distinct handles to two passwords in the vault. Anyone know of an example of referencing two passwords from the vault in standalone.xml?? I am unable to get this to work. I know, this is not a help forum, but here is my issue below. Or is there a bug here as well?? I need an example of putting two passwords into the vault and then referencing them in standalone.xml. I have referenced the keystore file and password via the vault in the ssl connector line in standalone.xml, and have put the following reference to the truststore and password in as system properties. If I hardcode the unmasked truststore password all works, but even when using two interactive sessions (so that I get a separate handle for the second password), I cannot put two passwords into the vault and get the truststore reference to work. I get IOException: keystore was tampered with of password is incorrect. In standalone.xml: <system-property> <property name="javax.net.ssl.trustStore" value="Path /to/truststore/file" /> <property name="javax.net.ssl.trustStorePassword" value="VAULT::truststore_pass::password::YjdkMDU10TMzTdmy........." /> </system-property> Do I need more lines in the <vault> <vault-option> section to reference the second password? Two vault tags will not parse. Any suggestions or two password example would be most welcome. I have tried referencing the keystore password with the same vault handle since it is the same--does not work. And I have generated vault dat files using a reference to the keystore alone or with a separate reference to the truststore. Neither approach works. Thanks Geoffrey Bays > CLONE - vault script generates identical shared keys when adding multiple passwords in one session > -------------------------------------------------------------------------------------------------- > > Key: AS7-5855 > URL: https://issues.jboss.org/browse/AS7-5855 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts, Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > > Adding multiple passwords in a single interactive session with vault.sh generates duplicate Shared Keys -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-95) Statefull memory corruption with insertLogical() and 2 nots

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-95: -------------------------------------- Summary: Statefull memory corruption with insertLogical() and 2 nots Key: DROOLS-95 URL: https://issues.jboss.org/browse/DROOLS-95 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Beta1 Reporter: Geoffrey De Smet Assignee: Mario Fusco Priority: Critical Statefull corruption in RETE. Ping ge0ffrey on IRC if you have ample time and a clear head. This bug is nasty :) -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6553) Parent Issue for Java EE 7 Support

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6553?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-6553: ---------------------------------- Thanks, I had missed that one. > Parent Issue for Java EE 7 Support > ---------------------------------- > > Key: AS7-6553 > URL: https://issues.jboss.org/browse/AS7-6553 > Project: Application Server 7 > Issue Type: Task > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Critical > Fix For: 8.0.0.Alpha1 > > > This is the parent issue for tracking tasks related to completing our Java EE 7 support. Do not close the issue unless Jason has given his blessing. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6833) JSR-196 JASPIC 1.1 Support

by David Lloyd (JIRA)

David Lloyd created AS7-6833: -------------------------------- Summary: JSR-196 JASPIC 1.1 Support Key: AS7-6833 URL: https://issues.jboss.org/browse/AS7-6833 Project: Application Server 7 Issue Type: Sub-task Components: Security Reporter: David Lloyd Assignee: Anil Saldhana Fix For: 8.0.0.Alpha1 Provide support for the 1.1 maintenance release of JASPIC. http://jcp.org/aboutJava/communityprocess/maintenance/jsr196/196ChangeLog... -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6830) spelling mistakes in the management security domain should be logged better

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6830?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6830: --------------------------------------- Darran, this is likely another variation of AS7-6046, the problem I mentioned in my second comment on Nov 27. > spelling mistakes in the management security domain should be logged better > --------------------------------------------------------------------------- > > Key: AS7-6830 > URL: https://issues.jboss.org/browse/AS7-6830 > Project: Application Server 7 > Issue Type: Bug > Components: Security, Server > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Darran Lofthouse > Priority: Minor > > A spelling mistake in the management security domain prevents the server from starting (good) but the message in the log file is only stating: > [Host Controller] 08:35:37,672 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. > There in fact no previous messages -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-93) Building rule file that contains event declaration with @duration ends with NPE

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-93?page=com.atlassian.jira.plugin.... ] Mario Fusco resolved DROOLS-93. ------------------------------- Fix Version/s: 5.6 6.0.0.Beta1 Resolution: Done The problem was actually caused by a wrong package name in the drl used in the provided test. I fixed the NPE by generating a proper compilation failure message. > Building rule file that contains event declaration with @duration ends with NPE > ------------------------------------------------------------------------------- > > Key: DROOLS-93 > URL: https://issues.jboss.org/browse/DROOLS-93 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Alpha1 > Reporter: Petr Široký > Assignee: Mario Fusco > Fix For: 5.6, 6.0.0.Beta1 > > Attachments: drools93-reproducer.zip > > > Building kbase with simple rule file with event declaration that has a @duration attribute ends with NPE. When the @duration is removed, file is built correctly. See attached maven reproducer (just run mvn test). > The rule file looks like this: > {code} > package org.jboss.drools.example.kbase > declare org.jboss.drools.example.kbase.SimpleFact > @role(event) > @duration(duration) > end > {code} > Exception thrown when building the file: > {code} > java.lang.NullPointerException > at org.drools.compiler.compiler.PackageBuilder.processTypeFields(PackageBuilder.java:2206) > at org.drools.compiler.compiler.PackageBuilder.processTypeDeclarations(PackageBuilder.java:2123) > at org.drools.compiler.compiler.PackageBuilder.mergePackage(PackageBuilder.java:1254) > at org.drools.compiler.compiler.PackageBuilder.processTypeDeclarations(PackageBuilder.java:2000) > at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildTypeDeclarations(CompositeKnowledgeBuilderImpl.java:273) > at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildTypeDeclarations(CompositeKnowledgeBuilderImpl.java:249) > at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildPackages(CompositeKnowledgeBuilderImpl.java:87) > at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:76) > at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:140) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:39) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieModule(KieBuilderImpl.java:207) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:160) > at org.kie.internal.utils.KieHelper.build(KieHelper.java:25) > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-4464) EJB3 deployment metrics missing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4464?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4464: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 911117|https://bugzilla.redhat.com/show_bug.cgi?id=911117] Hi Carlo, I see that the changes are present in 6.1.0.ER4, but I only see method invocation metrics - execution time, invocation count and waiting time for each method. Nothing like cache size, passivated count, min/max invocation times, etc., as you specified in the first comment. Are you planning to add these? I am setting this to VERIFIED for now, so this should be considered just a reminder|question|whatever. Should you plan to add the mentioned metrics, feel free to reopen it. Thanks > EJB3 deployment metrics missing > ------------------------------- > > Key: AS7-4464 > URL: https://issues.jboss.org/browse/AS7-4464 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final > Reporter: Stefan Negrea > Assignee: Carlo de Wolf > Priority: Critical > Labels: rhq > Fix For: 8.0.0.Alpha1 > > > The following metrics are missing from AS7 EJB3 subsystem from deployment when compared to AS5 exposed metrics: > Stateless Session Bean > Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB > Stateful Session Bean > Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB > Cache Size - Cache Size > Passivated Count - Passivated Count > Total Size - Total Size -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-4464) EJB3 deployment metrics missing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4464?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4464: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 911117|https://bugzilla.redhat.com/show_bug.cgi?id=911117] from ON_QA to VERIFIED > EJB3 deployment metrics missing > ------------------------------- > > Key: AS7-4464 > URL: https://issues.jboss.org/browse/AS7-4464 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final > Reporter: Stefan Negrea > Assignee: Carlo de Wolf > Priority: Critical > Labels: rhq > Fix For: 8.0.0.Alpha1 > > > The following metrics are missing from AS7 EJB3 subsystem from deployment when compared to AS5 exposed metrics: > Stateless Session Bean > Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB > Stateful Session Bean > Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB > Cache Size - Cache Size > Passivated Count - Passivated Count > Total Size - Total Size -- 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

12 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013