April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1260) Allow System Property to override default First In First Out (FIFO) pooling behavior

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBJCA-1260: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1208206, https://bugzilla.redhat.com/show_bug.cgi?id=1210571 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1208206) > Allow System Property to override default First In First Out (FIFO) pooling behavior > ------------------------------------------------------------------------------------ > > Key: JBJCA-1260 > URL: https://issues.jboss.org/browse/JBJCA-1260 > Project: IronJacamar > Issue Type: Support Patch > Components: Core > Affects Versions: 1.0.32.Final > Reporter: Johnathon Lee > Assignee: Jesper Pedersen > > Introduce a system property "filo-pool-behavior" to override (revert) the changes introduced by JBJCA-1005. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-77) ConcurrentModificationException in deploy-artifact

by Daniele Gaffuri (JIRA)

Daniele Gaffuri created JBASMP-77: ------------------------------------- Summary: ConcurrentModificationException in deploy-artifact Key: JBASMP-77 URL: https://issues.jboss.org/browse/JBASMP-77 Project: JBoss AS Maven Plugins Issue Type: Bug Components: deploy Affects Versions: 7.7.Final Reporter: Daniele Gaffuri Assignee: James Perkins In the same situation of JBASMP-57 deploy-artifact throws the following exception: {code} [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.7.SCE:deploy-artifact (deploy) on project sideup-integration: Could not execute goal deploy-artifact on null. Reason: null: ConcurrentModificationException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.7.SCE:deploy-artifact (deploy) on project sideup-integration: Could not execute goal deploy-artifact on null. Reason: null at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal deploy-artifact on null. Reason: null at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:159) at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:112) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:394) at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405) at java.util.AbstractCollection.addAll(AbstractCollection.java:341) at org.jboss.as.plugin.deployment.DeployArtifact.validate(DeployArtifact.java:84) at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:136) ... 22 more {code} This is probably due to changes in related commit [37bc2c1], causing both deploy and undeploy validate methods to add the set of dependencies to itself: {code} final Set<Artifact> dependencies = project.getDependencyArtifacts(); // Allows provided dependencies to be seen dependencies.addAll(project.getDependencyArtifacts()); {code} {code} final Set<Artifact> dependencies = project.getDependencyArtifacts(); dependencies.addAll(this.project.getDependencyArtifacts()); {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1923) Discovery: add option to run each discovery requests in a separate thread

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1923?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1923. ---------------------------- Resolution: Done > Discovery: add option to run each discovery requests in a separate thread > ------------------------------------------------------------------------- > > Key: JGRP-1923 > URL: https://issues.jboss.org/browse/JGRP-1923 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.4 > > > Currently, {{async_discovery}} runs discovery in a separate thread. However, if we try to contact 10 servers and almost all are down and {{sock_conn_timeout}} is high, then discovery might not return any live servers and the caller becomes coordinator. > Add attribute {{async_discovery_use_separate_thread_per_request}} to enable this. This is orthogonal to {{async_discovery}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-312) response.setBufferSize() has no effect when using the response writer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-312?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-312: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1210365|https://bugzilla.redhat.com/show_bug.cgi?id=1210365] from NEW to ASSIGNED > response.setBufferSize() has no effect when using the response writer > --------------------------------------------------------------------- > > Key: JBWEB-312 > URL: https://issues.jboss.org/browse/JBWEB-312 > Project: JBoss Web > Issue Type: Bug > Affects Versions: JBossWeb-7.5.0.GA > Reporter: Aaron Ogburn > Assignee: Aaron Ogburn > > This is the same issue as https://issues.apache.org/bugzilla/show_bug.cgi?id=55842 > When using the response writer, we end up just flushing the buffer in org.apache.catalina.connector.OutputBuffer.realWriteChars instead of trying to grow the buffer. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1923) Discovery: add option to run each discovery requests in a separate thread

by Bela Ban (JIRA)

Bela Ban created JGRP-1923: ------------------------------ Summary: Discovery: add option to run each discovery requests in a separate thread Key: JGRP-1923 URL: https://issues.jboss.org/browse/JGRP-1923 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.6.4 Currently, {{async_discovery}} runs discovery in a separate thread. However, if we try to contact 10 servers and almost all are down and {{sock_conn_timeout}} is high, then discovery might not return any live servers and the caller becomes coordinator. Add attribute {{async_discovery_use_separate_thread_per_request}} to enable this. This is orthogonal to {{async_discovery}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski commented on WFLY-4496: ------------------------------------------ Upgrade due to: https://issues.jboss.org/browse/WFCORE-608 which should be fixed in AESH not core. > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-4496: ------------------------------------- Issue Type: Component Upgrade (was: Feature Request) > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-4496: ------------------------------------- Priority: Minor (was: Major) > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-4496: ---------------------------------------- Summary: Upgrade AESH from 0.33.14 to 0.33.15 Key: WFLY-4496 URL: https://issues.jboss.org/browse/WFLY-4496 Project: WildFly Issue Type: Feature Request Reporter: Bartosz Baranowski Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4496: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1210556 > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Feature Request > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015