SEVERE *** ERROR *** com.glide.db.impex.JDBCProbeLoader

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2017 11:32 AM
Hi.. I am doing test load on a data source connection I made. I got the below error messages. I am not able to determine what is the root cause of the problem. I need help reviewing this error messages and allow me to identify the root of the problem.
worker.1 SEVERE *** ERROR *** com.glide.db.impex.JDBCProbeLoader
java.lang.NullPointerException
at com.glide.db.impex.JDBCProbeLoader.getAttributesFromFirstRecord(JDBCProbeLoader.java:401)
at com.glide.db.impex.JDBCProbeLoader.getAttributes(JDBCProbeLoader.java:264)
at com.glide.db.impex.AbstractLoader.createMap(AbstractLoader.java:286)
at com.glide.db.impex.AbstractLoader.load(AbstractLoader.java:158)
at com.glide.db.impex.AbstractLoader.startWork(AbstractLoader.java:140)
at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:123)
at com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:34)
at com.glide.worker.AbstractProgressWorker.start(AbstractProgressWorker.java:98)
at com.glide.processors.ImportProcessorWorker.startWorker(ImportProcessorWorker.java:311)
at com.glide.processors.ImportProcessorWorker.loadDataSource(ImportProcessorWorker.java:153)
at com.glide.processors.ImportProcessorWorker.startWork(ImportProcessorWorker.java:104)
at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:123)
at com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:34)
at com.glide.worker.BackgroundProgressJob.execute(BackgroundProgressJob.java:54)
at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:103)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:89)
at com.glide.schedule.GlideScheduleWorker.executeJob(GlideScheduleWorker.java:219)
at com.glide.schedule.GlideScheduleWorker.lambda$process$30(GlideScheduleWorker.java:161)
at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
at com.glide.schedule.GlideScheduleWorker.process(GlideScheduleWorker.java:161)
at com.glide.schedule.GlideScheduleWorker.run(GlideScheduleWorker.java:72)
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2017 12:33 PM
If not, double check that url in your config.xml file and make sure it matches your instance. Stop / Re-Start Your ServiceNow MID Server.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2017 12:39 PM
Cheyennes. The problem is happening only on our JDBC connection to mysql server. We have a jdbc connection to a SQL server and that works. I noticed in the log that it is using a mariadb jdbc driver. how can is force the data source record to use the mysql jdbc driver. we have already uploaded the mysql jar file in the mid server and we still have the connection problem.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2017 05:50 AM
Cheyennes... I ran the test load again and extracted the below from the MID server logs. What is the meaning of the first row. Does it even say I am not able to access the schema?
05:33:23.516 | Warning | worker.5 | worker.5 WARNING *** WARNING *** Get for non-existent record: discovery_status:381a1741db7acb80de5d3f3ffe96194a, initializing | |
05:33:23.520 | Info | worker.5 | worker.5 Published amb message, sys_id:db1a1741db7acb80de5d3f3ffe96194e | |
05:33:23.526 | Error | worker.5 | worker.5 SEVERE *** ERROR *** com.glide.db.impex.JDBCProbeLoader java.lang.NullPointerException at com.glide.db.impex.JDBCProbeLoader.getAttributesFromFirstRecord(JDBCProbeLoader.java:401) at com.glide.db.impex.JDBCProbeLoader.getAttributes(JDBCProbeLoader.java:264) at com.glide.db.impex.AbstractLoader.createMap(AbstractLoader.java:286) at com.glide.db.impex.AbstractLoader.load(AbstractLoader.java:158) at com.glide.db.impex.AbstractLoader.startWork(AbstractLoader.java:140) at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:123) at com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:34) at com.glide.worker.AbstractProgressWorker.start(AbstractProgressWorker.java:98) at com.glide.processors.ImportProcessorWorker.startWorker(ImportProcessorWorker.java:311) at com.glide.processors.ImportProcessorWorker.loadDataSource(ImportProcessorWorker.java:153) at com.glide.processors.ImportProcessorWorker.startWork(ImportProcessorWorker.java:104) at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:123) at com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:34) at com.glide.worker.BackgroundProgressJob.execute(BackgroundProgressJob.java:54) at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:103) at com.glide.schedule.JobExecutor.execute(JobExecutor.java:89) at com.glide.schedule.GlideScheduleWorker.executeJob(GlideScheduleWorker.java:219) at com.glide.schedule.GlideScheduleWorker.lambda$process$30(GlideScheduleWorker.java:161) at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35) at com.glide.schedule.GlideScheduleWorker.process(GlideScheduleWorker.java:161) at com.glide.schedule.GlideScheduleWorker.run(GlideScheduleWorker.java:72) | |
05:33:23.547 | Info | worker.5 | worker.5 Completed: ImportProcessor in 0:00:10.203, next occurrence is null | |
05:33:23.558 | Warning | worker.5 | worker.5 WARNING *** WARNING *** Connections active at session disconnect are being released | |
05:33:23.558 | Warning | worker.5 | worker.5 WARNING *** WARNING *** Validating and freeing unreleased connection 12 | |
05:33:23.558 | Info | worker.5 | worker.5 isValid(): entered for connection 12 | |
05:33:23.558 | Info | worker.5 | worker.5 isValid(): Connection 12 is valid | |
05:33:23.886 | Warning | http-22 | WARNING *** WARNING *** Resource does not exist: /scs/snc_node_disable.html | |
05:33:23.991 | Info | com.glide.db.pool.DBPoolSweeperJobStatus@ed5d9f | Pool: glide: Waiting for SYSTEM to release a connection (id = 15) | |
05:33:23.991 | Info | com.glide.db.pool.DBPoolSweeperJobStatus@ed5d9f | Pool: glide: Last sql:ContainerBackgroundProcessor[StandardEngine[Catalina]]:SELECT sys_user_session0.`last_accessed`, sys_user_session0.`data`, sys_user_session0.`csrf_token`, sys_user_session0.`sys_mod_count`, sys_user_session0.`sys_updated_on`, sys_user_session0.`sys_id`, sys_user_session0.`sys_updated_by`, sys_user_session0.`sys_created_on`, sys_user_session0.`name`, sys_user_session0.`id`, sys_user_session0.`invalidated`, sys_user_session0.`sys_created_by` FROM sys_user_session sys_user_session0 WHERE sys_user_session0.`sys_id` = '16a993cddb3acb80de5d3f3ffe961996' /* experiandev004 */ | |
05:33:23.992 | Info | com.glide.db.pool.DBPoolSweeperJobStatus@ed5d9f | Pool: glide: Waiting for 1 connections to close on obsolete pool jdbc:mysql://db160151.ams5.service-now.com:3401/ | |
05:33:23.992 | Info | com.glide.db.pool.DBPoolSweeperJobStatus@ed5d9f | Pool: glide: Waiting for SYSTEM to release a connection (id = 15) | |
05:33:23.992 | Info | com.glide.db.pool.DBPoolSweeperJobStatus@ed5d9f | Pool: glide: Last sql:ContainerBackgroundProcessor[StandardEngine[Catalina]]:SELECT sys_user_session0.`last_accessed`, sys_user_session0.`data`, sys_user_session0.`csrf_token`, sys_user_session0.`sys_mod_count`, sys_user_session0.`sys_updated_on`, sys_user_session0.`sys_id`, sys_user_session0.`sys_updated_by`, sys_user_session0.`sys_created_on`, sys_user_session0.`name`, sys_user_session0.`id`, sys_user_session0.`invalidated`, sys_user_session0.`sys_created_by` FROM sys_user_session sys_user_session0 WHERE sys_user_session0.`sys_id` = '16a993cddb3acb80de5d3f3ffe961996' /* experiandev004 */ | |
05:33:23.992 | Info | com.glide.db.pool.DBPoolSweeperJobStatus@ed5d9f | Pool: glide: Waiting for 1 connections to close on obsolete pool jdbc:mysql://db160151.ams5.service-now.com:3401/ |

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2017 06:26 AM
Cheyennes.. When creating the data source record, the transform record should exist before you can do a successful test load, correct?