像内存计算器一样打开JDK错误Cloud Foundry [英] Open JDK Like Memory Calculator Error Cloud Foundry

查看:46
本文介绍了像内存计算器一样打开JDK错误Cloud Foundry的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在将spring boot hello world应用程序部署到Cloud Foundry。使用下面的cf push命令。得到以下错误:

 打开JDK内存计算器错误:3.13中的'2.0.2_RELEASE'版本不合理.0_RELEASE 

有人对此有想法吗?
从stackoverflow下面,我可以看到2.0.2.RELEASE是开放的jdk版本:
Cloud Foundry中的JDK可用性
我无法获得3.13.0_RELEASE吗?



完整日志:

 更新应用程序TestPOC1 ... 
映射路线...
比较本地文件与远程缓存...
包装要上传的文件...
正在上传文件...
256.00 KiB / 256.00 KiB [========================== ================================================== ================================================== =======================================] 100.00%1s

等待API完成处理文件...

暂存应用程序和跟踪日志...
单元919f72a9-975c-4bf3-8b2f-1f0e73bda65b创建实例0597e6a8-7b92- 4c71-8942-15c68c29b535
单元格919f72a9-975c-4bf3-8b2f-1f0e73bda65b成功创建了实例0597e6a8-7b92-4c7的容器1-8942-15c68c29b535
正在下载应用程序包...
已下载应用程序包(16.2M)
[Buildpack]错误编译失败,出现异常#< RuntimeError:像内存计算器一样打开JDK错误:在3.13.0_RELEASE>中,无法解析 2.0.2_RELEASE的版本。
像内存计算器一样打开JDK,错误:3.13.0_RELEASE中的'2.0.2_RELEASE'无法解析版本
未能编译Droplet:未能编译Droplet:退出状态1
退出状态223
单元919f72a9-975c-4bf3-8b2f-1f0e73bda65b停止实例0597e6a8-7b92-4c71-8942-15c68c29b535
单元919f72a9-975c-4bf3-8b2f-1f0e73bda65b销毁实例容器0597e6a8-7-7942
单元919f72a9-975c-4bf3-8b2f-1f0e73bda65b成功销毁了实例容器0597e6a8-7b92-4c71-8942-15c68c29b535
错误登台应用程序:在构建包编译阶段,应用登台失败
FAILED


解决方案

它看起来像一个CloudFundry问题,它根据此评论通过将堆栈更新为可信任的解决。。 p>

似乎精确堆栈不支持版本2.0.2_RELEASE,而可信任堆栈可以。 仿生堆栈仅适用于3.X。


I am deploying spring boot hello world app to cloud foundry. Used cf push command.Getting below Error:

Open JDK Memory Calculator Error: No Version Reasonable for '2.0.2_RELEASE' in 3.13.0_RELEASE

Any one have idea about this? From below stackoverflow, I can see 2.0.2.RELEASE as open jdk version: JDK availability in Cloud Foundry I am unable to get 3.13.0_RELEASE?

Complete Log:

Updating app TestPOC1...
Mapping routes...
Comparing local files to remote cache...
Packaging files to upload...
Uploading files...
 256.00 KiB / 256.00 KiB [=====================================================================================================================================================================] 100.00% 1s

Waiting for API to complete processing files...

Staging app and tracing logs...
   Cell 919f72a9-975c-4bf3-8b2f-1f0e73bda65b creating container for instance 0597e6a8-7b92-4c71-8942-15c68c29b535
   Cell 919f72a9-975c-4bf3-8b2f-1f0e73bda65b successfully created container for instance 0597e6a8-7b92-4c71-8942-15c68c29b535
   Downloading app package...
   Downloaded app package (16.2M)
   [Buildpack]                      ERROR Compile failed with exception #<RuntimeError: Open JDK Like Memory Calculator error: No version resolvable for '2.0.2_RELEASE' in 3.13.0_RELEASE>
   Open JDK Like Memory Calculator error: No version resolvable for '2.0.2_RELEASE' in 3.13.0_RELEASE
   Failed to compile droplet: Failed to compile droplet: exit status 1
   Exit status 223
   Cell 919f72a9-975c-4bf3-8b2f-1f0e73bda65b stopping instance 0597e6a8-7b92-4c71-8942-15c68c29b535
   Cell 919f72a9-975c-4bf3-8b2f-1f0e73bda65b destroying container for instance 0597e6a8-7b92-4c71-8942-15c68c29b535
   Cell 919f72a9-975c-4bf3-8b2f-1f0e73bda65b successfully destroyed container for instance 0597e6a8-7b92-4c71-8942-15c68c29b535
Error staging application: App staging failed in the buildpack compile phase
FAILED

解决方案

It looks like a CloudFundry issue which according to this comment is solved by updating stack to trusty.

It seems that precise stack doesn't support version 2.0.2_RELEASE while trusty stack does. Somehow bionic stack only works with 3.X.

这篇关于像内存计算器一样打开JDK错误Cloud Foundry的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆