Sorry about this nullpointer exception. We need more debug info to pinpoint what's causing it. Put the attached file inside jAlbum's "tools" folder, thereby replacing the existing file there. Now try making and uploading albums in batch again. When you get a nullpointer exception this time, a triangle should show in jAlbum's lower right corner. Click it to reveal the full error details (aka "Stack trace"), and pass those details to me here.
When something like this happens, the question should always be, "what's different about the project that fails?" Take a look, for example, at the settings under Settings > Advanced > General. Are the settings on the failing project different from the others?
One of the things I do with my projects, there are many that are in groups relating to events and gatherings, is to import the settings from the relevant set so I can have a consistent look and feel and also use any common links or themes that run through various album groups, so almost all are very very similar, but I take that on board and shall have a look.
Meanwhile I shall do as David has requested and hopefully see something...
Just a hunch, based on an odd coincidence. I notice that the album that's failing to upload also happens to be open in the main Explore window. Try closing the project, then do the batch routine again.
I've been digging into the settings files for the uploads that fail vs. the ones that succeed, and I think I'm onto something.
Here's what I think I'm seeing. On the projects where it fails, the uploading account profile is MM. On the ones where it succeeds, it's New account.
So, open one of the failing projects, like GP-MK1. On the big Upload button at lower left, click the down arrow, and see which account is selected. If it's MM, try changing it to New account, or vice-versa. Save the project. Now try the batch mode again.
If I'm right about this, there's no need to fix all of the "wrong account" projects. Instead, you just need to go into Upload/Manage, and make the "bad" account profile settings match, exactly, the "good" account profile settings.
OK, I think I understand what's happening here, though it's tough to sort out. Some of your projects were saved with an uploading account of MM, but others were saved with an uploading account of New account.
When you're dealing with a project in the normal way, and you hit Upload, there's no problem. If the saved account name doesn't exist, the upload routine just uses the next one available - in your case, there is only one, so that's fine.
But in batch mode, it's apparently paying attention to the upload account name that was saved with the project. If it doesn't exist, it's stuck, and doesn't know what to do next.
How to fix? Well, batch mode could do what normal mode does, and just grab the next available uploading account. If there's only one uploading account profile, that would be safe. But for those with multiple accounts (like me), that could be disastrously wrong, so that's not a good idea. In normal mode it's safer, because you get a confirmation dialog before the upload actually happens. If the choice of uploading account is wrong, you have a chance to fix it. But in batch mode, it would just march ahead, no matter what.
In your case, I think the quickest fix is to create a new uploading account with the default New account name. Copy all of the settings from the MM account. I think batch mode will work after that.