| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
thx! let me test that |
Sorry, something went wrong.
|
@andrijapanicsb a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-334 |
Sorry, something went wrong.
|
@andrijapanicsb a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
Sorry, something went wrong.
There was a problem hiding this comment.
Hi @marcaurele thanks for the changes. I tested this but unfortunately I couldn't see any difference after changing the value on server.properties and restarting the management server
Sorry, something went wrong.
|
Trillian test result (tid-438)
|
Sorry, something went wrong.
|
Trillian test result (tid-439)
|
Sorry, something went wrong.
There was a problem hiding this comment.
Unfortunately, not working @marcaurele 😢
Sorry, something went wrong.
|
I did some testing on a simple server and I had to set the timeout after the server was started. I pushed an update, let me know if it's working now @andrijapanicsb |
Sorry, something went wrong.
|
thx @marcaurele. @blueorangutan package |
Sorry, something went wrong.
|
@andrijapanicsb a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-335 |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks @marcaurele, this is working now but I think it can be improved a bit:
Instead of creating a pair to pass the sessionHandler, it can be defined as a variable and set the timeout after the server starts, reducing the lines of code:
private SessionHandler sessionHandler;
...
private HandlerCollection createHandlers() {
...
sessionHandler = webApp.getSessionHandler();
...
}
public void start() {
...
server.start();
// Must set the session timeout after the server has started
sessionHandler.setMaxInactiveInterval(sessionTimeout * 60);
...
}
Sorry, something went wrong.
|
@marcaurele @nvazquez - I've tested both your solutions - it works fine! (tried both setting session to 2minutes and 45 minutes) - so all good! |
Sorry, something went wrong.
|
@nvazquez IMO it does not look well coded to keep a reference of the SessionHandler as a class member to only skip having to return this pair of objects. |
Sorry, something went wrong.
|
@marcaurele no urgency, was trying to propose an improvement and tried with the comments but thought those were not being added until I click Submit on the review. So I created the PR for clarity but didn't realise the comments were already added, please discard them. Thanks for the fix |
Sorry, something went wrong.
|
Guys, please let me know once you have agreed on the way forward, so I can merge this one. |
Sorry, something went wrong.
|
I have closed the other PR, I'm ok with this one |
Sorry, something went wrong.
|
@nvazquez I wish we could return multiple argument without creating a custom class in Java. Thanks for taking my point in consideration. |
Sorry, something went wrong.
|
Rebase done to only leave the good commit. Good for review & merge on my side. |
Sorry, something went wrong.
|
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-339 |
Sorry, something went wrong.
|
@nvazquez a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-452)
|
Sorry, something went wrong.
|
the latest code is NOT ok. |
Sorry, something went wrong.
|
@marcaurele can you try https://stackoverflow.com/a/56091476 |
Sorry, something went wrong.
|
@andrijapanicsb weird as I don't see any difference so far from the previous 2 commits. Can you double check you're using the right branch and cleared up the compiled classes of the client module, just in case. @rhtyd that's what it's doing, but I found out that the session must be set after doing the server.start(). I modified the jetty example embbeded project to try out. |
Sorry, something went wrong.
|
my bad, give me 2 minutes... |
Sorry, something went wrong.
|
all good @marcaurele. LGTM from my side (manual testing). |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
merging based on 2 LGTM, manual testing and automated test results. thx @marcaurele ! |
Sorry, something went wrong.
|
For the record, this is the small embedded app to validate: https://github.com/marcaurele/embedded-jetty-uber-jar/tree/session-test |
Sorry, something went wrong.
fixed inability to set a custom session duration via server.properties on mgmt server.
fixed inability to set a custom session duration via server.properties on mgmt server.
| Back | FazBrowse Home | New Git URL |
Description
Related to #2329 (comment) the session timeout is not taken into account. This change creates a session handler explicitly and the timeout value should be correctly taken into account.
Types of changes
How Has This Been Tested?
This has not been tested yet.