May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (HIBERNATE-89) Change Hibernate logging to info

by Gail Badner (JIRA)

Change Hibernate logging to info -------------------------------- Key: HIBERNATE-89 URL: http://jira.jboss.com/jira/browse/HIBERNATE-89 Project: Hibernate Issue Type: Sub-task Reporter: Gail Badner Assigned To: Gail Badner -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1769) Portlet disappears in IE 7.0 after it is maximized

by krish p (JIRA)

Portlet disappears in IE 7.0 after it is maximized -------------------------------------------------- Key: JBPORTAL-1769 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.1 Final Environment: Windows XP, Internet Explorer 7.0 Reporter: krish p Assigned To: Julien Viet I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues. Essentially, this is the problem: * Add a portlet on the page. * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally). After doing a fair bit of testing, I've narrowed down the test case to the following: * This does NOT reproduce in Firefox and happens only in IE * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore). It is a little painful to reproduce this but the problem does exist in IE. -- 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

16 years, 1 month

4
21
0 / 0

[JBoss JIRA] Created: (JBAS-4662) XADatasource property names are not using the javabean convention

by Adrian Brock (JIRA)

XADatasource property names are not using the javabean convention ----------------------------------------------------------------- Key: JBAS-4662 URL: http://jira.jboss.com/jira/browse/JBAS-4662 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Adrian Brock Fix For: JBossAS-4.2.2.GA, JBossAS-5.0.0.GA XADataSource properties are not following the javabean convention. i.e. <xa-datasource-property name="lower">value</xa-datasource-property> should work with XADataSourceImpl.setLower() Currently you have to capitalize the name "Lower" to make it work. See org.jboss.resource.connectionmanager.RARDeployment::setManagedConnectionFactoryAttribute(...) for the correct code to do this safely. -- 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

16 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-1341) JBossCache 2.x can be intergated in AS4.x

by Mircea Markus (JIRA)

JBossCache 2.x can be intergated in AS4.x ----------------------------------------- Key: JBCACHE-1341 URL: http://jira.jboss.com/jira/browse/JBCACHE-1341 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.GA Reporter: Mircea Markus Assigned To: Manik Surtani enhace http://wiki.jboss.org/wiki/JBossCacheAsCompatibility with compatibility checking in the EJB layer also (this might involve some DelegatingCL configuration) -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-698) Exception serialization issue when remotely accessing stateless session bean

by David Green (JIRA)

Exception serialization issue when remotely accessing stateless session bean ---------------------------------------------------------------------------- Key: EJBTHREE-698 URL: http://jira.jboss.com/jira/browse/EJBTHREE-698 Project: EJB 3.0 Issue Type: Bug Reporter: David Green Accessing a remote EJB (Session bean) results in exception. Stack trace follows: 13:54:39,546 ERROR [SocketClientInvoker] Got marshalling exception, exiting java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement; at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50) at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128) at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66) at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) at $Proxy0.postNotification(Unknown Source) at com.hgea.hch.service.HchClientDelegate.postNotification(HchClientDelegate.java:99) at com.hgea.hch.client.RemoteHchClientTest.testRemotePostNotification(RemoteHchClientTest.java:38) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) -- 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

16 years, 1 month

7
7
0 / 0

[JBoss JIRA] Created: (JBAOP-537) JoinPointInfo synchronization is not working on wrappers

by Flavia Rainone (JIRA)

JoinPointInfo synchronization is not working on wrappers -------------------------------------------------------- Key: JBAOP-537 URL: http://jira.jboss.com/jira/browse/JBAOP-537 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR7 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.CR8 Synchronizing only the joinpoint class generation is not enough. The wrappers must be entirely synchronized with the joinpoint info interceptor chain lock, since their execution depends on the interceptor chain. This bug causes rebuldingChain test to fail. -- 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

16 years, 1 month

2
6
0 / 0

[JBoss JIRA] Deleted: (JBAOP-571) Container and Class proxy cache keeps reference to the class proxy

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-571?page=all ] Kabir Khan deleted JBAOP-571: ----------------------------- > Container and Class proxy cache keeps reference to the class proxy > ------------------------------------------------------------------- > > Key: JBAOP-571 > URL: http://jira.jboss.com/jira/browse/JBAOP-571 > Project: JBoss AOP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assigned To: Kabir Khan > > If we create a proxy for ArrayList for deployment1, since ArrayList is in the bootstrap classloader, it is created against deployment1's loader. > If we deploy deployment2 that attempts to use the cache, it will access deployment1's proxy for ArrayList. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-571) Container and Class proxy cache keeps reference to the class proxy

by Kabir Khan (JIRA)

Container and Class proxy cache keeps reference to the class proxy ------------------------------------------------------------------- Key: JBAOP-571 URL: http://jira.jboss.com/jira/browse/JBAOP-571 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR8 Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.CR9 If we create a proxy for ArrayList for deployment1, since ArrayList is in the bootstrap classloader, it is created against deployment1's loader. If we deploy deployment2 that attempts to use the cache, it will access deployment1's proxy for ArrayList. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1588) collect fails when using treeset

by pchar (JIRA)

collect fails when using treeset -------------------------------- Key: JBRULES-1588 URL: http://jira.jboss.com/jira/browse/JBRULES-1588 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.6 Reporter: pchar Assigned To: Mark Proctor Hi All, i've a simple rules that retract objects form the WM rule "Retract From TreeSet" when $tree: TreeSet() from collect (Message() ) then System.out.println($tree.first()); retract($tree.first()); end after the firts run the following exception is thrown org.drools.FactException: Retract error: handle not found for object: [Hello World]. Is it in the working memory? [Hello World] at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:120) at com.sample.Rule_Retract_From_TreeSet_0.consequence(Rule_Retract_From_TreeSet_0.java:9) at com.sample.Rule_Retract_From_TreeSet_0ConsequenceInvoker.evaluate(Rule_Retract_From_TreeSet_0ConsequenceInvoker.java:22) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550) at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:471) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:433) at com.sample.DroolsTest.main(DroolsTest.java:36) org.drools.spi.ConsequenceException: org.drools.FactException: Retract error: handle not found for object: [Hello World]. Is it in the working memory? at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:554) at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:471) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:433) at com.sample.DroolsTest.main(DroolsTest.java:36) Caused by: org.drools.FactException: Retract error: handle not found for object: [Hello World]. Is it in the working memory? at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:120) at com.sample.Rule_Retract_From_TreeSet_0.consequence(Rule_Retract_From_TreeSet_0.java:9) at com.sample.Rule_Retract_From_TreeSet_0ConsequenceInvoker.evaluate(Rule_Retract_From_TreeSet_0ConsequenceInvoker.java:22) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550) ... 4 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

16 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBMETA-31) message-destination-ref must be allowed in jboss-client descriptor

by Carlo de Wolf (JIRA)

message-destination-ref must be allowed in jboss-client descriptor ------------------------------------------------------------------ Key: JBMETA-31 URL: http://jira.jboss.com/jira/browse/JBMETA-31 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical Fix For: 1.0.0.Beta11 org.xml.sax.SAXException: The content of element type "jboss-client" must match "(jndi-name,ejb-ref*,service-ref*,resource-ref*,resource-env-ref*)". @ *unknown*[18,16] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:432) -- 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

16 years, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2008