WSRP between two LR 6.1ga1 causes "Unable to find <liferay-wsrp-portlet>" Exception

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.1.0 CE GA1
• Fix Version/s: --Sprint 11/12, 6.2.0 CE M2
• Component/s: Deployment, Deployment > WSRP
• Labels:
  • community-verifier
• Environment: Tested on SLES 11sp1 64Bit Java 1.6.0_21
• Similar Issues: Show 5 results ; ;

  LPS-10127	Consumer cannot find <liferay-wsrp-portlet>
  LPS-31722	WSRP portlet from Customer Portal generates exception: Unable to find <liferay-wsrp-portlet>
  LPS-10962	WSRP Plugin Portlet Exception
  LPS-10525	exception on the Producer instance on receiving action request
  LPS-24889	Connecting (producer) LR 6.0.6 CE via WSRP to (consumer) 6.1GA causes NPE on consumer side

Connecting two LR 6.1ga1 via WSRP does not work.
It causes the following Exception on producer side:

09:01:09,148 ERROR [V2MarkupServiceImpl:104] com.liferay.portal.kernel.exception.SystemException: Unable to find <liferay-wsrp-portlet>
com.liferay.portal.kernel.exception.SystemException: Unable to find <liferay-wsrp-portlet>
at com.liferay.wsrp.bind.V2MarkupServiceImpl.getContent(V2MarkupServiceImpl.java:556)
at com.liferay.wsrp.bind.V2MarkupServiceImpl.doGetMarkup(V2MarkupServiceImpl.java:244)
at com.liferay.wsrp.bind.V2MarkupServiceImpl.getMarkup(V2MarkupServiceImpl.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at com.liferay.util.axis.AxisServlet.service(AxisServlet.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:72)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:121)
at com.liferay.util.axis.AxisCleanUpFilter.processFilter(AxisCleanUpFilter.java:48)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:48)
at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.processDoFilter(InvokerFilterChain.java:203)
at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:105)
at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilter.doFilter(InvokerFilter.java:70)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:928)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:539)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:298)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

1. Add a producer for a build-in portlet (i.e. Unit Converter) in one instance of LR 6.1GA1
2. Add a consumer for the URL given in step 1 in another instance of LR 6.1GA1
3. Configure a portlet for the consumer in step 2
4. Add portlet from step 3 to the frontpage
5. Get the message "Portlet is temporarily unavailable."
6. Find the Exception in producer logfile

This might be a Regression to LPS-10127.

[Drew Blessing]

Arne,

Thank you for your report. As part of the community verifier program I am going to take a look at this issue. In the meantime, if you find any other information that may help me verify this bug please add a comment.

Thanks!

[Arne v.Irmer]

Hi Drew,
we want to implement a server with a frontend LR 6.1ga1, several backend LR 6.1ga1 (one for each institute at our university) and one LR 6.0.5 for running the "old" portlets.
In my investigations only WSRP from 6.0.5 to 6.0.5 works.
I'm always downloading the official tomcat-distributions of LR-CE and start them on a single machine with the default data.

I hope you find that bug, because I sold my soul for WSRP in my architecture of the new University portal.

Yours
Arne

[Drew Blessing]

Alright, so let me be sure I understand the steps I need to reproduce this bug.

1. Liferay instance 1 - Add some portlet to the page (i.e. Unit Converter).
2. Open portlet configuration -> Sharing tab.
3. Copy code given
4. Liferay instance 2 - Add new Web Content Display
5. Paste source code from step 3
6. Public Web Content
7. Observe effects

Please let me know if this is correct. If not, please provide me with detailed steps so that I may confirm this bug.

Thanks, Arne.

[Drew Blessing]

I believe I misunderstood the WSRP. I am on the right track now.

[Arne v.Irmer]

Reproduce this bug as posted:
1. Add a producer for a build-in portlet (i.e. Unit Converter) in instance 1
2. Add a consumer for the URL given in step 1 in instance 2
3. Configure a portlet for the consumer in step 2
4. Add portlet from step 3 to the frontpage
5. Get the message "Portlet is temporarily unavailable." in instance 2
6. Find the Exception in instance 1

[Drew Blessing]

Thanks, Arne. I was unable to reproduce this bug. I tested this in two fresh Liferay 6.1.0 CE GA1 instances with sample data.

Steps I used to attempt to reproduce the problem:
1. On 1st Liferay instance - Control Panel -> WSRP
2. Producers -> Add Producer
3. Name the Producer, move "Unit Converter" to the Current column, and Save.
4. Copy the Producer URL.
5. On 2nd Liferay instance - Control Panel -> WSRP
6. Add Consumer
7. Name the Consumer, paste the Producer URL from step 4, and save.
8. Select Action -> Manage Portlets for the Consumer
9. Add Portlet
10. Name the portlet, select the Remote Portlet and save.
11. Go to main site
12. Choose Add -> More -> WSRP -> <Name of portlet you just created in step 10>

After completing these steps the new WSRP portlet is correctly displayed. Please make sure you have a fresh environment with no other issues interfering with this bug. If you still experience the issue please provide more information so that we may correctly verify the problem.

Thanks!

[Arne v.Irmer]

Hi Drew

I went back to the beginning and installed two fresh LR6.1ga1 on my desktop. There I can't reproduce the problem, too. Now I used the last hours to go step by step back in the configuration to the constellation that has the problem. The reported exception occurs in that moment where I bound the tomcat-connectors to an interface different than localhost via tomcat/conf/server.xml . Switching back and for can turn on and of the exception on my server now.
Now I went back to the initial installation on my desktop and tried to reproduce the exception there but it doesn't appear. I can switch the interface to what I want, it always run on my desktop.
So here is what I've done on my Server:

• JAVA_OPTS="-DproxySet=true -Dhttp.proxyHost=cache.uni-dortmund.de -Dhttp.proxyPort=1234 -DproxyHost=cache.uni-dortmund.de -DproxyPort=1234 -Dhttp.nonProxyHosts=lr-itmc|lr-bib|lr-verw|10.0.0.10|lr-bib.itmc.tu-dortmund.de -Djavax.net.ssl.trustStore=/home/portal/conf/jssecacerts"
• Using an empty database and this portal-ext.properties

  ## MySQL
  jdbc.default.driverClassName=com.mysql.jdbc.Driver
  jdbc.default.url=jdbc:mysql://localhost:3306/foo?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
  jdbc.default.username=foo
  jdbc.default.password=foo
  
  # Hoks
  dl.hook.impl=com.liferay.documentlibrary.util.JCRHook
  image.hook.impl=com.liferay.portal.image.DatabaseHook
  
  
  ##
  ## JCR
  ##
  jcr.initialize.on.startup=true
  jcr.workspace.name=liferay
  jcr.node.documentlibrary=documentlibrary
  jcr.jackrabbit.repository.root=${liferay.home}/data/jackrabbit
  jcr.jackrabbit.config.file.path=${jcr.jackrabbit.repository.root}/repository.xml
  jcr.jackrabbit.repository.home=${jcr.jackrabbit.repository.root}/home
  jcr.jackrabbit.credentials.username=none
  jcr.jackrabbit.credentials.password=none
  
  #default.landing.page.path=/web/guest/logout
  
  ##
  ## Redirect
  ##
  
      #
      # Set this property to "ip" or "domain" for the redirect security method. If
      # set to "domain", the portal will only redirect users to domains listed in
      # the property "redirect.url.domain.allowed". If set to "ip", the portal
      # will only redirect to domains whose IP address resolve to an IP address
      # listed in the property "redirect.url.ip.allowed".
      #
      redirect.url.security.mode=domain
      #redirect.url.security.mode=ip
  
      #
      # Input a list of comma delimited domains which the portal is allowed to
      # redirect to. Input a blank list to allow any domain.
      #
      redirect.url.domains.allowed=
  
      #
      # Input a list of comma delimited IPs which the portal is allowed to
      # redirect to. Input a blank list to allow any IP. SERVER_IP will be
      # replaced with the IP of the host server.
      #
      redirect.url.ips.allowed=127.0.0.1,123.123.123.123
  
  layout.user.private.layouts.enabled=false   //activate Personal Community with *private* pages 
  layout.user.public.layouts.enabled=false
  admin.default.role.names=
  

Something will cause the problem. I have a solution for me now and no more time to find out, what in my server-constellation causes the exception.

Yours
Arne

[Drew Blessing]

Thanks for getting back to me, Arne. Sounds like this is not a Liferay bug.

Recommending closure based on previous response.

[Vivek Srivastava]

Hi Drew,

In above scenario while adding consumer portlet if we enable parallel rendering then we able to reproduce the bug.
please check at let me know is it reproducible in that scenario.

yours
Vivek

[Avadhoot Sawant]

This issue still persists. It happens when you try to deploy liferay.war on tomcat with putting following entry for context file in tomcat 7

<Context path="/liferay" docBase="C:/FASTAS_3.1.0/fcHome/deployment/tomcat01/apps/liferay"
distributable="true" crossContext="true">

[Avadhoot Sawant]

I resolved this by commenting lines
V2MarkupServiceImpl.java in wsrp source code.

line 742 -line 749