Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] windows上broker启动失败 缺少引号 #7731

Closed
3 tasks done
scwlkq opened this issue Jan 8, 2024 · 3 comments · Fixed by #8338
Closed
3 tasks done

[Bug] windows上broker启动失败 缺少引号 #7731

scwlkq opened this issue Jan 8, 2024 · 3 comments · Fixed by #8338

Comments

@scwlkq
Copy link

scwlkq commented Jan 8, 2024

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

windows

RocketMQ version

4.9.4

JDK Version

11

Describe the Bug

image

Steps to Reproduce

类似namesvr.cmd 对runbroker.cmd的命令加上英文引号set "JAVA_OPT=%JAVA_OPT% -cp "%CLASSPATH%""
image

What Did You Expect to See?

提个pr解决一下

What Did You See Instead?

专门针对windows系统的二进制文件?

Additional Context

No response

@humkum
Copy link
Contributor

humkum commented Jan 8, 2024

You can check whether your RocketMQ_HOME contains spaces

@scwlkq
Copy link
Author

scwlkq commented Jan 8, 2024

You can check whether your RocketMQ_HOME contains spaces

I have checked and there are no spaces. In fact, I encountered this problem when searching and found many blogs like this, so I thought it might be a small bug

我检查过了没有空格。事实上我是出现这个问题去搜索然后发现很多这样的博客,于是想着可能是小bug(?)

@Camio1945
Copy link

@RongtongJin @scwlkq 你们是不是只改了 else 分支,没有改 if 分支?我的 if 分支报了同样的错。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants