[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3937:
-------------------------------------
Comment: was deleted
(was: This works fine for me on my Macbook, docker version 17.09.1-ce-mac42 (which is fairly old as later versions of Docker had bug on OSX.) But Jeff has reproduced it so I'm just mentioning this as a data point.
Never mind; I got distracted and hadn't done the 'docker run --rm -it testing' step!
)
> Error when running configured wildfly
> -------------------------------------
>
> Key: WFCORE-3937
> URL: https://issues.jboss.org/browse/WFCORE-3937
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 5.0.0.Final
> Reporter: Stephen Buergler
> Assignee: Jeff Mesnil
> Priority: Minor
> Attachments: Dockerfile
>
>
> 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
> ...
> 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot.
> To reproduce:
> docker build -t testing .
> docker run --rm -it testing
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3937:
------------------------------------------
This works fine for me on my Macbook, docker version 17.09.1-ce-mac42 (which is fairly old as later versions of Docker had bug on OSX.) But Jeff has reproduced it so I'm just mentioning this as a data point.
> Error when running configured wildfly
> -------------------------------------
>
> Key: WFCORE-3937
> URL: https://issues.jboss.org/browse/WFCORE-3937
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 5.0.0.Final
> Reporter: Stephen Buergler
> Assignee: Jeff Mesnil
> Priority: Minor
> Attachments: Dockerfile
>
>
> 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
> ...
> 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot.
> To reproduce:
> docker build -t testing .
> docker run --rm -it testing
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3937:
-------------------------------------
Description:
08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
...
08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot.
To reproduce:
docker build -t testing .
docker run --rm -it testing
was:
08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
...
08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot.
To reproduce:
docker build -ttesting .
docker run --rm -it testing
> Error when running configured wildfly
> -------------------------------------
>
> Key: WFCORE-3937
> URL: https://issues.jboss.org/browse/WFCORE-3937
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 5.0.0.Final
> Reporter: Stephen Buergler
> Assignee: Jeff Mesnil
> Priority: Minor
> Attachments: Dockerfile
>
>
> 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
> ...
> 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot.
> To reproduce:
> docker build -t testing .
> docker run --rm -it testing
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2643) Extraneous parentheses generated by Guided Rule editor
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2643?page=com.atlassian.jira.plugi... ]
Jozef Marko moved RHDM-644 to DROOLS-2643:
------------------------------------------
Project: Drools (was: Red Hat Decision Manager)
Key: DROOLS-2643 (was: RHDM-644)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: Guided Rule Editor
(was: Decision Central)
Affects Version/s: 7.8.0.Final
(was: 7.0.0.GA)
QE Status: NEW
> Extraneous parentheses generated by Guided Rule editor
> ------------------------------------------------------
>
> Key: DROOLS-2643
> URL: https://issues.jboss.org/browse/DROOLS-2643
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Affects Versions: 7.8.0.Final
> Environment: RHDM 7.0.0.GA on Oracle JDK 1.8.0_172 on Mac OSX 10.13.5
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: Central, Decision, RHDM
>
> The Guided Rule editor inserts extraneous parentheses in the generated DRL around the phrase "(OrderLine : quantity > 0) from $o.orderlines)" as shown below:
> package com.redhat.rhdm.demo;
> import java.lang.Number;
> rule "SpecialHandlingGuidedRule"
> dialect "mvel"
> when
> $o : Order( orderlines.size() > 0 )
> Number( intValue() > 100 ) from accumulate ( (OrderLine( $q : quantity > 0 ) from $o.orderlines)
> ,
> sum($q))
> then
> end
> This above DRL will fail to validate. If the extraneous parentheses are removed, as shown below, then the DRL is valid.
> package com.redhat.rhdm.demo;
> import java.lang.Number;
> rule "Assign Special Handling for Large Orders"
> dialect "mvel"
> when
> $o : Order( orderlines.size() > 0 )
> Number( intValue() > 100 )
> from accumulate (OrderLine( $q : quantity > 0 ) from $o.orderlines, sum($q))
> then
> $o.setIsSpecial( true )
> end
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2643) Extraneous parentheses generated by Guided Rule editor
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2643?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2643:
--------------------------------
Tester: Michael Anstis (was: Jozef Marko)
> Extraneous parentheses generated by Guided Rule editor
> ------------------------------------------------------
>
> Key: DROOLS-2643
> URL: https://issues.jboss.org/browse/DROOLS-2643
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Affects Versions: 7.8.0.Final
> Environment: RHDM 7.0.0.GA on Oracle JDK 1.8.0_172 on Mac OSX 10.13.5
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: Central, Decision, RHDM
>
> The Guided Rule editor inserts extraneous parentheses in the generated DRL around the phrase "(OrderLine : quantity > 0) from $o.orderlines)" as shown below:
> package com.redhat.rhdm.demo;
> import java.lang.Number;
> rule "SpecialHandlingGuidedRule"
> dialect "mvel"
> when
> $o : Order( orderlines.size() > 0 )
> Number( intValue() > 100 ) from accumulate ( (OrderLine( $q : quantity > 0 ) from $o.orderlines)
> ,
> sum($q))
> then
> end
> This above DRL will fail to validate. If the extraneous parentheses are removed, as shown below, then the DRL is valid.
> package com.redhat.rhdm.demo;
> import java.lang.Number;
> rule "Assign Special Handling for Large Orders"
> dialect "mvel"
> when
> $o : Order( orderlines.size() > 0 )
> Number( intValue() > 100 )
> from accumulate (OrderLine( $q : quantity > 0 ) from $o.orderlines, sum($q))
> then
> $o.setIsSpecial( true )
> end
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2643) Extraneous parentheses generated by Guided Rule editor
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2643?page=com.atlassian.jira.plugi... ]
Jozef Marko reassigned DROOLS-2643:
-----------------------------------
Assignee: Jozef Marko (was: Michael Anstis)
> Extraneous parentheses generated by Guided Rule editor
> ------------------------------------------------------
>
> Key: DROOLS-2643
> URL: https://issues.jboss.org/browse/DROOLS-2643
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Affects Versions: 7.8.0.Final
> Environment: RHDM 7.0.0.GA on Oracle JDK 1.8.0_172 on Mac OSX 10.13.5
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Minor
> Labels: Central, Decision, RHDM
>
> The Guided Rule editor inserts extraneous parentheses in the generated DRL around the phrase "(OrderLine : quantity > 0) from $o.orderlines)" as shown below:
> package com.redhat.rhdm.demo;
> import java.lang.Number;
> rule "SpecialHandlingGuidedRule"
> dialect "mvel"
> when
> $o : Order( orderlines.size() > 0 )
> Number( intValue() > 100 ) from accumulate ( (OrderLine( $q : quantity > 0 ) from $o.orderlines)
> ,
> sum($q))
> then
> end
> This above DRL will fail to validate. If the extraneous parentheses are removed, as shown below, then the DRL is valid.
> package com.redhat.rhdm.demo;
> import java.lang.Number;
> rule "Assign Special Handling for Large Orders"
> dialect "mvel"
> when
> $o : Order( orderlines.size() > 0 )
> Number( intValue() > 100 )
> from accumulate (OrderLine( $q : quantity > 0 ) from $o.orderlines, sum($q))
> then
> $o.setIsSpecial( true )
> end
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3941) elytron-tool.sh script detects JBOSS_HOME incorrectly
by Paramvir Jindal (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3941?page=com.atlassian.jira.plugi... ]
Paramvir Jindal commented on WFCORE-3941:
-----------------------------------------
PR Sent : https://github.com/wildfly/wildfly-core/pull/3368
> elytron-tool.sh script detects JBOSS_HOME incorrectly
> -----------------------------------------------------
>
> Key: WFCORE-3941
> URL: https://issues.jboss.org/browse/WFCORE-3941
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 5.0.0.Final, 6.0.0.Alpha1
> Reporter: Paramvir Jindal
>
> If JBOSS_HOME is set then :
> Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
> WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
> This script has two issues :
> It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
> It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
> *Current elytron-tool.sh :*
> ----------------------------------------------------------------------------------
> RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
> if [ "x$JBOSS_HOME" = "x" ]; then
> JBOSS_HOME=$RESOLVED_JBOSS_HOME
> else
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
> if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
> echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
> echo ""
> fi
> fi
> export JBOSS_HOME
> ---------------------------------------------------------------------------------
> *Expected elytron-tool.sh*
> ---------------------------------------------------------------------------------
> RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
> if [ "x$JBOSS_HOME" = "x" ]; then
> JBOSS_HOME=$RESOLVED_JBOSS_HOME
> else
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
> if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
> echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
> echo ""
> fi
> fi
> export JBOSS_HOME
> ------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3941) elytron-tool.sh script detects JBOSS_HOME incorrectly
by Paramvir Jindal (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3941?page=com.atlassian.jira.plugi... ]
Paramvir Jindal updated WFCORE-3941:
------------------------------------
Description:
If JBOSS_HOME is set then :
Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
This script has two issues :
It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
*Current elytron-tool.sh :*
----------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
---------------------------------------------------------------------------------
*Expected elytron-tool.sh*
---------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
------------------------------------------------------------------------------
was:
If JBOSS_HOME is set then :
Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
This script has two issues :
It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
*Current elytron-tool.sh :*
----------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
---------------------------------------------------------------------------------
*Expected elytron-tool.sh*
---------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
------------------------------------------------------------------------------
> elytron-tool.sh script detects JBOSS_HOME incorrectly
> -----------------------------------------------------
>
> Key: WFCORE-3941
> URL: https://issues.jboss.org/browse/WFCORE-3941
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 5.0.0.Final, 6.0.0.Alpha1
> Reporter: Paramvir Jindal
>
> If JBOSS_HOME is set then :
> Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
> WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
> This script has two issues :
> It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
> It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
> *Current elytron-tool.sh :*
> ----------------------------------------------------------------------------------
> # Setup JBOSS_HOME
> RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
> if [ "x$JBOSS_HOME" = "x" ]; then
> # get the full path (without any relative bits)
> JBOSS_HOME=$RESOLVED_JBOSS_HOME
> else
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
> if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
> echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
> echo ""
> fi
> fi
> export JBOSS_HOME
> ---------------------------------------------------------------------------------
> *Expected elytron-tool.sh*
> ---------------------------------------------------------------------------------
> # Setup JBOSS_HOME
> RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
> if [ "x$JBOSS_HOME" = "x" ]; then
> # get the full path (without any relative bits)
> JBOSS_HOME=$RESOLVED_JBOSS_HOME
> else
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
> if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
> echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
> echo ""
> fi
> fi
> export JBOSS_HOME
> ------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3941) elytron-tool.sh script detects JBOSS_HOME incorrectly
by Paramvir Jindal (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3941?page=com.atlassian.jira.plugi... ]
Paramvir Jindal updated WFCORE-3941:
------------------------------------
Description:
If JBOSS_HOME is set then :
Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
This script has two issues :
It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
*Current elytron-tool.sh :*
----------------------------------------------------------------------------------
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
---------------------------------------------------------------------------------
*Expected elytron-tool.sh*
---------------------------------------------------------------------------------
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
------------------------------------------------------------------------------
was:
If JBOSS_HOME is set then :
Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
This script has two issues :
It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
*Current elytron-tool.sh :*
----------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
---------------------------------------------------------------------------------
*Expected elytron-tool.sh*
---------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
------------------------------------------------------------------------------
> elytron-tool.sh script detects JBOSS_HOME incorrectly
> -----------------------------------------------------
>
> Key: WFCORE-3941
> URL: https://issues.jboss.org/browse/WFCORE-3941
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 5.0.0.Final, 6.0.0.Alpha1
> Reporter: Paramvir Jindal
>
> If JBOSS_HOME is set then :
> Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
> WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
> This script has two issues :
> It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
> It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
> *Current elytron-tool.sh :*
> ----------------------------------------------------------------------------------
> RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
> if [ "x$JBOSS_HOME" = "x" ]; then
> JBOSS_HOME=$RESOLVED_JBOSS_HOME
> else
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
> if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
> echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
> echo ""
> fi
> fi
> export JBOSS_HOME
> ---------------------------------------------------------------------------------
> *Expected elytron-tool.sh*
> ---------------------------------------------------------------------------------
> RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
> if [ "x$JBOSS_HOME" = "x" ]; then
> JBOSS_HOME=$RESOLVED_JBOSS_HOME
> else
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
> if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
> echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
> echo ""
> fi
> fi
> export JBOSS_HOME
> ------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3941) elytron-tool.sh script detects JBOSS_HOME incorrectly
by Paramvir Jindal (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3941?page=com.atlassian.jira.plugi... ]
Paramvir Jindal updated WFCORE-3941:
------------------------------------
Description:
If JBOSS_HOME is set then :
Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
This script has two issues :
It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
*Current elytron-tool.sh :*
----------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
---------------------------------------------------------------------------------
*Expected elytron-tool.sh*
---------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
------------------------------------------------------------------------------
was:
If JBOSS_HOME is set then :
Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
This script has two issues :
It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*.
It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*.
*Current elytron-tool.sh :*
----------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
---------------------------------------------------------------------------------
*Expected elytron-tool.sh*
---------------------------------------------------------------------------------
# Setup JBOSS_HOME
RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
if [ "x$JBOSS_HOME" = "x" ]; then
# get the full path (without any relative bits)
JBOSS_HOME=$RESOLVED_JBOSS_HOME
else
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
echo ""
fi
fi
export JBOSS_HOME
------------------------------------------------------------------------------
> elytron-tool.sh script detects JBOSS_HOME incorrectly
> -----------------------------------------------------
>
> Key: WFCORE-3941
> URL: https://issues.jboss.org/browse/WFCORE-3941
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 5.0.0.Final, 6.0.0.Alpha1
> Reporter: Paramvir Jindal
>
> If JBOSS_HOME is set then :
> Running $JBOSS_HOME/bin/elytron-tool.sh results in a warning:
> WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
> This script has two issues :
> It sets *SANITIZED_JBOSS_HOME* to *$JBOSS_HOME/..* instead of *$JBOSS_HOME*
> It compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of *RESOLVED_JBOSS_HOME*
> *Current elytron-tool.sh :*
> ----------------------------------------------------------------------------------
> # Setup JBOSS_HOME
> RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
> if [ "x$JBOSS_HOME" = "x" ]; then
> # get the full path (without any relative bits)
> JBOSS_HOME=$RESOLVED_JBOSS_HOME
> else
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
> if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
> echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
> echo ""
> fi
> fi
> export JBOSS_HOME
> ---------------------------------------------------------------------------------
> *Expected elytron-tool.sh*
> ---------------------------------------------------------------------------------
> # Setup JBOSS_HOME
> RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
> if [ "x$JBOSS_HOME" = "x" ]; then
> # get the full path (without any relative bits)
> JBOSS_HOME=$RESOLVED_JBOSS_HOME
> else
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
> if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
> echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
> echo ""
> fi
> fi
> export JBOSS_HOME
> ------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month