Everything was going well. Nightly builds ran for more than a month with no problems. However, suddenly when invoking the feature builder from Eclipse the execution ends right away with the message.
一切都很顺利。每晚构建运行超过一个月没有问题。但是,突然从Eclipse调用功能构建器时,执行会立即结束消息。
ERRORLEVEL 13
As far as I know I haven't changed anything, as this computer is normally not touched. (It is only used for the nightly builds).
据我所知,我没有改变任何东西,因为这台电脑通常不会被触及。 (它仅用于夜间构建)。
I've googled around to see what this error means but to no avail. I found a link from IBM that shows a custom bat file that catches this error, but the explanation given is not very useful.
我已经google了一下,看看这个错误意味着什么,但无济于事。我发现IBM的一个链接显示了一个捕获此错误的自定义bat文件,但给出的解释并不是很有用。
My guess is that this is related to the workspace, somehow, or that the whole eclipse installation is corrupted.
我的猜测是,这与工作空间有关,不知何故,或整个eclipse安装已损坏。
Do you have any idea what this error means and how can it be corrected?
您是否知道此错误的含义以及如何纠正?
2 个解决方案
#1
4
After reading what the error code means thanks to the answer from VonC I understood where to look. The problem was a lot more obscure that it seems.
在阅读了VonC的答案后,阅读了错误代码意味着什么,我明白了在哪里看。看起来这个问题更加模糊不清。
I looked into the configuration folder for Eclipse (logs are either written there or in the .metadata folder when something goes wrong), and I found a huge log file. Inside the file I found the following error:
我查看了Eclipse的配置文件夹(当出现问题时,日志会写在那里或在.metadata文件夹中),我发现了一个巨大的日志文件。在文件里面我发现了以下错误:
application org.eclipse.sdk not found
and the following exception, followed by a plugin name, several times:
和以下异常,后跟一个插件名称,几次:
java.util.zip.ZipException: Too many open files
Several plugins could not be loaded, causing a cascade of missing dependencies that prevented Eclipse from launching. I searched the web for this exception and found the following bug description from SUN, which says that Java 1.5.0 can not open more than 2,100 zip files.
无法加载多个插件,导致一系列缺少依赖项,导致Eclipse无法启动。我在网上搜索了这个异常,并从SUN发现了以下错误描述,其中说Java 1.5.0无法打开2,100多个zip文件。
The problem started a while after I installed the BABEL project translations for Eclipse into the build computer. These are more than 900 fragments, containing translations for many plugins, one for each language. As I installed it on top of an existing eclipse installation, it seemed that it was not a problem to open them.... until I cleared the workspace for the builds. Then Eclipse wouldn't launch anymore. I went over the limit. It didn't help that the first thing I tried to fix the build was, again.... clearing everything.
在我将Eclipse的BABEL项目翻译安装到构建计算机后,问题开始了一段时间。这些是超过900个片段,包含许多插件的翻译,每种语言一个。当我将它安装在现有的eclipse安装之上时,打开它们似乎不是问题....直到我清除了构建的工作区。然后Eclipse将不再启动。我超过了极限。我尝试修复构建的第一件事是,再次......清除所有内容,这没有任何帮助。
Because I only use this computer for headless builds, I didn't realize that the problem was in Eclipse itself and I was looking inside the build process. I only realized when I looked into the log file.
因为我只使用这台计算机进行无头构建,所以我没有意识到问题出在Eclipse本身,我正在查看构建过程。当我查看日志文件时,我才意识到。
After installing Java 1.6.0_11 I was able to launch Eclipse and go on with my build.
安装Java 1.6.0_11后,我能够启动Eclipse并继续我的构建。
#2
3
It should mean "ant build failed", meaning the headless ant script fails at some point.
它应该意味着“蚂蚁构建失败”,这意味着无头蚂蚁脚本在某些时候失败了。
You should check if you can catch the log/output generated by this script to analyze this ant session and see at what point the ant script fails.
您应该检查是否可以捕获此脚本生成的日志/输出以分析此ant会话,并查看ant脚本失败的位置。
If it fails right away, it usually is because of:
如果它立即失败,通常是因为:
- a change in rights (writing access), or
- in environment variable modifications, or
- in resource access (path non accessible).
权利的变化(写作访问),或
在环境变量修改中,或
在资源访问(路径不可访问)。
You also have to check if the computer is still in its original windows domain, and if the rights (admin ?) associated with the account running the ant script are still the same.
您还必须检查计算机是否仍在其原始Windows域中,以及与运行ant脚本的帐户关联的权限(admin?)是否仍然相同。
#1
4
After reading what the error code means thanks to the answer from VonC I understood where to look. The problem was a lot more obscure that it seems.
在阅读了VonC的答案后,阅读了错误代码意味着什么,我明白了在哪里看。看起来这个问题更加模糊不清。
I looked into the configuration folder for Eclipse (logs are either written there or in the .metadata folder when something goes wrong), and I found a huge log file. Inside the file I found the following error:
我查看了Eclipse的配置文件夹(当出现问题时,日志会写在那里或在.metadata文件夹中),我发现了一个巨大的日志文件。在文件里面我发现了以下错误:
application org.eclipse.sdk not found
and the following exception, followed by a plugin name, several times:
和以下异常,后跟一个插件名称,几次:
java.util.zip.ZipException: Too many open files
Several plugins could not be loaded, causing a cascade of missing dependencies that prevented Eclipse from launching. I searched the web for this exception and found the following bug description from SUN, which says that Java 1.5.0 can not open more than 2,100 zip files.
无法加载多个插件,导致一系列缺少依赖项,导致Eclipse无法启动。我在网上搜索了这个异常,并从SUN发现了以下错误描述,其中说Java 1.5.0无法打开2,100多个zip文件。
The problem started a while after I installed the BABEL project translations for Eclipse into the build computer. These are more than 900 fragments, containing translations for many plugins, one for each language. As I installed it on top of an existing eclipse installation, it seemed that it was not a problem to open them.... until I cleared the workspace for the builds. Then Eclipse wouldn't launch anymore. I went over the limit. It didn't help that the first thing I tried to fix the build was, again.... clearing everything.
在我将Eclipse的BABEL项目翻译安装到构建计算机后,问题开始了一段时间。这些是超过900个片段,包含许多插件的翻译,每种语言一个。当我将它安装在现有的eclipse安装之上时,打开它们似乎不是问题....直到我清除了构建的工作区。然后Eclipse将不再启动。我超过了极限。我尝试修复构建的第一件事是,再次......清除所有内容,这没有任何帮助。
Because I only use this computer for headless builds, I didn't realize that the problem was in Eclipse itself and I was looking inside the build process. I only realized when I looked into the log file.
因为我只使用这台计算机进行无头构建,所以我没有意识到问题出在Eclipse本身,我正在查看构建过程。当我查看日志文件时,我才意识到。
After installing Java 1.6.0_11 I was able to launch Eclipse and go on with my build.
安装Java 1.6.0_11后,我能够启动Eclipse并继续我的构建。
#2
3
It should mean "ant build failed", meaning the headless ant script fails at some point.
它应该意味着“蚂蚁构建失败”,这意味着无头蚂蚁脚本在某些时候失败了。
You should check if you can catch the log/output generated by this script to analyze this ant session and see at what point the ant script fails.
您应该检查是否可以捕获此脚本生成的日志/输出以分析此ant会话,并查看ant脚本失败的位置。
If it fails right away, it usually is because of:
如果它立即失败,通常是因为:
- a change in rights (writing access), or
- in environment variable modifications, or
- in resource access (path non accessible).
权利的变化(写作访问),或
在环境变量修改中,或
在资源访问(路径不可访问)。
You also have to check if the computer is still in its original windows domain, and if the rights (admin ?) associated with the account running the ant script are still the same.
您还必须检查计算机是否仍在其原始Windows域中,以及与运行ant脚本的帐户关联的权限(admin?)是否仍然相同。