[JBoss JIRA] Created: (JBCACHE-937) Benchmark VersionAwareMarshaller
by Galder Zamarreno (JIRA)
Benchmark VersionAwareMarshaller
--------------------------------
Key: JBCACHE-937
URL: http://jira.jboss.com/jira/browse/JBCACHE-937
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.ALPHA2
Reporter: Galder Zamarreno
Assigned To: Manik Surtani
Fix For: 2.0.0.BETA2
Benchmark VersionAwareMarshaller to make it more performant. There's already a
unit test to use it as base: VersionAwareMarshallerPerfTest.
It should probably make comparison failures based on results from different
marshalling methods, i.e, if difference bigger than x, fail. Also add marshalling different
types of objects.
Potential performance improvements:
- Using similar techniques as used in ExposedByteArrayOutputStream (JGroups) for VAM?
Needs profiling to determine effect.
--
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
19 years, 3 months
[JBoss JIRA] Created: (EJBTHREE-881) IsLocalInterceptor not detecting local container after failover
by Brian Stansberry (JIRA)
IsLocalInterceptor not detecting local container after failover
---------------------------------------------------------------
Key: EJBTHREE-881
URL: http://jira.jboss.com/jira/browse/EJBTHREE-881
Project: EJB 3.0
Issue Type: Bug
Components: Clustering
Affects Versions: EJB 3.0 RC9 - Patch 1
Reporter: Brian Stansberry
Some unit tests I've written are showing a problem with nested SFSBs where the IsLocalInterceptor doesn't treat a call from a parent SFSB to a nested SFSB as local, but Remoting optimizes it locally. This leads to an exception in the transaction propagation handling.
What's strange is for the call that fails AFAICT IsLocalInterceptor and AOPRemotingInvocationHandler are both dealing with Dispatcher using the same Invocation and the same metadata. But when IsLocalInterceptor queries Dispatcher, it says the container isn't registered, while when AOPRemotingInvocationHandler asks Dispatcher to handle the invocation, it finds the container just fine.
See forum thread for details.
--
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
19 years, 3 months
[JBoss JIRA] Created: (JBPORTAL-1278) CMS create content item fails on save
by Ian White (JIRA)
CMS create content item fails on save
-------------------------------------
Key: JBPORTAL-1278
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1278
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.Alpha2
Environment: AS 4.0.5.GA, XP
Reporter: Ian White
Assigned To: Roy Russo
In the CMS admin portlet, click to create a new file.
Use the WYSIWYG editor ...
Try to save the new file by clicking "create".
You get the error: Cannot mark the content as "Live"
javax.servlet.ServletException
org.jboss.portal.server.servlet.PortalServlet.service(Unknown Source)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
java.lang.IllegalStateException
org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:418)
org.jboss.portal.core.controller.classic.AbstractResponseHandler.sendStatusCode(Unknown Source)
org.jboss.portal.core.controller.portlet.PortletResponseHandler.handleResponse(Unknown Source)
org.jboss.portal.core.controller.classic.ClassicController.handleResponse(Unknown Source)
...
01:17:22,540 ERROR [STDERR] Caused by: org.jboss.portal.cms.CMSException: Cannot mark the content as "Live"
01:17:22,540 ERROR [STDERR] at org.jboss.portal.cms.impl.jcr.util.VersionUtil.createContentVersion(VersionUtil.java:91)
01:17:22,540 ERROR [STDERR] at org.jboss.portal.cms.impl.jcr.util.VersionUtil.createVersion(VersionUtil.java:63)
01:17:22,540 ERROR [STDERR] at org.jboss.portal.cms.impl.jcr.command.ContentCreateNewVersionCommand.execute(ContentCreateNewVersionCommand.java:117)
01:17:22,540 ERROR [STDERR] ... 246 more
01:17:22,540 ERROR [org_jboss_portal_core_cms_ui_admin_CMSAdminPortlet] The portlet threw an exception
java.lang.RuntimeException: org.jboss.portal.cms.CMSException: Cannot mark the content as "Live"
at org.jboss.portal.cms.impl.jcr.command.ContentCreateNewVersionCommand.execute(ContentCreateNewVersionCommand.java:127)
at org.jboss.portal.cms.impl.jcr.JCRCompositeCommand.execute(JCRCompositeCommand.java:49)
at org.jboss.portal.cms.impl.jcr.JCRCMS$1.invoke(JCRCMS.java:115)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Unknown Source)
at org.jboss.portal.cms.impl.interceptors.ApprovalWorkflowInterceptor.invoke(ApprovalWorkflowInterceptor.java:87)
at org.jboss.portal.cms.CMSInterceptor.invoke(CMSInterceptor.java:36)
--
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
19 years, 3 months