-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apache SSL config: Many SSL warnings in Glassfish server log (SSLEngine is null) #643
Comments
Original Redmine Comment Kevin Condon wrote:
Yes, I did notice this and it's easy to replicate by hitting a SWORD URL with curl like this: curl -u user1:user1 https://dataverse-demo.iq.harvard.edu/dvn/api/data-deposit/v1/swordv2/service-document I did leave that jira bug number in this commit: progress on fronting glassfish with apache #1096 #2657 · 71cd4ef · IQSS/dataverse - 71cd4ef |
Due to #647 we've moved API testing from the demo site to http://apitest.dataverse.org Here's a new URL for replicating the SSL error: curl -u pete:pete https://apitest.dataverse.org/dvn/api/data-deposit/v1/swordv2/service-document |
A couple of times I've tried adding variations on For now I'm going with This only hides the error, of course. Perhaps we could move this issue to a different milestone to come up with a better fix. Sending to QA for comment. |
Not sure what you are looking for: what log level do we want in prod? Generally good idea not to have lots of warnings in logs but if after a reasonable amount of effort it cannot be resolved then not sure what to do. As for the schedule, that's not my call but hiding the errors makes it less obtrusive for now. Passing back to dev. |
tried suggestions on https://java.net/jira/si/jira.issueviews:issue-html/GLASSFISH-20694/GLASSFISH-20694.html but still see the same in the log. |
I feel like I've put a reasonable amount of effort in. Someone else is welcome to take a crack at it. My proposed workaround as I mentioned at #643 (comment) is (sadly) to hide the errors. I'm willing to document this in the Installer's Guide. I'll put this in the "in review" milestone for a decision. |
@esotiri now that Glassfish 4.1 is out, are you interested in seeing if upgrading makes the errors go away? |
This error really fills up the logs and would be a showstopper for production in my opinion. |
Can we try Glassfish 4.1? 1000+ bug fixes: https://pbs.twimg.com/media/BypemmWIMAIFaQN.jpg |
did yo talk to Bob and Ellen about our recent Glassfish update in Mercè Crosas, Ph.D. On Thu, Oct 16, 2014 at 3:57 PM, Philip Durbin [email protected]
|
@kcondon as we discussed a couple weeks ago, I simply documented the workaround for hiding these errors. If you do a build you'll find them here: https://dvn-build.hmdc.harvard.edu/guides/Installers/dataverse-installer-main.html#sslengine-is-null-workaround Moving to QA. |
applied workaround on dvn-build. |
Author Name: Kevin Condon (@kcondon)
Original Redmine Issue: 4092, https://redmine.hmdc.harvard.edu/issues/4092
Original Date: 2014-06-10
Original Assignee: Philip Durbin
Since fronting demo with Apache to support Shibboleth/SSL, we are seeing numerous glassfish server log errors and at one point some people could not get to the site, though this last issue may not be related.
The repeated warnings are:
There are some web posts on this error but I did not see an immediate answer, though discussion centered around gfish/apache config and apache not passing cert info along to gfish:
https://java.net/jira/browse/GLASSFISH-20694?page=com.atlassian.streams.streams-jira-plugin%3Aactivity-stream-issue-tab
Redmine related issue(s): 1096
The text was updated successfully, but these errors were encountered: