July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-703) Display server VM metrics in console

by Heiko Braun (JIRA)

Display server VM metrics in console ------------------------------------ Key: AS7-703 URL: https://issues.jboss.org/browse/AS7-703 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun 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

13 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBRULES-3150) NPE in ObjectTypeConfigurationRegistry when accumulate returns null (and "quick hack for 5.2")

by Wolfgang Laun (JIRA)

NPE in ObjectTypeConfigurationRegistry when accumulate returns null (and "quick hack for 5.2") ---------------------------------------------------------------------------------------------- Key: JBRULES-3150 URL: https://issues.jboss.org/browse/JBRULES-3150 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.1.Final rule foo # the problem is usually better "hidden" when Object() from accumulate( Object(), init( Object res = null; ) action( res = null; ) result( res ) ) then end causes the exception as shown below, or similar. A runtime diagnostic should tell the user (at least) that an accumulate result is null. ALSO, PLEASE NOTE THIS COMMENT in AccumulateNode.java:642! // this is a quick hack for the 5.2 release Exception in thread "main" java.lang.NullPointerException at org.drools.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:58) at org.drools.reteoo.AccumulateNode.evaluateResultConstraints(AccumulateNode.java:646) at org.drools.reteoo.AccumulateNode.assertLeftTuple(AccumulateNode.java:183) at org.drools.reteoo.SingleLeftTupleSinkAdapter.doPropagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:197) at org.drools.reteoo.SingleLeftTupleSinkAdapter.createAndPropagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:146) at org.drools.reteoo.LeftInputAdapterNode.assertObject(LeftInputAdapterNode.java:154) at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:59) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:204) at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:191) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:332) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:293) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:905) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:864) at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:255) at match.Main.makeFacts(Main.java:120) at match.Main.execute(Main.java:98) at match.Main.main(Main.java:126) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1054) The CallbackHandler is called multiple times on the client side with Remoting / Managent Interface

by Darran Lofthouse (JIRA)

The CallbackHandler is called multiple times on the client side with Remoting / Managent Interface -------------------------------------------------------------------------------------------------- Key: AS7-1054 URL: https://issues.jboss.org/browse/AS7-1054 Project: Application Server 7 Issue Type: Bug Components: Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Alpha1 This may be a side effect of the current problems where Remoting is looped to establish the connection but it means that we need to cache the users username and password from the first attempt so we don't keep prompting them - the problem then is we do not know if the subsequent call is because their values were invalid or just because of the retries. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1374) Domain Management - Ensure we keep Native connections alive where appropriate

by Darran Lofthouse (JIRA)

Domain Management - Ensure we keep Native connections alive where appropriate ----------------------------------------------------------------------------- Key: AS7-1374 URL: https://issues.jboss.org/browse/AS7-1374 Project: Application Server 7 Issue Type: Task Components: Domain Management, Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 Establishing a connection can generally also involve negotiating the security before the connection is first used, this has the potential to become a major performance drain especially if the management load is high (management can be everything from updating the model to querying metrics). This task is to ensure we keep the connections alive where it makes sense. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1102) Create PKCS#11 Compitable Cryptographic Services for Domain Management

by Darran Lofthouse (JIRA)

Create PKCS#11 Compitable Cryptographic Services for Domain Management ---------------------------------------------------------------------- Key: AS7-1102 URL: https://issues.jboss.org/browse/AS7-1102 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Fix For: 7.1.0.Beta1 Within domain management there are occasions where passwords need to be stored or keystores accessed either for encryption / decryption of password or to load the keys used for SSL exchanges. Commonly a password within code is used for password based encryption of other passwords, this obfuscates the password but does not over complicate the process of recovering the password, alternatively a local keystore can be used for the encryption but again everything is available on the local disk to recover the password. PKCS#11 will allow the cryptographic to be delegated to hardware which contains it's own protection against keys being made available. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (AS7-1395) Domain Management Security - Remote Repository Caching

by Darran Lofthouse (JIRA)

Domain Management Security - Remote Repository Caching ------------------------------------------------------ Key: AS7-1395 URL: https://issues.jboss.org/browse/AS7-1395 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 Where we are accessing remote stores for the users we need a cache for the information retrieved, will need features such as an expiration time and a possibility to flush the whole cache or individual entries. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-3117) Compiling two functions fails

by Wolfgang Laun (JIRA)

Compiling two functions fails ------------------------------ Key: JBRULES-3117 URL: https://issues.jboss.org/browse/JBRULES-3117 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Blocker Fix For: 5.2.1.Final Compiling these two function together fails: function boolean isOutOfRange( Object value, int lower ){ return true; } function boolean isNotContainedInt( Object object, int[] values ){ return true; } [ isNotContainedInt : unable to resolve type while building function ] If the first one is removed, or its arguments are reduced, the remainder compiles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-790) Subsystem "jms": attributes not writable

by Heiko Braun (JIRA)

Subsystem "jms": attributes not writable ---------------------------------------- Key: AS7-790 URL: https://issues.jboss.org/browse/AS7-790 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry { "outcome" => "failed", "failure-description" => {"domain-failure-description" => {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "Attribute selector is not writeable"}}} } w/o modifications to existing queues/topics are not possible -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3111) Regression: constraint comparing nested accessor to true fires when false

by Wolfgang Laun (JIRA)

Regression: constraint comparing nested accessor to true fires when false --------------------------------------------------------------------------- Key: JBRULES-3111 URL: https://issues.jboss.org/browse/JBRULES-3111 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Blocker Fix For: FUTURE The .drl file below produces r3:one false r2:one false r1:one true but only r1 is expected to fire. Removing all "== true" is one way of showing the correct result. declare Bool123 bool1 : boolean bool2 : boolean bool3 : boolean end declare Thing name : String bool123 : Bool123 end rule kickOff when then insert( new Thing( "one", new Bool123( true, false, false ) ) ); insert( new Thing( "two", new Bool123( false, false, false ) ) ); insert( new Thing( "three", new Bool123( false, false, false ) ) ); end rule r1 when $t: Thing( bool123.bool1 == true ) then System.out.println( "r1:" + $t.getName() + " " + $t.getBool123().isBool1() ); end rule r2 when $t: Thing( bool123.bool2 == true ) then System.out.println( "r2:" + $t.getName() + " " + $t.getBool123().isBool2() ); end rule r3 when $t: Thing( bool123.bool3 == true ) then System.out.println( "r3:" + $t.getName() + " " + $t.getBool123().isBool3() ); end ~ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1142) Exception when starting OSGi in AS7

by David Bosschaert (JIRA)

Exception when starting OSGi in AS7 ------------------------------------ Key: AS7-1142 URL: https://issues.jboss.org/browse/AS7-1142 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Priority: Minor When starting the OSGi Framework with Start Level 2 or higher, the following exception sometimes appears. It seems harmless though... 13:17:02,289 WARN [/] (CM Configuration Updater (ManagedService Update: pid=org.apache.felix.webconsole.internal.servlet.OsgiManager)) org.ops4j.pax.web.service.spi.model.ServletModel-2: unbindHttpService: Failed unregistering Servlet: java.lang.IllegalStateException: ServletModel{id=org.ops4j.pax.web.service.spi.model.ServletModel-2,name=org.ops4j.pax.web.service.spi.model.ServletModel-2,urlPatterns=[/system/console/*],alias=/system/console,servlet=org.apache.felix.webconsole.internal.servlet.OsgiManager@13dc8ea3,initParams={},context=ContextModel{id=org.ops4j.pax.web.service.spi.model.ContextModel-1,name=,httpContext=org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext(a)75187984,contextParams={}}} was not found at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.removeServlet(JettyServerImpl.java:230) at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Started.removeServlet(ServerControllerImpl.java:271) at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.removeServlet(ServerControllerImpl.java:112) at org.ops4j.pax.web.service.internal.HttpServiceStarted.unregister(HttpServiceStarted.java:205) at org.ops4j.pax.web.service.internal.HttpServiceProxy.unregister(HttpServiceProxy.java:72) at org.apache.felix.webconsole.internal.servlet.OsgiManager.unbindHttpService(OsgiManager.java:772) [OsgiManager.class:] at org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.removedService(OsgiManager.java:660) [OsgiManager$HttpServiceTracker.class:] at org.osgi.util.tracker.ServiceTracker$Tracked.untrack(ServiceTracker.java:1126) [ServiceTracker$Tracked.class:] at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:347) [ServiceTracker.class:] at org.apache.felix.webconsole.internal.servlet.OsgiManager.updateConfiguration(OsgiManager.java:826) [OsgiManager.class:] at org.apache.felix.webconsole.internal.servlet.ConfigurationListener.updated(ConfigurationListener.java:66) [ConfigurationListener.class:] at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1160) at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104) at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011