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 07:25 AM
This may help:
This message can happen if you are using the JDBC Probe with MIDs in a cluster (for load balancing).
If one MID handles the JDBC query and another MID in the cluster and picks up the results set then
this data will sit in the ECC queue and never be processed. After five minutes you will see the "Did not get a response from the MID server"
message.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2017 08:47 AM
Thank you for the input Cheyennes. I had the load balancing removed and we still get the same problem

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2017 09:07 AM
Cheyennes.. what do you think is the problem here with this warning message.
WARNING *** WARNING *** java.net.SocketTimeoutException: connect timed out when posting to https://nodestats.service-now.com/ecc_queue.do?SOAP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2017 12:31 PM
There's something going on with your MID server connection to your instance. Check your proxy settings, it could be the firewall.