Syndication Problem in WebSphere Portal V6.1 - Websphere

This is a discussion on Syndication Problem in WebSphere Portal V6.1 - Websphere ; am trying to syndicate between two environment , syndicator being non-clustered and subscriber being clustered and subscriber is on secondary node. i can able to ping each other , when i click on update syndicator .i get following error. [2/26/09 ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: Syndication Problem in WebSphere Portal V6.1

  1. Syndication Problem in WebSphere Portal V6.1

    am trying to syndicate between two environment , syndicator being non-clustered and subscriber being clustered and subscriber is on secondary node.

    i can able to ping each other , when i click on update syndicator .i get following error.

    [2/26/09 13:12:53:845 AST] 00000044 ServletWrappe I SRVE0242I: [wps] [/wps] [CacheProxyServlet]: Initialization successful.
    com.aptrix.deployment.DeploymentException: IWKMU1062X: Message: IWKSY1057X: Code #300, IWKSY1058X: phrase: Generic catastrophic payload error, IWKSY1059X: detail: IWKSY1051X: Response code was not OK: 403, Cause: com.aptrix.syndication.messaging.GenericPayloadExc eption: IWKSY1057X: Code #300, IWKSY1058X: phrase: Generic catastrophic payload error, IWKSY1059X: detail: IWKSY1051X: Response code was not OK: 403
    [2/26/09 13:13:08:339 AST] 00000043 UpdateSyndica E Could not update syndicator with name TestingToStagingSyndication
    com.aptrix.deployment.DeploymentException: IWKMU1062X: Message: IWKSY1057X: Code #300, IWKSY1058X: phrase: Generic catastrophic payload error, IWKSY1059X: detail: IWKSY1051X: Response code was not OK: 403, Cause: com.aptrix.syndication.messaging.GenericPayloadExc eption: IWKSY1057X: Code #300, IWKSY1058X: phrase: Generic catastrophic payload error, IWKSY1059X: detail: IWKSY1051X: Response code was not OK: 403
    at com.aptrix.deployment.syndicator.PlutoSyndicator.s endUpdateRequest(PlutoSyndicator.java:486)
    at com.ibm.workplace.wcm.app.ui.admin.syndicator.Upda teSyndicatorCommand.doCommand(UpdateSyndicatorComm and.java:169)
    at com.ibm.workplace.wcm.app.ui.portlet.command.Abstr actCommand.commandPerformed(AbstractCommand.java:1 74)
    at com.ibm.psw.wcl.core.CommandHandler.handleCommand( CommandHandler.java:74)
    at com.ibm.psw.wcl.core.markup.WHyperlink$EHyperlinkC allbackWrapper.handleTrigger(WHyperlink.java:475)
    at com.ibm.psw.wcl.core.trigger.Trigger.process(Trigg er.java:299)
    at com.ibm.psw.wcl.core.trigger.TriggerManager.proces sTrigger(TriggerManager.java:781)
    at com.ibm.psw.wcl.portlet.WclPortletTriggerManager.h andleRequest(WclPortletTriggerManager.java:260)
    at com.ibm.psw.wcl.portlet.WclPortletFacade.handleReq uest(WclPortletFacade.java:497)
    at com.ibm.psw.wcl.portlet.WclPortletFacade.handleReq uest(WclPortletFacade.java:478)
    at com.ibm.workplace.wcm.app.ui.admin.AdminPortlet.ha ndleActionPerformed(AdminPortlet.java:284)
    at com.ibm.workplace.wcm.app.ui.admin.AdminPortlet.ac tionPerformed(AdminPortlet.java:238)
    at com.ibm.wps.pe.pc.legacy.SPIPortletInterceptorImpl .handleEvents(SPIPortletInterceptorImpl.java:337)
    at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDeleg ateImpl._dispatch(PortletDelegateImpl.java:382)
    at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDeleg ateImpl.access$200(PortletDelegateImpl.java:70)
    at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDeleg ateImpl$Context.callPortlet(PortletDelegateImpl.ja va:550)
    at com.ibm.wps.pe.pc.legacy.services.PortletFilterSer viceImpl.doFilter(PortletFilterServiceImpl.java:36 7)
    at com.ibm.wps.pe.pc.legacy.services.PortletFilter.do Filter(PortletFilter.java:42)
    at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDeleg ateImpl.dispatch(PortletDelegateImpl.java:141)
    at org.apache.jetspeed.portlet.Portlet.doGet(Portlet. java:499)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:743)
    at com.ibm.wps.pe.pc.legacy.cache.CacheablePortlet.se rvice(CacheablePortlet.java:120)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
    at org.apache.jetspeed.portlet.Portlet.service(Portle t.java:493)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1068)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:543)
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:478)
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cher.include(WebAppRequestDispatcher.java:639)
    at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletInvok erImpl.callMethod(PortletInvokerImpl.java:370)
    at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletInvok erImpl.action(PortletInvokerImpl.java:78)
    at com.ibm.wps.pe.pc.legacy.PortletContainerImpl.call PortletMethod(PortletContainerImpl.java:1125)
    at com.ibm.wps.pe.pc.legacy.EventEnvironmentImpl.incl udePortlet(EventEnvironmentImpl.java:171)
    at com.ibm.wps.pe.pc.legacy.event.ActionEventImpl.pre pare(ActionEventImpl.java:201)
    at com.ibm.wps.pe.pc.legacy.event.EventQueueManager.p rocessEventLoop(EventQueueManager.java:88)
    at com.ibm.wps.pe.pc.legacy.PortletContainerImpl.perf ormEvents(PortletContainerImpl.java:218)
    at com.ibm.wps.pe.pc.PortletContainerImpl.performEven ts(PortletContainerImpl.java:296)
    at com.ibm.wps.engine.phases.WPActionPhase.processPor tlets(WPActionPhase.java:2461)
    at com.ibm.wps.engine.phases.WPActionPhase.execute(WP ActionPhase.java:678)
    at com.ibm.wps.state.phases.AbstractActionPhase.next( AbstractActionPhase.java:130)
    at com.ibm.wps.engine.Servlet.callPortal(Servlet.java :800)
    at com.ibm.wps.engine.Servlet.doGet(Servlet.java:607)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:743)
    at com.ibm.wps.engine.Servlet.doFilter(Servlet.java:1 184)
    at com.ibm.wps.resolver.servlet.ContentHandlerCleanup .doFilter(ContentHandlerCleanup.java:648)
    at com.ibm.wps.resolver.servlet.AbstractFilter.doFilt er(AbstractFilter.java:82)
    at com.ibm.wps.engine.Servlet.service(Servlet.java:11 75)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1068)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1009)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:145)
    at com.ibm.wps.engine.ExtendedLocaleFilter.doFilter(E xtendedLocaleFilter.java:93)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.wps.state.filter.StateCleanup.doFilter(Sta teCleanup.java:89)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.wps.resolver.friendly.servlet.FriendlySele ctionFilter.doFilter(FriendlySelectionFilter.java: 189)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.wps.engine.VirtualPortalFilter.doFilter(Vi rtualPortalFilter.java:88)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.wps.mappingurl.impl.URLAnalyzer.doFilter(U RLAnalyzer.java:282)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain._ doFilter(WebAppFilterChain.java:87)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager .doFilter(WebAppFilterManager.java:771)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager .doFilter(WebAppFilterManager.java:679)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:539)
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:478)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleReques t(WebApp.java:3365)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequ est(WebGroup.java:267)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:814)
    at com.ibm.ws.wswebcontainer.WebContainer.handleReque st(WebContainer.java:1455)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:115)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:454)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:383)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.ready(HttpInboundLink.java:279)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.sendToDiscriminators(NewConnectionIniti alReadCallback.java:214)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.complete(NewConnectionInitialReadCallba ck.java:113)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListe ner.futureCompleted(AioReadCompletionListener.java :165)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallbac k(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletion Actions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture .java:136)
    at com.ibm.io.async.ResultHandler.complete(ResultHand ler.java:195)
    at com.ibm.io.async.ResultHandler.runEventProcessingL oop(ResultHandler.java:743)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler .java:873)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)
    Caused by: com.aptrix.syndication.messaging.GenericPayloadExc eption: IWKSY1057X: Code #300, IWKSY1058X: phrase: Generic catastrophic payload error, IWKSY1059X: detail: IWKSY1051X: Response code was not OK: 403
    at com.aptrix.syndication.messaging.HttpMessaging.ret rieveIceHttpResponse(HttpMessaging.java:157)
    at com.aptrix.syndication.messaging.HttpMessaging.sen dIceHttpRequest(HttpMessaging.java:92)
    at com.aptrix.syndication.business.AbstractRequestBL. sendRequest(AbstractRequestBL.java:64)
    at com.aptrix.syndication.business.syndicator.Request BL.getCurrentState(RequestBL.java:85)
    at com.aptrix.syndication.business.syndicator.Syndica torTaskManager.addSubscriptionUpdate(SyndicatorTas kManager.java:666)
    at com.aptrix.deployment.syndicator.PlutoSyndicator.s endUpdateRequest(PlutoSyndicator.java:452)
    ... 86 more

  2. Re: Syndication Problem in WebSphere Portal V6.1


  3. Re: Syndication Problem in WebSphere Portal V6.1

    I hope we have to change deployment.subscriberUrl property to subscriber hostname in the subscriber machine.

    my Subscriber hostname is 10.10.10.207 and my syndicator machine ip is 10.10.10.212, so the property in the subscriber machine is

    deployment.subscriberUrl=http://10.10.10.207:10040/wcm/connect/?MOD=Subs .

    I did this but it didnt worked for me .............

  4. Re: Syndication Problem in WebSphere Portal V6.1

    I think that your URL should read: http://10.10.10.207:10040/wps/wcm/connect/?MOD=Subs

    Also make sure that these servers can ping each other with FQDN/alias/IP.

  5. Re: Syndication Problem in WebSphere Portal V6.1

    I modified the url as you told , i can ping both my subscriber and syndicator , but still Syndication doesnt work

    see attach for SystemOut.log and trace.log

  6. Re: Syndication Problem in WebSphere Portal V6.1

    http://10.10.72.4:10040/wps/wcm/connect/?MOD=Subs (see line 37 of trace.log)?
    Also is the IP of tstwps 10.10.10.212?

  7. Re: Syndication Problem in WebSphere Portal V6.1

    Sorry ,That was different machine .Now I tried Syndication with these machines , syndicator ip 10.10.71.4 and subscriber ip 10.10.72.4 , But am getting same error.

  8. Re: Syndication Problem in WebSphere Portal V6.1

    This is the error am getting at the subscriber side when am trying to update

  9. Re: Syndication Problem in WebSphere Portal V6.1

    that error looks like the subscriber name does not match between the syndicator and subscriber objects.

    If teh subscriber name on the synd object is SubscribingFromTesting, it should be the same on teh subscriber

  10. Re: Syndication Problem in WebSphere Portal V6.1

    On Mar 12, 12:51*pm, thoma...@us.ibm.com wrote:
    > that error looks like the subscriber name does not match between the syndicator and subscriber objects.
    >
    > If teh subscriber name on the synd object is SubscribingFromTesting, it should be the same on teh subscriber


    HI

    You were saying that you are trying to syndicate between two
    environment , could you please check that the servers in two
    environment are able to talk to each other without any firewall/ports
    blocked issue..

+ Reply to Thread