brad,
first, its fun playing around with box. now I want to make the start up time faster. its currently taking roughly 50 seconds.
Is that normal?
No, that’s waay slow. Check your antivirus program. Should be well less than 10 seconds depending on how fast your computer is.
Usually, when box is taking a while to start, if you look in your task manager and sort the processes by CPU descending, you’ll see something like “Windows Defender” or “McAfee Antivirus” at the top of the list churning away. Make sure they’re not set to inspect archive files (zips, jars, etc) or set an exception on your CommandBox home folder.
Oh, and if you have a JDK installed, grab the jstack binary from java’s bin folder and you can grab a stack trace of exactly what box is doing.
$> jstack -l
Where is the process ID of the box.exe process.
Its McAfee. Getting an exception .for Commandbox at work for this will be hard. Thanks Brad.
You might want to see what else is running. I’ve noticed slow start times when running GoToMeeting and also the screen sharing system through Blackboard. Need to remember to start the servers I need before class starts.
McAfee USUALLY only goes crazy the first time you start it. Once it scans the jars it won’t scan them again until you restart your machine. Or so I’ve seen in the past. If you open the McAfee window, you can usually see what file it’s currently scanning.
I am able to temporarily add an exception to McAfee, so I added “.CommandBox” home folder, but McAfee still spiked up in CPU.
I also can’t get the PID because while McAfee and box.exe are starting up, the command “tasklist” is super slow and prints results only 2 seconds before box is finished starting up.
Ok I was able to get PID on time and run “jstack” command but I get this error:
36248: Unable to attach to 32-bit process running under WOW64
36248 is the PID of box.exe