October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4658) The jms destinations classes need to be updated with management annotations

by Scott M Stark (JIRA)

The jms destinations classes need to be updated with management annotations --------------------------------------------------------------------------- Key: JBAS-4658 URL: http://jira.jboss.com/jira/browse/JBAS-4658 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service, Management services Reporter: Scott M Stark Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3 The org.jboss.jms.server.destination.QueueService/TopicService and org.jboss.jms.server.connectionfactory.ConnectionFactory need to be updated with management annotations for creating the ManagedObjects. -- 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

18 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBCOMMON-29) Unable to read in jarfile if application installed to location with spaces in directory name

by klaasjan elzinga (JIRA)

Unable to read in jarfile if application installed to location with spaces in directory name -------------------------------------------------------------------------------------------- Key: JBCOMMON-29 URL: http://jira.jboss.com/jira/browse/JBCOMMON-29 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 2.0.4.GA Environment: windows XP sun-jre, happens also in core-2.2.0.GA Reporter: klaasjan elzinga Assigned To: Dimitris Andreadis I get an exception if the application is installed to a directory containing a space. I I rename the directory to a name without a space, the application runs perfectly. Exception in thread "main" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [loadtool/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: error trying to scan <jar-file>: file:/C:/TIS%20FIIBLoadTool-3.0.2.SN APSHOT/TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: file:/C:/TIS%20FIIBLoadTool-3.0.2.SNAPSHOT/TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:635) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:350) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:218) at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:251) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248) ... at loadtool.Main.main(Main.java:40) Caused by: java.lang.RuntimeException: java.io.FileNotFoundException: C:\TIS%20FIIBLoadTool-3.0.2.SNAPSHOT\TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar (The system cannot find th e path specified) at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:74) at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:48) at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:57) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:626) ... 29 more Caused by: java.io.FileNotFoundException: C:\TIS%20FIIBLoadTool-3.0.2.SNAPSHOT\TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar (The system cannot find the path specified) at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:114) at java.util.jar.JarFile.<init>(JarFile.java:133) at java.util.jar.JarFile.<init>(JarFile.java:97) at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:69) ... 32 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

18 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1773) Unable to destroy instance customization

by Ovidiu Nichifor (JIRA)

Unable to destroy instance customization ---------------------------------------- Key: JBPORTAL-1773 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.1 Final Environment: Fedora Core 7 JVM 1.5.0_12 JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile) JBoss Potal 2.6.1.GA Reporter: Ovidiu Nichifor Assigned To: Julien Viet Create & place a window on a region of an ordinary page of your personal dashboard. Make sure it is visible on your dashboard. Destroy that window. Recreate the window with the same name, content type, instance, page parent, region and order as before. An error will appear in the console: 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table. Sample: `JBP_PORTLET_STATE` PK PORTLET_ID REGISTRATION_ID REGISTRATION_TIME TERMINATION_TIME PARENT_PK 1 /portal-news-samples.NewsPortlet NULL 2007-10-25 11:57:28 NULL NULL `JBP_INSTANCE_PER_USER` PK INSTANCE_PK SER_STATE USER_ID PORTLET_REF 1 16 [BLOB - NULL] dashboard:/admin/default/Preferences local._2 2 16 [BLOB - NULL] dashboard:/admin/sample/Preferences local._3 3 16 [BLOB - NULL] dashboard:/admin/sample/P local._4 Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid. Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'. -- 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

18 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-602) Update FLUSH diagrams for joining and for state transfer

by Bela Ban (JIRA)

Update FLUSH diagrams for joining and for state transfer -------------------------------------------------------- Key: JGRP-602 URL: http://jira.jboss.com/jira/browse/JGRP-602 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6 Update the 2 png files to reflect the new simplified FLUSH protocol -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4903) EJB 2.1 view cannot be realized

by Thomas Diesler (JIRA)

EJB 2.1 view cannot be realized ------------------------------- Key: JBAS-4903 URL: http://jira.jboss.com/jira/browse/JBAS-4903 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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

18 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1093) create tutorial for validating jboss.xml

by William DeCoste (JIRA)

create tutorial for validating jboss.xml ---------------------------------------- Key: EJBTHREE-1093 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1093 Project: EJB 3.0 Issue Type: Task Components: Documentation Reporter: William DeCoste Assigned To: William DeCoste -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4901) Reverse paths are not allowed (containing a . or ..)

by Thomas Diesler (JIRA)

Reverse paths are not allowed (containing a . or ..) ---------------------------------------------------- Key: JBAS-4901 URL: http://jira.jboss.com/jira/browse/JBAS-4901 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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

18 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-1177) NullPointerException in PessimistickLockInterceptor

by Jacek Halat (JIRA)

NullPointerException in PessimistickLockInterceptor --------------------------------------------------- Key: JBCACHE-1177 URL: http://jira.jboss.com/jira/browse/JBCACHE-1177 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.1.SP4 Environment: WindowsXP, Reporter: Jacek Halat Assigned To: Jason T. Greene Sometimes when put operation is invoked in transaction that is timed out, NPE is throw from PessimistickLockInterceptor. java.lang.NullPointerException at org.jboss.cache.interceptors.PessimisticLockInterceptor.hasBeenRemovedInCurrentTx(PessimisticLockInterceptor.java:342) at org.jboss.cache.interceptors.PessimisticLockInterceptor.needToReverseRemove(PessimisticLockInterceptor.java:336) at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:300) at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:175) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:32) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:365) at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:160) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:157) at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5863) at org.jboss.cache.TreeCache.put(TreeCache.java:3833) at org.jboss.cache.aop.PojoCache.lockPojo(PojoCache.java:635) at org.jboss.cache.aop.PojoCache.putObject(PojoCache.java:445) -- 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

18 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1021) bind local interfaces to java: not global for 5.0

by William DeCoste (JIRA)

bind local interfaces to java: not global for 5.0 ------------------------------------------------- Key: EJBTHREE-1021 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1021 Project: EJB 3.0 Issue Type: Task Reporter: William DeCoste Assigned To: William DeCoste -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup

by Galder Zamarreno (JIRA)

InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup ---------------------------------------------------------------------------------- Key: JBAS-4805 URL: http://jira.jboss.com/jira/browse/JBAS-4805 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2 Reporter: Galder Zamarreno Assigned To: Carlo de Wolf Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA org.jboss.ejb3.InitialContextFactory.getHAContext() contains: env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort()); InitialContext haCtx = new InitialContext(env); The code should not have hardcoded localhost because as soon as someone binds JBoss to something different, a localhost lookup will fail. This could should instead check HAJNDI service's BindAddress attribute and use that. -- 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

18 years, 8 months

4
9
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 2007