Highlighted
Honored Contributor.
Honored Contributor.
1355 views

jdbc driver won't start -- EOFException

root install of eDir / idm
was working previously. Database was moved to another subnet. Don't recall any other changes.

I have deleted the associated .TAO and dx files as well as the jdbc files in the dib directory. I have also restarted the box. one of the files shown below remains at 0 bytes.

-rw-------. 1 root root 33104 Nov 2 12:37 jdbc_a4a86c18-1ae5-4269-539c-186ca8a4e51a
-rw-rw-rw-. 1 root root 0 Nov 2 12:37 jdbc_a4a86c18-1ae5-4269-539c-186ca8a4e51a.p
-rw-------. 1 root root 5168 Nov 2 12:37 jdbc_a4a86c18-1ae5-4269-539c-186ca8a4e51a.p.1.bak
-rw-------. 1 root root 16 Nov 2 12:37 jdbc_a4a86c18-1ae5-4269-539c-186ca8a4e51a.t.1.bak


ll 272479.TAO
-rw-------. 1 root root 72 Nov 2 12:35 272479.TAO

ll dx272479*
-rw-------. 1 root root 33240 Nov 2 12:37 dx272479
-rw-------. 1 root root 17504 Nov 2 12:37 dx272479.p
-rw-------. 1 root root 16 Nov 2 12:37 dx272479.t


[11/02/17 12:37:55.930]:PeopleSoft JDBC driver PT:Publisher is active.
[11/02/17 12:37:55.931]:PeopleSoft JDBC driver PT:This driver's GUID: A4A86C18-1AE5-4269-539C-186CA8A4E51A
[11/02/17 12:37:55.931]:PeopleSoft JDBC driver PT:Opening triggerless publication state file.
[11/02/17 12:37:55.973]:PeopleSoft JDBC driver PT:Restricting file Permission for ./jdbc_a4a86c18-1ae5-4269-539c-186ca8a4e51a.t
[11/02/17 12:37:55.974]:PeopleSoft JDBC driver PT:Restricting file Permission for ./jdbc_a4a86c18-1ae5-4269-539c-186ca8a4e51a.p
[11/02/17 12:37:55.974]:PeopleSoft JDBC driver PT:Restricting file Permission for ./jdbc_a4a86c18-1ae5-4269-539c-186ca8a4e51a
[11/02/17 12:37:55.986]:PeopleSoft JDBC driver PT:File opened.
[11/02/17 12:37:55.986]:PeopleSoft JDBC driver PT:Publication domain (JDBC URL or schema) change detected. Archiving existing triggerless publication state file '
./jdbc_a4a86c18-1ae5-4269-539c-186ca8a4e51a'.
[11/02/17 12:37:55.992]:PeopleSoft JDBC driver PT:File archived.
[11/02/17 12:37:55.994]:PeopleSoft JDBC driver PT:Unhandled Exception: java.io.IOError: java.io.EOFException
[11/02/17 12:37:55.995]:PeopleSoft JDBC driver PT:java.io.IOError: java.io.EOFException
at org.mapdb.Volume$FileChannelVol.getInt(Volume.java:988)
at org.mapdb.StoreDirect.checkHeaders(StoreDirect.java:253)
at org.mapdb.StoreWAL.checkHeaders(StoreWAL.java:115)
at org.mapdb.StoreDirect.<init>(StoreDirect.java:207)
at org.mapdb.StoreWAL.<init>(StoreWAL.java:74)
at org.mapdb.DBMaker.extendStoreWAL(DBMaker.java:981)
at org.mapdb.DBMaker.makeEngine(DBMaker.java:758)
at org.mapdb.DBMaker.make(DBMaker.java:701)
at com.novell.nds.dirxml.driver.jdbc.util.jdbm.JDBMFile.setRecMan(Unknown Source)
at com.novell.nds.dirxml.driver.jdbc.util.jdbm.JDBMFile.open(Unknown Source)
at com.novell.nds.dirxml.driver.jdbc.JDBCTriggerlessPublicationShim.openTriggerlessFile(Unknown Source)
at com.novell.nds.dirxml.driver.jdbc.JDBCTriggerlessPublicationShim.beforePoll(Unknown Source)
at com.novell.nds.dirxml.driver.jdbc.JDBCPublicationShim.start(Unknown Source)
at com.novell.nds.dirxml.driver.jdbc.JDBCPublicationProxy.start(Unknown Source)
at com.novell.nds.dirxml.engine.Publisher.run(Publisher.java:549)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EOFException
at org.mapdb.Volume$FileChannelVol.readFully(Volume.java:947)
at org.mapdb.Volume$FileChannelVol.getInt(Volume.java:985)
... 15 more

[11/02/17 12:37:55.998]:PeopleSoft JDBC driver PT:Shutting down...

Any thoughts on what else may be causing the issue?

thanks,
Fred
Labels (1)
5 Replies
Highlighted
Knowledge Partner
Knowledge Partner

I would have guessed corrupt files, but you said you already recreated the
jdbc* and other files for the Publisher channel. Are you sure you are not
out of disk space, preventing the files from being created fully? The TAO
file should be irrelevant in this case, unless I am missing something,
though you cleared it anyway so no harm there. When you did clear it, did
you restart choosing to NOT resync the driver, I presume? Disabling the
driver config object should clear it.

You may want to look at the DirXML-DriverStorage attribute on the driver
config object, probably via LDAP or iManager. If it has a value (it
should) then delete that while the driver object is stopped and see if
that makes a difference. I do not really think this will fix it, but I do
not know the intimate details of how that works with JDBC in general or
your configuration in particular.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
Highlighted
Knowledge Partner
Knowledge Partner

On 11/2/2017 11:38 PM, ab wrote:
> I would have guessed corrupt files, but you said you already recreated the
> jdbc* and other files for the Publisher channel. Are you sure you are not
> out of disk space, preventing the files from being created fully? The TAO
> file should be irrelevant in this case, unless I am missing something,
> though you cleared it anyway so no harm there. When you did clear it, did
> you restart choosing to NOT resync the driver, I presume? Disabling the
> driver config object should clear it.
>
> You may want to look at the DirXML-DriverStorage attribute on the driver
> config object, probably via LDAP or iManager. If it has a value (it
> should) then delete that while the driver object is stopped and see if
> that makes a difference. I do not really think this will fix it, but I do
> not know the intimate details of how that works with JDBC in general or
> your configuration in particular.


Also DirXML-DriverStorage is per-server, so when looking in LDAP you
have to check on each server (though mainly the one you are trying to
run it on). iManager may not reliably show it if it has a value on one
but not other servers.


Highlighted
Honored Contributor.
Honored Contributor.

thanks!

Deleting the DirXML-DriverStorage attribute at first didn't fix it.

With the attribute deleted I deleted the files again, disabled the driver and set it to auto start, with it checked not to auto resync. After that I stopped the eDir instance and restarted it.

It started fine. So it appears that the attribute plays a factor in cleaning up the corrupt file(s).

thanks!
Highlighted
Absent Member.
Absent Member.

I can confirm that deleting the DirXML-DriverStorage attribute via iManager on a JDBC driver (4.1.0.1 on IDM 4.7, on RHEL 7.4) allowed it to start, after seeing the message:

Message: Code(-9005) The driver returned a "fatal" status indicating that the driver should be shut down. Detail from driver: <description>java.lang.IndexOutOfBoundsException: Index: 1, Size: 1</description>
Highlighted
Contributor.
Contributor.

I confirm too: after deleting the DirXML-DriverStorage attribute and delete statefiles, JDBC driver  allowed it to start.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.