[JBoss JIRA] (REMJMX-157) Resource Leak in RemotingConnector
by Stefan Mocken (JIRA)
[ https://issues.jboss.org/browse/REMJMX-157?page=com.atlassian.jira.plugin... ]
Stefan Mocken commented on REMJMX-157:
--------------------------------------
copied from https://github.com/jbossas/remoting-jmx/issues/26
> Resource Leak in RemotingConnector
> ----------------------------------
>
> Key: REMJMX-157
> URL: https://issues.jboss.org/browse/REMJMX-157
> Project: Remoting JMX
> Issue Type: Bug
> Reporter: Stefan Mocken
> Assignee: Darran Lofthouse
>
> If opening a Connection fails for any reason, the Endpoint is not closed.
> So in a corrosponding thread dump for every failed connection there will be the following dead entries:
> ############################################################
> "Remoting "endpoint" Accept" #215802 daemon prio=5 os_prio=0 tid=0x00007f48dc21a000 nid=0x4e8e runnable [0x00007f48894d6000]
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
> - locked <0x00000000f01d1d10> (a sun.nio.ch.Util$3)
> - locked <0x00000000f01d1d00> (a java.util.Collections$UnmodifiableSet)
> - locked <0x00000000f01d1be8> (a sun.nio.ch.EPollSelectorImpl)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:509)
> "Remoting "endpoint" I/O-1" #215801 daemon prio=5 os_prio=0 tid=0x00007f48dc08c000 nid=0x4e8d runnable [0x00007f4885ea0000]
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
> - locked <0x00000000f01cc188> (a sun.nio.ch.Util$3)
> - locked <0x00000000f01cc178> (a java.util.Collections$UnmodifiableSet)
> - locked <0x00000000f01cc060> (a sun.nio.ch.EPollSelectorImpl)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:509)
> ############################################################
> NitinRanjan suggested to patch
> the close() method of RemotingConnector.java which is responsible for closing the endpoint threads and others.
> In case of connection not established the state is UNUSED which makes the close method to return without closing the endpoint thread.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (REMJMX-157) Resource Leak in RemotingConnector
by Stefan Mocken (JIRA)
Stefan Mocken created REMJMX-157:
------------------------------------
Summary: Resource Leak in RemotingConnector
Key: REMJMX-157
URL: https://issues.jboss.org/browse/REMJMX-157
Project: Remoting JMX
Issue Type: Bug
Reporter: Stefan Mocken
Assignee: Darran Lofthouse
If opening a Connection fails for any reason, the Endpoint is not closed.
So in a corrosponding thread dump for every failed connection there will be the following dead entries:
############################################################
"Remoting "endpoint" Accept" #215802 daemon prio=5 os_prio=0 tid=0x00007f48dc21a000 nid=0x4e8e runnable [0x00007f48894d6000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- locked <0x00000000f01d1d10> (a sun.nio.ch.Util$3)
- locked <0x00000000f01d1d00> (a java.util.Collections$UnmodifiableSet)
- locked <0x00000000f01d1be8> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:509)
"Remoting "endpoint" I/O-1" #215801 daemon prio=5 os_prio=0 tid=0x00007f48dc08c000 nid=0x4e8d runnable [0x00007f4885ea0000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- locked <0x00000000f01cc188> (a sun.nio.ch.Util$3)
- locked <0x00000000f01cc178> (a java.util.Collections$UnmodifiableSet)
- locked <0x00000000f01cc060> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:509)
############################################################
NitinRanjan suggested to patch
the close() method of RemotingConnector.java which is responsible for closing the endpoint threads and others.
In case of connection not established the state is UNUSED which makes the close method to return without closing the endpoint thread.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9851) Remove secuity dependancy on clustering subsystem / infinispan
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFLY-9851:
---------------------------------
Summary: Remove secuity dependancy on clustering subsystem / infinispan
Key: WFLY-9851
URL: https://issues.jboss.org/browse/WFLY-9851
Project: WildFly
Issue Type: Task
Components: Clustering, Domain Management, Security
Reporter: Tomaz Cerar
Assignee: Paul Ferraro
Priority: Critical
Currently security subsystem depends on clustering subsystem modules which bring in a big transitive dependency tree (that cannot be broken).
Dependency is there only to establish capability requirements.
Please change code to use string constants instead of enums from clustering subsystem to break down the dependency tree. Whole reason for capabilities was to not have tightly coupled subsystems.
current sip from security subsystem dependency tree
{noformat}
[INFO] +- org.wildfly:wildfly-clustering-infinispan-spi:jar:12.0.0.Beta2-SNAPSHOT:compile
[INFO] | +- org.wildfly:wildfly-clustering-common:jar:12.0.0.Beta2-SNAPSHOT:compile
[INFO] | | +- org.wildfly:wildfly-clustering-service:jar:12.0.0.Beta2-SNAPSHOT:compile
[INFO] | | \- org.wildfly:wildfly-naming:jar:12.0.0.Beta2-SNAPSHOT:compile
[INFO] | | +- org.wildfly:wildfly-naming-client:jar:1.0.7.Final:compile
[INFO] | | | +- org.wildfly.client:wildfly-client-config:jar:1.0.0.Final:compile
[INFO] | | | \- org.jboss.marshalling:jboss-marshalling-river:jar:2.0.2.Final:compile
[INFO] | | \- org.wildfly.wildfly-http-client:wildfly-http-naming-client:jar:1.0.9.Final:compile
[INFO] | | +- org.wildfly.wildfly-http-client:wildfly-http-client-common:jar:1.0.9.Final:compile
[INFO] | | +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.1.Final:compile
[INFO] | | \- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.1.1.Final:compile
[INFO] | +- org.wildfly:wildfly-clustering-marshalling-spi:jar:12.0.0.Beta2-SNAPSHOT:compile
[INFO] | | \- org.wildfly:wildfly-clustering-marshalling-api:jar:12.0.0.Beta2-SNAPSHOT:compile
[INFO] | +- org.infinispan:infinispan-core:jar:9.1.6.Final:compile
[INFO] | | \- org.infinispan:infinispan-commons:jar:9.1.6.Final:compile
[INFO] | \- com.github.ben-manes.caffeine:caffeine:jar:2.6.1:compile
{noformat}
we even bring in inifinspan, as otherwise it does not compile.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3617) Unable to enable disabled deployment through the CLI in domain mode
by Martin Stefanko (JIRA)
Martin Stefanko created WFCORE-3617:
---------------------------------------
Summary: Unable to enable disabled deployment through the CLI in domain mode
Key: WFCORE-3617
URL: https://issues.jboss.org/browse/WFCORE-3617
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 4.0.0.Beta1
Reporter: Martin Stefanko
Assignee: Martin Stefanko
The CLI detects duplicate resource when trying to enable disabled deployment for a server-group in domain mode:
{code}
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [
(\"server-group\" => \"main-server-group\"),
(\"deployment\" => \"app.war\")
]"}}
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9850) wsprovide fails on HPUX machines
by Marek Kopecký (JIRA)
Marek Kopecký created WFLY-9850:
-----------------------------------
Summary: wsprovide fails on HPUX machines
Key: WFLY-9850
URL: https://issues.jboss.org/browse/WFLY-9850
Project: WildFly
Issue Type: Bug
Components: Scripts, Web Services
Affects Versions: 12.0.0.Beta1
Reporter: Marek Kopecký
Assignee: R Searls
Priority: Blocker
wsprovide.sh script fails on HPUX machines
This issue is caused by WFLY-9538
*Actual results:*
{noformat}
hudson@eap-perf-hpux-02.mw.lab.eng.bos.redhat.com:/mnt/hudson_workspace/workspace/mkopecky/wildfly/bin>./wsprovide.sh
./wsprovide.sh[86]: JAVA_OPTS=${JAVA_OPTS/-secmgr/}: bad substitution
hudson@eap-perf-hpux-02.mw.lab.eng.bos.redhat.com:/mnt/hudson_workspace/workspace/mkopecky/wildfly/bin>
{noformat}
*Expected results:*
{noformat}
[mkopecky@dhcp-10-40-5-4 bin]$ ./wsprovide.sh
Error: endpoint implementation was not specified!
WSProvideTask generates portable JAX-WS artifacts for an endpoint implementation.
usage: wsprovide.sh [options] <endpoint class name>
options:
-h, --help Show this help message
-k, --keep Keep/Generate Java source
-w, --wsdl Enable WSDL file generation
-a, --address=<address> The generated port soap:address in wsdl
-c, --classpath=<path> The classpath that contains the endpoint
-o, --output=<directory> The directory to put generated artifacts
-r, --resource=<directory> The directory to put resource artifacts
-s, --source=<directory> The directory to put Java source
-e, --extension Enable SOAP 1.2 binding extension
-q, --quiet Be somewhat more quiet
-t, --show-traces Show full exception stack traces
-v, --verbose Show full exception stack traces
-l, --load-provider Load the provider and exit (debug utility)
[mkopecky@dhcp-10-40-5-4 bin]$
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3566) Different results of disabling commands already disabled deployment
by Martin Stefanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3566?page=com.atlassian.jira.plugi... ]
Martin Stefanko reassigned WFCORE-3566:
---------------------------------------
Assignee: Martin Stefanko (was: Jean-Francois Denise)
> Different results of disabling commands already disabled deployment
> -------------------------------------------------------------------
>
> Key: WFCORE-3566
> URL: https://issues.jboss.org/browse/WFCORE-3566
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Vratislav Marek
> Assignee: Martin Stefanko
>
> *Different command result of disabling already disabled deployment in standalone and domain mode*
> * In standalone return
> {noformat}
> WFLYCTL0155: 'steps' may not be null
> {noformat}
> * In domain return nothing, no warning or error
> {noformat}
> [standalone@localhost:9990 /] deployment info
> NAME RUNTIME-NAME PERSISTENT ENABLED STATUS
> cli-test-another-deploy.war cli-test-another-deploy.war true true OK
> cli-test-app1-deploy.war cli-test-app1-deploy.war true false STOPPED
> cli-test-app2-deploy.war cli-test-app2-deploy.war true true OK
> [standalone@localhost:9990 /] deployment disable cli-test-app1-deploy-all.war
> WFLYCTL0155: 'steps' may not be null
> [standalone@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] deployment info --server-groups=main-server-group
> NAME RUNTIME-NAME STATE
> cli-test-another-deploy-all.war cli-test-another-deploy-all.war enabled
> cli-test-app1-deploy-all.war cli-test-app1-deploy-all.war added
> cli-test-app2-deploy-all.war cli-test-app2-deploy-all.war not added
> cli-test-app3-deploy-all.war cli-test-app3-deploy-all.war enabled
> [domain@localhost:9990 /] deployment disable --server-groups=main-server-group cli-test-app1-deploy-all.war
> [domain@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months