[jboss-user] [JBoss Portal] - Re: CMSAdminPortlet 2.6.4 Upload Archive Fails:

laurent.vernet do-not-reply at jboss.com
Fri Feb 15 10:26:23 EST 2008


Hi All,

Same problem with File System Repository.
JBP 2.6.4 starts well, building of default content in filesystem OK.
But when uploading my archive file (80kb .zip), the process is a bit long.
Looking at the file system, all the workspace's directories are created,
but the CMSAdminPortlet returns with a stack trace:

  | Etat HTTP 500 -
  | 
  | type Rapport d'exception
  | 
  | message
  | 
  | description Le serveur a rencontré une erreur interne () qui l'a empêché de satisfaire la requête.
  | 
  | exception
  | 
  | javax.servlet.ServletException: java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
  | 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:276)
  | 	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 
  | cause mère
  | 
  | java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
  | 	com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1379)
  | 	com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
  | 	com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
  | 	org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175)
  | 	org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87)
  | 	org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262)
  | 	org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
  | 	org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java)
  | 	org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
  | 	org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	org.jboss.portal.server.aspects.LockInterceptor$InternalLock.invoke(LockInterceptor.java:69)
  | 	org.jboss.portal.server.aspects.LockInterceptor.invoke(LockInterceptor.java:130)
  | 	org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
  | 	org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
  | 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:250)
  | 	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 
  | note La trace complète de la cause mère de cette erreur est disponible dans les fichiers journaux de JBossWeb/2.0.1.GA.


Why is this process so long ? Any recursion ? Filtering ? or antivirus ?

Thanks for your attention.

Be back in some hours or days maybe. 

Laurent.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129679#4129679

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129679




More information about the jboss-user mailing list