[JBoss JIRA] (WFLY-3108) Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3108?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3108:
-----------------------------------------------
Rostislav Svoboda <rsvoboda(a)redhat.com> changed the Status of [bug 1076066|https://bugzilla.redhat.com/show_bug.cgi?id=1076066] from MODIFIED to ON_QA
> Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-3108
> URL: https://issues.jboss.org/browse/WFLY-3108
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.1.Final
>
>
> The prescribed mechanism for converting a slave HC to master is to:
> 1) Start the slave with --backup so a local copy of the domain config is maintained (in file domain.cached-remote.xml).
> 2) Stop the existing master.
> 3) Use the cli to connect to the slave and
> /host=<slavename>:write-local-domain-controller
> 4) Then, in the CLI
> reload --host=<slavename>
> Problem is this fails because the HC expects to have a domain config file "domain.xml".
> 2014-03-13 09:54:04,829 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:514) [wildfly-host-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.io.FileNotFoundException: /Users/bstansberry/tmp/WF801/slave/domain/configuration/domain.xml (No such file or directory)
> at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_45]
> at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_45]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:100) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> ... 3 more
> Or, MUCH WORSE, there happens to be a random domain.xml in the filesystem, which has content that is out of sync with the correct domain config. This domain.xml config will be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-3005) cannot override logging.configuration in jboss-cli.sh and jboss-cli.bat
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-3005?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky resolved WFLY-3005.
-------------------------------------
Fix Version/s: 8.0.1.Final
Resolution: Done
Merged.
> cannot override logging.configuration in jboss-cli.sh and jboss-cli.bat
> -----------------------------------------------------------------------
>
> Key: WFLY-3005
> URL: https://issues.jboss.org/browse/WFLY-3005
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CLI
> Affects Versions: 8.0.0.Final
> Environment: windows and linux
> Reporter: Gabriele Garuglieri
> Assignee: Alexey Loubyansky
> Fix For: 8.0.1.Final
>
>
> when using cli scripts jboss-cli.sh and jboss-cli.bat and you cannot write in $JBOSS_HOME because it is serving many server instances, you can override default jboss-cli.xml setting -Djboss.cli.config in $JAVA_OPTS but you cannot override logging.configuration because in both scripts is set with default after expanding $JAVA_OPTS
> last lines of bat script could be modified as follows:
> echo "%JAVA_OPTS%" | findstr /I "logging.configuration" > nul
> if errorlevel == 1 (
> set "JAVA_OPTS=%JAVA_OPTS% -Dlogging.configuration=file:%JBOSS_HOME%\bin\jboss-cli-logging.properties"
> ) else (
> echo logging.configuration already set in JAVA_OPTS
> )
> "%JAVA%" %JAVA_OPTS% ^
> -jar "%JBOSS_RUNJAR%" ^
> -mp "%JBOSS_MODULEPATH%" ^
> org.jboss.as.cli ^
> %*
> Last lines of sh script could be modified as follows:
> LOG_CONF=`echo $JAVA_OPTS | $GREP "logging.configuration"`
> if [ "x$LOG_CONF" = "x" ]; then
> JAVA_OPTS="$JAVA_OPTS -Dlogging.configuration=file:$JBOSS_HOME/bin/jboss-cli-logging.properties"
> else
> echo "logging.configuration already set in JAVA_OPTS"
> fi
> # Sample JPDA settings for remote socket debugging
> #JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
> eval \"$JAVA\" $JAVA_OPTS -jar \"$JBOSS_HOME/jboss-modules.jar\" -mp \"${JBOSS_MODULEPATH}\" org.jboss.as.cli '"$@"'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-3101) CLI: hide stacktraces for exceptions w/o messages when logging errors
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-3101?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky resolved WFLY-3101.
-------------------------------------
Resolution: Done
Merged.
> CLI: hide stacktraces for exceptions w/o messages when logging errors
> ---------------------------------------------------------------------
>
> Key: WFLY-3101
> URL: https://issues.jboss.org/browse/WFLY-3101
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: CLI
> Affects Versions: 8.0.0.Final
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 8.0.1.Final
>
>
> CommandContextImpl contains the following logic
> public void handleSafe(String line) {
> exitCode = 0;
> try {
> handle(line);
> } catch(Throwable t) {
> final StringBuilder buf = new StringBuilder();
> buf.append(t.getLocalizedMessage());
> Throwable t1 = t.getCause();
> while(t1 != null) {
> if(t1.getLocalizedMessage() != null) {
> buf.append(": ").append(t1.getLocalizedMessage());
> } else {
> t1.printStackTrace();
> }
> t1 = t1.getCause();
> }
> error(buf.toString());
> }
> }
> When an exception does not contain any message, e.g. in some cases IllegalArgumentException, etc, the full stacktraces are logged that are useful for debugging but not nice from the user interface point of view. It was suggested to hide them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-3050) '=' character removed from request cookie
by roy mizrachi (JIRA)
[ https://issues.jboss.org/browse/WFLY-3050?page=com.atlassian.jira.plugin.... ]
roy mizrachi edited comment on WFLY-3050 at 3/20/14 6:26 AM:
-------------------------------------------------------------
There should add "allow-equals-in-cookie-value" attribute to wildfly-undertow_1_0.xsd under http-listener.
The options already exists in io.undertow.UndertowOptions.
Will this be fixed in the near future and is there a bypass for this for final version?
This issue is a major issue and prevent me to migrate to jboss.
By the way the issue does not exists in wildfly 8 beta 1
Thanks
was (Author: roim):
Will this be fixed in the near future and is there a bypass for this for final version?
This issue is a major issue and prevent me to migrate to jboss.
By the way the issue does not exists in wildfly 8 beta 1
Thanks
> '=' character removed from request cookie
> ------------------------------------------
>
> Key: WFLY-3050
> URL: https://issues.jboss.org/browse/WFLY-3050
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Environment: windows 7
> Reporter: roy mizrachi
> Assignee: Stuart Douglas
>
> I'm saving encrypted user token in session cookie:
> Cookie: JCORESESSIONID=aes256$/tew4VVsfdJ32iUX1AOqBGRb717TJC9KkejjAPl6BIAG6kCP4beSraL51eQG2iu5bV9uT3OsubXUcjO+sG2lYNWbu5NliQd361oUz2Yl4LQ=
> The problem is that in the server i see that the '=' character is removed hence i cannot decrypt it.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-2658) (-Djboss.dist) jboss.dist property is not correctly propagated using -Djboss.dist
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2658?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2658:
-----------------------------------------------
Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1078701|https://bugzilla.redhat.com/show_bug.cgi?id=1078701] from NEW to POST
> (-Djboss.dist) jboss.dist property is not correctly propagated using -Djboss.dist
> ---------------------------------------------------------------------------------
>
> Key: WFLY-2658
> URL: https://issues.jboss.org/browse/WFLY-2658
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: 8.0.0.Beta1
> Reporter: Ondrej Lukas
> Assignee: Ondrej Zizka
>
> This JIRA is clone of bz-970610 (https://bugzilla.redhat.com/show_bug.cgi?id=970610)
> When I run testsuite of EAP 6.1.0 using command [1], where JBOSS_HOME is a path EAP 6.1.0, the manualmode tests fail with error [2]:
> It uses path defined in jboss.dist property defined in testsuite/integration/pom.xml instead of the one provided -Djboss.dist which should redefine it.
> [1] ./integration-tests.sh -Dpublic-repos -DallTests -Dmaven.repo.local=${MAVEN_REPO_LOCAL} -Djboss.dist=${JBOSS_HOME} -Dmaven.test.failure.ignore=true -Dsurefire.forked.process.timeout=3600
> [2]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7-redhat-1:run (build-manual-mode-servers) on project jboss-as-ts-integ-manualmode: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/src/test/scripts/manualmode-build.xml:52: /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/build/target/jboss-as-7.2.0.Final-redhat-8/modules does not exist.
> [ERROR] around Ant part ...<ant antfile="/mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/manualmode/../src/test/scripts/manualmode-build.xml">... @ 4:180 in /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/manualmode/target/antrun/build-main.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (SECURITY-808) Password not passed into DatabaseServerLoginModule
by Stefan Eder (JIRA)
Stefan Eder created SECURITY-808:
------------------------------------
Summary: Password not passed into DatabaseServerLoginModule
Key: SECURITY-808
URL: https://issues.jboss.org/browse/SECURITY-808
Project: PicketBox
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: WildFly8 on Windows 7 64-bit
Reporter: Stefan Eder
Assignee: Stefan Guilhen
Priority: Critical
Trying to migrate an application to WildFly (from AS6.1) the migration went pretty smooth except for using the security domain.
The application uses a the ClientLoginModule on the client side and the DatabaseserverLoginModule on the server side.
Though the DatabaseServerLoginModule is called the validation of the password fails. I debugged it and the reason seems to be that in {{org.jboss.security.auth.callback.JBossCallbackHandler.getPassword()}} a {{org.jboss.as.security.remoting.RemotingConnectionCredential@22341334}} is not handled and hence instead of a password the String {{org.jboss.as.security.remoting.RemotingConnectionCredential@22341334}} is passed through to the DatabaseLoginModule.
See also [DatabaseServerLoginModule broken?|https://community.jboss.org/message/863295] and the related posts
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-3050) '=' character removed from request cookie
by roy mizrachi (JIRA)
[ https://issues.jboss.org/browse/WFLY-3050?page=com.atlassian.jira.plugin.... ]
roy mizrachi commented on WFLY-3050:
------------------------------------
Will this be fixed in the near future and is there a bypass for this for final version?
This issue is a major issue and prevent me to migrate to jboss.
By the way the issue does not exists in wildfly 8 beta 1
Thanks
> '=' character removed from request cookie
> ------------------------------------------
>
> Key: WFLY-3050
> URL: https://issues.jboss.org/browse/WFLY-3050
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Environment: windows 7
> Reporter: roy mizrachi
> Assignee: Stuart Douglas
>
> I'm saving encrypted user token in session cookie:
> Cookie: JCORESESSIONID=aes256$/tew4VVsfdJ32iUX1AOqBGRb717TJC9KkejjAPl6BIAG6kCP4beSraL51eQG2iu5bV9uT3OsubXUcjO+sG2lYNWbu5NliQd361oUz2Yl4LQ=
> The problem is that in the server i see that the '=' character is removed hence i cannot decrypt it.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-2658) (-Djboss.dist) jboss.dist property is not correctly propagated using -Djboss.dist
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2658?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-2658:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=970610, https://bugzilla.redhat.com/show_bug.cgi?id=1078701 (was: https://bugzilla.redhat.com/show_bug.cgi?id=970610)
> (-Djboss.dist) jboss.dist property is not correctly propagated using -Djboss.dist
> ---------------------------------------------------------------------------------
>
> Key: WFLY-2658
> URL: https://issues.jboss.org/browse/WFLY-2658
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: 8.0.0.Beta1
> Reporter: Ondrej Lukas
> Assignee: Ondrej Zizka
>
> This JIRA is clone of bz-970610 (https://bugzilla.redhat.com/show_bug.cgi?id=970610)
> When I run testsuite of EAP 6.1.0 using command [1], where JBOSS_HOME is a path EAP 6.1.0, the manualmode tests fail with error [2]:
> It uses path defined in jboss.dist property defined in testsuite/integration/pom.xml instead of the one provided -Djboss.dist which should redefine it.
> [1] ./integration-tests.sh -Dpublic-repos -DallTests -Dmaven.repo.local=${MAVEN_REPO_LOCAL} -Djboss.dist=${JBOSS_HOME} -Dmaven.test.failure.ignore=true -Dsurefire.forked.process.timeout=3600
> [2]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7-redhat-1:run (build-manual-mode-servers) on project jboss-as-ts-integ-manualmode: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/src/test/scripts/manualmode-build.xml:52: /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/build/target/jboss-as-7.2.0.Final-redhat-8/modules does not exist.
> [ERROR] around Ant part ...<ant antfile="/mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/manualmode/../src/test/scripts/manualmode-build.xml">... @ 4:180 in /mnt/hudson_workspace/workspace/eap-60-as-testsuite-one-offs-rhatlapa/jboss-eap-6.1-src/testsuite/integration/manualmode/target/antrun/build-main.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-1547) deploy directories not cleaned up
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1547?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-1547:
------------------------------------------
Bugzilla Update: Perform
> deploy directories not cleaned up
> ---------------------------------
>
> Key: WFLY-1547
> URL: https://issues.jboss.org/browse/WFLY-1547
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.0.0.Alpha1
> Reporter: Shaun Appleton
> Assignee: jaikiran pai
> Fix For: 8.0.0.Beta1
>
> Attachments: deployment_with_hack_no_hook.txt
>
>
> JBoss EAP 6.0.0 (and 6.0.1.ER3) doesn't clean up it's tmp/vfs directories.
> The following reproduces this -
> i) ensure run.conf has the -Xrs set
> ii) ensure deployments has a deployable .ear in it
> iii) ./run standalone.sh and allow the deployments to deploy
> iv) stop the EAP process ie kill <process_id>
> v) observe content tmp/vfs
> (The -Xrs parameter is used to "-Xrs" to prevent possible interference when JVM is running as a service and receives CTRL_LOGOFF_EVENT or SIGHUP)
> This will eventually cause problems with lack of disk space.
> Note if the -Xrs parameter content is removed but the tmp/vfs dirs stills exist. This could potentially cause inode problems.
> It would be better if there were any additional code so the temp dirs are cleaned up on start up. That would resolve both the -Xrs problem and the excessive dir creation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months