March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-795) AdvancedLdap login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-795?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-795: -------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1065476|https://bugzilla.redhat.com/show_bug.cgi?id=1065476] from ASSIGNED to MODIFIED > AdvancedLdap login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-795 > URL: https://issues.jboss.org/browse/SECURITY-795 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Derek Horton > Fix For: Negotiation_2_2_7 > > Attachments: SECURITY-795.patch > > > AdvancedLdap login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-450) Cannot use decimal formatters for integers in an excel decision table

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-450?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-450: ------------------------------------------------ Edson Tirelli <etirelli(a)redhat.com> changed the Status of [bug 1077228|https://bugzilla.redhat.com/show_bug.cgi?id=1077228] from NEW to MODIFIED > Cannot use decimal formatters for integers in an excel decision table > --------------------------------------------------------------------- > > Key: DROOLS-450 > URL: https://issues.jboss.org/browse/DROOLS-450 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Maxime Falaize > Assignee: Michael Anstis > Priority: Minor > Fix For: 6.1.0.Beta2 > > Attachments: issue_example.png > > > When I use decimal formatter in an excel action column for numbers that are in fact integers, I am getting this exception : > {noformat} > Exception in thread "main" java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=com/sample/my_decision_table.xls, line=5, column=0 > text=Rule Compilation error The method setParameter(double) in the type MyObject is not applicable for the arguments (int, int)]] > at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:260) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:400) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:375) > {noformat} > Actually, the system uses the format number "1,00000" (with comma in french) instead of "1.00000" like it should use. > This is causing by the line 174 in org.drools.decisiontable.parser.xls.ExcelParser : > {code:java} > if ( num - Math.round( num ) != 0 ) > {code} > I don't understand why we use the formatted value when this test is not passed. > I think the end users should have the possibility to keep the same formatter for the same column, with integers or not. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3144) Session replication doesn't work as expected

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-3144?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-3144: ------------------------------------ For the record: I was able to reproduce the problem with cURL and forged JSESSIONID. > Session replication doesn't work as expected > -------------------------------------------- > > Key: WFLY-3144 > URL: https://issues.jboss.org/browse/WFLY-3144 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld, EJB > Affects Versions: 8.0.0.Final > Reporter: Tomas Remes > Assignee: Stuart Douglas > Attachments: translator.zip > > > I am experimenting with quite simple Stateful SessionScoped bean ( see org.jboss.weld.tests.clustering.translator.TranslatorControllerBean from attached reproducer) and actually there's not any specific exception, but the behavior is at least weird. I haven't tried with plain EJB so far. Reproducible by following steps: > 1. Run first node with "/bin/standalone.sh -c standalone-ha.xml" > 2. Run second node with "./bin/standalone.sh -c standalone-ha.xml -Djboss.socket.binding.port-offset=100 -Djboss.node.name=second" > 3. Build and deploy attached reproducer > 4. Open 127.0.0.1:8080/translator in your browser and translate something. > 5. Open 127.0.0.1:8180/translator and note that number of translated sentences is not replicated correctly. > This works correctly in EAP. I am running with default standalone-ha configuration on oracle's 1.7.0_45 jdk. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-263) JASPI Support for Web Services

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-263?page=com.atlassian.jira.plugin.s... ] Alessio Soldano resolved WFLY-263. ---------------------------------- Resolution: Done Included in JBossWS 4.3.0.Final upgrade. Some doc at https://docs.jboss.org/author/display/JBWS/Authentication (JASPI Authentication section) > JASPI Support for Web Services > ------------------------------ > > Key: WFLY-263 > URL: https://issues.jboss.org/browse/WFLY-263 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security, Web Services > Reporter: Anil Saldhana > Assignee: Jim Ma > Fix For: 9.0.0.CR1 > > > Take care of the JASPI requirements for SOAP layer. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3144) Session replication doesn't work as expected

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/WFLY-3144?page=com.atlassian.jira.plugin.... ] Tomas Remes updated WFLY-3144: ------------------------------ Attachment: translator.zip > Session replication doesn't work as expected > -------------------------------------------- > > Key: WFLY-3144 > URL: https://issues.jboss.org/browse/WFLY-3144 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld, EJB > Affects Versions: 8.0.0.Final > Reporter: Tomas Remes > Assignee: Stuart Douglas > Attachments: translator.zip > > > I am experimenting with quite simple Stateful SessionScoped bean ( see org.jboss.weld.tests.clustering.translator.TranslatorControllerBean from attached reproducer) and actually there's not any specific exception, but the behavior is at least weird. I haven't tried with plain EJB so far. Reproducible by following steps: > 1. Run first node with "/bin/standalone.sh -c standalone-ha.xml" > 2. Run second node with "./bin/standalone.sh -c standalone-ha.xml -Djboss.socket.binding.port-offset=100 -Djboss.node.name=second" > 3. Build and deploy attached reproducer > 4. Open 127.0.0.1:8080/translator in your browser and translate something. > 5. Open 127.0.0.1:8180/translator and note that number of translated sentences is not replicated correctly. > This works correctly in EAP. I am running with default standalone-ha configuration on oracle's 1.7.0_45 jdk. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3144) Session replication doesn't work as expected

by Tomas Remes (JIRA)

Tomas Remes created WFLY-3144: --------------------------------- Summary: Session replication doesn't work as expected Key: WFLY-3144 URL: https://issues.jboss.org/browse/WFLY-3144 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: CDI / Weld, EJB Affects Versions: 8.0.0.Final Reporter: Tomas Remes Assignee: Stuart Douglas I am experimenting with quite simple Stateful SessionScoped bean ( see org.jboss.weld.tests.clustering.translator.TranslatorControllerBean from attached reproducer) and actually there's not any specific exception, but the behavior is at least weird. I haven't tried with plain EJB so far. Reproducible by following steps: 1. Run first node with "/bin/standalone.sh -c standalone-ha.xml" 2. Run second node with "./bin/standalone.sh -c standalone-ha.xml -Djboss.socket.binding.port-offset=100 -Djboss.node.name=second" 3. Build and deploy attached reproducer 4. Open 127.0.0.1:8080/translator in your browser and translate something. 5. Open 127.0.0.1:8180/translator and note that number of translated sentences is not replicated correctly. This works correctly in EAP. I am running with default standalone-ha configuration on oracle's 1.7.0_45 jdk. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-315) Avoid running out of threads when connecting to the DC from a slave to pull down missing data

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-315?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-315: ---------------------------------- Priority: Blocker (was: Major) > Avoid running out of threads when connecting to the DC from a slave to pull down missing data > --------------------------------------------------------------------------------------------- > > Key: WFLY-315 > URL: https://issues.jboss.org/browse/WFLY-315 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Emanuel Muckenhuber > Priority: Blocker > Fix For: 9.0.0.CR1 > > > For WFLY-259 when a slave connects to the DC to pull down missing data, it does this by either getting a lock for the DC, or by joining the permit of the existing DC lock if the request to update a slave's server-config was executed as part of a composite obtaining a lock on the DC. > The way it works at present there is a thread per slave which is blocked until the transaction completes. The DC threads are a finite resource, so a large number of slaves trying to pull down dats will cause deadlock -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2415) Add configuration option to enable/disable Infinispan statistics

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2415?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2415: ----------------------------------------------- Richard Janík <rjanik(a)redhat.com> changed the Status of [bug 1025023|https://bugzilla.redhat.com/show_bug.cgi?id=1025023] from ON_QA to VERIFIED > Add configuration option to enable/disable Infinispan statistics > ---------------------------------------------------------------- > > Key: WFLY-2415 > URL: https://issues.jboss.org/browse/WFLY-2415 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Scott Marlow > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > When the Infinispan MBean is enabled, Infinispan statistics are enabled by default. Could we allow Infinispan statistics to be enabled/disabled via a WF configuration setting? -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3106) Infinispan cache statistics cannot be enabled/disabled independently of the cache manager statistics

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3106?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3106: ----------------------------------------------- Richard Janík <rjanik(a)redhat.com> changed the Status of [bug 1025023|https://bugzilla.redhat.com/show_bug.cgi?id=1025023] from ON_QA to VERIFIED > Infinispan cache statistics cannot be enabled/disabled independently of the cache manager statistics > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-3106 > URL: https://issues.jboss.org/browse/WFLY-3106 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 8.0.1.Final > > > The Infinispan subsystem allows enabling and disabling the collection of statistics for cache managers and caches via the "statistics-enabled" management API attribute. > It is possible to set statistics-enabled attributes independently for cache managers and caches in the management API, but when checking the Infinispan MBeans, we see that statistics are either enabled for cache managers and their caches, or disabled for cache managers and caches. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-809) Release JBoss Negotiation 2.3.0.Beta1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-809?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-809. --------------------------------------- Resolution: Done > Release JBoss Negotiation 2.3.0.Beta1 > ------------------------------------- > > Key: SECURITY-809 > URL: https://issues.jboss.org/browse/SECURITY-809 > Project: PicketBox > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_0.Beta1 > > -- 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, 3 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 March 2014