[JBoss JIRA] Created: (JBAS-4016) failing org.jboss.test.jca.test.BaseConnectionManager{Unit|Stress}TestCase
by Dimitris Andreadis (JIRA)
failing org.jboss.test.jca.test.BaseConnectionManager{Unit|Stress}TestCase
--------------------------------------------------------------------------
Key: JBAS-4016
URL: http://jira.jboss.com/jira/browse/JBAS-4016
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Test Suite
Environment: Java Version 1.5.0_10
Java Vendor Sun Microsystems Inc.
Java VM Name Java HotSpot(TM) Server VM
Java VM Version 1.5.0_10-b03
Java VM Info mixed mode
OS Name Linux
OS Version 2.6.9-42.0.2.ELsmp
OS Arch i386
Reporter: Dimitris Andreadis
Assigned To: Weston Price
Fix For: JBossAS-4.2.0.CR1
Probably already seen those those?
org.jboss.test.jca.test.BaseConnectionManagerStressTestCase
testShortBlockingPartFill Failure Wrong number of connections counted: 2
junit.framework.AssertionFailedError: Wrong number of connections counted: 2
at org.jboss.test.jca.test.BaseConnectionManagerStressTestCase.doShortBlocking(BaseConnectionManagerStressTestCase.java:275)
at org.jboss.test.jca.test.BaseConnectionManagerStressTestCase.testShortBlockingPartFill(BaseConnectionManagerStressTestCase.java:127)
2.786
testShortBlockingNearlyFill Failure Wrong number of connections counted: 4
junit.framework.AssertionFailedError: Wrong number of connections counted: 4
at org.jboss.test.jca.test.BaseConnectionManagerStressTestCase.doShortBlocking(BaseConnectionManagerStressTestCase.java:275)
at org.jboss.test.jca.test.BaseConnectionManagerStressTestCase.testShortBlockingNearlyFill(BaseConnectionManagerStressTestCase.java:133)
1.404
org.jboss.test.jca.test.BaseConnectionManagerUnitTestCase
testMisConfiguredFillToMin Failure Wrong number of connections counted: 6
junit.framework.AssertionFailedError: Wrong number of connections counted: 6
at org.jboss.test.jca.test.BaseConnectionManagerUnitTestCase.testMisConfiguredFillToMin(BaseConnectionManagerUnitTestCase.java:244)
1.008
--
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] Updated: (JBPORTAL-730) "Copy" should copy the live revision
by Julien Viet (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-730?page=all ]
Julien Viet updated JBPORTAL-730:
---------------------------------
Fix Version/s: (was: 2.6.Beta1)
Priority: Optional (was: Major)
is that task useful ?
> "Copy" should copy the live revision
> ------------------------------------
>
> Key: JBPORTAL-730
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-730
> Project: JBoss Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Portal CMS
> Affects Versions: 2.6.Beta1
> Reporter: Thomas Heute
> Assigned To: Roy Russo
> Priority: Optional
>
> The current "copy" feature using Jackrabbit Workspace.copy() seems to copy the latest revision and only that one.
> Jackrabbit implementation won't help here (since it should be faster to do it at this level)
> If we decide to copy a unique revision we should copy the Live version. (can be different from the latest)
> Now the question is: should we copy all revisions or only the live one ?
--
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-1237) delete user does not delete dashboard settings for the user
by Anders Andersen (JIRA)
delete user does not delete dashboard settings for the user
-----------------------------------------------------------
Key: JBPORTAL-1237
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1237
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Identity
Affects Versions: 2.6.Alpha2, 2.6.Alpha1
Environment: mac osx 10.4.8 PPC
JVM 1.5.0_06-64
Browser Firefox 1.5.0.9
Reporter: Anders Andersen
Priority: Minor
When I delete a user and creates the user again I see that dashboard content is keept.
There seems to miss a handler that delete content in other tables when the "Users Portlet" deletes a user.
This error remains in ALPHA2.
Under the test of this, I did the following:
1) created a user brian
2) logged in as brian
3) logged in as admin
3) deleted brian (using Users Portlet)
4) Logged in as brian again.
Here I got a null-pointer error.
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException
org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:407)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
java.lang.NullPointerException
org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.injectDashboardNav(PageCustomizerInterceptor.java:192)
org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:127)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:68)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:54)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:86)
org.jboss.portal.core.controller.classic.ClassicController.handle(ClassicController.java:88)
sun.reflect.GeneratedMethodAccessor406.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:287)
$Proxy218.handle(Unknown Source)
org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:46)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:67)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:108)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:188)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.server.aspects.server.SessionInvalidatorInterceptor.invoke(SessionInvalidatorInterceptor.java:85)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49)
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
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.common.invocation.Invocation.invoke(Invocation.java:157)
org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:381)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
--
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