February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4845) Allow Remote Debug Connections on Java 9+ With StandaloneCommandBuilder

by Josh Fisher (Jira)

[ https://issues.redhat.com/browse/WFCORE-4845?page=com.atlassian.jira.plug... ] Josh Fisher updated WFCORE-4845: -------------------------------- Description: When using StandaloneCommandBuilder#setDebug method to set the debug VM argument it will use this format: -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=$debugPort On Java 9+, this will only accept connections from the localhost, while in Java 8 this will accept connections from any host. It is possible to support remote connections on Java 9+ by configuring the argument in the Java options list instead of using setDebug as a workaround. While debug connections from remote hosts are not especially common, there are some use cases where it may be desired. For consistency between Java versions, we should consider using the wildcard "*" host so the debug argument format is: -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=*:$debugPort I believe one way this could be achieved is by modifying the DEBUG_FORMAT to: DEBUG_FORMAT = "-agentlib:jdwp=transport=dt_socket,server=y,suspend=%s,address=%s" then in setDebug check the environment VM and format the address accordingly. {code:java} public StandaloneCommandBuilder setDebug(boolean suspend, int port) { final String address; if (environment.getJvm().isModular()){ address = "*:" + port; } else { address = String.valueOf(port); } debugArg = String.format(DEBUG_FORMAT, (suspend ? "y" : "n"), address); return this; } {code} was: When using StandaloneCommandBuilder#setDebug method to set the debug VM argument it will use this format: -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=$debugPort On Java 9+, this will only accept connections from the localhost, while in Java 8 this will accept connections from any host. It is possible to support remote connections on Java 9+ by configuring the argument in the Java options list instead of using setDebug as a workaround. While debug connections from remote hosts are not especially common, there are some use cases where it may be desired. For consistency between Java versions, we should consider using the wildcard "*" host so the debug argument format is: -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=*:$debugPort I believe one way this could be achieved is by modifying the DEBUG_FORMAT to: DEBUG_FORMAT = "-agentlib:jdwp=transport=dt_socket,server=y,suspend=%s,address=%s" then in setDebug can check the environment VM and format the address accordingly. {code:java} public StandaloneCommandBuilder setDebug(boolean suspend, int port) { final String address; if (environment.getJvm().isModular()){ address = "*:" + port; } else { address = String.valueOf(port); } debugArg = String.format(DEBUG_FORMAT, (suspend ? "y" : "n"), address); return this; } {code} > Allow Remote Debug Connections on Java 9+ With StandaloneCommandBuilder > ----------------------------------------------------------------------- > > Key: WFCORE-4845 > URL: https://issues.redhat.com/browse/WFCORE-4845 > Project: WildFly Core > Issue Type: Enhancement > Components: Launcher > Reporter: Josh Fisher > Assignee: Jeff Mesnil > Priority: Minor > > When using StandaloneCommandBuilder#setDebug method to set the debug VM argument it will use this format: > -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=$debugPort > On Java 9+, this will only accept connections from the localhost, while in Java 8 this will accept connections from any host. It is possible to support remote connections on Java 9+ by configuring the argument in the Java options list instead of using setDebug as a workaround. > While debug connections from remote hosts are not especially common, there are some use cases where it may be desired. For consistency between Java versions, we should consider using the wildcard "*" host so the debug argument format is: > -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=*:$debugPort > > I believe one way this could be achieved is by modifying the DEBUG_FORMAT to: > DEBUG_FORMAT = "-agentlib:jdwp=transport=dt_socket,server=y,suspend=%s,address=%s" > then in setDebug check the environment VM and format the address accordingly. > {code:java} > public StandaloneCommandBuilder setDebug(boolean suspend, int port) { > final String address; > if (environment.getJvm().isModular()){ > address = "*:" + port; > } else { > address = String.valueOf(port); > } > debugArg = String.format(DEBUG_FORMAT, (suspend ? "y" : "n"), address); > return this; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4845) Allow Remote Debug Connections on Java 9+ With StandaloneCommandBuilder

by Josh Fisher (Jira)

[ https://issues.redhat.com/browse/WFCORE-4845?page=com.atlassian.jira.plug... ] Josh Fisher commented on WFCORE-4845: ------------------------------------- As a side note, it would also be possible to offer a setDebug(boolean, String) method, where the String parameter is the address argument value, to allow full control over the address argument; however, based on discussion with [~jamezp] we found it would be unlikely for it to be used and would like to avoid adding another method. With that in mind, we would only be focusing on consistency between Java 8 and Java 9+ at this time. I just wanted to document this idea in case there is interest in the future. > Allow Remote Debug Connections on Java 9+ With StandaloneCommandBuilder > ----------------------------------------------------------------------- > > Key: WFCORE-4845 > URL: https://issues.redhat.com/browse/WFCORE-4845 > Project: WildFly Core > Issue Type: Enhancement > Components: Launcher > Reporter: Josh Fisher > Assignee: Jeff Mesnil > Priority: Minor > > When using StandaloneCommandBuilder#setDebug method to set the debug VM argument it will use this format: > -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=$debugPort > On Java 9+, this will only accept connections from the localhost, while in Java 8 this will accept connections from any host. It is possible to support remote connections on Java 9+ by configuring the argument in the Java options list instead of using setDebug as a workaround. > While debug connections from remote hosts are not especially common, there are some use cases where it may be desired. For consistency between Java versions, we should consider using the wildcard "*" host so the debug argument format is: > -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=*:$debugPort > > I believe one way this could be achieved is by modifying the DEBUG_FORMAT to: > DEBUG_FORMAT = "-agentlib:jdwp=transport=dt_socket,server=y,suspend=%s,address=%s" > then in setDebug can check the environment VM and format the address accordingly. > {code:java} > public StandaloneCommandBuilder setDebug(boolean suspend, int port) { > final String address; > if (environment.getJvm().isModular()){ > address = "*:" + port; > } else { > address = String.valueOf(port); > } > debugArg = String.format(DEBUG_FORMAT, (suspend ? "y" : "n"), address); > return this; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4845) Allow Remote Debug Connections on Java 9+ With StandaloneCommandBuilder

by Josh Fisher (Jira)

Josh Fisher created WFCORE-4845: ----------------------------------- Summary: Allow Remote Debug Connections on Java 9+ With StandaloneCommandBuilder Key: WFCORE-4845 URL: https://issues.redhat.com/browse/WFCORE-4845 Project: WildFly Core Issue Type: Enhancement Components: Launcher Reporter: Josh Fisher Assignee: Jeff Mesnil When using StandaloneCommandBuilder#setDebug method to set the debug VM argument it will use this format: -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=$debugPort On Java 9+, this will only accept connections from the localhost, while in Java 8 this will accept connections from any host. It is possible to support remote connections on Java 9+ by configuring the argument in the Java options list instead of using setDebug as a workaround. While debug connections from remote hosts are not especially common, there are some use cases where it may be desired. For consistency between Java versions, we should consider using the wildcard "*" host so the debug argument format is: -agentlib:jdwp=transport=dt_socket,server=y,suspend=$suspend,address=*:$debugPort I believe one way this could be achieved is by modifying the DEBUG_FORMAT to: DEBUG_FORMAT = "-agentlib:jdwp=transport=dt_socket,server=y,suspend=%s,address=%s" then in setDebug can check the environment VM and format the address accordingly. {code:java} public StandaloneCommandBuilder setDebug(boolean suspend, int port) { final String address; if (environment.getJvm().isModular()){ address = "*:" + port; } else { address = String.valueOf(port); } debugArg = String.format(DEBUG_FORMAT, (suspend ? "y" : "n"), address); return this; } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12797) WFLY quickstart 'jts' contains errors after import into Code Ready in the 'jboss-ejb3.xml' file

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-12797?page=com.atlassian.jira.plugi... ] Eduardo Martins updated WFLY-12797: ----------------------------------- Git Pull Request: https://github.com/wildfly/quickstart/pull/376 (was: https://github.com/wildfly/quickstart/pull/365, https://github.com/wildfly/quickstart/pull/376) > WFLY quickstart 'jts' contains errors after import into Code Ready in the 'jboss-ejb3.xml' file > ----------------------------------------------------------------------------------------------- > > Key: WFLY-12797 > URL: https://issues.redhat.com/browse/WFLY-12797 > Project: WildFly > Issue Type: Bug > Components: Quickstarts, Transactions > Affects Versions: 18.0.1.Final > Environment: OS X 10.14.5 > Reporter: Ondrej Chaloupka > Assignee: Sudeshna Sur > Priority: Major > Fix For: 19.0.0.Beta2 > > > h1. *The "jboss-ejb3.xml" file in the EAP "jts" quickstart contains the following 2 errors:* > * cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:ejb-name'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":ejb-name}' is expected. > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > h2. Red Hat CodeReady Studio version: 12.12.0.GA -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12445) Document some quickstarts to use new openshift templates

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-12445?page=com.atlassian.jira.plugi... ] Eduardo Martins updated WFLY-12445: ----------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta3) > Document some quickstarts to use new openshift templates > -------------------------------------------------------- > > Key: WFLY-12445 > URL: https://issues.redhat.com/browse/WFLY-12445 > Project: WildFly > Issue Type: Enhancement > Components: Documentation, Quickstarts > Reporter: Jean Francois Denise > Assignee: Eduardo Martins > Priority: Major > Fix For: 19.0.0.Beta2 > > Attachments: README_WITHOUT_H2.html, README_WITH_H2.html > > > A subset of openshift quickstarts can take benefit of chained build and usage of galleon offered by new template. This should be documented in README. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5059) Verifier: GDST columns empty enumeration should be ignored

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-5059: ------------------------------------ Summary: Verifier: GDST columns empty enumeration should be ignored Key: DROOLS-5059 URL: https://issues.redhat.com/browse/DROOLS-5059 Project: Drools Issue Type: Bug Components: verifier Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1933) Look into how to prevent GitHub Pages from ignoring Javadoc files in _private directories

by Farah Juma (Jira)

Farah Juma created ELY-1933: ------------------------------- Summary: Look into how to prevent GitHub Pages from ignoring Javadoc files in _private directories Key: ELY-1933 URL: https://issues.redhat.com/browse/ELY-1933 Project: WildFly Elytron Issue Type: Task Reporter: Farah Juma Something we should look into is making sure that the website builds do not remove Javadoc files that are in _private directories. These files were already getting removed when being built by GitHub Pages for the existing Javadoc website so this behaviour isn’t specific to the new website but we should try to fix it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13086) Upgrade gson from 2.8.2 to gson 2.8.5

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFLY-13086?page=com.atlassian.jira.plugi... ] Bartosz Spyrko updated WFLY-13086: ---------------------------------- Labels: downstream_dependency (was: ) > Upgrade gson from 2.8.2 to gson 2.8.5 > ------------------------------------- > > Key: WFLY-13086 > URL: https://issues.redhat.com/browse/WFLY-13086 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, MP OpenTracing > Reporter: Bartosz Spyrko > Assignee: Emmanuel Hugonnet > Priority: Major > Labels: downstream_dependency > > Downstream dependency to align with Runtimes versions -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13087) Upgrade reactive-streams from 1.0.2 to 1.0.3

by Bartosz Spyrko (Jira)

Bartosz Spyrko created WFLY-13087: ------------------------------------- Summary: Upgrade reactive-streams from 1.0.2 to 1.0.3 Key: WFLY-13087 URL: https://issues.redhat.com/browse/WFLY-13087 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Bartosz Spyrko Assignee: Brian Stansberry Downstream dependency to align with Runtimes versions -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13087) Upgrade reactive-streams from 1.0.2 to 1.0.3

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFLY-13087?page=com.atlassian.jira.plugi... ] Bartosz Spyrko updated WFLY-13087: ---------------------------------- Labels: downstream_dependency (was: ) > Upgrade reactive-streams from 1.0.2 to 1.0.3 > -------------------------------------------- > > Key: WFLY-13087 > URL: https://issues.redhat.com/browse/WFLY-13087 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Bartosz Spyrko > Assignee: Brian Stansberry > Priority: Major > Labels: downstream_dependency > > Downstream dependency to align with Runtimes versions -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 2020