February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBPORTAL-868) Consumer managed state testing

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-868?page=all ] Julien Viet resolved JBPORTAL-868. ---------------------------------- Resolution: Done > Consumer managed state testing > ------------------------------ > > Key: JBPORTAL-868 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-868 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Julien Viet > Fix For: 2.6.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I have added InstanceContext.portletCloned(String portletId, byte[] state) method. We need a test case that retrieves the byte array state from the WSRP PortletContext and makes a callback to the InstanceContext.portletCloned method as we must support consumer state management in our WSRP consumer. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1232) Portlet instances could not be created

by Ryszard Kozmik (JIRA)

Portlet instances could not be created -------------------------------------- Key: JBPORTAL-1232 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1232 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1, 2.6.Alpha2 Environment: AS 4.0.5 JBoss Portal 2.6Alpha1 and Alpha2 Reporter: Ryszard Kozmik Assigned To: Julien Viet Fix For: 2.6.Beta1 Below is part of AS starting log while deploying JBoss Portal 2.6Alpha2. 01:05:48,173 WARN [InstanceMetaData] The instance PolicyConfiguratorPortletInstance will not be created because the component referenced is outside of the same web app portal.PolicyConfiguratorPortlet 01:05:48,173 WARN [InstanceMetaData] The instance DefaultCMSPortletInstance will not be created because the component referenced is outside of the same web app portal.CMSPortlet 01:05:48,173 WARN [InstanceMetaData] The instance CMSAdminPortletInstance will not be created because the component referenced is outside of the same web app portal.CMSAdminPortlet 01:05:48,173 WARN [InstanceMetaData] The instance ManagementPortletInstance will not be created because the component referenced is outside of the same web app portal.ManagementPortlet 01:05:48,173 WARN [InstanceMetaData] The instance NavigationPortletInstance will not be created because the component referenced is outside of the same web app portal.NavigationPortlet 01:05:48,173 WARN [InstanceMetaData] The instance UserPortletInstance will not be created because the component referenced is outside of the same web app portal.UserPortlet 01:05:48,173 WARN [InstanceMetaData] The instance RolePortletInstance will not be created because the component referenced is outside of the same web app portal.RolePortlet 01:05:48,173 WARN [InstanceMetaData] The instance CatalogPortletInstance will not be created because the component referenced is outside of the same web app portal.CatalogPortlet 01:05:48,173 WARN [InstanceMetaData] The instance ThemePortletInstance will not be created because the component referenced is outside of the same web app portal.ThemeManager 01:05:48,173 WARN [InstanceMetaData] The instance ThemeSelectorInstance will not be created because the component referenced is outside of the same web app portal.ThemeSelectorPortlet 01:05:48,184 ERROR [PortletAppDeployment] Error when creating instances java.lang.ClassCastException: org.jboss.portal.core.deployment.jboss.PortletAppDeployment$InstanceMetaDataContext at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.buildInstances(PortletAppDeployment.java:244) at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(PortletAppDeployment.java:99) at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:210) at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerDeployer.java:217) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy156.deploy(Lorg.jboss.deployment.DeploymentInfo;)V(Unknown Source) at org.jboss.portal.server.deployment.jboss.ServerDeployer.deploy(ServerDeployer.java:259) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) All you have to do to achieve such an impressive failure of instances is place in your AS deployment directory an app with some old default-object.xml(in my case it was like that) in WEB-INF directory. I had default-object.xml there by mistake but still whatever I had in my ear I shouldn't be able to cause Portal's portlet instances to fail. After looking into sources I noticed that in line 445 "extends InstanceMetaData" is missing. When I ran AS with this change code moved a bit further but still there are problems: 01:29:41,074 ERROR [PortletAppDeployment] Error when creating instances java.lang.NullPointerException at org.apache.xml.serializer.TreeWalker.dispatachChars(TreeWalker.java:244) at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:414) at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:143) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:389) at org.jboss.portal.common.util.XML.toString(XML.java:173) at org.jboss.portal.common.util.XML.toString(XML.java:137) at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.buildInstances(PortletAppDeployment.java:252) at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(PortletAppDeployment.java:99) at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:210) at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerDeployer.java:217) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy156.deploy(Lorg.jboss.deployment.DeploymentInfo;)V(Unknown Source) at org.jboss.portal.server.deployment.jboss.ServerDeployer.deploy(ServerDeployer.java:259) -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1229) no clean shutdown of jboss portal

by Prabhat Jha (JIRA)

no clean shutdown of jboss portal --------------------------------- Key: JBPORTAL-1229 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1229 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Reporter: Prabhat Jha Fix For: 2.6.Beta1 It would be good to have a clean shutdown of JBoss Portal. I get following message currently: 8:07:16,433 WARN [ThemeDeploymentFactory] Stopping failed portal:deploymentFactory=Theme java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:785) at java.util.HashMap$KeyIterator.next(HashMap.java:818) at org.jboss.portal.common.util.SetMap$1.next(SetMap.java:187) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.remove(PortalDeploymentInfoContext.java:114) 18:07:16,431 WARN [LayoutFeaturesDeploymentFactory] Stopping failed portal:deploymentFactory=LayoutFeatures java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:785) at java.util.HashMap$KeyIterator.next(HashMap.java:818) at org.jboss.portal.common.util.SetMap$1.next(SetMap.java:187) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.remove(PortalDeploymentInfoContext.java:114) -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-405) New lifecycle classes don't have copyright statement.

by Mark Little (JIRA)

New lifecycle classes don't have copyright statement. ----------------------------------------------------- Key: JBESB-405 URL: http://jira.jboss.com/jira/browse/JBESB-405 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.0 Reporter: Mark Little Assigned To: Kevin Conner Fix For: 4.0 Maintenance Pack 1 E.g., ManagedLifecycleController -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-946) Window changes in admin ui not immediate

by Roy Russo (JIRA)

Window changes in admin ui not immediate ---------------------------------------- Key: JBPORTAL-946 URL: http://jira.jboss.com/jira/browse/JBPORTAL-946 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4 Final Reporter: Roy Russo Assigned To: Julien Viet Moving windows via the ui do not register immediatley when the page refreshes. You must log in again to see the changes. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-403) Quickstart package hierarchy should be org.jboss...

by Mark Little (JIRA)

Quickstart package hierarchy should be org.jboss... --------------------------------------------------- Key: JBESB-403 URL: http://jira.jboss.com/jira/browse/JBESB-403 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.0 Reporter: Mark Little Assigned To: Burr Sutter Priority: Minor Fix For: 4.0 Maintenance Pack 1 -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-695) RemotingRMIClientSocketFactory.createSocket() should return a socket even if a RMIClientInvoker has not been registered.

by Ron Sigal (JIRA)

RemotingRMIClientSocketFactory.createSocket() should return a socket even if a RMIClientInvoker has not been registered. ------------------------------------------------------------------------------------------------------------------------ Key: JBREM-695 URL: http://jira.jboss.com/jira/browse/JBREM-695 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) A new test, org.jboss.test.remoting.callback.asynch.RMIAsynchCallbackTestCase, failed with a null pointer exception because a "premature" call to createSocket() returns null. However, it passes if createSocket() returns a vanilla socket. -- 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

1
1
0 / 0

[JBoss JIRA] Assigned: (JBRULES-41) Enhance no-loop functionality

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-41?page=all ] Michael Neale reassigned JBRULES-41: ------------------------------------ Assignee: Edson Tirelli (was: Michael Neale) Edson, this is low priority, but I thought you may have ideas on this. Its been around for quite a while. > Enhance no-loop functionality > ----------------------------- > > Key: JBRULES-41 > URL: http://jira.jboss.com/jira/browse/JBRULES-41 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rule Assemply/SPI > Affects Versions: 3.0-beta1 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Fix For: 3.1-m3 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > At present, no-loop is simply limited to stopping a rule firing itself with the same facts. > A common request I get, whenever visiting anyone, is how to remember all rule activations (rule/fact combinations that have fired in the past) and stop the same happening in the future in a single instance of working memory. > This can be an option set on a per instance, or per haps per-file basis. By default it must be off, as it will require extra memory to record the history, and I don't think it would be suitable for long lived working memories. > However, for the pseudo "stateless" pattern (which probably 70-80% of people use) it would be quite safe and beneficial. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3971) Add basic classloader leakage tests

by Brian Stansberry (JIRA)

Add basic classloader leakage tests ----------------------------------- Key: JBAS-3971 URL: http://jira.jboss.com/jira/browse/JBAS-3971 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: ClassLoading Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1 Add basic tests for classloader leaks following deployment, use and undeployment of various packages (wars, ejb jars and ears with and without scoped classloaders). As part of deploy setup, test drivfer will deploy a sar with a service that deployments can use to register their classloader. Service will maintain a WeakReference to the classloader. Test will deploy various packages and invoke operations on them (web requests and remote ejb invocations). Deployments will register their classloader, and during invocations will log using commons-logging (thus testing for leaks via commons-logging). Test driver will then undeploy the package check with the service to see if the classloader was released. If JBoss Profiler is on the path and -agentlib:jbossAgent is passed to java, if the classloader is not released the service will generate and log a report tracing references to the classloader. This can be used to isolate the cause of the leak. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-645) Package config saves to be versioned (just the config) if possible

by Michael Neale (JIRA)

Package config saves to be versioned (just the config) if possible ------------------------------------------------------------------ Key: JBRULES-645 URL: http://jira.jboss.com/jira/browse/JBRULES-645 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007