Re: [geogig-dev] geogig import error

[admire <admire@xxxxxxxxxxx>]

Hi

On 22/06/2016 07:07, Gabriel Roldan wrote:

Hello,

thanks for reaching up to us.

I looked at the Berkeley DB Java Edition source code and the error message you're getting is definitely caused by a bug in the database (*).

Do you mean error in my database or in the source code regarding database connection.

That said, my understanding is it should be harmless for the geogig import process.

I think giving informative error is better than having it spit out this errors if the table is large.

So, question is, besides getting that stack trace in the console, did the import finish or not?

The import did finish . I will check to see if it exported the whole table.

And what geogig version are you using? (output of geogig --version?)

the following is the output for checking version.
$ geogig --version
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
         Project Version : 1.0-SNAPSHOT
              Build Time : April 29, 2015 at 16:40:10 SAST
         Build User Name : admire
        Build User Email : admire@xxxxxxxxxxx
              Git Branch : master
           Git Commit ID : e92012ff85bc8f6dc99350ad1e774b82f9f95e42
         Git Commit Time : November 17, 2014 at 13:57:48 SAST
  Git Commit Author Name : Gabriel Roldan
 Git Commit Author Email : gabriel.roldan@xxxxxxxxx
      Git Commit Message : Merge pull request #824 from volaya/fix_823

Fixed issue when exporting to shp a layer with long fields (>10 chars)

Best regards,

Gabriel

(*) 

They're calling the following  method with all null arguments but the first two, and it fails with an NPE at the line that reads as sb.append(" key=").append(key.dumpData());

void trace(final Level level,

               final String methodName,

               final Transaction txn,

               final DatabaseEntry key,

               final DatabaseEntry data,

               final LockMode lockMode)

        throws DatabaseException {

        if (logger.isLoggable(level)) {

            StringBuilder sb = new StringBuilder();

            sb.append(methodName);

            if (txn != null) {

                sb.append(" txnId=").append(txn.getId());

            }

            sb.append(" key=").append(key.dumpData());

            if (data != null) {

                sb.append(" data="" lockMode=").append(lockMode);

            }

            LoggerUtils.logMsg(

                logger, envHandle.getEnvironmentImpl(), level, sb.toString());

        }

    }

On Tue, Jun 21, 2016 at 4:00 AM, admire <admire@xxxxxxxxxxx> wrote:

Hi

I am trying to import a large postgis table into geogig. the table has about six million records.

Exception in thread "BDBJE-index-SYNC-THREAD-1" java.lang.NullPointerException
    at com.sleepycat.je.Database.trace(Database.java:2198)
    at com.sleepycat.je.Database.sync(Database.java:684)
    at org.locationtech.geogig.storage.bdbje.JEObjectDatabase$FlushLogTask$1.run(JEObjectDatabase.java:586)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)


Regards
_______________________________________________
geogig-dev mailing list
geogig-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geogig-dev

--

Gabriel Roldán
Software Developer | Boundless
groldan@xxxxxxxxxxxxxxxx
@boundlessgeo

_______________________________________________
geogig-dev mailing list
geogig-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geogig-dev