OAI client : message "javax.ejb.EJBTransactionRolledbackException, Exception thrown from bean: java.lang.NullPointerException"

243 views
Skip to first unread message

Thomas Jouneau

unread,
Feb 11, 2021, 1:03:40 PM2/11/21
to Dataverse Users Community
Dear list,

I feel a little uncomfortable by coming up with a problem already
documented in this github issue :
https://github.com/IQSS/dataverse/issues/7546 ; but I really, really
could use some help now.

To summarize very briefly :

- I'm trying to harvest sets on two fairly generic repositories (I'm
pretty sure the OAI protocol is perfectly implemented in both of them).

- The clients as configured report n records found, zero harvested.

- The message is always the same for non-harvested records (see mail
subject).

Symptoms and the exact same message detected for both repositories
mentioned in the ticket, but also with some others since.

Right now I can't decide if :

- it's a fairly generic issue and I would bet some other DV user has met
the same symptoms and message if it's the case (apparently not) ;

- the fault is on our configuration and where does I need to look first?

Many thanks in advance for any help.

Best

Thomas



Philip Durbin

unread,
Feb 12, 2021, 10:33:29 AM2/12/21
to dataverse...@googlegroups.com
Hi Thomas,

I'm sorry to hear you're having trouble with harvesting.

Whenever I hear about a NullPointerException (which should never happen, in theory), I'm curious which line of code is causing it. The line number should be in your Payara server.log and if you tell us which version of Dataverse you're running (it looks like 5.3, from the issue you mentioned) we can figure out what's happening on that line (the version number is important because code moves around as it is edited over time). If there's nothing incriminating in your server.log you can reply with the relevant part here (please give lots of lines before and after, just to make sure) or put it in the issue or you can email it to sup...@dataverse.org

If you have any theories on if a specific dataset might be causing the problem, please include those as well.

Since you already have an issue going, should we move the conversation there? We can always summarize later for the list.

Thanks,

Phil

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/10dc2c68-0fa1-7498-b889-ffd7f76bc17a%40gmail.com.


--

Thomas Jouneau

unread,
Mar 11, 2021, 9:33:30 AM3/11/21
to dataverse...@googlegroups.com

Hi Philip, all,

Sorry for the delay. I had to postpone further testing for a while.

Now it's done, I added

- a rather large (sorry) excerpt of my server log to the github issue.

- a mention of the very same message appearing when trying to import a dataverse json file as described in the docs.

I agree the best place to further the discussion is on github. See you there.

Best

Thomas

Thomas Jouneau

unread,
May 26, 2021, 2:32:15 AM5/26/21
to dataverse...@googlegroups.com

Hi,

I've been observing the same problem with the following OAI server :

https://archives.ahp-numerique.fr/index.php/;oai

I've been adding some elements to https://github.com/IQSS/dataverse/issues/7546.

Could we pick this issue up again?

Thanks!

Thomas

arnau merino

unread,
Jan 19, 2023, 6:03:10 AM1/19/23
to Dataverse Users Community
Hi,

I've been having the same problem you mention latelly.

Did you finally fix it? In that case what was the problem?

Thanks!

Arnau.
Reply all
Reply to author
Forward
0 new messages