August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SASL-11) From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-11?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-11: --------------------------------- Fix Version/s: 1.0.4.CR1 (was: 1.0.3.Final) > From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect > --------------------------------------------------------------------------------------------------------------------------- > > Key: SASL-11 > URL: https://issues.jboss.org/browse/SASL-11 > Project: JBoss SASL Provider > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR1 > > > By using space as the separator a single realm name that contains a space is split into two realms. > Either support quoted realm names if they contain a space or choose a different delimiter - (A different delimiter other than a control character may be difficult as the rest can appear in a realm name) -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SASL-10) Pluggable nonce handling strategy

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-10?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-10: --------------------------------- Fix Version/s: 1.0.4.CR1 (was: 1.0.3.Final) > Pluggable nonce handling strategy > --------------------------------- > > Key: SASL-10 > URL: https://issues.jboss.org/browse/SASL-10 > Project: JBoss SASL Provider > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR1 > > > Implement a pluggable nonce handling strategy. > At the very least we need to be able to switch to using a SecureRandom instead of Random. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SASL-38) Release JBoss SASL 1.0.3.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-38: ------------------------------------ Summary: Release JBoss SASL 1.0.3.Final Key: SASL-38 URL: https://issues.jboss.org/browse/SASL-38 Project: JBoss SASL Provider Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.3.CR1 -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (AS7-4939) CLONE - CLI: unable to specify command arguments to echo-dmr command

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-4939?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky resolved AS7-4939. ------------------------------------ Fix Version/s: 7.1.3.Final (EAP) (was: 7.1.4.Final (EAP)) Resolution: Done This was fixed two months ago, commit d3cefc40ceb1716d76d8d6f8e9a71078422afb29 > CLONE - CLI: unable to specify command arguments to echo-dmr command > -------------------------------------------------------------------- > > Key: AS7-4939 > URL: https://issues.jboss.org/browse/AS7-4939 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Reporter: Dominik Pospisil > Assignee: Alexey Loubyansky > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > It seems to be impossible to specify command arguments to echo-dmr command beginning with double-dash. > While e.g. this works: > [domain@localhost:9999 /] echo-dmr undeploy deployment0.war > { > "operation" => "composite", > "address" => [], > "steps" => [{ > "operation" => "remove", > "address" => [("deployment" => "deployment0.war")] > }] > } > This does not: > [domain@localhost:9999 /] echo-dmr deploy /home/dpospisi/deploy/deployment1.war --all-server-groups > Unrecognized arguments: [--all-server-groups] > Putting requested command in quotes does not work as well. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SASL-37) Using deleteOnExit for files leading to memory leak.

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-37: ------------------------------------ Summary: Using deleteOnExit for files leading to memory leak. Key: SASL-37 URL: https://issues.jboss.org/browse/SASL-37 Project: JBoss SASL Provider Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.2.Final Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.3.CR1 Using deleteOnExit for the temporary files used by the local mechanism is leading to a memory leak - clean up for the files themselves has now been added but the deleteOnExit registration is not cleared when the file is actually deleted. -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (AS7-5388) Upgrade to JBoss SASL 1.0.3.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5388: ------------------------------------- Summary: Upgrade to JBoss SASL 1.0.3.Final Key: AS7-5388 URL: https://issues.jboss.org/browse/AS7-5388 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse This is primarily to receive the fix for SASL-37 to correct a memory leak when using the local mechanism. -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (JGRP-1502) NAKACK / NAKACK2: modifying header of copy can still lead to side effects

by Bela Ban (JIRA)

Bela Ban created JGRP-1502: ------------------------------ Summary: NAKACK / NAKACK2: modifying header of copy can still lead to side effects Key: JGRP-1502 URL: https://issues.jboss.org/browse/JGRP-1502 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0.12, 3.2 NAKACK and NAKACK2 copy a message (e.g. for retransmission) and then modify the NakackHeader of the copy *in place*. However, as Message.copy() does *not* copy the headers themselves, only the array holding the references to the headers, the modification of NakackHeader will also modify the original message ! SOLUTION: Create a new header off of the exitsing header and call Message.putHeader(), overwriting the old header. -- 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

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] (JBWEB-245) Issue with jboss 4.2.3

by Neetha Jaligama (JIRA)

Neetha Jaligama created JBWEB-245: ------------------------------------- Summary: Issue with jboss 4.2.3 Key: JBWEB-245 URL: https://issues.jboss.org/browse/JBWEB-245 Project: JBoss Web Issue Type: Task Security Level: Public (Everyone can see) Reporter: Neetha Jaligama Assignee: Remy Maucherat -- 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

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] (AS7-4268) Create subsystem for JMS bridge

by Justin Bertram (JIRA)

Justin Bertram created AS7-4268: ----------------------------------- Summary: Create subsystem for JMS bridge Key: AS7-4268 URL: https://issues.jboss.org/browse/AS7-4268 Project: Application Server 7 Issue Type: Task Components: JMS Affects Versions: 7.1.1.Final Reporter: Justin Bertram Assignee: Jeff Mesnil Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7. In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it. The bridge is a nice feature so we need a way to deploy it. It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server. It really needs its own subsystem. -- 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

13 years, 8 months

5
11
0 / 0

[JBoss JIRA] (JBRULES-3537) JIT crash when throwing RuntimeException

by Willem van Asperen (JIRA)

Willem van Asperen created JBRULES-3537: ------------------------------------------- Summary: JIT crash when throwing RuntimeException Key: JBRULES-3537 URL: https://issues.jboss.org/browse/JBRULES-3537 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.4.0.Final Environment: linux java version "1.7.0_04-icedtea" OpenJDK Runtime Environment (IcedTea7 2.2) (ArchLinux build 7.u4_2.2-1-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode) Reporter: Willem van Asperen Assignee: Mark Proctor There is probably something wrong with my rules. But I get a funny error (see trace below). This seems to be because the ConditionAnalyzer wants to throw a RuntimeException (line 229): if (accessor == null) { throw new RuntimeException("Null accessor on node: " + node); } Then the toString of ASTNode node crashes with a NullPointerException at line 427: public String toString() { return isOperator() ? "<<" + DebugTools.getOperatorName(getOperator()) + ">>" : (PCTX_STORED & fields) != 0 ? nameCache : new String(expr, start, offset); } This is because the variable expr is null. Exception in thread "Thread-1" java.lang.NullPointerException at java.lang.String.<init>(String.java:229) at org.mvel2.ast.ASTNode.toString(ASTNode.java:426) at java.lang.String.valueOf(String.java:2902) at java.lang.StringBuilder.append(StringBuilder.java:128) at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:229) at org.drools.rule.constraint.ConditionAnalyzer.analyzeSingleCondition(ConditionAnalyzer.java:126) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:102) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCombinedCondition(ConditionAnalyzer.java:133) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:94) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCombinedCondition(ConditionAnalyzer.java:133) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:94) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCombinedCondition(ConditionAnalyzer.java:133) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:94) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCombinedCondition(ConditionAnalyzer.java:133) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:94) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCombinedCondition(ConditionAnalyzer.java:133) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:94) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCombinedCondition(ConditionAnalyzer.java:133) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:94) at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:73) at org.drools.rule.constraint.MvelConditionEvaluator.getAnalyzedCondition(MvelConditionEvaluator.java:83) at org.drools.rule.constraint.MvelConstraint.executeJitting(MvelConstraint.java:214) at org.drools.rule.constraint.MvelConstraint.access$000(MvelConstraint.java:41) at org.drools.rule.constraint.MvelConstraint$1.run(MvelConstraint.java:201) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- 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

13 years, 8 months

2
3
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 August 2012