PUBLIC - Liferay Portal Community Edition

Confirm friend request: This URL can only be invoked using POST

Details

  • Similar Issues:
    Show 5 results 

Description

When a user tries to confirm/accept a friend request, they get the red box 'Requests is temporarily unavailable' error message and the following is written to the log:

2011-06-20 10:37:09,481 <TP-Processor15> WARN [PortletRequestProcessor:160] - This URL can only be invoked using POST: /web/<user_name>/profile?p_auth=gt9D9F8B&p_p_id=121&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_pos=1&p_p_col_count=2&_121_struts_action=%2Frequests%2Fupdate_request&_121_redirect=http%3A%2F%2F<domain_name>%2Fweb%2F<user_name>%2Fprofile%3Fp_p_id%3D121%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-2%26p_p_col_pos%3D1%26p_p_col_count%3D2&_121_requestId=1604&_121_status=1
2011-06-20 10:37:09,567 <TP-Processor15> ERROR [jsp:154] - com.liferay.portal.security.auth.PrincipalException: /web/<user_name>/profile?p_auth=gt9D9F8B&p_p_id=121&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_pos=1&p_p_col_count=2&_121_struts_action=%2Frequests%2Fupdate_request&_121_redirect=http%3A%2F%2F<domain_name>%2Fweb%2F<user_name>%2Fprofile%3Fp_p_id%3D121%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-2%26p_p_col_pos%3D1%26p_p_col_count%3D2&_121_requestId=1604&_121_status=1
at com.liferay.portal.struts.PortletRequestProcessor.process(PortletRequestProcessor.java:165)
at com.liferay.portlet.StrutsPortlet.processAction(StrutsPortlet.java:186)
at com.liferay.portlet.FilterChainImpl.doFilter(FilterChainImpl.java:70)
at com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(PortletFilterUtil.java:48)
at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:652)
at com.liferay.portlet.InvokerPortletImpl.invokeAction(InvokerPortletImpl.java:687)
at com.liferay.portlet.InvokerPortletImpl.processAction(InvokerPortletImpl.java:360)
at com.liferay.portal.action.LayoutAction.processPortletRequest(LayoutAction.java:784)
at com.liferay.portal.action.LayoutAction.processLayout(LayoutAction.java:582)
at com.liferay.portal.action.LayoutAction.execute(LayoutAction.java:232)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:153)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:508)
at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:485)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

This occurs randomly for different users on different browsers.

Steps to reproduce:
1. Log in as user A
2. Find user B and click Add as Friend
3. Log out as user A
4. Log in as user B
5. Click 'Confirm' to accept user A's request

Sometimes is works just fine, but most of the time for us we get the 'Requests is temporarily unavailable' error message.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tammy Fong added a comment -

Hi Jeremy,

Thank for the report. I am unable to reproduce this error on 6.0.6 using these browsers: Chrome 12, Firefox 4, IE 9, Safari 5. Have you had the opportunity to discuss this issue on the community forums? If so, were there other users who were also experiencing this problem? If you still experience this issue, please provide additional information and we can re-visit it.

Show
Tammy Fong added a comment - Hi Jeremy, Thank for the report. I am unable to reproduce this error on 6.0.6 using these browsers: Chrome 12, Firefox 4, IE 9, Safari 5. Have you had the opportunity to discuss this issue on the community forums? If so, were there other users who were also experiencing this problem? If you still experience this issue, please provide additional information and we can re-visit it.
Hide
Permalink
Jeremy Wier added a comment -

Yes, I have posted this issue in the forums (http://www.liferay.com/community/forums/-/message_boards/message/9480143) and created this ticket at the request of Amos Fong (http://issues.liferay.com/browse/LPS-2652). So far, no one else seems to be having this issue. And like I said above and in my community post, it's not consistent by any means. One minute I get this error with a user, the next minute everything works fine. Even after spending the past 2 days trying to track down this issue, I still cannot determine the exact steps to get the error to occur on demand. It's very random.

Show
Jeremy Wier added a comment - Yes, I have posted this issue in the forums ( http://www.liferay.com/community/forums/-/message_boards/message/9480143 ) and created this ticket at the request of Amos Fong ( http://issues.liferay.com/browse/LPS-2652 ). So far, no one else seems to be having this issue. And like I said above and in my community post, it's not consistent by any means. One minute I get this error with a user, the next minute everything works fine. Even after spending the past 2 days trying to track down this issue, I still cannot determine the exact steps to get the error to occur on demand. It's very random.
Hide
Permalink
Tammy Fong added a comment -

Hi Jeremy,
Could you provide more details such as:

Were the members in the same organization, community, user group?
What were the roles assigned to them?
Where were the portlets added? (user public page?)
What portlets were involved? (Wall, Requests, Friends)

Please ensure you have a fresh environment with no other issues that may interfere with the bug. If I cannot reproduce this issue, it cannot be fixed. Thanks!

Show
Tammy Fong added a comment - Hi Jeremy, Could you provide more details such as: Were the members in the same organization, community, user group? What were the roles assigned to them? Where were the portlets added? (user public page?) What portlets were involved? (Wall, Requests, Friends) Please ensure you have a fresh environment with no other issues that may interfere with the bug. If I cannot reproduce this issue, it cannot be fixed. Thanks!
Hide
Permalink
Jeremy Wier added a comment -

The members are all in the same community.
They all have the same roles: Power User and custom roles (SEG Member, Member Active, etc).
The portlets are on each user's public page.
We are using a custom portlet to make the friend request (Add as friend), but using the out-of-the-box Friends and Requests portlets to view friends and confirm/ignore friend requests. The Requests portlet is where we are having problems.

Show
Jeremy Wier added a comment - The members are all in the same community. They all have the same roles: Power User and custom roles (SEG Member, Member Active, etc). The portlets are on each user's public page. We are using a custom portlet to make the friend request (Add as friend), but using the out-of-the-box Friends and Requests portlets to view friends and confirm/ignore friend requests. The Requests portlet is where we are having problems.
Hide
Permalink
Tammy Fong added a comment -

Hi Jeremy, I am still unable to reproduce this bug on 6.0.6. As non-friends, I can successfully add/request others as friends from the Summary and Wall portlets. On the other end, users of different roles (power user, admin) can successfully confirm/ignore requests in the Request portlet without triggering the error.

Show
Tammy Fong added a comment - Hi Jeremy, I am still unable to reproduce this bug on 6.0.6. As non-friends, I can successfully add/request others as friends from the Summary and Wall portlets. On the other end, users of different roles (power user, admin) can successfully confirm/ignore requests in the Request portlet without triggering the error.
Hide
Permalink
Michael Saechang added a comment -

Closing as per Tammy's comment.

Show
Michael Saechang added a comment - Closing as per Tammy's comment.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    1 year, 5 weeks, 2 days ago