April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2925) Separate heap settings in standalone.conf and domain.conf from rest of JAVA_OPTS

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2925?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-2925: ----------------------------------- Assignee: James Perkins (was: Tomaz Cerar) > Separate heap settings in standalone.conf and domain.conf from rest of JAVA_OPTS > -------------------------------------------------------------------------------- > > Key: WFCORE-2925 > URL: https://issues.jboss.org/browse/WFCORE-2925 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Reporter: Brian Stansberry > Assignee: James Perkins > > Let's do this: > {code} > if [ "x$JBOSS_JAVA_SIZING" = "x" ]; then > JBOSS_JAVA_SIZING="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m" > fi > if [ "x$JAVA_OPTS" = "x" ]; then > JAVA_OPTS="$JBOSS_JAVA_SIZING -Djava.net.preferIPv4Stack=true" > JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" > else > echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS" > fi > {code} > That will allow users to easily control memory sizing by setting that specific env var externally while still relying on our defaults for all the other fussy stuff in JAVA_OPTS. > The JBOSS_JAVA_SIZING name was 20 secs of thought on my part. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7618) Fix code to not use default platform dependant encoding

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7618?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-7618: --------------------------------- Assignee: (was: Tomaz Cerar) > Fix code to not use default platform dependant encoding > ------------------------------------------------------- > > Key: WFLY-7618 > URL: https://issues.jboss.org/browse/WFLY-7618 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > > WFLY codebase depends in some cases on system default encoding. This should be fixed to use de facto standard UTF8. > This JIRA is followup of WFCORE-1510 in the main codebase. Main concern (proven by history too) is Windows. > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7366) Remove PicketLink

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7366?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-7366: --------------------------------- Assignee: (was: Tomaz Cerar) > Remove PicketLink > ----------------- > > Key: WFLY-7366 > URL: https://issues.jboss.org/browse/WFLY-7366 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Tomaz Cerar > > Subsystem should be removed in same way we did it with all legacy subsystems like web, messaging, cmp and others. > This way it would still be possible to manage EAP6.4 hosts with EAP 7.1 domain controller that use picketlink. > PicketLink subsystem was never supported in EAP, it was added in EAP 6.3 but as unsupported feature. > in 6.4 it was also deprecated and marked for removal, as such it stayed also in 7.0. > It was never officially supported in any of EAP releases and it would make sense to remove it in 7.1 as KeyCloak / RH SSO took over as main project/product for single sign on -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1374) Make it build & work on JDK9

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1374?page=com.atlassian.jira.plugi... ] Tomaz Cerar resolved WFCORE-1374. --------------------------------- Fix Version/s: 4.0.0.Final Resolution: Done > Make it build & work on JDK9 > ---------------------------- > > Key: WFCORE-1374 > URL: https://issues.jboss.org/browse/WFCORE-1374 > Project: WildFly Core > Issue Type: Task > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 4.0.0.Final > > > Parent task to track all JDK9 related work in wildfly core. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1031) PS1 scripts invocation ends with "cannot be loaded because running scripts is disabled on thi s system", affect MS Windows desktop series

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1031?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-1031: ----------------------------------- Assignee: (was: Tomaz Cerar) > PS1 scripts invocation ends with "cannot be loaded because running scripts is disabled on thi s system", affect MS Windows desktop series > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1031 > URL: https://issues.jboss.org/browse/WFCORE-1031 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Rostislav Svoboda > > PS1 scripts invocation ends with "cannot be loaded because running scripts is disabled on thi s system". > This was spotted on Windows 10 but it seems it affect more MS Windows desktop series (at leas 8.x too) - based on HiChat discussion. > When I open PowerShel, enter the bin folder and run .\standalone.ps1 I get this: > {code} > .\standalone.ps1 : File E:\jboss-eap-7.0\bin\standalone.ps1 cannot be loaded because running scripts is disabled on this s system. > For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170. > At line:1 char:1 > + .\standalone.ps1 > + ~~~~~~~~~~~~~~~~ > + CategoryInfo : SecurityError: (:) [], PSSecurityException > + FullyQualifiedErrorId : UnauthorizedAccess > {code} > what "helped" is this: > Set-ExecutionPolicy RemoteSigned > but I had to run powershell as administrator because it's changing registry key ... so well, not straightforward usage of ps1 scripts ... Not everybody is able to run in admin mode. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2442) Update Kie Navigator to the new git/rest structure

by Tiago Bento (JIRA)

Tiago Bento created DROOLS-2442: ----------------------------------- Summary: Update Kie Navigator to the new git/rest structure Key: DROOLS-2442 URL: https://issues.jboss.org/browse/DROOLS-2442 Project: Drools Issue Type: Bug Components: eclipse plugin Affects Versions: 7.5.0.Final Environment: 7.7.0-SNAPSHOT Reporter: Tiago Bento Assignee: Tiago Bento Fix For: 7.7.0.Final Drools eclipse plugin contains Kie Navigator tool which uses git structure and rest calls to connect to kie-wb. According to changes made in kie-wb 7.7.0 the tooling should be updated. The rest api and the git structure changed. and the kie navigator doesn't work. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-134) Incompatible type error with @Cause and ctors with unusual exception types

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-134?page=com.atlassian.jira.plugi... ] David Lloyd updated LOGTOOL-134: -------------------------------- Workaround Description: Use the {{Signature}} annotation like this: {code:java} @Message(id = 442, value = "Unexpected Error") @Signature(String.class) EJBException unexpectedError(@Cause Throwable cause); {code} Workaround: Workaround Exists > Incompatible type error with @Cause and ctors with unusual exception types > -------------------------------------------------------------------------- > > Key: LOGTOOL-134 > URL: https://issues.jboss.org/browse/LOGTOOL-134 > Project: Log Tool > Issue Type: Bug > Affects Versions: 2.1.0.Final > Reporter: David Lloyd > Priority: Minor > > Incorrect generated code can be generated if an exception constructor's "cause" parameter is a subtype of {{Throwable}} (say, {{Exception}}) instead of being {{Throwable}} itself, and a {{\@Cause}} parameter exists whose type is a superclass of that type (say, {{Throwable}}). > The compilation errors can look something like this: > {noformat} > 2018-04-02 12:37:40 [ERROR] /home/david/src/java/wildfly/ejb3/target/generated-sources/annotations/org/jboss/as/ejb3/logging/EjbLogger_$logger.java:[3340,112] incompatible types: java.lang.Throwable cannot be converted to java.lang.Exception > 2018-04-02 12:37:40 [ERROR] /home/david/src/java/wildfly/ejb3/target/generated-sources/annotations/org/jboss/as/ejb3/logging/EjbLogger_$logger.java:[3479,164] incompatible types: java.lang.Error cannot be converted to java.lang.Exception > {noformat} > If the {{\@Cause}} method parameter type is not assignable to the exception's cause parameter type, then the {{initCause}} strategy should be used instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-134) Incompatible type error with @Cause and ctors with unusual exception types

by David Lloyd (JIRA)

David Lloyd created LOGTOOL-134: ----------------------------------- Summary: Incompatible type error with @Cause and ctors with unusual exception types Key: LOGTOOL-134 URL: https://issues.jboss.org/browse/LOGTOOL-134 Project: Log Tool Issue Type: Bug Affects Versions: 2.1.0.Final Reporter: David Lloyd Priority: Minor Incorrect generated code can be generated if an exception constructor's "cause" parameter is a subtype of {{Throwable}} (say, {{Exception}}) instead of being {{Throwable}} itself, and a {{\@Cause}} parameter exists whose type is a superclass of that type (say, {{Throwable}}). The compilation errors can look something like this: {noformat} 2018-04-02 12:37:40 [ERROR] /home/david/src/java/wildfly/ejb3/target/generated-sources/annotations/org/jboss/as/ejb3/logging/EjbLogger_$logger.java:[3340,112] incompatible types: java.lang.Throwable cannot be converted to java.lang.Exception 2018-04-02 12:37:40 [ERROR] /home/david/src/java/wildfly/ejb3/target/generated-sources/annotations/org/jboss/as/ejb3/logging/EjbLogger_$logger.java:[3479,164] incompatible types: java.lang.Error cannot be converted to java.lang.Exception {noformat} If the {{\@Cause}} method parameter type is not assignable to the exception's cause parameter type, then the {{initCause}} strategy should be used instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3709) Upgrade JBoss Remoting to 5.0.7.Final

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3709?page=com.atlassian.jira.plugi... ] David Lloyd updated WFCORE-3709: -------------------------------- Summary: Upgrade JBoss Remoting to 5.0.7.Final (was: Upgrade JBoss Remoting from 5.0.5.Final to 5.0.6.Final) > Upgrade JBoss Remoting to 5.0.7.Final > ------------------------------------- > > Key: WFCORE-3709 > URL: https://issues.jboss.org/browse/WFCORE-3709 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Lin Gao > Assignee: David Lloyd > Labels: downstream_dependency > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3724) stop-servers following by a reload operation could end up in a long period with an unmanageable domain

by Yeray Borges (JIRA)

Yeray Borges created WFCORE-3724: ------------------------------------ Summary: stop-servers following by a reload operation could end up in a long period with an unmanageable domain Key: WFCORE-3724 URL: https://issues.jboss.org/browse/WFCORE-3724 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 5.0.0.Alpha2 Reporter: Yeray Borges Assignee: Brian Stansberry When {{:stop-servers}} operation is used with a timeout different than 0, a graceful stop is performed on each server. If the user executes {{/host=master:reload}} in a DC, the reload operation waits for the servers until they are completely stopped. This could be an issue for a DC since the user is unable to execute any operation meanwhile the reload op is waiting for the previous stop. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 2018