March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4103) Remove fallback mechanism from taking any AS7 property content

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-4103?page=com.atlassian.jira.plugin.s... ] Pavel Janousek moved JBPAPP-8387 to AS7-4103: --------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4103 (was: JBPAPP-8387) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.1.Final (was: EAP 6.0.0 ER 3) Component/s: Test Suite (was: Testsuite) Security: (was: JBoss Internal) Docs QE Status: (was: NEW) > Remove fallback mechanism from taking any AS7 property content > -------------------------------------------------------------- > > Key: AS7-4103 > URL: https://issues.jboss.org/browse/AS7-4103 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > > There are several places where fallback mechanism is used when someone can take AS7 property content. Final decision is to force using this mechanism inside pom.xml's and not in java code. Thus, after resolving AS7-4102 is needed to remove every piece of code which use the old approach. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4079) ModClusterSubsystemTestCase.java subsystem.xml needs extending

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4079: ----------------------------------- Summary: ModClusterSubsystemTestCase.java subsystem.xml needs extending Key: AS7-4079 URL: https://issues.jboss.org/browse/AS7-4079 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.2.Final This is testing only tiny part of the entire configuration. Needs extending. This could lead to issues like AS7-4077 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-3340) NPE during stop of service jboss.jacorb.poa-service.rootpoa

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/AS7-3340?page=com.atlassian.jira.plugin.s... ] Stefan Guilhen closed AS7-3340. ------------------------------- The fix has been merged. Now we only destroy the RootPOA and let JacORB code handle the child POAs destruction. > NPE during stop of service jboss.jacorb.poa-service.rootpoa > ----------------------------------------------------------- > > Key: AS7-3340 > URL: https://issues.jboss.org/browse/AS7-3340 > Project: Application Server 7 > Issue Type: Bug > Components: IIOP > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Stefan Guilhen > Priority: Critical > Fix For: 7.1.1.Final > > > There is randomly occured NPE when stopping EAP a bit quickly after it started. > {code} > 15:55:17,151 ERROR [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started (with errors) in 8066ms - Started 132 of 222 services (20 services failed or missing dependencies, 68 services are passive or on-demand) > ^C15:55:19,867 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/queue/test > 15:55:19,870 INFO [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011921: Stopping OSGi Framework > 15:55:19,876 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory > 15:55:19,878 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] > 15:55:19,888 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers > 15:55:19,897 INFO [jacorb.poa] POA IRPOA destroyed > 15:55:19,898 INFO [jacorb.poa] POA Naming destroyed > 15:55:19,906 WARN [org.jboss.msc.service.fail] MSC000004: Failure during stop of service jboss.jacorb.poa-service.rootpoa: java.lang.NullPointerException > at org.jacorb.poa.POA.destroy(Unknown Source) > at org.jboss.as.jacorb.service.CorbaPOAService.stop(CorbaPOAService.java:187) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] > 15:55:19,910 INFO [jacorb.orb] prepare ORB for shutdown... > {code} > As you can see above, I hit Ctrl-C in two seconds after start is done. NPE isn't occurred every time and I didn't see it anytime when EAP was running for a longer time (let say 10 seconds and more). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3156) Cannot add clustered caches to a cache container started without a transport

by Tristan Tarrant (Created) (JIRA)

Cannot add clustered caches to a cache container started without a transport ---------------------------------------------------------------------------- Key: AS7-3156 URL: https://issues.jboss.org/browse/AS7-3156 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Tristan Tarrant Assignee: Paul Ferraro Fix For: 7.1.0.Final Because a transport is bound to a cache container only if there are clustered caches in the initial configuration, adding a clustered cache to such a cache container will result in Infinispan complaining about not having a transport. This can be solved by either always starting with a transport, or by making a distinction between local and clustered cache containers. Furthermore, making a clustered cache EAGER within the configuration XML file (they are LAZY by default), will trigger this problem even on startup: MSC00001: Failed to start service jboss.infinispan.sfsb.repl: org.jboss.msc.service.StartException in service jboss.infinispan.sfsb.repl: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] Caused by: org.infinispan.config.ConfigurationException: Cache cannot use a clustered mode (REPL_ASYNC) mode and not define a transport! at org.infinispan.config.Configuration.assertValid(Configuration.java:1664) at org.infinispan.manager.DefaultCacheManager.wireCache(DefaultCacheManager.java:683) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:645) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:541) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:555) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:118) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:109) at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:80) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] ... 3 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
8
0 / 0

[JBoss JIRA] (AS7-3877) standalone EE profile references non-existent hornetq resouce adapter

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3877: ----------------------------------- Summary: standalone EE profile references non-existent hornetq resouce adapter Key: AS7-3877 URL: https://issues.jboss.org/browse/AS7-3877 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: David Lloyd Fix For: 7.1.1.Final Either messaging subsystem is part of the server or the EE should not be using it. {noformat} <mdb> <resource-adapter-ref resource-adapter-name="hornetq-ra"/> <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> </mdb> {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
5
0 / 0

[JBoss JIRA] (AS7-3498) LoginModule defined with cached=default, but called between web and ejb container

by Daniel Straub (JIRA)

Daniel Straub created AS7-3498: ---------------------------------- Summary: LoginModule defined with cached=default, but called between web and ejb container Key: AS7-3498 URL: https://issues.jboss.org/browse/AS7-3498 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.CR1b Reporter: Daniel Straub Priority: Critical Each calling between web and ejb container calls the LoginModule associated to, regardless of whether this is defined with "cache=default" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
4
0 / 0

[JBoss JIRA] (AS7-3945) Fail to enable DS

by Heiko Braun (JIRA)

Heiko Braun created AS7-3945: -------------------------------- Summary: Fail to enable DS Key: AS7-3945 URL: https://issues.jboss.org/browse/AS7-3945 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.1.Final Disable the default DS in standalone mode and re-eanble it: {noformat} { "outcome" => "failed", "failure-description" => "JBAS014749: Operation handler failed: Service jboss.data-source-config.ExampleDS is already registered", "rolled-back" => true, "response-headers" => {"process-state" => "restart-required"} } {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] (AS7-3743) Sporadic IE 8&9 failure: stylesheets do not load

by Heiko Braun (JIRA)

Heiko Braun created AS7-3743: -------------------------------- Summary: Sporadic IE 8&9 failure: stylesheets do not load Key: AS7-3743 URL: https://issues.jboss.org/browse/AS7-3743 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.1.Final A simliar problem: http://drupal.org/node/387962 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
8
0 / 0

[JBoss JIRA] (AS7-3993) Fix up generation of IPv6 ready configs for IPv6 testing

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-3993: ---------------------------------------- Summary: Fix up generation of IPv6 ready configs for IPv6 testing Key: AS7-3993 URL: https://issues.jboss.org/browse/AS7-3993 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.Final Reporter: Richard Achmatowicz Assignee: Andrew Rubinger Fix For: 7.1.1.Final The testsuite uses a combination of: - the ant script clustering-build.xml, with target build-clustering-udp - the ant script common-targets.xml, with target ts.config-as.ip-with-multicast and - the XSLT script changeIAddresses.xsl to set up IPv6 addresses for testing single and multi-node tests. There are several problems: - the XSLT script is broken and does not change the multicast addresses - a number of multicast addresses are not receiving IPv6 defaults/overrides; in particular, we have the following required overrides: UDP JGroups stack multicast requirements: -- socket-binding jgroups-udp: no IPv6 multicast address assigned, due to broken changeIPAddresses.xml -- socket-binding jgroups-diagnostics: no IPv6 multicast address assigned, due to no parameter passed in ts.config-as.ip-with-multicast TCP JGroups stack multicast-requirements: -- socket-binding jgroups-mping: no IPv6 multicast address assigned, due to no parameter passed in ts.config-as.ip-with-multicast -- socket-binding jgroups-diagnostics: no IPv6 multicast address assigned, due to no parameter passed in ts.config-as.ip-with-multicast mosdcluster multicast-requirements: -- socket-binding modcluster: no IPv6 multicast address assigned, due to no parameter passed in ts.config-as.ip-with-multicast -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
54
0 / 0

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

by Stian Thorgersen (Created) (JIRA)

javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection ---------------------------------------------------------------------------------------------------------- Key: AS7-2138 URL: https://issues.jboss.org/browse/AS7-2138 Project: Application Server 7 Issue Type: Bug Reporter: Stian Thorgersen Attachments: jmx-test.jar, JMXConnectionBean.java When trying to create a MBeanServerConnection from within an EJB a "javax.naming.NameNotFoundException" is thrown. When executed as a standalone Java the same code works fine. 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

13
42
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 March 2012