May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4438) Singleton EJB constructor called per method invocation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4438?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4438: ----------------------------------------------- Panagiotis Sotiropoulos <psotirop(a)redhat.com> changed the Status of [bug 1331819|https://bugzilla.redhat.com/show_bug.cgi?id=1331819] from NEW to POST > Singleton EJB constructor called per method invocation > ------------------------------------------------------ > > Key: WFLY-4438 > URL: https://issues.jboss.org/browse/WFLY-4438 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.2.0.Final, 9.0.0.Alpha1 > Reporter: Kirill Gaevskii > Assignee: Martin Kouba > Fix For: 9.0.0.Beta1 > > > @Singleton EJB constructor and @PostConstruct method call not once. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1153) Version detection when adding drools runtime doesn't work

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1153?page=com.atlassian.jira.plugi... ] Tomas David updated DROOLS-1153: -------------------------------- Description: When you add a drools runtime, version is not automatically detected and "Version must be in the form major#.minor#.patch#" text is displayed. User has to specify a version manually instead of automatic detection from binaries. (was: When you add a drools runtime, version is not automatically detected and "Version must be in the form major#.minor#.patch#" text is displayed. User has to specifies a version manually instead of automatic detection from binaries.) > Version detection when adding drools runtime doesn't work > --------------------------------------------------------- > > Key: DROOLS-1153 > URL: https://issues.jboss.org/browse/DROOLS-1153 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: JBDS 9.1.0.GA > Drools plugin 6.4.1-Snapshot > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Priority: Minor > Labels: reported-by-qe > Attachments: add_drools_runtime_dialog.png > > > When you add a drools runtime, version is not automatically detected and "Version must be in the form major#.minor#.patch#" text is displayed. User has to specify a version manually instead of automatic detection from binaries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1153) Version detection when adding drools runtime doesn't work

by Tomas David (JIRA)

Tomas David created DROOLS-1153: ----------------------------------- Summary: Version detection when adding drools runtime doesn't work Key: DROOLS-1153 URL: https://issues.jboss.org/browse/DROOLS-1153 Project: Drools Issue Type: Bug Components: eclipse plugin Environment: JBDS 9.1.0.GA Drools plugin 6.4.1-Snapshot Reporter: Tomas David Assignee: Robert (Bob) Brodt Priority: Minor Attachments: add_drools_runtime_dialog.png When you add a drools runtime, version is not automatically detected and "Version must be in the form major#.minor#.patch#" text is displayed. User has to specifies a version manually instead of automatic detection from binaries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1152) New jBPM maven project can be created only with hello world process

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-1152: ----------------------------------- Summary: New jBPM maven project can be created only with hello world process Key: DROOLS-1152 URL: https://issues.jboss.org/browse/DROOLS-1152 Project: Drools Issue Type: Bug Components: eclipse plugin Affects Versions: 6.4.0.Final Environment: JBDS 9.1.0.GA + drools-jbpm plugin from http://downloads.jboss.org/jbpm/updatesite-6.4.1/ Reporter: Jozef Marko Assignee: Robert (Bob) Brodt In project created via [1] can be created only hello world sample process while in project created via [2] can be created also more complex sample process and optionally JUnit test. [1] File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using maven [2] File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using Java and jBPM classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1151) Missing libraries in new jBPM project

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-1151: ----------------------------------- Summary: Missing libraries in new jBPM project Key: DROOLS-1151 URL: https://issues.jboss.org/browse/DROOLS-1151 Project: Drools Issue Type: Bug Components: eclipse plugin Affects Versions: 6.4.0.Final Environment: JBDS 9.1.0.GA + drools-jbpm plugin from [1] [1] http://downloads.jboss.org/jbpm/updatesite-6.4.1/ Reporter: Jozef Marko Assignee: Robert (Bob) Brodt In project created via [1] are missing libraries. Specifically classes from packages [2] can not be found. [1] File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using Java and jBPM classes [2] javax.persistence.* org.jbpm.test.* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1151) Missing libraries in new jBPM project

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1151?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1151: -------------------------------- Environment: JBDS 9.1.0.GA + drools-jbpm plugin from http://downloads.jboss.org/jbpm/updatesite-6.4.1/ (was: JBDS 9.1.0.GA + drools-jbpm plugin from [1] [1] http://downloads.jboss.org/jbpm/updatesite-6.4.1/) > Missing libraries in new jBPM project > ------------------------------------- > > Key: DROOLS-1151 > URL: https://issues.jboss.org/browse/DROOLS-1151 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.4.0.Final > Environment: JBDS 9.1.0.GA + drools-jbpm plugin from http://downloads.jboss.org/jbpm/updatesite-6.4.1/ > Reporter: Jozef Marko > Assignee: Robert (Bob) Brodt > > In project created via [1] are missing libraries. Specifically classes from packages [2] can not be found. > [1] > File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using Java and jBPM classes > [2] > javax.persistence.* > org.jbpm.test.* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6576) mod_cluster advertise="false" does not disable advertise if there are no proxies configured

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-6576?page=com.atlassian.jira.plugin.... ] Michal Karm Babacek updated WFLY-6576: -------------------------------------- Labels: ux (was: ) > mod_cluster advertise="false" does not disable advertise if there are no proxies configured > ------------------------------------------------------------------------------------------- > > Key: WFLY-6576 > URL: https://issues.jboss.org/browse/WFLY-6576 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Labels: ux > > {noformat} > 17:05:56,822 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 64) MODCLUSTER000001: Initializing mod_cluster version 1.3.2.Final > 17:05:56,833 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 64) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364 > {noformat} > {noformat} > [standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration:read-resource > { > "outcome" => "success", > "result" => { > "advertise" => false, > "advertise-security-key" => undefined, > "advertise-socket" => undefined, > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6559) Expose stats for transaction System Rollbacks and Average Commit Time in the CLI

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-6559?page=com.atlassian.jira.plugin.... ] Tomas Hofman commented on WFLY-6559: ------------------------------------ I could take care of this, if you didn't start yet [~mmusgrov]. > Expose stats for transaction System Rollbacks and Average Commit Time in the CLI > -------------------------------------------------------------------------------- > > Key: WFLY-6559 > URL: https://issues.jboss.org/browse/WFLY-6559 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > JBTM-2341 added to two statistics for counting the number of transaction system rollbacks and for reporting the average commit time. These should be exposed in the wildfly CLI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1503) Reading the logging subsystem resource can be slow if several log files exist

by Paul Vorbach (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1503?page=com.atlassian.jira.plugi... ] Paul Vorbach commented on WFCORE-1503: -------------------------------------- [~jamezp]: Thank you for the patch. Both the logging configuration page in the WildFly console as well as the MBeans tree load really fast. So the issue seems to be fixed by this patched version of wildfly-logging. > Reading the logging subsystem resource can be slow if several log files exist > ----------------------------------------------------------------------------- > > Key: WFCORE-1503 > URL: https://issues.jboss.org/browse/WFCORE-1503 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Labels: 2.2 > Attachments: wildfly-logging-patch-02.jar > > > The logging subsystem uses a dynamic resource to list log files as resources. These are the files that are allowed to be read or downloaded and are attached to known file handlers. > When several file handlers are defined the file tree walker is invoked several times per {{read-resource-operation}}. This may be happening for each stage of an operation. Ideally we could either cache the file listing per-operation or only execute at the runtime stage. This may not be an option for dynamic resources however. > As a result of this poor performance the web console is very slow to load the logging subsystem configuration. This is not an issue with the web console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JASSIST-248) Constant pool index 268 is invalid

by Laurent Pellegrino (JIRA)

[ https://issues.jboss.org/browse/JASSIST-248?page=com.atlassian.jira.plugi... ] Laurent Pellegrino commented on JASSIST-248: -------------------------------------------- [~chiba] I had time to test the fix you mentioned. It solves the issue I was experiencing. Does a new Javassist release is planned soon? > Constant pool index 268 is invalid > ---------------------------------- > > Key: JASSIST-248 > URL: https://issues.jboss.org/browse/JASSIST-248 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.19.0-GA > Reporter: Laurent Pellegrino > Assignee: Shigeru Chiba > Labels: regression > Fix For: 3.21.0-GA > > Attachments: _StubLinkedList.class > > > We are using Javassist for one of our open source projects since about 10 years. Recently, I have tried to upgrade to version 3.19 and 3.20. Unfortunately, with both versions, generated byte code seems to cause errors with the JVM. > Below is the output: > {code} > Exception in thread "RestartDownNodesPolicy node status check" java.lang.VerifyError: Illegal type at constant pool entry 268 in class pa.stub.java.util._StubLinkedList > Exception Details: > Location: > pa/stub/java/util/_StubLinkedList.replaceAll(Ljava/util/function/UnaryOperator;)V @43: invokespecial > Reason: > Constant pool index 268 is invalid > Bytecode: > 0x0000000: 2ab4 00cc 9900 252a b400 0db2 002c 100b > 0x0000010: 32c0 0028 04bd 00ce 5903 2b53 b200 26b8 > 0x0000020: 00d7 b900 dd02 0057 b12a 2bb7 010c b1 > Stackmap Table: > same_frame(@41) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at org.objectweb.proactive.core.mop.MOP.forName(MOP.java:155) > at org.objectweb.proactive.core.mop.MOP.findStubConstructor(MOP.java:649) > at org.objectweb.proactive.core.mop.MOP.createStubObject(MOP.java:822) > at org.objectweb.proactive.core.mop.MOP.newInstance(MOP.java:338) > at org.objectweb.proactive.core.mop.MOP.newInstance(MOP.java:196) > at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.reifyAsAsynchronous(AbstractBodyProxy.java:277) > at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.invokeOnBody(AbstractBodyProxy.java:154) > at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.reify(AbstractBodyProxy.java:123) > at pa.stub.org.ow2.proactive.resourcemanager.nodesource._StubNodeSource.getDownNodes(_StubNodeSource.java) > at org.ow2.proactive.resourcemanager.nodesource.policy.RestartDownNodesPolicy$1.run(RestartDownNodesPolicy.java:92) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > {code} > The issue seems related to default methods introduced in Java 8. Perhaps its not an issue with Javassist but to be honest I don't understand the exception. However, I have noticed that using Javassist in version 3.18.2 solves the problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 May 2016