It's difficult to identify this without seeing the whole job and having a play, but this could be due to a number of things. Sometimes you get errors in the code like you have when a component's parameters are not populated properly. For example, a String param which is set to a literal that is not close (e.g. "My literal is not closed...). You can also end up with problems like this with tMaps when something has corrupted the tMap. The only way to solve that is to delete the tMap and add a new one and configure it.
Can you show us where the errors in the Java start (ie the first line they appear?). Can you also show us inside the tMap? We may be able to help a bit more with that info.
