October 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2338) NullPointerException in PortletManagementHandler.getPortletProperties

by Lionel ROSIER (JIRA)

NullPointerException in PortletManagementHandler.getPortletProperties --------------------------------------------------------------------- Key: JBPORTAL-2338 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2338 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.7 Final Environment: Tested on JBoss AS 4.2.3 and Portal 2.6.6 Reporter: Lionel ROSIER Assignee: Chris Laprun It's possible to create new properties with "InstanceDefinition.setProperties" on remote portlet with WSRP but when we try to read these new properties, we have a NPE in getPortletProperties from PortletManagementHandler. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2071) Investigate non-isolation of WSRP tests

by Chris Laprun (JIRA)

Investigate non-isolation of WSRP tests --------------------------------------- Key: JBPORTAL-2071 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2071 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 Alpha1 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.7.0 Beta1 It seems that test set up is not done in complete isolation of the environment. I have lost a day trying to figure out what changed in my code that was causing tests to fail with an NPE related to a null registration policy when it seems that the issue came from the database state of the AS instance... :( Need to find exactly what is causing the problem (seems like RegistrationManager might be the culprit) and use a properly isolated test set up. -- 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

15 years, 9 months

2
5
0 / 0

[JBoss JIRA] Work stopped: (JBPORTAL-875) Test WSRP implementation conformance

by Chris Laprun (JIRA)

[ https://jira.jboss.org/browse/JBPORTAL-875?page=com.atlassian.jira.plugin... ] Work on JBPORTAL-875 stopped by Chris Laprun. > Test WSRP implementation conformance > ------------------------------------ > > Key: JBPORTAL-875 > URL: https://jira.jboss.org/browse/JBPORTAL-875 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Priority: Critical > Fix For: 2.8 Final > > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Improve the WSRP tests to deliver best in class WSRP implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2192) Too many permits released on StrictMaxPool.release

by Carlo de Wolf (JIRA)

Too many permits released on StrictMaxPool.release -------------------------------------------------- Key: EJBTHREE-2192 URL: https://jira.jboss.org/browse/EJBTHREE-2192 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: depchain-1.0.0-alpha-4, bom-eap5-1.0.1 Reporter: Carlo de Wolf StrictMaxPool.release releases permit and calls remove (sometimes) which also releases permit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8561) Classload failure because of GC on MountHandle

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/browse/JBAS-8561?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler closed JBAS-8561. -------------------------------- http://github.com/jbosgi/jboss-as/commit/480d24204d958d8e0960b695a64674c9... > Classload failure because of GC on MountHandle > ----------------------------------------------- > > Key: JBAS-8561 > URL: https://jira.jboss.org/browse/JBAS-8561 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.0.0.M1 > > > We see intermittent failures where a bundle cannot load a class from a dependent module > org.osgi.framework.BundleException: Cannot start bundle: bundle12:1.0.0 > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:243) > at org.jboss.osgi.framework.bundle.AbstractBundle.start(AbstractBundle.java:435) > at org.jboss.osgi.framework.bundle.BundleWrapper.start(BundleWrapper.java:166) > at org.jboss.as.osgi.xservice.ModuleAccessesOSGiServiceTestCase.testModuleInvokesTargetBundleService(ModuleAccessesOSGiServiceTestCase.java:179) > .... > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: java.lang.NoClassDefFoundError: org/jboss/as/osgi/deployment/c/Echo > at org.jboss.as.osgi.deployment.b.TargetBundleActivator.start(TargetBundleActivator.java:33) > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:205) > ... 31 more > Investigate how the ModuleClassLoader is created and whether there are perhaps some race conditions involved -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-8561) Classload failure because of GC on MountHandle

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/browse/JBAS-8561?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler reopened JBAS-8561: ---------------------------------- > Classload failure because of GC on MountHandle > ----------------------------------------------- > > Key: JBAS-8561 > URL: https://jira.jboss.org/browse/JBAS-8561 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.0.0.M1 > > > We see intermittent failures where a bundle cannot load a class from a dependent module > org.osgi.framework.BundleException: Cannot start bundle: bundle12:1.0.0 > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:243) > at org.jboss.osgi.framework.bundle.AbstractBundle.start(AbstractBundle.java:435) > at org.jboss.osgi.framework.bundle.BundleWrapper.start(BundleWrapper.java:166) > at org.jboss.as.osgi.xservice.ModuleAccessesOSGiServiceTestCase.testModuleInvokesTargetBundleService(ModuleAccessesOSGiServiceTestCase.java:179) > .... > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: java.lang.NoClassDefFoundError: org/jboss/as/osgi/deployment/c/Echo > at org.jboss.as.osgi.deployment.b.TargetBundleActivator.start(TargetBundleActivator.java:33) > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:205) > ... 31 more > Investigate how the ModuleClassLoader is created and whether there are perhaps some race conditions involved -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-8561) Classload failure because of GC on MountHandle

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/browse/JBAS-8561?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler resolved JBAS-8561. ---------------------------------- Resolution: Done > Classload failure because of GC on MountHandle > ----------------------------------------------- > > Key: JBAS-8561 > URL: https://jira.jboss.org/browse/JBAS-8561 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.0.0.M1 > > > We see intermittent failures where a bundle cannot load a class from a dependent module > org.osgi.framework.BundleException: Cannot start bundle: bundle12:1.0.0 > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:243) > at org.jboss.osgi.framework.bundle.AbstractBundle.start(AbstractBundle.java:435) > at org.jboss.osgi.framework.bundle.BundleWrapper.start(BundleWrapper.java:166) > at org.jboss.as.osgi.xservice.ModuleAccessesOSGiServiceTestCase.testModuleInvokesTargetBundleService(ModuleAccessesOSGiServiceTestCase.java:179) > .... > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: java.lang.NoClassDefFoundError: org/jboss/as/osgi/deployment/c/Echo > at org.jboss.as.osgi.deployment.b.TargetBundleActivator.start(TargetBundleActivator.java:33) > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:205) > ... 31 more > Investigate how the ModuleClassLoader is created and whether there are perhaps some race conditions involved -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2101) Remove reference to jboss-ejb3-metadata-deployers from bom-eap5.

by Carlo de Wolf (JIRA)

Remove reference to jboss-ejb3-metadata-deployers from bom-eap5. ---------------------------------------------------------------- Key: EJBTHREE-2101 URL: https://jira.jboss.org/browse/EJBTHREE-2101 Project: EJB 3.0 Issue Type: Task Components: bom Affects Versions: bom-eap5-0.1.2 Reporter: Carlo de Wolf Fix For: bom-eap5-0.1.3 jboss-ejb3-metadata-deployers is an AS 6 artifact and not used in EAP 5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Resolved: (JBAS-8561) Classload failure because of GC on MountHandle

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/browse/JBAS-8561?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler resolved JBAS-8561. ---------------------------------- Resolution: Done Done // Mount virtual file try { Closeable mount = deploymentRepo.mountDeploymentContent(deploymentName, runtimeName, deploymentHash, deploymentRoot); handle = new MountHandle(mount); } catch (IOException e) { throw new RuntimeException("Failed to mount deployment archive", e); } ... // Create deployment service DeploymentService deploymentService = new DeploymentService(handle); ... attachVirtualFile(deploymentUnitContext, deploymentRoot); deploymentUnitContext.putAttachment(MountHandle.ATTACHMENT_KEY, handle); > Classload failure because of GC on MountHandle > ----------------------------------------------- > > Key: JBAS-8561 > URL: https://jira.jboss.org/browse/JBAS-8561 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.0.0.M1 > > > We see intermittent failures where a bundle cannot load a class from a dependent module > org.osgi.framework.BundleException: Cannot start bundle: bundle12:1.0.0 > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:243) > at org.jboss.osgi.framework.bundle.AbstractBundle.start(AbstractBundle.java:435) > at org.jboss.osgi.framework.bundle.BundleWrapper.start(BundleWrapper.java:166) > at org.jboss.as.osgi.xservice.ModuleAccessesOSGiServiceTestCase.testModuleInvokesTargetBundleService(ModuleAccessesOSGiServiceTestCase.java:179) > .... > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: java.lang.NoClassDefFoundError: org/jboss/as/osgi/deployment/c/Echo > at org.jboss.as.osgi.deployment.b.TargetBundleActivator.start(TargetBundleActivator.java:33) > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:205) > ... 31 more > Investigate how the ModuleClassLoader is created and whether there are perhaps some race conditions involved -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-8561) Classload failure because of GC on MountHandle

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/browse/JBAS-8561?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler updated JBAS-8561: --------------------------------- Summary: Classload failure because of GC on MountHandle (was: Bundle cannot load class from dependent module) Assignee: Thomas Diesler Fix Version/s: 7.0.0.M1 (was: 7.0.0.M2) Component/s: Deployers (was: OSGi integration) > Classload failure because of GC on MountHandle > ----------------------------------------------- > > Key: JBAS-8561 > URL: https://jira.jboss.org/browse/JBAS-8561 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.0.0.M1 > > > We see intermittent failures where a bundle cannot load a class from a dependent module > org.osgi.framework.BundleException: Cannot start bundle: bundle12:1.0.0 > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:243) > at org.jboss.osgi.framework.bundle.AbstractBundle.start(AbstractBundle.java:435) > at org.jboss.osgi.framework.bundle.BundleWrapper.start(BundleWrapper.java:166) > at org.jboss.as.osgi.xservice.ModuleAccessesOSGiServiceTestCase.testModuleInvokesTargetBundleService(ModuleAccessesOSGiServiceTestCase.java:179) > .... > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: java.lang.NoClassDefFoundError: org/jboss/as/osgi/deployment/c/Echo > at org.jboss.as.osgi.deployment.b.TargetBundleActivator.start(TargetBundleActivator.java:33) > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:205) > ... 31 more > Investigate how the ModuleClassLoader is created and whether there are perhaps some race conditions involved -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
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 October 2010