April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6862) EjbUtilities is used without regard for dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6862?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6862: ---------------------------------------------- Jason T. Greene <jason.greene(a)redhat.com> made a comment on [bug 950864|https://bugzilla.redhat.com/show_bug.cgi?id=950864] Need the acks > EjbUtilities is used without regard for dependencies > ---------------------------------------------------- > > Key: AS7-6862 > URL: https://issues.jboss.org/browse/AS7-6862 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > > org.jboss.as.ejb3.component.EJBUtilities is used to get services in the EJB subsystem, without setting up proper dependencies (e.g. in org.jboss.as.ejb3.component.EJBComponentCreateService#getEJBUtilities). Occasionally this can cause problems at startup as EJBUtilities can end up being null for some EJB's. > We should probably just remove this class, or at the very least make sure it is injected properly and not looked up. -- 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-6962) Remove AbstractRuntimeOnlyHandler.waitFor

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6962?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6962: ---------------------------------- Assignee: (was: Brian Stansberry) Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Alpha1) Git Pull Request: (was: https://github.com/jbossas/jboss-as/pull/4403) Description: Remove this method; it was deprecated in 8.0.0. (was: Remove this method; it was deprec.) > Remove AbstractRuntimeOnlyHandler.waitFor > ----------------------------------------- > > Key: AS7-6962 > URL: https://issues.jboss.org/browse/AS7-6962 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > Remove this method; it was deprecated in 8.0.0. -- 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-6911) jconsole fails if trying to connect to a standalone EAP instance running with offset ports

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/AS7-6911?page=com.atlassian.jira.plugin.s... ] Stan Silvert resolved AS7-6911. ------------------------------- Resolution: Done > jconsole fails if trying to connect to a standalone EAP instance running with offset ports > ------------------------------------------------------------------------------------------ > > Key: AS7-6911 > URL: https://issues.jboss.org/browse/AS7-6911 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Stan Silvert > Labels: cli > > If JBoss AS7/8 is started using port-offset as following: > ie. with -Djboss.socket.binding.port-offset=100 > Then While connecting to it using "jconsole.sh" as a Local Process it throws the following Exception: > +++++++++++++++++++++++++++++ > Exception in thread "AWT-EventQueue-0" java.lang.RuntimeException: Error connecting to JBoss AS. > at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:80) > at sun.tools.jconsole.VMPanel.createPluginTabs(VMPanel.java:641) > at sun.tools.jconsole.VMPanel.propertyChange(VMPanel.java:315) > at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) > at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:75) > at javax.swing.event.SwingPropertyChangeSupport$1.run(SwingPropertyChangeSupport.java:80) > at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:646) > at java.awt.EventQueue.access$000(EventQueue.java:84) > at java.awt.EventQueue$1.run(EventQueue.java:607) > at java.awt.EventQueue$1.run(EventQueue.java:605) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:616) > at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269) > at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) > Caused by: java.lang.NullPointerException > at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectCommandContext(JConsoleCLIPlugin.java:109) > at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:77) > +++++++++++++++++++++++ > And the Code "org.jboss.as.cli.gui.JConsoleCLIPlugin" classes Line 109 throws NullPointerException, Because "cliGuiCtx" object is null and not initialized earlier: > 109 JOptionPane.showMessageDialog(cliGuiCtx.getMainWindow(), message); -- 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-6962) Remove AbstractRuntimeOnlyHandler.waitFor

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6962: ------------------------------------- Summary: Remove AbstractRuntimeOnlyHandler.waitFor Key: AS7-6962 URL: https://issues.jboss.org/browse/AS7-6962 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.0.Alpha1 Deprecate this method and move the existing usage of it to SecurityDomainResourceDefinition. This method has nothing in particular to do with AbstractRuntimeOnlyHandler other than > 1 subclass wanted the behavior. Also, the i18n in the logic is not handled. -- 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-6962) Remove AbstractRuntimeOnlyHandler.waitFor

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6962?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6962: ---------------------------------- Description: Remove this method; it was deprec. (was: Deprecate this method and move the existing usage of it to SecurityDomainResourceDefinition. This method has nothing in particular to do with AbstractRuntimeOnlyHandler other than > 1 subclass wanted the behavior. Also, the i18n in the logic is not handled.) > Remove AbstractRuntimeOnlyHandler.waitFor > ----------------------------------------- > > Key: AS7-6962 > URL: https://issues.jboss.org/browse/AS7-6962 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Remove this method; it was deprec. -- 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-5403) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5403: ---------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] Documentation ------------- If one wants to use advertise=true and no proxy-list, a proper socket-binding must be added. Here is the whole batch op executed from a command line: ./jboss-cli.sh --connect --commands=" /extension=org.jboss.as.modcluster:add(), /subsystem=web/connector=ajp:add(name=ajp,protocol=ajp,scheme=ajp,socket-binding=ajp), batch, /:composite(steps=[ {\"operation\" => \"add\", \"address\" => [ (\"subsystem\" => \"modcluster\") ] }, { \"operation\" => \"add\", \"address\" => [ (\"subsystem\" => \"modcluster\"), (\"mod-cluster-config\" => \"configuration\") ], \"connector\" => \"ajp\", \"advertise-socket\" => \"modcluster\" }, {\"operation\" => \"add\", \"address\" => [(\"socket-binding-group\" => \"standard-sockets\"), (\"socket-binding\" => \"modcluster\")], \"port\" => 0, \"multicast-address\" => \"224.0.1.105\", \"multicast-port\" => \"23364\"} ]), run-batch" (Note socket-binding and advertise-socket.) > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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-6936) Intermittent failures in AdminOnlyTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6936?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6936: ---------------------------------- Git Pull Request: (was: https://github.com/jbossas/jboss-as/pull/4404) > Intermittent failures in AdminOnlyTestCase > ------------------------------------------ > > Key: AS7-6936 > URL: https://issues.jboss.org/browse/AS7-6936 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Test Suite > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Failures like the following are popping up frequently in some EAP test environments. There is no reason to expect the same issue wouldn't exist upstream. > java.lang.IllegalStateException: Didn't get a remoting channel from the DomainTestClient. > at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.executeAwaitConnectionClosed(DomainLifecycleUtil.java:316) > at org.jboss.as.test.integration.domain.AdminOnlyModeTestCase.testAdminOnlyMode(AdminOnlyModeTestCase.java:105) > 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > 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 org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) -- 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-6961) NPE when calling a runtime handler on a HornetQ server that just has been activated

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-6961: -------------------------------- Summary: NPE when calling a runtime handler on a HornetQ server that just has been activated Key: AS7-6961 URL: https://issues.jboss.org/browse/AS7-6961 Project: Application Server 7 Issue Type: Bug Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Priority: Minor if a hornetq-server has just been activated (a backup server that has just failed over), a client can get a NPE if he calls a runtime operation on the server's children resources: {noformat} 22:59:18,142 ERROR org.jboss.as.controller.management-operation JBAS014612: Operation ("read-attribute") failed - address: ([ ("subsystem" => "messaging"), ("hornetq-server" => "default"), ("queue" => "bb37547c-3d64-4800-be47-3ef0434d1b11") ]): java.lang.NullPointerException at org.jboss.as.messaging.QueueReadAttributeHandler.executeRuntimeStep(QueueReadAttributeHandler.java:115) at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:86) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:439) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:321) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:228) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:223) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:235) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:124) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:148) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:97) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:114) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] {noformat} The NPE happens because the HornetQ server has been activated, yet the resource (in this case a queue) is not available (the queue service is installing and the queue is not deployed by HornetQ). The operation is ignored if the HornetQ server is not activated[1] but that's not enough. We also have to check whether the QueueService is installed before using the QueueControl. There will still be a window of failure but we can report to the user that the runtime resource is not (yet) available instead of a ugly NPE [1] https://github.com/jbossas/jboss-as/blob/master/messaging/src/main/java/o... -- 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-6960) Injection failure in an ejb's superclass when superclass is loaded from a jboss module

by Andrei Serea (JIRA)

[ https://issues.jboss.org/browse/AS7-6960?page=com.atlassian.jira.plugin.s... ] Andrei Serea updated AS7-6960: ------------------------------ Attachment: ejbmoduledep_testcase.zip jboss_module.zip > Injection failure in an ejb's superclass when superclass is loaded from a jboss module > -------------------------------------------------------------------------------------- > > Key: AS7-6960 > URL: https://issues.jboss.org/browse/AS7-6960 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final > Reporter: Andrei Serea > Assignee: jaikiran pai > Attachments: ejbmoduledep_testcase.zip, jboss_module.zip > > -- 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-6960) Injection failure in an ejb's superclass when superclass is loaded from a jboss module

by Andrei Serea (JIRA)

Andrei Serea created AS7-6960: --------------------------------- Summary: Injection failure in an ejb's superclass when superclass is loaded from a jboss module Key: AS7-6960 URL: https://issues.jboss.org/browse/AS7-6960 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Andrei Serea Assignee: jaikiran pai -- 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