April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6956) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6956?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6956: ----------------------------------- You might want to follow [CDI-162|https://issues.jboss.org/browse/CDI-162] which is about adding extended persistence context support to managed beans which is currently not supported. > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: AS7-6956 > URL: https://issues.jboss.org/browse/AS7-6956 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brand Neu > Assignee: Scott Marlow > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6959) Make naming fail in case no context is present

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/AS7-6959?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski updated AS7-6959: ------------------------------------ Assignee: Bartosz Baranowski (was: Eduardo Martins) > Make naming fail in case no context is present > ---------------------------------------------- > > Key: AS7-6959 > URL: https://issues.jboss.org/browse/AS7-6959 > Project: Application Server 7 > Issue Type: Feature Request > Components: Naming > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 8.0.0.Alpha1 > > > This is a followup of AS7-2138. Original code, in case no URL context threw NamingException. The AS7-2138 introduced a fallback to NamingContext in case AS7 does not provide custom hack for url( like EJB ). However the fallback did not fail with NamingException in case it did not locate Context. This essentially made it go knee deep into AS7 service lookups, which hides real cause of failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6959) Make naming fail in case no context is present

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created AS7-6959: --------------------------------------- Summary: Make naming fail in case no context is present Key: AS7-6959 URL: https://issues.jboss.org/browse/AS7-6959 Project: Application Server 7 Issue Type: Feature Request Components: Naming Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Bartosz Baranowski Assignee: Eduardo Martins Fix For: 8.0.0.Alpha1 This is a followup of AS7-2138. Original code, in case no URL context threw NamingException. The AS7-2138 introduced a fallback to NamingContext in case AS7 does not provide custom hack for url( like EJB ). However the fallback did not fail with NamingException in case it did not locate Context. This essentially made it go knee deep into AS7 service lookups, which hides real cause of failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6941) CLI jboss-cli.sh/bat --help fails with StringIndexOutOfBoundsException

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-6941?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky resolved AS7-6941. ------------------------------------ Resolution: Done Fixed. > CLI jboss-cli.sh/bat --help fails with StringIndexOutOfBoundsException > ---------------------------------------------------------------------- > > Key: AS7-6941 > URL: https://issues.jboss.org/browse/AS7-6941 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Alpha1 > > > The CLI doesn't initialize the console when it is launched in the non-interactive mode. But the help content formatter relies on the current terminal width and height that are set to -1 in the non-interactive mode. > So, the console should be initialized on demand/lazily in these cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6522) Expose "upload-deployment-url" operation via the CLI high-level "deploy" command

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-6522?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky resolved AS7-6522. ------------------------------------ Fix Version/s: 8.0.0.Alpha1 Resolution: Done Done. deploy now accepts --url argument. > Expose "upload-deployment-url" operation via the CLI high-level "deploy" command > -------------------------------------------------------------------------------- > > Key: AS7-6522 > URL: https://issues.jboss.org/browse/AS7-6522 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Alpha1 > > > The core management API "upload-deployment-url" operation on the root resource allows the user to upload content located on remote location, as long as it is available via a URL accessible to the server. Feature request is to add support for using this to the CLI deploy command. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6851) javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/AS7-6851?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski commented on AS7-6851: ----------------------------------------- Few things: 1. Which OS? 2. Which VM? 3. Did you add this: <path name="com/sun/jndi/url/rmi"/> in sun module? Im able to observe this only in case of OpenJDK on ubuntu, this is due: 1. OpenJDK bug in rmiURLContext( though Ive seen similar bugs in other JDKs iirc ): https://bugs.openjdk.java.net/show_bug.cgi?id=100312 2. ubuntu haveing by default two definition for localhost - - 127.0.0.1 -> localhost - 127.0.1.1 -> `uname -n` Hence the URI hack context. > javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection > ---------------------------------------------------------------------------------------------------------- > > Key: AS7-6851 > URL: https://issues.jboss.org/browse/AS7-6851 > Project: Application Server 7 > Issue Type: Bug > Components: JMX > Affects Versions: 7.0.0.Final, 7.0.1.Final, 7.0.2.Final, 7.1.0.Final, 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Alex Corvino > Assignee: Bartosz Baranowski > Attachments: jmx-test.jar, JmxClient.java, JMXConnectionBean.java, JmxServer.java > > > When trying to create a MBeanServerConnection to a NON-JBoss application from within an EJB a "javax.naming.NameNotFoundException" is thrown. > Steps to reproduce: > Set up a stand-alone application that exposes an MBean. (ActiveMQ will work in this case.) > Modify the attached JMXConnectionBean.java to connect to the ActiveMQ instance. > Deploy the bean. A NameNotFoundException will be thrown. > I've seen this behavior in 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final). > Note that this behavior is NOT seen when connecting to another JBoss server. > Full stack trace: > {code} > Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:340) [:1.6.0_26] > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) [:1.6.0_26] > at com.example.JMXConnectionBean.init(JMXConnectionBean.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:70) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ee.component.ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:44) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor$CustomSessionInvocationContext.proceed(SessionInvocationContextInterceptor.java:126) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:211) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:313) > at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) > at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:42) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:71) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:152) > ... 9 more > Caused by: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:209) > at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_26] > at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1888) [:1.6.0_26] > at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1858) [:1.6.0_26] > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) [:1.6.0_26] > ... 37 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-734) Slow policy evaluation with a large number of policy sets

by Maxim Zinal (JIRA)

[ https://issues.jboss.org/browse/SECURITY-734?page=com.atlassian.jira.plug... ] Maxim Zinal updated SECURITY-734: --------------------------------- Attachment: fix-734.patch A small patch fixing performance problem > Slow policy evaluation with a large number of policy sets > --------------------------------------------------------- > > Key: SECURITY-734 > URL: https://issues.jboss.org/browse/SECURITY-734 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Environment: RedHat Linux 6.0, WebSphere Application Server 7.0 > Reporter: Maxim Zinal > Assignee: Anil Saldhana > Attachments: fix-734.patch > > > We suffer a performance problem in the evaluation of large XACML configuration. We use JBoss (Sun?) XACML library to process a large number of policy sets (over 2400 policy set files) using "deny-override" combining algorithm. > Initially the number of policies was relatively small, but it increased with time, leading to performance degradation, with 100% CPU (single)core consumption. > After running a code sample under Java profiler, we found that 99% of time is spent in method PolicySetFinderModule.findPolicy(URI, int, VersionConstraints, PolicyMetaData). > This method walks through a list of AbstractPolicy objects, comparing an ID of each object with it's first argument. In our configuration the number of such objects is relatively large, leading to slow execution with high CPU consumption. > We suggest replacing the list of AbstractPolicy with a HashMap. Our experiments show that total evaluation time reduces ~50 times with a HashMap over List implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-734) Slow policy evaluation with a large number of policy sets

by Maxim Zinal (JIRA)

Maxim Zinal created SECURITY-734: ------------------------------------ Summary: Slow policy evaluation with a large number of policy sets Key: SECURITY-734 URL: https://issues.jboss.org/browse/SECURITY-734 Project: PicketBox Issue Type: Enhancement Security Level: Public (Everyone can see) Environment: RedHat Linux 6.0, WebSphere Application Server 7.0 Reporter: Maxim Zinal Assignee: Anil Saldhana We suffer a performance problem in the evaluation of large XACML configuration. We use JBoss (Sun?) XACML library to process a large number of policy sets (over 2400 policy set files) using "deny-override" combining algorithm. Initially the number of policies was relatively small, but it increased with time, leading to performance degradation, with 100% CPU (single)core consumption. After running a code sample under Java profiler, we found that 99% of time is spent in method PolicySetFinderModule.findPolicy(URI, int, VersionConstraints, PolicyMetaData). This method walks through a list of AbstractPolicy objects, comparing an ID of each object with it's first argument. In our configuration the number of such objects is relatively large, leading to slow execution with high CPU consumption. We suggest replacing the list of AbstractPolicy with a HashMap. Our experiments show that total evaluation time reduces ~50 times with a HashMap over List implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6956) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Brand Neu (JIRA)

[ https://issues.jboss.org/browse/AS7-6956?page=com.atlassian.jira.plugin.s... ] Brand Neu edited comment on AS7-6956 at 4/19/13 8:15 AM: --------------------------------------------------------- Hi, relevant source-snippet from class: {code:java} @ManagedBean(name="KorrekturgrundFacade") @SessionScoped @Stateful public class StdGrundKorrekturFacade extends AbstractFacade<StdGrundKorrektur> { @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) ... } {code} was (Author: brand-neu): Hi, relevant source-snippet from class: @ManagedBean(name="KorrekturgrundFacade") @SessionScoped @Stateful public class StdGrundKorrekturFacade extends AbstractFacade<StdGrundKorrektur> { @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) ... } > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: AS7-6956 > URL: https://issues.jboss.org/browse/AS7-6956 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brand Neu > Assignee: Scott Marlow > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6956) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Brand Neu (JIRA)

[ https://issues.jboss.org/browse/AS7-6956?page=com.atlassian.jira.plugin.s... ] Brand Neu commented on AS7-6956: -------------------------------- Hi, relevant source-snippet from class: <pre> @ManagedBean(name="KorrekturgrundFacade") @SessionScoped @Stateful public class StdGrundKorrekturFacade extends AbstractFacade<StdGrundKorrektur> { @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) ... } </pre> > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: AS7-6956 > URL: https://issues.jboss.org/browse/AS7-6956 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brand Neu > Assignee: Scott Marlow > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
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 2013