February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-406) Race condition for threaded managed lifecycles

by Kevin Conner (JIRA)

Race condition for threaded managed lifecycles ---------------------------------------------- Key: JBESB-406 URL: http://jira.jboss.com/jira/browse/JBESB-406 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.0 Maintenance Pack 1 There is race condition in the AbstractThreadedManagedLifecycle class between the original thread and the background thread. The background thread must wait until the lifecycle state has transitioned out of the STARTING state before continuing. At present the background thread ignores this and attempts to transition into the RUNNING state as soon as it starts. This transition could fail resulting in the background thread terminating. -- 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

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Deleted: (JBAS-3989) failing org.jboss.test.txiiop.test.IIOPUserTransactionStressTestCase

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3989?page=all ] Dimitris Andreadis deleted JBAS-3989: ------------------------------------- > failing org.jboss.test.txiiop.test.IIOPUserTransactionStressTestCase > -------------------------------------------------------------------- > > Key: JBAS-3989 > URL: http://jira.jboss.com/jira/browse/JBAS-3989 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Environment: Java Version 1.5.0_05 > Java Vendor Sun Microsystems Inc. > Java VM Name Java HotSpot(TM) Server VM > Java VM Version 1.5.0_05-b05 > 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: Francisco Reverbel > > testUserTx Error N/A > java.lang.IllegalStateException > at org.jboss.tm.iiop.client.IIOPClientUserTransaction.commit(IIOPClientUserTransaction.java:315) > at org.jboss.test.txiiop.test.IIOPUserTransactionStressTestCase.testUserTx(IIOPUserTransactionStressTestCase.java:72) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > Caused by: org.omg.CosTransactions.NoTransaction: IDL:omg.org/CosTransactions/NoTransaction:1.0 > at org.jboss.tm.iiop.client.IIOPClientUserTransaction.getThreadLocalTerminator(IIOPClientUserTransaction.java:164) > at org.jboss.tm.iiop.client.IIOPClientUserTransaction.commit(IIOPClientUserTransaction.java:310) > ... 22 more > testTxMandatory Error CORBA TRANSACTION_REQUIRED 0 No; nested exception is: org.omg.CORBA.TRANSACTION_REQUIRED: Server-side Exception: javax.transaction.TransactionRequiredException: Transaction Required vmcid: 0x0 minor code: 0 completed: No > javax.transaction.TransactionRequiredException: CORBA TRANSACTION_REQUIRED 0 No; nested exception is: > org.omg.CORBA.TRANSACTION_REQUIRED: Server-side Exception: javax.transaction.TransactionRequiredException: Transaction Required vmcid: 0x0 minor code: 0 completed: No > at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:203) > at javax.rmi.CORBA.Util.mapSystemException(Util.java:67) > at org.jboss.proxy.ejb.DynamicIIOPStub.invoke(DynamicIIOPStub.java:150) > at org.jboss.test.txiiop.interfaces._StatefulSession_Stub.txMandatoryMethod(Unknown Source) > at org.jboss.test.txiiop.test.IIOPUserTransactionStressTestCase.testTxMandatory(IIOPUserTransactionStressTestCase.java:114) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > Caused by: org.omg.CORBA.TRANSACTION_REQUIRED: Server-side Exception: javax.transaction.TransactionRequiredException: Transaction Required vmcid: 0x0 minor code: 0 completed: No > at java.lang.reflect.Constructor.newInstance(Constructor.java:494) > at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:173) > at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:325) > at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:967) > at org.jacorb.orb.Delegate.invoke(Delegate.java:868) > at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457) > at org.jboss.proxy.ejb.DynamicIIOPStub.invoke(DynamicIIOPStub.java:125) > ... 23 more > -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-560) CLONE -Referencing JAR file in persistence.xml - Still a bug and referenced duplicate issue does not exist

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-560?page=all ] Carlo de Wolf resolved EJBTHREE-560. ------------------------------------ Resolution: Cannot Reproduce Bug unit test: factory > CLONE -Referencing JAR file in persistence.xml - Still a bug and referenced duplicate issue does not exist > ---------------------------------------------------------------------------------------------------------- > > Key: EJBTHREE-560 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-560 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC1 > Reporter: geoffm74 > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC10 - FD > > Attachments: PersistenceUnitDeployment.diff > > > I've installed EJB3.0RC1 and the release notes states that now all persistence.xml features are implemented. So I went on trying to use the jar file referencing. > Unfortunately I found that during deployment the only place being searched for this jar file was in JBOSS_HOME/bin. I tried with absolute paths and relative - but it kept hangin on to the bin folder - probably the working folder for jboss launcher. > My jar is bundled with my ear - where should it really be to get the jar reference workin? I think the bin folder is not a proper place.... > Peter -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Assigned: (EJBTHREE-560) CLONE -Referencing JAR file in persistence.xml - Still a bug and referenced duplicate issue does not exist

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-560?page=all ] Carlo de Wolf reassigned EJBTHREE-560: -------------------------------------- Assignee: Carlo de Wolf > CLONE -Referencing JAR file in persistence.xml - Still a bug and referenced duplicate issue does not exist > ---------------------------------------------------------------------------------------------------------- > > Key: EJBTHREE-560 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-560 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC1 > Reporter: geoffm74 > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC10 - FD > > Attachments: PersistenceUnitDeployment.diff > > > I've installed EJB3.0RC1 and the release notes states that now all persistence.xml features are implemented. So I went on trying to use the jar file referencing. > Unfortunately I found that during deployment the only place being searched for this jar file was in JBOSS_HOME/bin. I tried with absolute paths and relative - but it kept hangin on to the bin folder - probably the working folder for jboss launcher. > My jar is bundled with my ear - where should it really be to get the jar reference workin? I think the bin folder is not a proper place.... > Peter -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-946) How-To for installing/creating pojocacheable classes in JBoss 4.0.5/Cache 1.4.1/JDK5

by Jamie Reifsnyder (JIRA)

How-To for installing/creating pojocacheable classes in JBoss 4.0.5/Cache 1.4.1/JDK5 ------------------------------------------------------------------------------------ Key: JBCACHE-946 URL: http://jira.jboss.com/jira/browse/JBCACHE-946 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.1.GA Environment: JBoss 4.0.5.GA, JBoss AOP 1.5.2.GA, JBoss Cache 1.4.1GA, JDK5 Reporter: Jamie Reifsnyder Assigned To: Ben Wang Attachments: To set up the PojoCache in JBoss 4.doc I pulled together install and compile instructions to create precompiled POJOs and an installed version of PojoCache on JBoss. For Ben Wang (requested in http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004847#4004847 ) -- 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

17 years, 4 months

2
3
0 / 0

(no subject)

by 78jk22hg5jk7＠fszz.com.cn

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4062) Remove use of JGroups Debugger from ClusterPartition

by Brian Stansberry (JIRA)

Remove use of JGroups Debugger from ClusterPartition ---------------------------------------------------- Key: JBAS-4062 URL: http://jira.jboss.com/jira/browse/JBAS-4062 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta2 Debugger no longer exists in 2.5, so we need to get rid of it. -- 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

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4063) Remove EVENT_TRACE from cluster module

by Brian Stansberry (JIRA)

Remove EVENT_TRACE from cluster module -------------------------------------- Key: JBAS-4063 URL: http://jira.jboss.com/jira/browse/JBAS-4063 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta2 Class org.javagroups.protocols.EventTrace is a utlility JGroups protocol in the AS cluster module source tree. It won't compile if JG 2.5 is used, and if the non-conforming bits are left it won't work properly with 2.4.x. I'm unaware of anyone using it, so I'm going to remove it. If the functionality is still desired, the protocol should be added to the JGroups src tree. -- 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

17 years, 4 months

1
1
0 / 0

[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

17 years, 4 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

17 years, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007