July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1475) Convert project to use i18n logging and exceptions

by James Perkins (JIRA)

James Perkins created JGRP-1475: ----------------------------------- Summary: Convert project to use i18n logging and exceptions Key: JGRP-1475 URL: https://issues.jboss.org/browse/JGRP-1475 Project: JGroups Issue Type: Task Reporter: James Perkins Assignee: Bela Ban As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- 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, 9 months

2
12
0 / 0

[JBoss JIRA] (JBRULES-3515) Getting runtime exception while I remove a validation Rule in version 5.4

by Premasis S (JIRA)

Premasis S created JBRULES-3515: ----------------------------------- Summary: Getting runtime exception while I remove a validation Rule in version 5.4 Key: JBRULES-3515 URL: https://issues.jboss.org/browse/JBRULES-3515 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.4.0.Final Reporter: Premasis S Assignee: Mark Proctor I am getting the following exception while removing/disabling a Drool Validation Rule, using Drools Version 5.4.FINAL i.e when I call - knowledgeBase.removeRule("pkg.trade", "2.8.I23"); java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:980) at java.util.HashMap$EntryIterator.next(HashMap.java:1018) at java.util.HashMap$EntryIterator.next(HashMap.java:1016) at org.drools.reteoo.EvalConditionNode.doRemove(EvalConditionNode.java:302) at org.drools.common.BaseNode.remove(BaseNode.java:109) at org.drools.reteoo.FromNode.doRemove(FromNode.java:440) at org.drools.common.BaseNode.remove(BaseNode.java:109) at org.drools.reteoo.RightInputAdapterNode.doRemove(RightInputAdapterNode.java:285) at org.drools.common.BaseNode.remove(BaseNode.java:109) at org.drools.reteoo.BetaNode.doRemove(BetaNode.java:499) at org.drools.common.BaseNode.remove(BaseNode.java:109) at org.drools.reteoo.RuleTerminalNode.doRemove(RuleTerminalNode.java:358) at org.drools.common.BaseNode.remove(BaseNode.java:109) at org.drools.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:261) at org.drools.reteoo.ReteooRuleBase.removeRule(ReteooRuleBase.java:460) at org.drools.common.AbstractRuleBase.removeRule(AbstractRuleBase.java:1107) at org.drools.common.AbstractRuleBase.removeRule(AbstractRuleBase.java:1085) at org.drools.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:210) Here is the Rule: package pkg.trade; rule "2.8.I23" when $trade : Trade() $trdDeskId : Id() from mediator.getTradingDeskId($trade) eval(isPositiveId($trdDeskId)) eval($trdDeskId != null && !mediator.isValidTradingDesk($trdDeskId)) then raiseException(kcontext, $trade, "tradingDeskId", stringValue($trdDeskId)); end -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-3975) EJB client invocations sometimes hang indefinitely

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3975: ----------------------------------- Summary: EJB client invocations sometimes hang indefinitely Key: AS7-3975 URL: https://issues.jboss.org/browse/AS7-3975 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: jaikiran pai Priority: Critical Fix For: 7.1.1.Final When running a EJB stress test when the test is over some clients hang indefinitely. This is a positive test, there are no failures being injected in the test. {noformat} "Runner - 16" daemon prio=10 tid=0x00007fb7a0025000 nid=0x4d7a in Object.wait() [0x00007fb78b3f2000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:330) - locked <0x00000006c013ae50> (a java.lang.Object) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:140) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) at $Proxy0.getSerialAndIncrement(Unknown Source) at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68) at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) at java.lang.Thread.run(Thread.java:662) {noformat} I originally filed a feature request to implement a timeout AS7-3811, needless to say this needs to get fixed first. -- 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, 9 months

6
20
0 / 0

[JBoss JIRA] (JBBUILD-720) Change modeshape-tools-continuous Jenkins Job Update-Site Output Directory

by Dan Florian (JIRA)

Dan Florian created JBBUILD-720: ----------------------------------- Summary: Change modeshape-tools-continuous Jenkins Job Update-Site Output Directory Key: JBBUILD-720 URL: https://issues.jboss.org/browse/JBBUILD-720 Project: JBoss Build System Issue Type: Task Components: Maven Builds Affects Versions: Build Support 2011 Reporter: Dan Florian Assignee: Nick Boldt The modeshape-tools-continuous job outputs the ModeShape Tools update-site to here: /downloads_htdocs/modeshape/builds/staging/modeshape-tools-continuous/all/repo We would like the path to be (something like) this: /downloads_htdocs/modeshape/tools/update/{stable|develop}/{helios|indigo|juno|etc} At a minimum, the path needs to have the "tools" segment as this identifies it from the ModeShape project. What do other projects do as far as stable vs. develop build? Do other project's put the Eclipse release in the path? Please see MODE-1506 for additional questions/discussion. I was told to get with you on this Nick. Please update this issue's project and component as appropriate as I wasn't sure. -- 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, 9 months

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-8201) Patching system

by Brian Stansberry (JIRA)

Patching system --------------- Key: JBAS-8201 URL: https://jira.jboss.org/browse/JBAS-8201 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M2 "Server" side of the patching system. Server not in the sense of the domain model Server, but rather client-server where the client is whatever tool (JON) determines there are patches available and asks the server to apply them. This does not need to implemented until M2 but thinking about it during the design of the InstalledImage is good. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

6
9
0 / 0

[JBoss JIRA] (JBRULES-3543) KnowledgeAgent: Doesn't remove insertLogical() Facts correctly with incremental build

by Torsten Schöne (JIRA)

13 years, 10 months

4
14
0 / 0

[JBoss JIRA] (JBRULES-3532) NPE in DefaultHardAndSoftScore.compareTo()

by Martin Vecera (JIRA)

Martin Vecera created JBRULES-3532: -------------------------------------- Summary: NPE in DefaultHardAndSoftScore.compareTo() Key: JBRULES-3532 URL: https://issues.jboss.org/browse/JBRULES-3532 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (expert) Affects Versions: 5.4.0.Final Reporter: Martin Vecera Assignee: Mark Proctor When running a benchmark on a very slow machine (virtual machine), hard and soft part of the score might remain uninitialized for long time (might be related to JBRULES-3317). This discovered an issue in the compareTo() method. Caused by: java.lang.NullPointerException at org.drools.planner.core.score.buildin.hardandsoft.DefaultHardAndSoftScore.compareTo(DefaultHardAndSoftScore.java:125) at org.drools.planner.core.score.buildin.hardandsoft.DefaultHardAndSoftScore.compareTo(DefaultHardAndSoftScore.java:27) at org.drools.planner.benchmark.core.ProblemBenchmark.determineWinningResult(ProblemBenchmark.java:180) at org.drools.planner.benchmark.core.ProblemBenchmark.benchmarkingEnded(ProblemBenchmark.java:173) at org.drools.planner.benchmark.core.DefaultPlannerBenchmark.benchmarkingEnded(DefaultPlannerBenchmark.java:201) at org.drools.planner.benchmark.core.DefaultPlannerBenchmark.benchmark(DefaultPlannerBenchmark.java:135) at org.drools.planner.examples.tournaments.Benchmark.main(Benchmark.java:25) ... 6 more -- 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, 10 months

2
8
0 / 0

[JBoss JIRA] (AS7-2411) servergroup view

by Rich Sharples (Created) (JIRA)

servergroup view ---------------- Key: AS7-2411 URL: https://issues.jboss.org/browse/AS7-2411 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.Alpha1 Environment: all Reporter: Rich Sharples Assignee: Heiko Braun Fix For: 7.1.0.Beta1 In the console when working with a large cluster or server-group it would be *really* useful to have a single view of all servers (local and remote) within the group. In thatview I'd expect to see the server name as well as the host IP / name and status. I think the natural place for this view would be unde Server Groups. The alterative today is to go to each host and view the server-group on each - that is a real pain in a production environment with a large number of machines / servers. -- 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, 10 months

7
13
0 / 0

[JBoss JIRA] Created: (AS7-887) Support legacy ServiceMBeans in SAR deployments

by Matt Drees (JIRA)

Support legacy ServiceMBeans in SAR deployments ----------------------------------------------- Key: AS7-887 URL: https://issues.jboss.org/browse/AS7-887 Project: Application Server 7 Issue Type: Enhancement Reporter: Matt Drees It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore. Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

7
13
0 / 0

[JBoss JIRA] (AS7-4444) Web deployment metrics missing

by Stefan Negrea (JIRA)

Stefan Negrea created AS7-4444: ---------------------------------- Summary: Web deployment metrics missing Key: AS7-4444 URL: https://issues.jboss.org/browse/AS7-4444 Project: Application Server 7 Issue Type: Enhancement Components: Web Reporter: Stefan Negrea Assignee: Remy Maucherat The following web deployment metrics are missing from AS7 when compared to AS5 exposed metrics: Clustered - True if this web application context is clustered Virtual Host - the virtual host with which this context is associated Response Time - the minimum, maximum, and average response times for requests serviced by this webapp Currently Active Sessions - the number of sessions that are currently active for this WAR Maximum Active Sessions - the maximum number of sessions that have been active for this WAR Created Sessions - the number of sessions created for this WAR Created Sessions per Minute - the number of sessions created for this WAR Expired Sessions - the number of expired sessions for this WAR Expired Sessions per Minute - the number of expired sessions for this WAR Rejected Sessions - the number of sessions rejected for this WAR Rejected Sessions per Minute - the number of sessions rejected for this WAR Average Session Alive Time - the average alive time of sessions for this WAR Max Session Alive Time - the maximum alive time of sessions for this WAR -- 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, 10 months

4
6
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 July 2012