[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1810:
---------------------------
Fix Version/s: 3.5
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
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-3151) Failure to start jboss-cli.sh due to space in the startup path
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3151?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-3151:
------------------------------
Summary: Failure to start jboss-cli.sh due to space in the startup path (was: Possible regression standalone.sh due to a space in the startup path)
> Failure to start jboss-cli.sh due to space in the startup path
> --------------------------------------------------------------
>
> Key: WFLY-3151
> URL: https://issues.jboss.org/browse/WFLY-3151
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Arun Gupta
> Assignee: James Perkins
>
> Sent email to wildfly-dev:
> -- cut here --
> Java EE 7 CI job on WildFly trunk is failing:
> https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
> Here is the error message:
> Started 45 of 56 services (22 services are lazy, passive or on-demand)
> [0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
> '--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
> Error: Could not find or load main class EE
> Process leaked file descriptors. See
> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
> for more information
> Build step 'Execute shell' marked build as failure
> -- cut here --
> David reponded:
> -- cut here --
> Looks like a possible regression in standalone.sh due to there being a
> space in the startup path.
> As a workaround you could change your workspace name from "Java EE 7
> Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
> similar (with no spaces).
> -- cut here --
--
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-3151) Failure to start jboss-cli.sh due to space in the startup path
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3151?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-3151:
------------------------------
Description:
The CLI startup script needs to be modified to process arguments like standalone.sh and friends to, to be tolerant of spaces in the original arg list.
Original report:
Sent email to wildfly-dev:
{noformat}
Java EE 7 CI job on WildFly trunk is failing:
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
Here is the error message:
Started 45 of 56 services (22 services are lazy, passive or on-demand)
[0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
'--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
Error: Could not find or load main class EE
Process leaked file descriptors. See
http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
for more information
Build step 'Execute shell' marked build as failure
{noformat}
David responded:
{noformat}
Looks like a possible regression in standalone.sh due to there being a
space in the startup path.
As a workaround you could change your workspace name from "Java EE 7
Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
similar (with no spaces).
{noformat}
was:
Sent email to wildfly-dev:
-- cut here --
Java EE 7 CI job on WildFly trunk is failing:
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
Here is the error message:
Started 45 of 56 services (22 services are lazy, passive or on-demand)
[0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
'--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
Error: Could not find or load main class EE
Process leaked file descriptors. See
http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
for more information
Build step 'Execute shell' marked build as failure
-- cut here --
David reponded:
-- cut here --
Looks like a possible regression in standalone.sh due to there being a
space in the startup path.
As a workaround you could change your workspace name from "Java EE 7
Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
similar (with no spaces).
-- cut here --
> Failure to start jboss-cli.sh due to space in the startup path
> --------------------------------------------------------------
>
> Key: WFLY-3151
> URL: https://issues.jboss.org/browse/WFLY-3151
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Arun Gupta
> Assignee: James Perkins
>
> The CLI startup script needs to be modified to process arguments like standalone.sh and friends to, to be tolerant of spaces in the original arg list.
> Original report:
> Sent email to wildfly-dev:
> {noformat}
> Java EE 7 CI job on WildFly trunk is failing:
> https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
> Here is the error message:
> Started 45 of 56 services (22 services are lazy, passive or on-demand)
> [0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
> '--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
> Error: Could not find or load main class EE
> Process leaked file descriptors. See
> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
> for more information
> Build step 'Execute shell' marked build as failure
> {noformat}
> David responded:
> {noformat}
> Looks like a possible regression in standalone.sh due to there being a
> space in the startup path.
> As a workaround you could change your workspace name from "Java EE 7
> Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
> similar (with no spaces).
> {noformat}
--
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] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Chris LeCompte (JIRA)
Chris LeCompte created JGRP-1810:
------------------------------------
Summary: Illegal format string in trace message in NAKACK2 protocol
Key: JGRP-1810
URL: https://issues.jboss.org/browse/JGRP-1810
Project: JGroups
Issue Type: Bug
Affects Versions: 3.4.3
Reporter: Chris LeCompte
Assignee: Bela Ban
Priority: Minor
The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
local_addr, my_hr, hr, member + "#" + hr);
This results in an error in the log:
ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
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-3151) Possible regression standalone.sh due to a space in the startup path
by Arun Gupta (JIRA)
Arun Gupta created WFLY-3151:
--------------------------------
Summary: Possible regression standalone.sh due to a space in the startup path
Key: WFLY-3151
URL: https://issues.jboss.org/browse/WFLY-3151
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Arun Gupta
Sent email to wildfly-dev:
-- cut here --
Java EE 7 CI job on WildFly trunk is failing:
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
Here is the error message:
Started 45 of 56 services (22 services are lazy, passive or on-demand)
[0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
'--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
Error: Could not find or load main class EE
Process leaked file descriptors. See
http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
for more information
Build step 'Execute shell' marked build as failure
-- cut here --
David reponded:
-- cut here --
Looks like a possible regression in standalone.sh due to there being a
space in the startup path.
As a workaround you could change your workspace name from "Java EE 7
Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
similar (with no spaces).
-- cut here --
--
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] (JBASMP-65) Could not execute goal add-resource / wildfly-maven-plugin
by Felix Coutinho (JIRA)
[ https://issues.jboss.org/browse/JBASMP-65?page=com.atlassian.jira.plugin.... ]
Felix Coutinho closed JBASMP-65.
--------------------------------
Resolution: Duplicate Issue
> Could not execute goal add-resource / wildfly-maven-plugin
> ----------------------------------------------------------
>
> Key: JBASMP-65
> URL: https://issues.jboss.org/browse/JBASMP-65
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Components: deploy, wildfly
> Affects Versions: 7.5.Final
> Environment: Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T14:37:52-03:00)
> Maven home: /home/felix/Downloads/apache-maven-3.2.1
> Java version: 1.7.0_51, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-7-oracle/jre
> Default locale: pt_BR, platform encoding: UTF-8
> OS name: "linux", version: "3.8.0-35-generic", arch: "amd64", family: "unix"
> Reporter: Felix Coutinho
> Assignee: James Perkins
> Priority: Blocker
> Labels: maven, wildfly
>
> My pom: http://pastebin.com/BJ9zcXrg
> felix@felix-DQ77PRO:~/workspaces/java/workspaceGastos/yyy-project$ mvn clean install -X
> The debug output:
> http://pastebin.com/cM8LbR62
> The problem is here:
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null: IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal add-resource. Reason: null
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:118)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.asList(ModelValue.java:132)
> at org.jboss.dmr.ModelNode.asList(ModelNode.java:1302)
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.resourceExists(AddResourceMojo.java:258)
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.addCompositeResource(AddResourceMojo.java:180)
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.processResources(AddResourceMojo.java:148)
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:112)
> ... 21 more
> Same problem:
> http://stackoverflow.com/questions/22533311/wildfly-maven-plugin-not-depl...
> Other:
> http://stackoverflow.com/questions/21020926/add-an-xa-datasource-fails-wi...
--
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] (JBASMP-66) Could not execute goal add-resource / wildfly-maven-plugin
by Felix Coutinho (JIRA)
Felix Coutinho created JBASMP-66:
------------------------------------
Summary: Could not execute goal add-resource / wildfly-maven-plugin
Key: JBASMP-66
URL: https://issues.jboss.org/browse/JBASMP-66
Project: JBoss AS Maven Plugins
Issue Type: Bug
Components: deploy, wildfly
Affects Versions: 7.5.Final
Environment: Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T14:37:52-03:00)
Maven home: /home/felix/Downloads/apache-maven-3.2.1
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-oracle/jre
Default locale: pt_BR, platform encoding: UTF-8
OS name: "linux", version: "3.8.0-35-generic", arch: "amd64", family: "unix"
Reporter: Felix Coutinho
Assignee: James Perkins
Priority: Blocker
My pom: http://pastebin.com/BJ9zcXrg
felix@felix-DQ77PRO:~/workspaces/java/workspaceGastos/yyy-project$ mvn clean install -X
The debug output:
http://pastebin.com/cM8LbR62
The problem is here:
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null: IllegalArgumentException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal add-resource. Reason: null
at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:118)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.asList(ModelValue.java:132)
at org.jboss.dmr.ModelNode.asList(ModelNode.java:1302)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.resourceExists(AddResourceMojo.java:258)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.addCompositeResource(AddResourceMojo.java:180)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.processResources(AddResourceMojo.java:148)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:112)
... 21 more
Same problem:
http://stackoverflow.com/questions/22533311/wildfly-maven-plugin-not-depl...
Other:
http://stackoverflow.com/questions/21020926/add-an-xa-datasource-fails-wi...
--
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