February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6273) Upgrade Narayana to 5.2.14.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created WFLY-6273: ----------------------------------- Summary: Upgrade Narayana to 5.2.14.Final Key: WFLY-6273 URL: https://issues.jboss.org/browse/WFLY-6273 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6271) SFSB methods can still be invoked after a calling transaction has rolledback

by Ryan Emerson (JIRA)

Ryan Emerson created WFLY-6271: ---------------------------------- Summary: SFSB methods can still be invoked after a calling transaction has rolledback Key: WFLY-6271 URL: https://issues.jboss.org/browse/WFLY-6271 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 10.0.0.Final Reporter: Ryan Emerson Assignee: Ryan Emerson -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6272) SFSB methods can still be invoked after a calling transaction has rolledback

by Ryan Emerson (JIRA)

Ryan Emerson created WFLY-6272: ---------------------------------- Summary: SFSB methods can still be invoked after a calling transaction has rolledback Key: WFLY-6272 URL: https://issues.jboss.org/browse/WFLY-6272 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 10.0.0.Final Reporter: Ryan Emerson Assignee: Ryan Emerson -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6270) Update to lucene-5.4 to align with camel-2.17

by Emmanuel Bernard (JIRA)

[ https://issues.jboss.org/browse/WFLY-6270?page=com.atlassian.jira.plugin.... ] Emmanuel Bernard commented on WFLY-6270: ---------------------------------------- Right, with Lucene being used by Hibernate Search and by proxy Infinispan, we should prioritize the alignment with Hibernate Search moves. Lucene APIs are exposed to the user as part of a regular Hibernate Search use (at the very least until the next major version), so we cannot treat it as a private module. > Update to lucene-5.4 to align with camel-2.17 > --------------------------------------------- > > Key: WFLY-6270 > URL: https://issues.jboss.org/browse/WFLY-6270 > Project: WildFly > Issue Type: Feature Request > Reporter: Thomas Diesler > Assignee: Sanne Grinovero > > Camel currently uses lucene-5.4.1 > https://github.com/apache/camel/blob/master/parent/pom.xml#L366 > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1061 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-465) Cannot find KieModule with LATEST

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-465?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-465: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1304051|https://bugzilla.redhat.com/show_bug.cgi?id=1304051] from NEW to MODIFIED > Cannot find KieModule with LATEST > --------------------------------- > > Key: DROOLS-465 > URL: https://issues.jboss.org/browse/DROOLS-465 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Beta1 > Reporter: Takami Hirata > Assignee: Mario Fusco > Fix For: 6.4.0.Beta2 > > Attachments: reproducer.zip > > > I install a kmodule into local repository with command {{mvn clean install}}. > Loading this kmodule with 'LATEST' works on the day, but will fail on next day. > Maven will find update on next day because of default updatePolicy 'daily', then maven check local repository ({{org.kie.scanner.Aether}} treats as a remote repository) but local artifact cache does not have 'maven-metadata.xml' which remote artifact should have, so finding update fails and {{org.sonatype.aether.connector.file.FileRepositoryWorker}} removes {{maven-metadata-local.xml}} for cleanup. > {{org.kie.scanner.Aether}} adds local repository to remote repositories, but this may be incorrect usage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6270) Update to lucene-5.4 to align with camel-2.17

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-6270?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-6270: --------------------------------------- Why do we need to align with Camel? We can upgrade Hibernate Search to 5.4 in this specific case, but we can't generally start tracking versions from Camel. BTW I'd rather upgrade to Lucene 5.5 as next step; in fact we already did that in master of Hibernate Search and we didn't leave a gap in our minor versions for a Lucene 5.4 based release. > Update to lucene-5.4 to align with camel-2.17 > --------------------------------------------- > > Key: WFLY-6270 > URL: https://issues.jboss.org/browse/WFLY-6270 > Project: WildFly > Issue Type: Feature Request > Reporter: Thomas Diesler > Assignee: Sanne Grinovero > > Camel currently uses lucene-5.4.1 > https://github.com/apache/camel/blob/master/parent/pom.xml#L366 > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1061 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4608) Omit no-op transaction if lifecycle method is missing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4608?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4608: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1036040|https://bugzilla.redhat.com/show_bug.cgi?id=1036040] from ASSIGNED to CLOSED > Omit no-op transaction if lifecycle method is missing > ----------------------------------------------------- > > Key: WFLY-4608 > URL: https://issues.jboss.org/browse/WFLY-4608 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.CR1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 10.0.0.CR5 > > > LifecycleCMTTxInterceptor creates a no-op transaction even if there is no lifecycle method defined in the bean. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-290) Need log-rotate feature for <audit-log/> in <management/>

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-290?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-290: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1116179|https://bugzilla.redhat.com/show_bug.cgi?id=1116179] from ASSIGNED to CLOSED > Need log-rotate feature for <audit-log/> in <management/> > --------------------------------------------------------- > > Key: WFCORE-290 > URL: https://issues.jboss.org/browse/WFCORE-290 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Hisanobu Okuda > Assignee: Ivo Studensky > Fix For: 1.0.0.Beta1 > > > Need log-rotate feature (periodically and by size) for <audit-log/> in <management/>. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-637) /subsystem=logging/log-file resource cannot cope with an expression in the path

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-637?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-637: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1203101|https://bugzilla.redhat.com/show_bug.cgi?id=1203101] from ASSIGNED to CLOSED > /subsystem=logging/log-file resource cannot cope with an expression in the path > ------------------------------------------------------------------------------- > > Key: WFCORE-637 > URL: https://issues.jboss.org/browse/WFCORE-637 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Affects Versions: 1.0.0.Beta3 > Reporter: Ivo Studensky > Priority: Optional > > In log subsystem, nested expression can be used for path. > {noformat} > "path" => { > "type" => STRING, > "description" => "The filesystem path.", > "expressions-allowed" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > } > {noformat} > so if I use following log configuration : > {noformat} > <periodic-rotating-file-handler name="FILE" autoflush="true"> > <formatter> > <named-formatter name="PATTERN"/> > </formatter> > <file relative-to="jboss.server.log.dir" path="${jboss.server.name}.log"/> > <suffix value=".yyyy-MM-dd"/> > <append value="true"/> > {noformat} > server log name will be HOST_NAME.log and there is no problems to write. > However, there is no log-file resource for it. This also leads into an issue that it cannot be displayed in Admin console Log Viewer menu. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6250) JMX inefficiently handles resource adapters

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/WFLY-6250?page=com.atlassian.jira.plugin.... ] Aaron Ogburn updated WFLY-6250: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/8713 > JMX inefficiently handles resource adapters > ------------------------------------------- > > Key: WFLY-6250 > URL: https://issues.jboss.org/browse/WFLY-6250 > Project: WildFly > Issue Type: Bug > Components: JCA, JMX > Affects Versions: 10.0.0.Final > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Attachments: README.txt, xaa, xab, xac, xad > > > If you connect to JBoss over JMX when it has many rars deployed (over 500), long running high CPU is seen in the following calls: > {code} > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:188) > at org.jboss.as.jmx.model.ResourceAccessControlUtil.getResourceAccess(ResourceAccessControlUtil.java:85) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:51) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:61) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:61) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:61) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:61) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:61) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:61) > at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:43) > {code} > It's evident that it is iterating over each deployment (each resource adapter counting as a deployment), but for each deployment, it is also iterating over all resource adapter's and their config properties. So it would iterate over all 500+ resource adapters once for each deployment, so it iterates over all 500 adapters at least 500 times. Is there anyway we could avoid that n^2 iteration for deployed rars? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

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