Re: Too many 302 redirects with 1.5.8 Wicket
Perfect, Martin. Thank you very much for tip, I will point my investigation in this way. cheers Tomas. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Too-many-302-redirects-with-1-5-8-Wicket-tp4674532p4674567.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Too many 302 redirects with 1.5.8 Wicket
On Thu, May 5, 2016 at 1:29 PM, tomask79wrote: > Hi Martin, > > REDIRECT_TO_BUFFER and by is meant > > "ILinkListener-content-contractDetailTabbedPanel-contractDetailTabbedPanel-panel-documentContentBusinessPanelsContainer-documentContentBusinessPanels-1-contractDetailClientDocumentBusinessPanel-revisionsPanel-table-body-rows-1-cells-2-cell-linkPropertyColumn.a=DlXvqFmLq9NbuPUcEk74 > HTTP/1.1" 302 333" > Is the always the same, i.e. the component path and the additional request parameters (e.g. tabId) are exactly the same for all redirects ? When REDIRECT_TO_BUFFER is used Wicket renders the page and stores the byte[] in a special Map in the Application. When a request comes Wicket uses its sessionId and request url as a composite key and checks whether there is a stored response for it in the Map. If there is stored result then there is no further processing and the byte[] is immediately written down in the response. If there is no stored byte[] then Wicket renders the page. If the original/requested url is the same as the one returned by RequestCycle.urlFor(new RenderPageRequestHandler(thePageInstance)) then the byte[] is written to the http response. If the url differs even in a single character then the byte[] is stored in the Map and a new redirect is made. The logic is in WebPageRenderer#respond(RequestCycle), but this is IMO the most complex code in Wicket. The final outcome depends on several variables (render strategy, is ajax, redirect strategy, original vs. current page url, etc.). > > thank you in advance for any hint where to look or what to check... > > T. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Too-many-302-redirects-with-1-5-8-Wicket-tp4674532p4674565.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Too many 302 redirects with 1.5.8 Wicket
Hi Martin, REDIRECT_TO_BUFFER and by is meant "ILinkListener-content-contractDetailTabbedPanel-contractDetailTabbedPanel-panel-documentContentBusinessPanelsContainer-documentContentBusinessPanels-1-contractDetailClientDocumentBusinessPanel-revisionsPanel-table-body-rows-1-cells-2-cell-linkPropertyColumn.a=DlXvqFmLq9NbuPUcEk74 HTTP/1.1" 302 333" thank you in advance for any hint where to look or what to check... T. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Too-many-302-redirects-with-1-5-8-Wicket-tp4674532p4674565.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Too many 302 redirects with 1.5.8 Wicket
Hi, What is in GET /wicket/page?420-1. ? Which render strategy do you use ? REDIRECT_TO_BUFFER (the default), REDIRECT_TO_RENDER or ONE_PASS_RENDER ? https://github.com/apache/wicket/blob/89c1290cb007f14c13c1d6d6648a8c0a090a97b2/wicket-core/src/main/java/org/apache/wicket/settings/RequestCycleSettings.java#L88 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, May 3, 2016 at 1:57 PM, tomask79wrote: > Hi guys, > > currently in the older deployed versions of our system in the cluster > environment, we're experiencing sometimes strange behaviour where one > session loops in the 302 redirect cyclethis is the log from load > balancer: > > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > > *when this 302 redirect loop could have happended with 1.5.8 please? * > > We've got sticky sessions ON, session replication ON as well. Btw we're not > experiencing this with Wicket 6.0.. > > thanks a lot in advance > > Tomas > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Too-many-302-redirects-with-1-5-8-Wicket-tp4674532.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Too many 302 redirects with 1.5.8 Wicket
Well, today I found out we experience this problem also with Wicket 6.0...(6.21) Guys, do you have any idea when this could happen? When Wicket could rotate the same request over and over again? Pattern is still the same...POST -> and eventual 302 GET for response is rotated many times(sometimes!) Eventuall requests are suspended by our app server... [0x7f016a955000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.apache.wicket.page.PageAccessSynchronizer$PageLock.waitForRelease(PageAccessSynchronizer.java:345) - locked <0x0007e8efefc0> (a org.apache.wicket.page.PageAccessSynchronizer$PageLock) at org.apache.wicket.page.PageAccessSynchronizer.lockPage(PageAccessSynchronizer.java:129) at org.apache.wicket.page.PageAccessSynchronizer$2.getPage(PageAccessSynchronizer.java:245) at org.apache.wicket.DefaultMapperContext.getPageInstance(DefaultMapperContext.java:148) at org.apache.wicket.core.request.handler.PageProvider.getStoredPage(PageProvider.java:296) at org.apache.wicket.core.request.handler.PageProvider.isNewPageInstance(PageProvider.java:208) at org.apache.wicket.core.request.mapper.AbstractBookmarkableMapper.processHybrid(AbstractBookmarkableMapper.java:213) thanks in advance... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Too-many-302-redirects-with-1-5-8-Wicket-tp4674532p4674563.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Too many 302 redirects with 1.5.8 Wicket
There are no less than 7 newer versions of 1.5.x, so perhaps update to 1.5.15 to see if you're having better luck? According to the changelog, there were several redirect-related bugs fixed in 1.5.11: https://github.com/apache/wicket/blob/wicket-1.5.x/CHANGELOG-1.5#L41 Sincerely, Jeroen 2016-05-03 13:57 GMT+02:00 tomask79: > Hi guys, > > currently in the older deployed versions of our system in the cluster > environment, we're experiencing sometimes strange behaviour where one > session loops in the 302 redirect cyclethis is the log from load > balancer: > > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > "GET /wicket/page?420-1. 302 333 (redir=-, > > SID=h_pXgpfMGo80oe7JYFor4SeZtr6kz_QC9BWFzlRyjw37_T9y6XhL!22895550!902922496) > "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" > > *when this 302 redirect loop could have happended with 1.5.8 please? * > > We've got sticky sessions ON, session replication ON as well. Btw we're not > experiencing this with Wicket 6.0.. > > thanks a lot in advance > > Tomas > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Too-many-302-redirects-with-1-5-8-Wicket-tp4674532.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Jeroen Steenbeeke