i'm new (well, super rusty) to commandbox. i'm try...
# box-products
j
i'm new (well, super rusty) to commandbox. i'm trying to set some jvm args but i don't think they're getting picked up. not sure how to troubleshoot this. does
server.json
at least look okay? https://gist.github.com/jamiejackson/96b83c3a83e9ac44a8d6a3699bf59ba5
@David Rogers, if you've tried luceedebug in commandbox, you might know this, btw.
i wanted to see about these windows paths.
d
I think we maybe have a server.json? but I just place agent args explicitly to the java invocation
small world ain't it
🙂 1
j
i normally run in docker (and set the luceedbug stuff in
setenv.sh
) but the windows drive letter case thing (or whatever that problem is) needs to be reproduced on a windows box directly. that's why i'm trying to spin it up in commandbox. but now commandbox is a can of worms because i haven't used it in so long.
also, i wasn't sure if the https://github.com/softwareCobbler/luceedebug/commit/2e1ff5771bbca9dc6050315b0a6b3837bd716f99 commit was intended to fix the windows pathing issues.
i figured it out. i thought i needed a
server.json
but it was
server-lucee@5.3.10.97.json
b
It sounds like you accidentally started up server at one point passing the cfengine in as the name
You probably typed something like Start lucee@5.3.10 Instead of Start cfengine=lucee@5.3.10
Which set the server name, and when you use an explicit name in the start command, we assume you want a custom server.json file by default.
You can forget your server, rename the json file to just server.json and run "start" to clean that up.
j
Yeah, I think you figured out the original issue. I eventually got it worked out to use a regular server.json
Happy new year!
👍 1