June 2018 - jboss-jira - Jboss List Archives

[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/..* _(extra ..)_ instead of *$JBOSS_HOME*, and it compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of RESOLVED_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

1
0
0 / 0

[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/..* _(extra ..)_ instead of *$JBOSS_HOME*, and it compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of RESOLVED_JBOSS_HOME. was: If JBOSS_HOME is set then > 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/..* _(extra ..)_ instead of *$JBOSS_HOME*, and it compares *RESOLVED_JBOSS* to *SANITIZED_JBOSS_HOME*, instead of RESOLVED_JBOSS_HOME. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3941) elytron-tool.sh script detects JBOSS_HOME incorrectly

by Paramvir Jindal (JIRA)

Paramvir Jindal created WFCORE-3941: --------------------------------------- Summary: 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: 6.0.0.Alpha1, 5.0.0.Final Reporter: Paramvir Jindal If JBOSS_HOME is set then -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-10612?page=com.atlassian.jira.plugin... ] Brad Maxwell updated WFLY-10612: -------------------------------- Description: It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings. <iiop enable-by-default="true" use-qualified-name="true"/> {code} INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote {code} Something like this when use-qualified-name="true" {code} IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: iiop-eap7/HelloSessionBean {code} or use-qualified-name="false" {code} IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: HelloSessionBean {code} was: It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings. <iiop enable-by-default="true" use-qualified-name="true"/> {code} INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote {code} > Include EJB's IIOP Binding when EJB is deployed logging > ------------------------------------------------------- > > Key: WFLY-10612 > URL: https://issues.jboss.org/browse/WFLY-10612 > Project: WildFly > Issue Type: Enhancement > Components: IIOP > Affects Versions: 12.0.0.Final > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > > It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings. > <iiop enable-by-default="true" use-qualified-name="true"/> > {code} > INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > {code} > Something like this when use-qualified-name="true" > {code} > IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > iiop-eap7/HelloSessionBean > {code} > or use-qualified-name="false" > {code} > IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > HelloSessionBean > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-10612: ----------------------------------- Summary: Include EJB's IIOP Binding when EJB is deployed logging Key: WFLY-10612 URL: https://issues.jboss.org/browse/WFLY-10612 Project: WildFly Issue Type: Enhancement Components: IIOP Affects Versions: 12.0.0.Final Reporter: Brad Maxwell Assignee: Tomasz Adamski It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings. <iiop enable-by-default="true" use-qualified-name="true"/> {code} INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-305) B18 is not working after istio-injector was deployed