-
15. Re: Running standalone - JBERET000601: Failed to get job xml file for job
This forClass() statement is a legacy requirement. With recent jdbc drivers, you shouldn't need that.
I just checked my mysql driver jar, which contains the following META-INF/service/java.sql.Driver declaration entry:
/Users/cfang/tmp > jar tvf mysql-connector-java-5.1.36-bin.jar
0 Fri Jun 19 21:26:20 EDT 2015 META-INF/
2008 Fri Jun 19 21:26:18 EDT 2015 META-INF/MANIFEST.MF
0 Fri Jun 19 21:26:20 EDT 2015 META-INF/services/
61 Fri Jun 19 21:26:20 EDT 2015 META-INF/services/java.sql.Driver
0 Fri Jun 19 21:25:52 EDT 2015 com/
0 Fri Jun 19 21:25:52 EDT 2015 com/mysql/
0 Fri Jun 19 21:25:58 EDT 2015 com/mysql/fabric/
761 Fri Jun 19 21:25:56 EDT 2015 com/mysql/fabric/FabricCommunicationException.class
This enables it to be auto discovered, without using any Class.forName().
Looks like your version of mysql jar is quite old. If possible, I suggest upgrading to more recent mysql client.
Otherwise, besides the forClass trick, another workaround is to use a sysprop: -D
jdbc.drivers=<driver class>. -
16. Re: Running standalone - JBERET000601: Failed to get job xml file for job
Thank you so much! That solved the problem.
-
17. Re: Running standalone - JBERET000601: Failed to get job xml file for job
> We were able to work out the path issue, and it was because of Eclipse.
How did you "work out" the path issue?
Remember other people may have the same problem. In the case, I have
-
18. Re: Running standalone - JBERET000601: Failed to get job xml file for job
Is the problem with the jobs path or the database driver?
-
19. Re: Running standalone - JBERET000601: Failed to get job xml file for job
The mysql jar I was using did not have the META-INF/service/java.sql.Driver in it. The batch jobs was not on the classpath, it was corrected by putting a resource folder with the META-INF/batch-jobs folder under it and put the resource folder as a source folder in the Eclipse Java Build Path.
