November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3283) Concurrency issue: Invalid bytecode generated by KnowledgeBuilder.add()

by Thomas Kruse (Created) (JIRA)

Concurrency issue: Invalid bytecode generated by KnowledgeBuilder.add() ----------------------------------------------------------------------- Key: JBRULES-3283 URL: https://issues.jboss.org/browse/JBRULES-3283 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.3.0.Final, 5.3.0.CR1 Environment: Oracle Java 6, Oracle Java 7, Linux, MacOS java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode) Reporter: Thomas Kruse Assignee: Mark Proctor Priority: Minor Since Drools 5.3.0.CR1 concurrent creation of different knowledgebases from filesystem DRL rule definition leads to illegal bytecode. Reproduceable with Janino and eclipse compiler. I have a maven based test project which executes the unit tests in parallel, this is the result: {code} runFirst(de.trion.drools53.TwoTest): -1 runFirst(de.trion.drools53.FourTest): (class: de/trion/drools53/Rule_When_a_user_is_young__print_his_name_DefaultConsequenceInvoker, method: equals signature: (Ljava/lang/Object;)Z) Expecting to find integer on stack runSecond(de.trion.drools53.FourTest): (class: de/trion/drools53/Rule_When_a_user_is_young__print_his_name_DefaultConsequenceInvoker, method: equals signature: (Ljava/lang/Object;)Z) Expecting to find integer on stack runFirst(de.trion.drools53.OneTest): (class: de/trion/drools53/Rule_When_a_user_is_young__print_his_name_DefaultConsequenceInvoker, method: equals signature: (Ljava/lang/Object;)Z) Expecting to find integer on stack runFirst(de.trion.drools53.ThreeTest): (class: de/trion/drools53/Rule_When_a_user_is_young__print_his_name_DefaultConsequenceInvoker, method: equals signature: (Ljava/lang/Object;)Z) Incompatible object argument for function call runSecond(de.trion.drools53.ThreeTest): (class: de/trion/drools53/Rule_When_there_is_god__the_light_always_shines_DefaultConsequenceInvoker, method: equals signature: (Ljava/lang/Object;)Z) Unable to pop operand off an empty stack {code} Workaround: synchronize access Not affected: Drools 5.3.0.Beta -- 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

12 years, 1 month

6
12
0 / 0

[JBoss JIRA] (AS7-5272) validate-address fails for remote targets

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-5272: ---------------------------------------- Summary: validate-address fails for remote targets Key: AS7-5272 URL: https://issues.jboss.org/browse/AS7-5272 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: 7.2.0.Alpha1, 7.1.2.Final (EAP) the "validate-address" operation doesn't handle proxy-controllers when navigating the resource model. -- 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

12 years, 1 month

4
5
0 / 0

[JBoss JIRA] (AS7-5942) Implement custom Stack resource for JGroups to maintain protocol order

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-5942: ---------------------------------------- Summary: Implement custom Stack resource for JGroups to maintain protocol order Key: AS7-5942 URL: https://issues.jboss.org/browse/AS7-5942 Project: Application Server 7 Issue Type: Task Components: Clustering, Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Richard Achmatowicz Assignee: Paul Ferraro Fix For: 7.2.0.Alpha1 -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] (AS7-5876) cli simplified dmr format parser should also support dmr style '=>'

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-5876: -------------------------------------- Summary: cli simplified dmr format parser should also support dmr style '=>' Key: AS7-5876 URL: https://issues.jboss.org/browse/AS7-5876 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.3.Final (EAP) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) The parser should recognize '=>' and treat it as '='. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] (JGRP-1535) SocketException WARN messages at startup

by Edward Sutter (JIRA)

Edward Sutter created JGRP-1535: ----------------------------------- Summary: SocketException WARN messages at startup Key: JGRP-1535 URL: https://issues.jboss.org/browse/JGRP-1535 Project: JGroups Issue Type: Enhancement Affects Versions: 3.2, 3.0.14 Reporter: Edward Sutter Assignee: Bela Ban Priority: Minor We are seeing the following messages when starting our server nodes. From what I can tell from the source, JGroups is attempting to attach to every detected network interface and logs warning messages when an IP address is not found. I'm not seeing any negative behavior from JGroups but the messages cause some alarm to our administrators. Ideally JGroups would *not* log a message in the case where the interface does not have an IP address associated with it. Alternatively, lowering the log level to DEBUG could also work. WARN [org.jgroups.protocols.TCP] failed to join /224.0.75.75:7500 on net3: java.net.SocketException: Unrecognized Windows Sockets error: 0: no Inet4Address associated with interface WARN [org.jgroups.protocols.TCP] failed to join /224.0.75.75:7500 on net4: java.net.SocketException: Unrecognized Windows Sockets error: 0: no Inet4Address associated with interface -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] (AS7-5925) Karaf configuration through ConfigAdmin

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5925: ----------------------------------- Summary: Karaf configuration through ConfigAdmin Key: AS7-5925 URL: https://issues.jboss.org/browse/AS7-5925 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.CR1 Currently we add these props to standalone.conf {code} -Dkaraf.home=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf -Dkaraf.base=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf -Dkaraf.startRemoteShell=true -Dkaraf.startLocalConsole=false {code} For this we should have sensible defaults as well as make the SSH port (and possibly other options) configurable through ConfigAdmin -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-5924) CNFE OsgiBundleApplicationContextListener on Karaf bootstrap

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5924: ----------------------------------- Summary: CNFE OsgiBundleApplicationContextListener on Karaf bootstrap Key: AS7-5924 URL: https://issues.jboss.org/browse/AS7-5924 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.CR1 {code} Caused by: java.lang.ClassNotFoundException: org.springframework.osgi.context.event.OsgiBundleApplicationContextListener from [Module "deployment.org.apache.karaf.shell.osgi:2.2.9" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA] ... 40 more {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, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ] Kabir Khan resolved AS7-5884. ----------------------------- Fix Version/s: 7.1.4.Final (EAP) Resolution: Done > CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1 > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-5884 > URL: https://issues.jboss.org/browse/AS7-5884 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Kabir Khan > Priority: Critical > Labels: deployers, domain, eap, jboss > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1. > In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group. > But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available. > The second deployment can be used as long as there is a action to it (e.g. restart). > In that case a FATAL error is thrown: > [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 11:43:36,496 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. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ] Kabir Khan closed AS7-5884. --------------------------- > CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1 > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-5884 > URL: https://issues.jboss.org/browse/AS7-5884 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Kabir Khan > Priority: Critical > Labels: deployers, domain, eap, jboss > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1. > In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group. > But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available. > The second deployment can be used as long as there is a action to it (e.g. restart). > In that case a FATAL error is thrown: > [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 11:43:36,496 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. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-85) slf4j-jboss-logmanager does not support parametization of a logging statement in the presence of a Throwable

by Hercules Zeus (JIRA)

Hercules Zeus created JBLOGGING-85: -------------------------------------- Summary: slf4j-jboss-logmanager does not support parametization of a logging statement in the presence of a Throwable Key: JBLOGGING-85 URL: https://issues.jboss.org/browse/JBLOGGING-85 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: slf4j-jboss-logmanager Reporter: Hercules Zeus Assignee: David Lloyd http://www.slf4j.org/faq.html#paramException describes that from slf4j 1.6 onwards doing the following will print a stacktrace: logger.error("Failed to format {}", s, e); However, due to the implementation of org.slf4j.impl.MessageFormatter in slf4j-jboss-logmanager, when logger.error(String, Object, Object) is called, even if the third parameter is a Throwable, it is not recognised as such. Investigating further, it seems that org.slf4j.impl.MessageFormatter is probably just an old copy of org.slf4j.helpers.MessageFormatter in slfj-api 1.6.1, where most formatting methods used to return a String now returns a FormattingTuple. This issue can be fixed by making all calls in Slf4Logger to org.slf4j.impl.MessageFormatter to call org.slf4j.helpers.MessageFormatter instead and appropriately call ExtLogRecord.setThrown(formattingTuple.getThrowable()). -- 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

12 years, 1 month

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012