JVM cacerts (keystore) location is wrong in container_certificate_trust_store, the location won't resolve during staging. This is fixed by pull request #310

Commit 915400c modifed the IBM JRE processing as a result of a fix that went in to the installer which meant that it would honor the provided install location rather than unpacking in to the current directory. This meant that .bin file didn't need to be copied out of the read-only admin_cache before use and the results didn't need to be copied in to the correct location. Unfortunately the fix appears to have stopped creating the response.properties file in the temporary directory and instead uses the directory containing the .bin. This works in the online case but not for an admin buildpack.

E, [2015-09-22T08:04:42.479925 #47] ERROR -- /var/vcap/data/dea_next/admin_buildpacks/5400c51d-3576-452f-a147-c55c53709820_b3b5d542c29f67f48a43192cf73b39c277a3ff4e/lib/liberty_buildpack/buildpack.rb:50:in `rescue in drive_buildpack_with_logger': Compile failed with exception #<Errno::EROFS: Read-only file system - /var/vcap/data/dea_next/admin_buildpacks/5400c51d-3576-452f-a147-c55c53709820_b3b5d542c29f67f48a43192cf73b39c277a3ff4e/admin_cache/response.properties>
Read-only file system - /var/vcap/data/dea_next/admin_buildpacks/5400c51d-3576-452f-a147-c55c53709820_b3b5d542c29f67f48a43192cf73b39c277a3ff4e/admin_cache/response.properties
Expanding JRE to .java ... Staging failed: Buildpack compilation step failed

FAILED
BuildpackCompileFailed

Good evening.

I have recently tried to package the buildpack as an offline buildpack (via bundle exec rake package OFFLINE=true) and it fails to download dependencies to the cache. I must use an HTTP proxy, so I configured its URL on $http_proxy and $https_proxyenvironment variables (I have tried both uppercase and lowercase names). However, it does not work.

Examining traces, it looks like rake insists on downloading them without using the proxy. This is strange because Net::HTTP Ruby class seems to be used to perform the download and that class is supposed to take the aforementioned environment variables into account (as pointed by its documentation).

I'm seeing errors which I think are related to the #63 change:

2014-06-03T16:37:27.337676+00:00 app[web.1]: Failed to load context initializer class [org.cloudfoundry.reconfiguration.spring.CloudApplicationContextInitializer]; nested exception is java.lang.ClassNotFoundException:  org.cloudfoundry.reconfiguration.spring.CloudApplicationContextInitializer
2014-06-03T16:37:28.006707+00:00 app[web.1]: [ERROR   ] SRVE0283E: Exception caught while initializing context: org.springframework.context.ApplicationContextException: Failed to load context initializer class [org.cloudfoundry.reconfiguration.spring.CloudApplicationContextInitializer]; nested exception is java.lang.ClassNotFoundException: org.cloudfoundry.reconfiguration.spring.CloudApplicationContextInitializer
2014-06-03T16:37:28.006715+00:00 app[web.1]:    at org.springframework.web.context.ContextLoader.determineContextInitializerClasses(ContextLoader.java:438)
2014-06-03T16:37:28.006717+00:00 app[web.1]:    at org.springframework.web.context.ContextLoader.customizeContext(ContextLoader.java:466)
2014-06-03T16:37:28.006719+00:00 app[web.1]:    at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:382)
2014-06-03T16:37:28.006721+00:00 app[web.1]:    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)
2014-06-03T16:37:28.006722+00:00 app[web.1]:    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
2014-06-03T16:37:28.006724+00:00 app[web.1]:    at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:2223)
2014-06-03T16:37:28.006726+00:00 app[web.1]:    at [internal classes]
2014-06-03T16:37:28.006728+00:00 app[web.1]: Caused by: java.lang.ClassNotFoundException: org.cloudfoundry.reconfiguration.spring.CloudApplicationContextInitializer

Looking at Java buildpack changes the spring auto-reconfiguration work requires more changes: cloudfoundry/java-buildpack@d3d17c5

I'm testing with a simple AcmeAir application. See: https://github.com/jgawor/acmeair

I have cloned the liberty build pack and deployed the logviewer sample app and adjusted some parameters for JVM custom properties , now to stop and start the JVM not able to do it as cf loads the VM's and builts it, the issue is java is not present. does any one has a solution how to overcome this

Note: IN CF after application is deployed we login to the application by cf ssh app name where it gets you to the place where the application contained is present ( on to ubuntu for pcf dev local) there I want this to be started.

Hello team,

I have deployed an application using liberty build pack and now after deploying I have to set JVM arguments custom properties for that application , how can I set the custom properties for the application built on libert build

Note: tried to set the evn variables but application is not working as expected.

For example, the error message that we put out when the JVM or Liberty license information is incorrect is not being seen by the end user.

To try and summarize some of my comments in other issues (#34, #37), this is to track the enhancement request to allow the liberty buildpack to exploit the full features of the CF loggregator feature for routing any/all logs outbound for use within any external/internal solution for log analysis.

This requires liberty to write any/all logs to STDOUT/STDERR which are the only locations for loggregator to pick them up.

This requires an easy way to set the logging level on the fly within the liberty buildpack and/or runtime on the CF platform. For example, changing the logging level from INFO to FINE using a command line option during push (manifest file option?) would be ideal to help with troubleshooting runtime and application probelms on the fly.

The Java Buildpack (https://github.com/cloudfoundry/java-buildpack) has CA Introscope support. I'm consulting at a company that would like to use Introscope with the IBM WAS Liberty Buildpack.

The java-buildpack can download and configure the introscope agent, however it is not configured with any URL from which to download the tar file containing the agent code.

We have been considering forking the liberty buildpack in order to copy over support for CA Introscope agent deployment, and add it into this repository. If we did that, and we created a PR, would it likely be accepted?

Hi,
I have created an offline liberty builpack using this command:

bundle exec rake 'package[,*,]'

I get this error when I try to push a new application....

n091197@n091197-HP-ProBook-430-G1:/tmp$ cf push testJDBC -f manifest.yml
Using manifest file manifest.yml

Updating app testJDBC in org Produban / space development as [email protected]...
OK

Using route jdbc.cf.lvtc.gsnet.corp
Uploading testJDBC...
Uploading app files from: /tmp/ROOT.war
Uploading 102.4K, 49 files
Done uploading
OK

Stopping app testJDBC in org Produban / space development as [email protected]...
OK

Starting app testJDBC in org Produban / space development as [email protected]...
-----> Downloaded app package (80K)
-----> Liberty Buildpack Version: unknown
-----> Downloading IBM 1.7.1_1 JRE from https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/jre/1.7.1/linux/ibm-java-jre-7.1-1.1-x86_64-archive.bin ... (0.0s)
Expanding JRE to .java ... (10.1s)
-----> Downloading from https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.4/wlp-developers-runtime-8.5.5.4.jar ... (0.0s)

FAILED
Server error, status code: 400, error code: 170004, message: App staging failed in the buildpack compile phase

TIP: use 'cf logs testJDBC --recent' for more information

Question, Why it is trying to download a binary? it is an offline buildpack, if you look at the ibm-websphere-liberty-buildpack.zip, it contains an "admin_chache" directory with all the following downloaded files:

    0  2014-12-24 10:47   admin_cache/
  555  2014-12-24 10:43   admin_cache/https:%2F%2Fpublic.dhe.ibm.com%2Fibmdl%2Fexport%2Fpub%2Fsoftware%2Fwebsphere%2Fwasdev%2Fdownloads%2Fwlp%2Findex.yml.cached
 3224  2014-12-24 10:42   admin_cache/https:%2F%2Fdownload.run.pivotal.io%2Fnew-relic%2Findex.yml.cached
  676  2014-12-24 10:44   admin_cache/https:%2F%2Fpublic.dhe.ibm.com%2Fibmdl%2Fexport%2Fpub%2Fsoftware%2Fwebsphere%2Fwasdev%2Fdownloads%2Fjre%2Findex.yml.cached

6811885 2014-12-24 10:43 admin_cache/https:%2F%2Fdownload.run.pivotal.io%2Fnew-relic%2Fnew-relic-3.12.0.jar.cached
58859348 2014-12-24 10:44 admin_cache/https:%2F%2Fpublic.dhe.ibm.com%2Fibmdl%2Fexport%2Fpub%2Fsoftware%2Fwebsphere%2Fwasdev%2Fdownloads%2Fwlp%2F8.5.5.4%2Fwlp-developers-runtime-8.5.5.4.jar.cached
31591007 2014-12-24 10:47 admin_cache/https:%2F%2Fdownload.run.pivotal.io%2Fopenjdk%2Flucid%2Fx86_64%2Fopenjdk-1.7.0_71.tar.gz.cached
3570 2014-12-24 10:46 admin_cache/https:%2F%2Fdownload.run.pivotal.io%2Fopenjdk%2Flucid%2Fx86_64%2Findex.yml.cached
1920 2014-12-24 10:47 admin_cache/https:%2F%2Fdownload.run.pivotal.io%2Fauto-reconfiguration%2Findex.yml.cached
100084166 2014-12-24 10:46 admin_cache/https:%2F%2Fpublic.dhe.ibm.com%2Fibmdl%2Fexport%2Fpub%2Fsoftware%2Fwebsphere%2Fwasdev%2Fdownloads%2Fjre%2F1.7.1%2Flinux%2Fibm-java-jre-7.1-1.1-x86_64-archive.bin.cached
71618 2014-12-24 10:44 admin_cache/https:%2F%2Fwww14.software.ibm.com%2Fcgi-bin%2Fweblap%2Flap.pl?la_formnum=&li_formnum=L-EWOD-99YA4J&title=IBM%C2%AE+SDK%2C+Java+Technology+Edition%2C+Version+7+Release+1&l=en.cached
1437795 2014-12-24 10:47 admin_cache/https:%2F%2Fdownload.run.pivotal.io%2Fauto-reconfiguration%2Fauto-reconfiguration-1.5.0_RELEASE.jar.cached
60487 2014-12-24 10:43 admin_cache/https:%2F%2Fpublic.dhe.ibm.com%2Fibmdl%2Fexport%2Fpub%2Fsoftware%2Fwebsphere%2Fwasdev%2Fdownloads%2Fwlp%2F8.5.5.4%2Flafiles%2Fruntime%2Fen.html.cached

Any idea how to fix this problem?

Many thanks.

Currently, the Go CLI doesn't support manifests.

This buildpack requires license keys to be set in the manifest file - in fact the buildpack silently fails with "Application failed to stage" if the values are not set correctly. Since there is also no way to set the env vars when the application is pushed, this buildpack cannot be used with the Go CLI.

Support for two-phase commit global transactions is disabled for applications running on a Liberty Profile server running in a Cloud Foundry environment. There is not a mechanism for the Liberty Profile to perform transaction recovery when running in a Cloud Foundry environment.

Rubocop should be updated and tests run on 2.2.4 only as 1.9 is deprecated.

Hi,
I'm struggling with getting the liberty buildpack fully functional within our intranet. I have followed the instructions in docs/util-repositories.md, the jre and wlp runtime are getting downloaded from my internal repo, but the deployments are still failing when trying to find the wlp features listed in the server.xml:

-----> Downloaded app package (4.7M)
-----> Downloading IBM 1.7.0 JRE from http://chrav012.swissre.com/images/Pivotal_Software/buildpacks/ibm/jre/ibm-java-jre-7.0-5.0-x86_64-archive.bin (1.0s)
Expanding JRE to .java (15.2s)
Downloading from http://chrav012.swissre.com/images/Pivotal_Software/buildpacks/ibm/wlp/8.5.5.2/wlp-developers-runtime-8.5.5.2.jar ... (0.5s).
Installing archive ... (1.0s).
E, [2014-05-15T12:47:25.359915 #50] ERROR -- /var/vcap/data/dea_next/admin_buildpacks/7f537c32-ec1e-4da1-833f-8e42bb338995_fd5a4d6e0fd8b9c9fca559aae7f904e567f9b41d/lib/liberty_buildpack/buildpack.rb:46:in `rescue in drive_buildpack_with_logger': Compile failed with exception #<RuntimeError: could not install required features, output is CWWKF1203E: Unable to obtain the following features: [webProfile-6.0]

could not install required features, output is CWWKF1203E: Unable to obtain the following features: [webProfile-6.0]
/var/vcap/packages/dea_next/buildpacks/lib/installer.rb:19:in compile': Buildpack compilation step failed: (RuntimeError) from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:74:inblock in compile_with_timeout'
from /usr/lib/ruby/1.9.1/timeout.rb:68:in timeout' from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:73:incompile_with_timeout'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:54:in block in stage_application' from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:50:inchdir'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:50:in stage_application' from /var/vcap/packages/dea_next/buildpacks/bin/run:10:in

'

FAILED
Server error, status code: 400, error code: 170001, message: Staging error: cannot get instances since staging failed

Attempting to follow the instructions from
https://www.ibmdw.net/wasdev/docs/deploying-application-liberty-profile-cloud-foundry/

I get:

➜  ServletSample  pwd
/Users/andyp/Development/cloudfoundry/liberty/wlp/usr/servers/ServletSample
➜  ServletSample  more manifest.yml

---
applications:
- name: apliberty
  env:
    IBM_JVM_LICENSE: <valid string>
    IBM_LIBERTY_LICENSE: <valid string>
➜  ServletSample  cf push --buildpack https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack.git
Using manifest file manifest.yml

Instances> 1

1: 128M
2: 256M
3: 512M
4: 1G
Memory Limit> 3

Creating apliberty... OK

1: apliberty
2: none
Subdomain> apliberty

1: cfapps.io
2: mqttbridge.com
3: thisweekincf.com
4: none
Domain> cfapps.io

Binding apliberty.cfapps.io to apliberty... OK
Uploading apliberty... OK
Preparing to start apliberty... OK
-----> Downloaded app package (108K)
Initialized empty Git repository in /tmp/buildpacks/ibm-websphere-liberty-buildpack.git/.git/
Checking status of app 'apliberty'...Application failed to stage
➜  ServletSample

Extra investigation needed to properly address this issue.

There seems to be a regression of function. We added the capability to push jar files to the Liberty buildpack,

See logs below
C:\Users\IBM_ADMIN>cf login -a http://api.run.pivotal.io
API endpoint: http://api.run.pivotal.io
Warning: Insecure http API endpoint detected: secure https API endpoints are recommended

Email> [email protected]

Password>
Authenticating...
OK

Targeted org kelapure-personal

Select a space (or press enter to skip):

1. development
2. staging
3. production
4. helloworld
5. test

Space> 1
Targeted space development

API endpoint: http://api.run.pivotal.io (API version: 2.4.0)
User: [email protected]
Org: kelapure-personal
Space: development

C:\Users\IBM_ADMIN>cf push standalone -p c:\yi\samples\standalone\export\hello-spring.jar --no-route
Creating app standalone in org kelapure-personal / space development as [email protected]...
OK

App standalone is a worker, skipping route creation
Uploading standalone...
Uploading app files from: c:\yi\samples\standalone\export\hello-spring.jar
Uploading 2.5K, 6 files
OK

Starting app standalone in org kelapure-personal / space development as [email protected]...
OK
-----> Downloaded app package (4.0K)
-----> Java Buildpack Version: v2.1.2 | https://github.com/cloudfoundry/java-buildpack.git#074fd9a
-----> Downloading Open Jdk JRE 1.7.0_55 from http://download.run.pivotal.io/openjdk/lucid/x86_64/openjdk-1.7.0_55.tar.gz (0.4s)
Expanding Open Jdk JRE to .java-buildpack/open_jdk_jre (1.3s)

-----> Uploading droplet (31M)

0 of 1 instances running, 1 starting
1 of 1 instances running

App started

Showing health and status for app standalone in org kelapure-personal / space development as [email protected]...
OK

requested state: started
instances: 1/1
usage: 1G x 1 instances
urls:

 state     since                    cpu    memory        disk

#0 running 2014-05-30 01:09:07 AM 0.0% 13.9M of 1G 88M of 1G

C:\Users\IBM_ADMIN>
C:\Users\IBM_ADMIN>cf delete standalone

Really delete the app standalone?>> y
Deleting app standalone in org kelapure-personal / space development as [email protected]...
OK

C:\Users\IBM_ADMIN>cf buildpacks
Getting buildpacks...

buildpack position enabled locked filename
ruby_buildpack 1 true false buildpack_ruby_v46-245-g2fc4ad8.zip
nodejs_buildpack 2 true false buildpack_nodejs_v8-177-g2b0a5cf.zip
java_buildpack 3 true false java-buildpack-v2.1.2.zip
go_buildpack 4 true false buildpack_go_cf-v1-4-geeb56b9.zip
liberty_buildpack 5 true false liberty_buildpack.zip

C:\Users\IBM_ADMIN>cf push standalone -p c:\yi\samples\standalone\export\hello-spring.jar --no-route -b liberty_buildpack
Creating app standalone in org kelapure-personal / space development as [email protected]...
OK

App standalone is a worker, skipping route creation
Uploading standalone...
Uploading app files from: c:\yi\samples\standalone\export\hello-spring.jar
Uploading 2.5K, 6 files
OK

Starting app standalone in org kelapure-personal / space development as [email protected]...
OK
-----> Downloaded app package (4.0K)
-----> Downloading IBM 1.7.0 JRE from http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/jre/1.7.0/linux/ibm-java-jre-7.0-5.0-x86_64-archive.bin (0.0s)
Expanding JRE to .java (15.2s)
-----> Uploading droplet (85M)

0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 failing
FAILED
Start unsuccessful

TIP: use 'cf logs standalone --recent' for more information

C:\Users\IBM_ADMIN>
C:\Users\IBM_ADMIN>
C:\Users\IBM_ADMIN>cf logs standalone --recent
Connected, dumping recent logs for app standalone in org kelapure-personal / space development as [email protected]...

2014-05-30T01:11:25.59-0400 [API] OUT Created app with guid 431c698d-5d24-4fb6-9163-1e6f3d908322
2014-05-30T01:11:40.35-0400 [DEA] OUT Got staging request for app with id 431c698d-5d24-4fb6-9163-1e6f3d908322
2014-05-30T01:11:41.59-0400 [API] OUT Updated app with guid 431c698d-5d24-4fb6-9163-1e6f3d908322 ({"state"=>"STARTED"})
2014-05-30T01:11:41.70-0400 [STG] OUT -----> Downloaded app package (4.0K)
2014-05-30T01:11:42.05-0400 [STG] OUT -----> Downloading IBM 1.7.0 JRE from http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/jre/1.7.0/linux/ibm-java-jre-7.0-5.0-x86_64-archive.bin (0.0s)
2014-05-30T01:11:57.31-0400 [STG] OUT Expanding JRE to .java (15.2s)
2014-05-30T01:12:07.90-0400 [STG] OUT -----> Uploading droplet (85M)
2014-05-30T01:12:20.64-0400 [DEA] OUT Starting app instance (index 0) with guid 431c698d-5d24-4fb6-9163-1e6f3d908322
2014-05-30T01:12:25.23-0400 [App/0] ERR Error: Could not find or load main class HelloWorld
2014-05-30T01:12:25.24-0400 [App/0] OUT
2014-05-30T01:12:25.32-0400 [API] OUT App instance exited with guid 431c698d-5d24-4fb6-9163-1e6f3d908322 payload: {"cc_partition"=>"default", "droplet"=>"431c698d-5d24-4fb6-9163-1e6f3d908322", "version"=>"2f667b5b-0915-43f6-8db8-7ae26e77052d", "instance"=>"d8de9df3fe0f477d9871318757c632a4", "index"=>0, "reason"=>"CRASHED", "exit_status"=>1, "exit_description"=>"app instance exited", "crash_timestamp"=>1401426745}
2014-05-30T01:13:08.45-0400 [DEA] OUT Starting app instance (index 0) with guid 431c698d-5d24-4fb6-9163-1e6f3d908322
2014-05-30T01:13:16.06-0400 [App/0] ERR Error: Could not find or load main class HelloWorld
2014-05-30T01:13:16.16-0400 [API] OUT App instance exited with guid 431c698d-5d24-4fb6-9163-1e6f3d908322 payload: {"cc_partition"=>"default", "droplet"=>"431c698d-5d24-4fb6-9163-1e6f3d908322", "version"=>"2f667b5b-0915-43f6-8db8-7ae26e77052d", "instance"=>"23ed3b18fc3d4ed7951160e15d3f0f40", "index"=>0, "reason"=>"CRASHED", "exit_status"=>1, "exit_description"=>"app instance exited", "crash_timestamp"=>1401426796}
2014-05-30T01:13:47.87-0400 [DEA] OUT Starting app instance (index 0) with guid 431c698d-5d24-4fb6-9163-1e6f3d908322
2014-05-30T01:13:53.36-0400 [App/0] ERR Error: Could not find or load main class HelloWorld
2014-05-30T01:13:53.43-0400 [API] OUT App instance exited with guid 431c698d-5d24-4fb6-9163-1e6f3d908322 payload: {"cc_partition"=>"default", "droplet"=>"431c698d-5d24-4fb6-9163-1e6f3d908322", "version"=>"2f667b5b-0915-43f6-8db8-7ae26e77052d", "instance"=>"7c0a666f22a54191a698a277909414d4", "index"=>0, "reason"=>"CRASHED", "exit_status"=>1, "exit_description"=>"app instance exited", "crash_timestamp"=>1401426833}
2014-05-30T01:14:27.76-0400 [DEA] OUT Starting app instance (index 0) with guid 431c698d-5d24-4fb6-9163-1e6f3d908322
2014-05-30T01:14:35.04-0400 [App/0] ERR Error: Could not find or load main class HelloWorld
2014-05-30T01:14:35.11-0400 [API] OUT App instance exited with guid 431c698d-5d24-4fb6-9163-1e6f3d908322 payload: {"cc_partition"=>"default", "droplet"=>"431c698d-5d24-4fb6-9163-1e6f3d908322", "version"=>"2f667b5b-0915-43f6-8db8-7ae26e77052d", "instance"=>"83a198d1ec0f4c36890d51e4cec2d49d", "index"=>0, "reason"=>"CRASHED", "exit_status"=>1, "exit_description"=>"app instance exited", "crash_timestamp"=>1401426875}
2014-05-30T01:15:37.78-0400 [DEA] OUT Starting app instance (index 0) with guid 431c698d-5d24-4fb6-9163-1e6f3d908322
2014-05-30T01:15:46.58-0400 [App/0] ERR Error: Could not find or load main class HelloWorld
2014-05-30T01:15:46.68-0400 [API] OUT App instance exited with guid 431c698d-5d24-4fb6-9163-1e6f3d908322 payload: {"cc_partition"=>"default", "droplet"=>"431c698d-5d24-4fb6-9163-1e6f3d908322", "version"=>"2f667b5b-0915-43f6-8db8-7ae26e77052d", "instance"=>"4d1279496d56471881c9e4e69e4eec46", "index"=>0, "reason"=>"CRASHED", "exit_status"=>1, "exit_description"=>"app instance exited", "crash_timestamp"=>1401426946}

This can be reproduced using any valid jar file with a valid manifest with a main-class entry.

/var/vcap/data/dea_next/admin_buildpacks/835c0bc0-b348-483e-b6b7-fba1a13b5eee_81ed6c377b313491ee3656bb8eae39b3ad8a74cf/lib/liberty_buildpack/buildpack.rb:50:in `rescue in drive_buildpack_with_logger': Compile failed with exception #<RuntimeError: No supported application type was detected>

the artifactory location is bmd-libs-snapshot-local/bluemix-mobile-services/bms-mqa/bms-mqa-56dce57d5fc821698f229cd7c009095e9dc810f6.zip
The zip contains a .war and other files.

The new dynatraceagent.yml contains repository_root: "" which breaks download_buildpack_cache.rb because it tries to download the file /index.yml.

I think we can fix it at https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack/blob/master/resources/download_buildpack_cache.rb#L175

The available documentation suggests the customization capability of the Java buildpack is not present for the IBM JRE or Open JRE as included here, specifically we are looking for the ability to add the unlimited JCE strength and custom CA certificates to the IBM JRE.

The license util can throw a NoMethodError (<NoMethodError: undefined method `first' for nil:NilClass>) if the license can not be read. Additional check needed to prevent the error and gracefully raise an error if a the license can't be read.

I'm unable to deploy any application using the buildpack. The staging process keeps timing out. After turning on the debugging (JBP_LOG_LEVEL=DEBUG) I see that the buildpack keeps looping calling cache_ready? on a license file:

D, [2014-07-21T13:23:55.801831 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:221:in `cache_ready?': should_use_cache for http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html, inputs: use_internet? = true, cached? = false, has_etag? = false, has_last_modified? = false
D, [2014-07-21T13:23:55.802061 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:221:in `cache_ready?': should_use_cache for http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html, inputs: use_internet? = true, cached? = false, has_etag? = false, has_last_modified? = false
D, [2014-07-21T13:23:55.990852 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:148:in `block in download': Download of http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html gave response 200
D, [2014-07-21T13:23:56.233237 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:221:in `cache_ready?': should_use_cache for http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html, inputs: use_internet? = true, cached? = true, has_etag? = false, has_last_modified? = true
D, [2014-07-21T13:23:56.233385 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:243:in `up_to_date_check': Performing up-to-date check on cached version of http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html
D, [2014-07-21T13:23:56.317588 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:251:in `block in up_to_date_check': Up-to-date check on cached version of http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html returned 200
D, [2014-07-21T13:23:56.317781 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:221:in `cache_ready?': should_use_cache for http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html, inputs: use_internet? = true, cached? = true, has_etag? = false, has_last_modified? = true
D, [2014-07-21T13:23:56.317875 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:243:in `up_to_date_check': Performing up-to-date check on cached version of http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html
D, [2014-07-21T13:23:56.402040 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:251:in `block in up_to_date_check': Up-to-date check on cached version of http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html returned 200
D, [2014-07-21T13:23:56.589696 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:148:in `block in download': Download of http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html gave response 200
D, [2014-07-21T13:23:56.832661 #88] DEBUG -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/cache/download_cache.rb:221:in `cache_ready?': should_use_cache for http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.2/lafiles/runtime/en.html, inputs: use_internet? = true, cached? = true, has_etag? = false, has_last_modified? = true

And so on...

I think the basic problem is that up_to_date_check() in download_cache() can return HTTP_OK if the server doesn't support If-Modified-Since header.

Symptom: When running the liberty detect script in the current directory and WEB-INF/lib/spring-core-3.1.2.RELEASE.jar is present in the application, a NoMethodError results.

$ ~/git/ibm-websphere-liberty-buildpack/bin/detect . /tmp
1.9.3-545
E, [2014-06-17T17:51:04.156018 #25555] ERROR -- /home/pat/git/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/buildpack.rb:50:in rescue in drive_buildpack_with_logger': Detect failed with exception #<NoMethodError: undefined methodgsub' for nil:NilClass> undefined method `gsub' for nil:NilClass

Issue: The 'WEB-INF' case of FrameworkUtils.find depends on at least one item being found by the scan of the pathname. When the current directory is named '.', the regular expression doesn't identify it as a string. The Spring auto-reconfiguration detect code triggers a 0-item list. When no item is present, gsub is called on nil, leading to the NoMethodException.
match = [path.scan(/.*\w+#{Regexp.quote(app_type)}/)[0].gsub('/WEB-INF', '')]

Proposed (and tested) resolution:
Replace this line:
match = [path.scan(/.\w+#{Regexp.quote(app_type)}/)[0].gsub('/WEB-INF', '')]
with these two lines:
match = path.scan(/.\w+#{Regexp.quote(app_type)}/)
match = match.length > 0 ? [match[0].gsub('/WEB-INF', '')] : [app_dir]

I will create a pull request for this change.

Pat Morrison

I am pushing a Spring Boot application built as a war using the Liberty buildpack and recieve the following exception when the application starts. The same war file works fine using the Cloud Foundry Java Buildpack

    2014-07-18T15:48:20.90-0400 [App/0]   OUT 2014-07-18 19:48:20.907 ERROR 33 --- [ost-startStop-1] org.apache.catalina.loader.WebappLoader  : LifecycleException 
    2014-07-18T15:48:20.90-0400 [App/0]   OUT java.io.IOException: Failed to access resource /WEB-INF/lib/spring-auto-reconfiguration-1.4.0_RELEASE.jar
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.catalina.loader.WebappLoader.setRepositories(WebappLoader.java:981)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.catalina.loader.WebappLoader.startInternal(WebappLoader.java:604)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5332)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at java.lang.Thread.run(Thread.java:781)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT Caused by: javax.naming.NameNotFoundException: Resource spring-auto-reconfiguration-1.4.0_RELEASE.jar not found
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.naming.resources.BaseDirContext.lookup(BaseDirContext.java:498)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   at org.apache.catalina.loader.WebappLoader.setRepositories(WebappLoader.java:979)
    2014-07-18T15:48:20.90-0400 [App/0]   OUT   ... 11 common frames omitted

Liberty profile supports 2PC transactions and the JCA spec (since 8.5.5.2). The WebSphere Liberty Profile deliberately sets -Dcom.ibm.tx.jta.disable2PC=true because Cloud Foundry containers lack persistent disk support. This custom system property disables support for two phase commit in distributed global transactions; however Liberty allows writing transaction logs to an external DB instead to the local file system .see.

With this approach the app in the container is stateless. The state (transaction log) is managed in a external db.

The JVM property can be set via the manifest.xml file.

      env:
        ...
        JVM: openjdk
        JAVA_OPTS: "-Dcom.ibm.tx.jta.disable2PC=false"
        JVM_ARGS: "-Dcom.ibm.tx.jta.disable2PC=false" 

With these two modifications JTA 2PC works with apps running in the Liberty Profile.

1. Is this supported in Bluemix ?
2. Should the disable2PC property be removed in the Liberty buildpack ?

@jgawor

If the build pack configuration adds a jvm option that is already set in the jvm.option file, the jvm option is duplicated.

I have seen multiple requests for the ability to configure JVM command line options when pushing jar/war/ear files.

We have a java_opts framework. I just looked at this and it is out-of-date as we expect. It does not have the capability of applying JVM options from the JAVA_OPTS environment variable set.

Can we sync up our java_opts framework with the java-buildpack one and ensure it works with our jvm.options capability for server packages

Add support for auto wiring for compose services such as postgresql and mongo.

What configuration changes are required so that Liberty will send all of its logs (SystemOut, SystemErr, trace, etc.) to stdout/stderr so they can be routed out of CF environment using loggregator?

Where would configuration changes be made to increase the logging levels?

Tks!

The top level readme references the license for Liberty 8.5.5.5 but the buildpack is now pulling 8.5.5.6 by default.

In standalone Liberty, the user has two models to choose from when they develop esas for user feattures. They can develop esas that get installed into wlp/etc/extensions or they can develop esas that get installed into the default location of wlp/usr/extension. In the Liberty buildpack, we require them to use the second model, we don't document that anywhere. The documentation for install and usage of user features in a buildpack needs to be fixed.

The ibm-buildpack can quite easily be used to drive a simple Java Main or DistZip-based microservice using the IBM JRE. When the user isn't using the Liberty runtime it seems strange to always output this warning if they stray below 512M?

    # Prints a warning message if a memory limit of less than 512M has been chosen when using the IBM JDK.
    def check_memory
      mem_limit = MemoryLimit.memory_limit
      unless mem_limit.nil?
        if mem_limit < MemorySize.new('512M')
          puts '-----> Avoid Trouble: Specify a minimum of 512M as the Memory Limit for your apps when using IBM JDK.'
        end
      end
    end

Hi,

We are running into below issue when we are using offline buildpack. please help.

Starting app test in org testorg / space TestDev as testuser...
OK
-----> Downloaded app package (25M)
-----> Liberty Buildpack Version: unknown
-----> Downloading IBM 1.7.1_1 JRE from http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/jre/1.7.1/linux/ibm-java-jre-7.1-1.1-x86_64-archive.bin ... (0.0s)
Expanding JRE to .java ... (11.5s)
-----> Downloading Auto Reconfiguration 1.5.0_RELEASE from https://download.run.pivotal.io/auto-reconfiguration/auto-reconfiguration-1.5.0_RELEASE.jar (0.0s)
Modifying /WEB-INF/web.xml for Auto Reconfiguration
-----> Downloading from http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.3/wlp-developers-runtime-8.5.5.3.jar ... (0.0s)
Installing archive ... (0.7s)

FAILED
Server error, status code: 400, error code: 170001, message: Staging error: cannot get instances since staging failed

TIP: use 'cf logs test --recent' for more information

2014-10-22T13:43:04.56-0400 [API] OUT Created app with guid e4588800-734a-493e-aed4-59e2fdcb86ca
2014-10-22T13:43:04.73-0400 [API] OUT Updated app with guid e4588800-734a-493e-aed4-59e2fdcb86ca ({"route"=>"fb9e2f9b-bcb6-4ba6-92d8-b560b1710d92"})
2014-10-22T13:43:11.45-0400 [DEA] OUT Got staging request for app with id e4588800-734a-493e-aed4-59e2fdcb86ca
2014-10-22T13:43:16.20-0400 [API] OUT Updated app with guid e4588800-734a-493e-aed4-59e2fdcb86ca ({"state"=>"STARTED"})
2014-10-22T13:43:16.56-0400 [STG] OUT -----> Downloaded app package (25M)
2014-10-22T13:43:16.95-0400 [STG] OUT -----> Liberty Buildpack Version: unknown
2014-10-22T13:43:16.96-0400 [STG] OUT -----> Downloading IBM 1.7.1_1 JRE from http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/jre/1.7.1/linux/ibm-java-jre-7.1-1.1-x86_64-archive.bin ... (0.0s)
2014-10-22T13:43:28.56-0400 [STG] OUT Expanding JRE to .java ... (11.5s)
2014-10-22T13:43:28.57-0400 [STG] OUT -----> Downloading Auto Reconfiguration 1.5.0_RELEASE from https://download.run.pivotal.io/auto-reconfiguration/auto-reconfiguration-1.5.0_RELEASE.jar (0.0s)
2014-10-22T13:43:28.58-0400 [STG] OUT Modifying /WEB-INF/web.xml for Auto Reconfiguration
2014-10-22T13:43:28.59-0400 [STG] OUT -----> Downloading from http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/8.5.5.3/wlp-developers-runtime-8.5.5.3.jar ... (0.0s)
2014-10-22T13:43:29.36-0400 [STG] OUT Installing archive ... (0.7s)
2014-10-22T13:46:40.51-0400 [STG] ERR E, [2014-10-22T17:46:40.518180 #50] ERROR -- /var/vcap/data/dea_next/admin_buildpacks/8ae20f5a-f606-4069-9298-3b2f6877b036_4c7fc82ce3d737697097a6af35224e3972208be9/lib/liberty_buildpack/buildpack.rb:48:in `rescue in drive_buildpack_with_logger': Compile failed with exception #<RuntimeError: could not install required features, output is CWWKF1203E: Unable to obtain the following features: [jdbc-4.0, managedBeans-1.0, jpa-2.0, jsf-2.0, jsp-2.2, jaxrs-1.1, servlet-3.0, jndi-1.0, cdi-1.0, ejbLite-3.1]
2014-10-22T13:46:40.51-0400 [STG] ERR >
2014-10-22T13:46:40.51-0400 [STG] ERR could not install required features, output is CWWKF1203E: Unable to obtain the following features: [jdbc-4.0, managedBeans-1.0, jpa-2.0, jsf-2.0, jsp-2.2, jaxrs-1.1, servlet-3.0, jndi-1.0, cdi-1.0, ejbLite-3.1]
2014-10-22T13:46:40.52-0400 [STG] OUT Staging failed: Buildpack compilation step failed
2014-10-22T13:46:40.62-0400 [API] ERR Encountered error: Staging error: failed to stage application:
2014-10-22T13:46:40.62-0400 [API] ERR Script exited with status 1

extended features enabled via configDropins do not install

This issue can be recreated by pushing the server package in the Liberty sample at https://developer.ibm.com/wasdev/downloads/#view/5358e03ec698647e66000012.

The error appears to be:
CWWKF1015E: The file /tmp/staged/app/.liberty/dev/api/spec/com.ibm.ws.javaee.jaxws.2.2_1.0.2.cl50220140403-1858.jar already exists.

Full error message:
E, [2014-07-03T18:42:04.562711 #88] ERROR -- /tmp/buildpacks/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/buildpack.rb:46:in rescue in drive_buildpack_with_logger': Compile failed with exception #<RuntimeError: could not install required features, output is The --acceptLicense argument was found. This indicates that you haveaccepted the terms of the license agreement.CWWKF1015E: The file /tmp/staged/app/.liberty/dev/api/spec/com.ibm.ws.javaee.jaxws.2.2_1.0.2.cl50220140403-1858.jar already exists.>could not install required features, output is The --acceptLicense argument wasfound. This indicates that you haveaccepted the terms of the license agreement.CWWKF1015E: The file /tmp/staged/app/.liberty/dev/api/spec/com.ibm.ws.javaee.jaxws.2.2_1.0.2.cl50220140403-1858.jar already exists./var/vcap/packages/dea_next/buildpacks/lib/installer.rb:19:incompile': Buildpack compilation step failed: (RuntimeError)
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:74:in block in compile_with_timeout' from /usr/lib/ruby/1.9.1/timeout.rb:68:intimeout'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:73:in compile_with_timeout' from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:54:inblock in stage_application'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:50:in chdir' from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:50:instage_application'
from /var/vcap/packages/dea_next/buildpacks/bin/run:10:in `'

FAILED
Server error, status code: 400, error code: 170001, message: Staging error: cann
ot get instances since staging failed

The document, https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack/blob/master/docs/restrictions.md, describes security configuration based on the ssl-1.0 feature. This needs to be updated to reflect the latest recommendation, https://developer.ibm.com/answers/questions/16016/how-do-i-enforce-ssl-for-my-bluemix-application/

The link pointing to the Cloud Foundry service variable specification (http://docs.cloudfoundry.com/docs/using/services/spring-service-bindings.html#properties) is outdated. Cloud Foundry is redirecting to a generic deprecation notice.

Hi,

I am trying to package the ibm liberty buildpack for my offline local cf deployment. I am following the https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack/blob/master/docs/installation.md to do this. I am getting the following error on issuing the command - bundle exec rake package

Using /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack-v0.1.0-289-g075aa62.zip as a buildpack zip output file
Caching files hosted on public.dhe.ibm.com
D, [2014-11-13T14:49:01.002721 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/logging.yml
D, [2014-11-13T14:49:01.003037 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/javaopts.yml
D, [2014-11-13T14:49:01.003307 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/openjdk.yml
D, [2014-11-13T14:49:01.003955 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/ibmjdk.yml
D, [2014-11-13T14:49:01.004102 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/components.yml
D, [2014-11-13T14:49:01.004261 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/liberty.yml
D, [2014-11-13T14:49:01.004476 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/env.yml
D, [2014-11-13T14:49:01.004573 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/cache.yml
D, [2014-11-13T14:49:01.004676 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/springautoreconfiguration.yml
D, [2014-11-13T14:49:01.004863 #6851] DEBUG -- : Checking /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/config/licenses.yml
D, [2014-11-13T14:49:01.005055 #6851] DEBUG -- : Downloading file to /tmp/d20141113-6851-1kop6yq/ibm-websphere-liberty-buildpack/admin_cache/https:%2F%2Fpublic.dhe.ibm.com%2Fibmdl%2Fexport%2Fpub%2Fsoftware%2Fwebsphere%2Fwasdev%2Fdownloads%2Fjre%2Findex.yml.cached
rake aborted!
undefined method keys' for #<String:0x00000001219c28> /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/resources/download_buildpack_cache.rb:55:inblock in download_cache'
/home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/resources/download_buildpack_cache.rb:43:in each' /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/resources/download_buildpack_cache.rb:43:indownload_cache'
/home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/Rakefile:100:in block (2 levels) in <top (required)>' /home/casa/liberty-buildpack/ibm-websphere-liberty-buildpack/Rakefile:83:inblock in <top (required)>'

PS: I did the same thing on the same machine a day before, the packaging and deployment was working fine. The problem started happening when I repeated the same packaging steps with a new clone today.

Hi,

jrebel 6.4.2a prevents this buildpack build. I tried to disable the repository in jrebelagent.yml , but it doesnt work. Since the buildpack stores the cached yml in /tmp location. I am not able to remove the latest version as well.

rake aborted!
Invalid micro version '2a'
/tmp/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/tokenized_version.rb:99:in micro_and_qualifier' /tmp/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/util/tokenized_version.rb:38:ininitialize'
/tmp/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/repository/version_resolver.rb:42:in new' /tmp/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/repository/version_resolver.rb:42:inblock in resolve'
/tmp/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/repository/version_resolver.rb:41:in map' /tmp/ibm-websphere-liberty-buildpack/lib/liberty_buildpack/repository/version_resolver.rb:41:inresolve'
/tmp/ibm-websphere-liberty-buildpack/resources/download_buildpack_cache.rb:59:in block in download_cache' /tmp/ibm-websphere-liberty-buildpack/resources/download_buildpack_cache.rb:47:ineach'
/tmp/ibm-websphere-liberty-buildpack/resources/download_buildpack_cache.rb:47:in download_cache' /tmp/ibm-websphere-liberty-buildpack/Rakefile:95:inblock (2 levels) in <top (required)>'
/tmp/ibm-websphere-liberty-buildpack/Rakefile:78:in block in <top (required)>' /usr/local/rvm/gems/ruby-1.9.3-p545/bin/ruby_executable_hooks:15:ineval'
/usr/local/rvm/gems/ruby-1.9.3-p545/bin/ruby_executable_hooks:15:in `

Hi ,

I am trying to deploy app with offline ibm websphere buildpack. I have created offline buildpack (followed steps mentioned here https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack/blob/master/docs/installation.md) but running into below issue:

2014-09-30T15:44:45.37-0400 [STG] OUT -----> Downloaded app package (25M)
2014-09-30T15:44:45.65-0400 [STG] OUT -----> Liberty Buildpack Version: unknown
2014-09-30T15:44:45.65-0400 [STG] OUT -----> Downloading IBM 1.7.1_1 JRE from http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/jre/1.7.1/linux/ibm-java-jre-7.1-1.1-x86_64-archive.bin ... (0.0s)
2014-09-30T15:44:56.91-0400 [STG] OUT Expanding JRE to .java ... (11.2s)
2014-09-30T15:45:46.93-0400 [STG] ERR E, [2014-09-30T19:45:46.935317 #50] ERROR -- /var/vcap/data/dea_next/admin_buildpacks/d3634ab1-cfeb-4699-b1e7-423b24a7b6cb_6702bf2138d8ce48c4c04e7d954d6fb2716d66f3/lib/liberty_buildpack/util/cache/buildpack_stash.rb:61:in look_aside': Buildpack cache does not contain https://download.run.pivotal.io/auto-reconfiguration/index.yml 2014-09-30T15:45:46.93-0400 [STG] ERR E, [2014-09-30T19:45:46.935628 #50] ERROR -- /var/vcap/data/dea_next/admin_buildpacks/d3634ab1-cfeb-4699-b1e7-423b24a7b6cb_6702bf2138d8ce48c4c04e7d954d6fb2716d66f3/lib/liberty_buildpack/buildpack.rb:48:inrescue in drive_buildpack_with_logger': Compile failed with exception #<RuntimeError: Buildpack cache does not contain https://download.run.pivotal.io/auto-reconfiguration/index.yml>
2014-09-30T15:45:46.93-0400 [STG] ERR Buildpack cache does not contain https://download.run.pivotal.io/auto-reconfiguration/index.yml
2014-09-30T15:45:46.94-0400 [STG] OUT Staging failed: Buildpack compilation step failed
2014-09-30T15:45:47.04-0400 [API] ERR Encountered error: Staging error: failed to stage application:
2014-09-30T15:45:47.04-0400 [API] ERR Script exited with status 1

please help!!!

When deploying Liberty packaged server into Bluemix and using ElephantSQL (PostgreSQL) JDBC the autowiring updates database connection properties, but fails to find proper JDBC driver in the library. See this post for more details: http://stackoverflow.com/questions/39370482/cant-find-valid-jdbc-driver-when-deploying-liberty-app-in-bluemix-with-elephant

Hi,

Using the repository.root variable in mongo.yml throws an exception. It would be practical to use this variable in all configuration files.

config line: client_jar_url: ! '{default.repository.root}/mongodb/2.13.3/mongo-java-driver-2.13.3.jar'

Failing with:

Installing archive ... (1.0s)
E, 2016-04-17T14:51:14.849569 #14 ERROR – /tmp/buildpacks/5ff2ca7f7e3f4422b1d4e131cbc34544/lib/liberty_buildpack/buildpack.rb:50:in `rescue in drive_buildpack_with_logger': Compile failed with exception #<URI::InvalidURIError: bad URI(is not URI?
):
{default.repository.root}/mongodb/2.13.3/mongo-java-driver-2.13.3.jar>
bad URI(is not URI?): {default.repository.root}
/mongodb/2.13.3/mongo-java-driver-2.13.3.jar
Failed to compile droplet
-----> Retrieving and installing client jar(s) from mongo-java-driver-2.13.3.jar Exit status 223

Best regards,
Murat