Glassfish 5 Upgrade #4248
Comments
|
@pameyer - please feel free to drop notes of the issue re: login that you experienced. |
|
quick check of this branch w\ glassfish5 + apache. curl on top-level url worked as expected (redirect to login page); using a browser triggered a glassfish exception (and failed to allow login).
|
|
I have spent about a day on this and made little progress aside from gaining background knowledge and identifying some errors. Works: Login & accountRegistration Broken:
1. Dataverse cannot be published.txt |
|
Huh, this is interesting, from 2.Search.starts.with.page.0.txt above: I don't know what to say about the other errors. I was able to create dataverses and datasets via API on Glassfish 5. I didn't test JSF much. |
|
@pdurbin That log message is the one from when I removed the getPage() setter. Was an easy way to get a useful stack trace (the trace when it errored on page == 0 hid a lot). |
|
From standup, we decided to let this wait until technical open hours next Tuesday for discussion. |
|
We revisited this in backlog grooming 11/15:
|
|
Hey guys, I am working on a deployment of Dataverse at Forschungszentrum Jülich in Germany. This might be a good solution to get a research data repository in place and we want to compare Dataverse with B2SHARE. As @pdurbin mentioned in some other issue/thread, I pretty much dislike patching Glassfish 4.1, too. Any chances this issue or PR #4244 hits a release anytime soon? I am willing to help in testing. I'm neither a JEE expert nor a Glassfish expert, but I know a bit or two about Java web dev (Spring) and I'm willing to dig deeper... ;-) Thx, |
|
@poikilotherm hi! Thanks for being willing to test! The best way to get a sense of where issues are in the queue is to look at the kanban board at https://waffle.io/IQSS/dataverse As of this writing this issue is in the "Backlog" column with a couple dozen of issues in front of it. This is a better spot to be than the "Inbox" column where new issues land when they are created. We are constantly shuffling the order of issues in the backlog. As I indicated at #4172 (comment) I've been concerned that Glassfish isn't updated very often compared to Payara. It sounds like your main concern is the patching you have to do and yes, I wrote about this at #2628. |
|
Hi @pdurbin, I will be on vacation for the next three weeks. After that I will come back to this topic... Cheers |
pdurbin
added
the
Component: Code Infrastructure
|
I've been meaning to mention that I was recently alarmed to read the following in https://www.eclipse.org/org/foundation/boardminutes/2019_03_26_Minutes.pdf "Mike noted that the future of Eclipse Glassfish beyond version 5.2 is uncertain due to resource constraints." |
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=429992 As we are stuck on Glassfish 4.1 for now (see IQSS#4172, IQSS#4248 and IQSS#4260), we cannot simply upgrade. Meh. This reverts commit c80aeea.
|
Closing in favor of #6230 |
Spun out of #4217. We are more confident with a Glassfish upgrade than we are with Java EE8/Java 9 upgrades. We'll plan to take Glassfish to conclusion and leave the spike as a separate issue.
The text was updated successfully, but these errors were encountered: