April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3633) Tidyup logging when transaction is no longer active

by Adrian Brock (JIRA)

Tidyup logging when transaction is no longer active --------------------------------------------------- Key: JBAS-3633 URL: http://jira.jboss.com/jira/browse/JBAS-3633 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JB5-Transaction Manager Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Priority: Minor Since JBossTM rollsback transactions at transaction timeout, we need to tidyup the transaction demarcation code (commit/rollback/setRollbackOnly, etc) such that the logging is more information and not so noisy. We still need to communicate that the transaction rolled back even if it is not the transaction demarcation point that does the rollback. Currrently, you get errors/warnings about not being able to setRollbackOnly or rollback, because the transaction is already ended. -- 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, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-4070) Generalize naming factory and remoting lookup

by Scott M Stark (JIRA)

Generalize naming factory and remoting lookup --------------------------------------------- Key: JBAS-4070 URL: http://jira.jboss.com/jira/browse/JBAS-4070 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Fix For: JBossAS-5.0.0.CR1 -- 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, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JGRP-278) Externalization of socket creation in TCP/TCP_NIO (BasicTCP)

by Bela Ban (JIRA)

Externalization of socket creation in TCP/TCP_NIO (BasicTCP) ------------------------------------------------------------ Key: JGRP-278 URL: http://jira.jboss.com/jira/browse/JGRP-278 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 User configures a socket factory which creates client and server sockets. There is always 1 default factory configured. This allows developers to override socket creation, e.g. for use with SSL sockets. This way, TCP and TCP_NIO can be used with SSL. -- 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, 6 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-129) Implement support for the generic metadata in the javassist implementation of ClassInfo

by Adrian Brock (JIRA)

Implement support for the generic metadata in the javassist implementation of ClassInfo --------------------------------------------------------------------------------------- Key: JBMICROCONT-129 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-129 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The support for generics has only been implemented in the reflection based ClassInfo implementation. This needs doing also for the Javassist implementation. -- 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, 6 months

6
9
0 / 0

[JBoss JIRA] Created: (JBRULES-535) allow for plugeable query result handlers

by Mark Proctor (JIRA)

allow for plugeable query result handlers ------------------------------------------- Key: JBRULES-535 URL: http://jira.jboss.com/jira/browse/JBRULES-535 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 Queries should be able to specify how the results are processed once they reach the terminal node. -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4344) Problematic casting to String in org.jboss.jmx.connector.invoker.AuthenticationInterceptor

by David Dossot (JIRA)

Problematic casting to String in org.jboss.jmx.connector.invoker.AuthenticationInterceptor ------------------------------------------------------------------------------------------ Key: JBAS-4344 URL: http://jira.jboss.com/jira/browse/JBAS-4344 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.4.GA Environment: Mac Os X, RedHat Reporter: David Dossot Assigned To: Dimitris Andreadis There is a problematic cast in org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(Invocation invocation) on line 110: String opname = (String) obj[1]; When Twiddling to get a particular attribute, the following code is used in org.jboss.console.twiddle.command.GetCommand.execute(String[] args) on line 165: attributeNames.toArray(names); (...) AttributeList attrList = server.getAttributes(objectName, names); So obj[1] ends up holding a String[] of attribute names (even if there is only one) and the cast fails: 14:14:44,760 ERROR [Twiddle] Exec failed java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String at org.jboss.jmx.connector.invoker.AuthorizationInterceptor.invoke(AuthorizationInterceptor.java:107) at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108) 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.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) 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:589) 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) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420) 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:589) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:679) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:704) at java.lang.Thread.run(Thread.java:637) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:331) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:194) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy0.getAttributes(Unknown Source) at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:168) at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305) -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4383) Allow a different JSF implementation to be packaged in the WAR

by Stan Silvert (JIRA)

Allow a different JSF implementation to be packaged in the WAR -------------------------------------------------------------- Key: JBAS-4383 URL: http://jira.jboss.com/jira/browse/JBAS-4383 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JavaServerFaces Affects Versions: JBossAS-4.2.0.CR2, JBossAS-5.0.0.Beta2 Reporter: Stan Silvert Assigned To: Stan Silvert Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-5.0.0.GA Prior to JEE5, most developers would bundle a JSF implementation such as MyFaces with the WAR. With AS 4.2 and 5.0, you should instead rely on the JSF implementation that ships with the container. However, for these legacy applications that rely on a particular implementation, we can disable the built-in JSF implementation as long as you stick with the default classloader settings. To disable the built-in JSF, you will add this to your web.xml: <context-param> <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name> <param-value>true</param-value> </context-param> -- 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, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-156) Look at options for reducing vfs memory usage

by Scott M Stark (JIRA)

Look at options for reducing vfs memory usage --------------------------------------------- Key: JBMICROCONT-156 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-156 Project: JBoss MicroContainer Issue Type: Task Components: VFS Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0_CR1 The vfs is eagerly creating URLs for every jar entry touched. This is resulting in a large amount of memory just for Strings. We need to look into reusing the existing name in combination with the root url handler rather than creating new urls to reduce the memory usage. -- 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, 7 months

4
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-706) NullPointerException in RunAsSecurityInterceptorFactory when there is no SecurityDomain annotation

by Roland R?z (JIRA)

NullPointerException in RunAsSecurityInterceptorFactory when there is no SecurityDomain annotation -------------------------------------------------------------------------------------------------- Key: EJBTHREE-706 URL: http://jira.jboss.com/jira/browse/EJBTHREE-706 Project: EJB 3.0 Issue Type: Bug Components: Security Reporter: Roland R?z Priority: Minor The class org.jboss.ejb3.security.RunAsSecurityInterceptorFactory throws in createPerClass() a NullPointerException when there is no SecurityDomain annotation. Possible Fix: if (securityAnnotation != null) { domain = ctx.lookup("java:/jaas/" + securityAnnotation.value()); } -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-724) persistence.xml jar-file processing

by Heiko W. Rupp (JIRA)

persistence.xml jar-file processing ----------------------------------- Key: EJBTHREE-724 URL: http://jira.jboss.com/jira/browse/EJBTHREE-724 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Heiko W. Rupp EJB 3 persistence spec says in 6.2.1.6, 2nd paragraph about <jar-file> "Such JAR files are specified relative to the root of the persistence unit (e.g.,utils/myUtils.jar)" When I have a persistence.xml like this: <persistence> <persistence-unit name="jon"> <jta-data-source>java:/JONDS</jta-data-source> <jar-file>lib/on-enterprise-server-2.0-SNAPSHOT.jar</jar-file> </persistence-unit> </persistence> The PersistenceUnitDeployment gives file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar] but the root of the PersistenceUnit is file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/on-enterprise-server-entity-ejb-2.0-SNAPSHOT.jar/ 2006-10-04 18:00:43,537 DEBUG [org.jboss.ejb3.entity.PersistenceUnitDeployment] Found persistence.xml file in EJB3 jar 2006-10-04 18:00:43,538 DEBUG [org.jboss.ejb3.entity.PersistenceUnitDeployment] adding JarFile URL: file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar 2006-10-04 18:00:43,586 INFO [org.hibernate.ejb.Version] Hibernate EntityManager 3.2.0.CR2 2006-10-04 18:00:43,625 INFO [org.hibernate.cfg.annotations.Version] Hibernate Annotations 3.2.0.CR2 2006-10-04 18:00:43,638 INFO [org.hibernate.cfg.Environment] Hibernate 3.2 cr4 2006-10-04 18:00:43,649 INFO [org.hibernate.cfg.Environment] hibernate.properties not found 2006-10-04 18:00:43,654 INFO [org.hibernate.cfg.Environment] Bytecode provider name : javassist 2006-10-04 18:00:43,666 INFO [org.hibernate.cfg.Environment] using JDK 1.4 java.sql.Timestamp handling 2006-10-04 18:00:43,906 DEBUG [org.hibernate.ejb.Ejb3Configuration] Processing PersistenceUnitInfo [ name: jon persistence provider classname: org.hibernate.ejb.HibernatePersistence classloader: org.jboss.mx.loading.UnifiedClassLoader3@3b31a6{ url=file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/ ,addedOrder=43} Temporary classloader: null excludeUnlistedClasses: false JTA datasource: org.jboss.resource.adapter.jdbc.WrapperDataSource@c90acb Non JTA datasource: null Transaction type: JTA PU root URL: file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/on-enterprise-server-entity-ejb-2.0-SNAPSHOT.jar/ Jar files URLs [ file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar] Managed classes names [] Mapping files names [] Properties [ -- 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, 7 months

4
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2007