AppD Archive

KeystoneJS application failed to start when running on Cloud Foundry?

CommunityUser
Splunk Employee
Splunk Employee

Hello everyone,

I work for IBM cloud division, we are currently delivering a rather large client application to production as a CloudFoundry application (IBM BlueMix). The application is a NodeJS application using the Keystone JS CMS framework (based on Node Express). When adding the appdynamics dependency and then adding the "require("appdynamics")..." line as the first call of the app entry file, we thought that we are good to go. Starting the app locally did not seem to cause any problems (except for the AppDynamics controller not detecting anything once the app was started, but that's a different story that does not concern me at this moment). But when we actually push our application to CloudFoundry using "cf push", the application failes to start up. The error message we get back is the following:

ERR [
2015-09-30T10:27:33.81+0200 [App/2]      ERR   {
2015-09-30T10:27:33.81+0200 [App/2]      ERR     "err": "TypeError: Cannot read property 'toLowerCase' of undefined\n    at /home/vcap/app/node_modules/keystone/node_modules/express/node_modules/send/node_modules/statuses/index.js:11:27\n    at Array.map (native)\n    at Object.<anonymous> (/home/vcap/app/node_modules/keystone/node_modules/express/node_modules/send/node_modules/statuses/index.js:7:35)\n at Module._compile (module.js:460:26)\n    at Object.Module._extensions..js (module.js:478:10)\n    at Module.load (module.js:355:32)\n    at Function.Module._load (module.js:310:12)\n    at Module.require (module.js:365:17)\n    at Module.newFunc (/home/vcap/app/node_modules/knj-plugin/lib/aspect.js:42:30)\n    at Module.obj.(anonymous function) [as require] (/home/vcap/app/node_modules/appdynamics/lib/core/proxy.js:214:22)",
2015-09-30T10:27:33.81+0200 [App/2]      ERR     "t": "30-08-2015 08:27:33.809"
2015-09-30T10:27:33.81+0200 [App/2]      ERR   }
2015-09-30T10:27:33.81+0200 [App/2]      ERR ]
...

We use the latest version of node and npm, as well as the lates version of AppDynamics.

Is this something that someone already saw? Any suggestions of why it might do this? Or even better, any idea as of how to solve this issue?

Thanks,

Michael

  

0 Karma
Get Updates on the Splunk Community!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

May 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

What's New in Splunk Observability Cloud and Splunk AppDynamics - May 2025

This month, we’re delivering several new innovations in Splunk Observability Cloud and Splunk AppDynamics ...