December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5792) Default TCP backlog is too small

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-5792: ------------------------------------ Summary: Default TCP backlog is too small Key: WFLY-5792 URL: https://issues.jboss.org/browse/WFLY-5792 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5791) Default TCP backlog is too small

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-5791: ------------------------------------ Summary: Default TCP backlog is too small Key: WFLY-5791 URL: https://issues.jboss.org/browse/WFLY-5791 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1187) Embedded server start / stop / start with new --jboss-home continues to refer to previous server.log

by Ken Wills (JIRA)

Ken Wills created WFCORE-1187: --------------------------------- Summary: Embedded server start / stop / start with new --jboss-home continues to refer to previous server.log Key: WFCORE-1187 URL: https://issues.jboss.org/browse/WFCORE-1187 Project: WildFly Core Issue Type: Bug Reporter: Ken Wills Assignee: Ken Wills - start-embedded-server --jboss-home=/foo/bar1 - stop-embedded-server - start-embedded-server --jboss-home=/foo/bar2 -- server.log in /foo/bar1/standalone/logs/server.log is still written to. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1186) Isolate embedded server / host-controller module loading when starting new server(s)

by Ken Wills (JIRA)

Ken Wills created WFCORE-1186: --------------------------------- Summary: Isolate embedded server / host-controller module loading when starting new server(s) Key: WFCORE-1186 URL: https://issues.jboss.org/browse/WFCORE-1186 Project: WildFly Core Issue Type: Enhancement Reporter: Ken Wills Assignee: Ken Wills Currently starting an embedded server obtains a single ModuleLoader instance, which is then statically initialized with specific pointers to certain filesystem directories & paths (server.log and module.path etc). It would be ideal if each embedded instance could use it's own ModuleLoader, as it would allow all of these properties to be managed separately, and potentially multiple servers to be started at the same time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-435) Add MBean server support to Management console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-435?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-435: ------------------------------------ Component/s: Domain Management > Add MBean server support to Management console > ---------------------------------------------- > > Key: WFCORE-435 > URL: https://issues.jboss.org/browse/WFCORE-435 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Sebastian Łaskawiec > Assignee: Jason Greene > Priority: Minor > > In JBoss 5.x server there was a web based tool for managing JMX Beans. Currently this functionality is supported via bundled JConsole. It would be convenient to have such functionality based on HTTP Web Management panel. > As discussed on email thread (subject: "JMX Console over Web Admin Console") it should be placed a part of standard management resource tree or in context of HTTP management interface. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1078) Always roll over configuration file history on reload similar to on a restart

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1078?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1078: ------------------------------------- Component/s: Domain Management > Always roll over configuration file history on reload similar to on a restart > ----------------------------------------------------------------------------- > > Key: WFCORE-1078 > URL: https://issues.jboss.org/browse/WFCORE-1078 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 2.0.0.CR8 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha1 > > > When working on WFCORE-1052 I noticed some discrepancies in PersistanceResourceTestCase -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1146) Research behavior of fork with ProcessBuilder on modern JVMs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1146?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1146: ------------------------------------- Component/s: Domain Management > Research behavior of fork with ProcessBuilder on modern JVMs > ------------------------------------------------------------ > > Key: WFCORE-1146 > URL: https://issues.jboss.org/browse/WFCORE-1146 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: David Lloyd > > Right now our Process Controller exists for two primary reasons: > # fork() misbehaves for large processes on some OSes, causing leaks or crashes > # if the HC crashes, the PC can respawn it > We have never (afaik) seen #2 happen. We need to verify whether #1 is still true on modern JVMs on the following operating systems: > * Linux > * Solaris > * IBM OSes > * Windows > * BSDs > * Mac OS X > Test by creating processes with large heap and lots of concurrent file descriptor activity while forking to see what happens. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5750) Hibernate 5 hibernate-java8 jar is missing

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-5750?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-5750. ------------------------------ Resolution: Done > Hibernate 5 hibernate-java8 jar is missing > ------------------------------------------ > > Key: WFLY-5750 > URL: https://issues.jboss.org/browse/WFLY-5750 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.CR4 > Reporter: Juergen Zimmermann > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > In $JBOSS_HOME/modules/system/layers/base/org/hibernate/main are these JARs: > * hibernate-core > * hibernate-entitymanager > * hibernate-envers > However, org.hibernate:hibernate-java8 is missing. This JAR enables the use of Instant, LocalDate, LocalDateTime LocalTime, ... being part of the new time API in JDK 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5790) Use a separate interface for JGroups sockets

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5790?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-5790: -------------------------------------- Assignee: Paul Ferraro (was: Brian Stansberry) [~jason.greene][~pferraro] My experimental PR passed CI and I know you wanted to get this done, Jason, so I created a JIRA and changed my PRs commit message to reflect it. I'm assigning this over to you, though, Paul, as your team would know better if there are any gotchas here, particularly any testsuite tweaks that are necessary to ensure the test servers are using the expected addresses. My PR has the basic change to the xslt that's used to change the default addresses to IPv6. > Use a separate interface for JGroups sockets > -------------------------------------------- > > Key: WFLY-5790 > URL: https://issues.jboss.org/browse/WFLY-5790 > Project: WildFly > Issue Type: Enhancement > Components: Clustering, Domain Management > Reporter: Brian Stansberry > Assignee: Paul Ferraro > Fix For: 10.0.0.Final > > > Our standard configs currently use the "public" interface for the JGroups sockets. However, best practice is to put intra-cluster traffic on a separate network from the network handling end user requests, both for possible performance reasons and to reduce the risk of exposing clustering to unwanted, possibly malevolent, traffic. > Since that is best practice, our standard configs should reflect that. So we'll create a new 'private' interface to go along with the existing 'public', 'management', and 'unsecure' ones, and use it for the JGroups sockets. > The default address will be ${jboss.bind.address.private:127.0.0.1} consistent with the others. > Users using our standard configs who wish to use -b startup switches to control the network address will need to add -bprivate=<theaddress> to the startup command. Simply using -b=<theaddress> will no longer affect the JGroups traffic if our standard configs are used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5790) Use a separate interface for JGroups sockets

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-5790: -------------------------------------- Summary: Use a separate interface for JGroups sockets Key: WFLY-5790 URL: https://issues.jboss.org/browse/WFLY-5790 Project: WildFly Issue Type: Enhancement Components: Clustering, Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 10.0.0.Final Our standard configs currently use the "public" interface for the JGroups sockets. However, best practice is to put intra-cluster traffic on a separate network from the network handling end user requests, both for possible performance reasons and to reduce the risk of exposing clustering to unwanted, possibly malevolent, traffic. Since that is best practice, our standard configs should reflect that. So we'll create a new 'private' interface to go along with the existing 'public', 'management', and 'unsecure' ones, and use it for the JGroups sockets. The default address will be ${jboss.bind.address.private:127.0.0.1} consistent with the others. Users using our standard configs who wish to use -b startup switches to control the network address will need to add -bprivate=<theaddress> to the startup command. Simply using -b=<theaddress> will no longer affect the JGroups traffic if our standard configs are used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 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 December 2015