Error in CAF

I getting the following error while trying to modify a value in DB using portlets.

com.webmethods.caf.faces.data.ContentProviderException: [POP.016.0009] Connection failed to datasource java:comp/env/VMRFIDBConnection. Caused by: 284conflicts while synchronizing
at com.webmethods.caf.faces.data.sql.RowSetTableContentProvider.handleException(RowSetTableContentProvider.java:452)
at com.webmethods.caf.faces.data.sql.RowSetTableContentProvider.applyChanges(RowSetTableContentProvider.java:812)
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 com.sun.el.parser.AstValue.invoke(AstValue.java:187)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297)
at com.sun.faces.application.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
at com.webmethods.caf.faces.application.CAFMethodBinding.invoke(CAFMethodBinding.java:65)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
at javax.faces.component.UICommand.broadcast(UICommand.java:387)
at com.webmethods.caf.faces.component.table.html.DataTable.broadcast(DataTable.java:759)
at com.webmethods.caf.faces.component.ViewRoot.broadcastEvents(ViewRoot.java:227)
at com.webmethods.caf.faces.component.ViewRoot.processApplication(ViewRoot.java:120)
at com.webmethods.caf.faces.portlet.PortletLifecycle$InvokeApplicationPhase.execute(PortletLifecycle.java:723)
at com.webmethods.caf.faces.portlet.PortletLifecycle.phase(PortletLifecycle.java:261)
at com.webmethods.caf.faces.portlet.PortletLifecycle.execute(PortletLifecycle.java:151)
at com.webmethods.caf.faces.portlet.FacesPortlet.processAction(FacesPortlet.java:300)
at com.webmethods.portal.framework.portletcontainer.impl.PortletApplicationHandler.process(PortletApplicationHandler.java:480)
at com.webmethods.portal.framework.portletcontainer.servlet.PortletServlet.service(PortletServlet.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:327)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
at com.webmethods.portal.framework.portletcontainer.PortletContainer.dispatch(PortletContainer.java:219)
at com.webmethods.portal.framework.portletcontainer.PortletContainer.process(PortletContainer.java:130)
at com.webmethods.portal.framework.portletcontainer.PortletContainer.processPortletAction(PortletContainer.java:108)
at com.webmethods.portal.framework.portlet.beans.rest.RestfulPCAHandler.handle(RestfulPCAHandler.java:194)
at com.webmethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:438)
at com.webmethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:369)
at com.webmethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:272)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.webmethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.webmethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:42)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:938)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)

The error reports 284 conflicts while synchronizing. I understood that the number “284” is actually the count of rows in DB. I am doing a join of 3 tables in the connector. I am working in 8.2 and I designed the same portlet view (with all the same settings) in 7.1.2 where it is working fine. Could someone please help me understant the error and how to fix it.

Any help will be really appreciated.

This issue has been resolved.

Whenever we modify the Aync table in Designer 8.2 (for portlet in MWS 8.2) to add the new column, it automatically resets the managed bean class to its default value (com.sun.rowset.CachedRowSetImpl) which causes the “conflicts while synchronizing” error.

I set this value to com.webmethods.caf.faces.data.sql.rowset.CAFRowSetImpl for the managed bean that was causing the error.

Now everything is working fine.

Thanks for the updating your valuable post and it helps:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.