1 Reply Latest reply on Apr 17, 2008 8:51 AM by Marco Antonio Porcho Souza

    Problem uploading file: "Unable to getNode"

    Marco Antonio Porcho Souza Newbie

      Hi there. I'm using JBoss Portal 2.6.4-GA on Windows XP, and PostgreSQL 8.1.

      Currently, I'm developing a portlet that access the CMSService to upload a file. Frequently, the directory I upload files into become corrupted, and I can't upload files to them anymore. I get an exception like the one that follows, from the moment the directory gets corrupted:

      ERROR
      Cause: javax.portlet.PortletException: java.lang.RuntimeException: javax.jcr.RepositoryException: Unable to getNode: org.apache.jackrabbit.core.state.NoSuchItemStateException: 4cddd4f0-e55e-454f-8cff-511b57df6428
      Message: java.lang.RuntimeException: javax.jcr.RepositoryException: Unable to getNode: org.apache.jackrabbit.core.state.NoSuchItemStateException: 4cddd4f0-e55e-454f-8cff-511b57df6428
      StackTrace:

      javax.portlet.PortletException: java.lang.RuntimeException: javax.jcr.RepositoryException: Unable to getNode: org.apache.jackrabbit.core.state.NoSuchItemStateException: 4cddd4f0-e55e-454f-8cff-511b57df6428
      at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.internalProcessAction(CMSAdminPortlet.java:826)
      at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.processAction(CMSAdminPortlet.java:686)
      at org.jboss.portlet.JBossPortlet.processAction(JBossPortlet.java:385)
      at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.invokeAction(PortletContainerImpl.java:458)
      at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:401)
      at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(PortletContainerInvoker.java:86)
      at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
      at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(TransactionInterceptor.java:106)
      at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.java)
      at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
      at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)

      (...)



      My CMSService uses the default configuration when it comes to store (ie. 100% database storage).

      Is there a way I can fix this problem? And how can I avoid this directory corruption?

      Thanks in advance!