[JBoss JIRA] Created: (JBPORTAL-1315) CMS content rendered with wrong tx on thread
by David Allen (JIRA)
CMS content rendered with wrong tx on thread
--------------------------------------------
Key: JBPORTAL-1315
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1315
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.Alpha2
Reporter: David Allen
Assigned To: Roy Russo
This might be a problem in "core" or somewhere else, but this only occurs with windows containing CMS content. The exact steps which cause it are:
1. Display a page with a CMS content window in a new browser window.
2. Click on the login link on the dashboard.
3. When the same page is rendered after successful login (now under authsec), the following exception occurs and the CMS content is not displayed (replaced with exception):
2007-03-09 16:02:06,874 ERROR [org.jboss.portal.server.servlet.PortalServlet] Unexpected exception
java.lang.IllegalStateException: Wrong tx on thread: expected TransactionImpl:XidImpl[FormatId=257, GlobalId=tines/83, BranchQual=, localId=83], actual TransactionImpl:XidImpl[FormatId=257, GlobalId=tines/84, BranchQual=, localId=84]
at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:162)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87)
at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262)
at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
at org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:381)
If more of the stack trace is needed, let me know. The rest doesn't look that useful -- just the usual processing. The same exception causes many different classes to log the error along the way, so I hope I picked up the right log message here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBPORTAL-1216) Problem with defining user listener service
by Mykola Hryhoryan (JIRA)
Problem with defining user listener service
-------------------------------------------
Key: JBPORTAL-1216
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1216
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.Alpha1
Environment: JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)]
Reporter: Mykola Hryhoryan
Assigned To: Julien Viet
User listener service, defined in <app>/META-INF/jboss-service.xml doesn't start.
jboss-service.xml code:
<server>
<mbean
code="org.jboss.portal.core.event.PortalEventListenerServiceImpl"
name="portal:service=ListenerService,type=window_listener"
xmbean-dd=""
xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
<xmbean />
<depends optional-attribute-name="Registry"
proxy-type="attribute">
portal:service=ListenerRegistry
</depends>
<attribute name="RegistryId">window_listener</attribute>
<attribute name="ListenerClassName">
biz.spacepeople.listeners.WindowConstraintEventListener
</attribute>
</mbean>
</server>
libarry with class WindowConstraintEventListener is in <JBOSS_HOME>\server\default\deploy\jboss-portal.sar\lib\
Sservice starts only if put mbean code into <JBOSS_HOME>\server\default\deploy\jboss-portal.sar\META-INF\jboss-service.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBPORTAL-1137) Programatic control of portlet caching behavior
by Jerry Lacy (JIRA)
Programatic control of portlet caching behavior
-------------------------------------------------
Key: JBPORTAL-1137
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1137
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Portlet
Affects Versions: 2.4 Final
Environment: Portal 2.4, JDK 1.5, WindowsXP
Reporter: Jerry Lacy
Assigned To: Julien Viet
Attempts to programatically alter the EXPIRATION_CACHE setting of a portlet from within the doView() method has not effect.
e.g.
response.setProperty( RenderResponse.EXPIRATION_CACHE, "0" );
Unless I am missing something, it doesn't appear that this was implemented anywhere (as of the 2.4 final release). I believe the problem is on line 65 of
org.jboss.portal.portlet.aspects.portlet.ProducerCacheInterceptor.invoke(). The cache expiration value is being updated on each request using the configured EXPIRATION_CACHE value regardless of whether an EXPIRATION_CACHE property was set on the response. I added the following test which seems to work based on what little testing I have done so far:
// Update the fragment cache info only if the value has not been overridden during render processing
if ( fragmentResult.getProperties().getProperty(RenderResponse.EXPIRATION_CACHE) == null ) {
fragmentResult.setExpirationSecs(cacheInfo.getExpirationSecs());
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months