[JBoss JIRA] (AS7-4443) Admin console hangs with "Loading..." icon spinning
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-4443?page=com.atlassian.jira.plugin.s... ]
Heiko Braun commented on AS7-4443:
----------------------------------
Pleae open up another issue with the same description, but also provide some information about the actual server version.
> Admin console hangs with "Loading..." icon spinning
> ---------------------------------------------------
>
> Key: AS7-4443
> URL: https://issues.jboss.org/browse/AS7-4443
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.1.Final
> Environment: Windows 7 Pro 64-bit, Java Version 1.7.0_02, BJoss 7.1.1 Final installed from .zip
> Reporter: Dean Schulze
> Assignee: Heiko Braun
>
> localhost:8080 works. When I click on Admin Console the screen comes up with the "loading..." icon spinning on the screen, but hangs there. I have created an administrative user with add-user.bat but I don't get prompted for credentials. I have successfully installed a REST application with maven and it is working.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (AS7-4443) Admin console hangs with "Loading..." icon spinning
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-4443?page=com.atlassian.jira.plugin.s... ]
Heiko Braun edited comment on AS7-4443 at 12/5/14 11:06 AM:
------------------------------------------------------------
Please open up another issue with the same description, but also provide some information about the actual server version.
was (Author: heiko.braun):
Pleae open up another issue with the same description, but also provide some information about the actual server version.
> Admin console hangs with "Loading..." icon spinning
> ---------------------------------------------------
>
> Key: AS7-4443
> URL: https://issues.jboss.org/browse/AS7-4443
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.1.Final
> Environment: Windows 7 Pro 64-bit, Java Version 1.7.0_02, BJoss 7.1.1 Final installed from .zip
> Reporter: Dean Schulze
> Assignee: Heiko Braun
>
> localhost:8080 works. When I click on Admin Console the screen comes up with the "loading..." icon spinning on the screen, but hangs there. I have created an administrative user with add-user.bat but I don't get prompted for credentials. I have successfully installed a REST application with maven and it is working.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFCORE-449) MBeanRegistrationService throws NameNotFoundException "java:comp/BeanManager" when starting/stoping the MBean
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/WFCORE-449?page=com.atlassian.jira.plugin... ]
Amos Feng updated WFCORE-449:
-----------------------------
Labels: JMX (was: )
> MBeanRegistrationService throws NameNotFoundException "java:comp/BeanManager" when starting/stoping the MBean
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-449
> URL: https://issues.jboss.org/browse/WFCORE-449
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 1.0.0.Alpha13
> Reporter: Amos Feng
> Assignee: Amos Feng
> Labels: JMX
> Fix For: 1.0.0.Alpha14
>
>
> This issue happens if you create an MBean in your EJB and deploy the EJB. The steps to reproduce the issue is the following:
> {code}
> git clone https://github.com/zhfeng/test_jmx_ejb
> cd test_jmx_ejb
> mvn clean install
> {code}
> After starting the wildfly server, copy the test_jmx_ejb-1.0.jar to the deployment directory of the wildfly and you will see the exception
> {code}
> 11:39:30,064 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
> at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)
> at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:106) [wildfly-jmx-1.0.0.Alpha9.jar:1.0.0.Alpha9]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> {code}
> It looks like the JavaNamespaceSetup teardown happens before the WeldContextSetup so it throws NameNotFoundException in the WeldContextSetup teardown.
> The possible fix is to reverse calling the setupActions.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFCORE-449) MBeanRegistrationService throws NameNotFoundException "java:comp/BeanManager" when starting/stoping the MBean
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/WFCORE-449?page=com.atlassian.jira.plugin... ]
Amos Feng updated WFCORE-449:
-----------------------------
Description:
This issue happens if you create an MBean in your EJB and deploy the EJB. The steps to reproduce the issue is the following:
{code}
git clone https://github.com/zhfeng/test_jmx_ejb
cd test_jmx_ejb
mvn clean install
{code}
After starting the wildfly server, copy the test_jmx_ejb-1.0.jar to the deployment directory of the wildfly and you will see the exception
{code}
11:39:30,064 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager
at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:106) [wildfly-jmx-1.0.0.Alpha9.jar:1.0.0.Alpha9]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
{code}
It looks like the JavaNamespaceSetup teardown happens before the WeldContextSetup so it throws NameNotFoundException in the WeldContextSetup teardown.
The possible fix is to reverse calling the setupActions.
was:
The steps to reproduce the issue is the following:
{code}
git clone https://github.com/zhfeng/test_jmx_ejb
cd test_jmx_ejb
mvn clean install
after starting the wildfly server, copy the test_jmx_ejb-1.0.jar to the deployment directory of the wildfly
{code}
you will see the exception
{code}
11:39:30,064 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager
at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:106) [wildfly-jmx-1.0.0.Alpha9.jar:1.0.0.Alpha9]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
{code}
It looks like the JavaNamespaceSetup teardown happens before the WeldContextSetup so it throws NameNotFoundException in the WeldContextSetup teardown.
The possible fix is to reverse calling the setupActions.
> MBeanRegistrationService throws NameNotFoundException "java:comp/BeanManager" when starting/stoping the MBean
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-449
> URL: https://issues.jboss.org/browse/WFCORE-449
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 1.0.0.Alpha13
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 1.0.0.Alpha14
>
>
> This issue happens if you create an MBean in your EJB and deploy the EJB. The steps to reproduce the issue is the following:
> {code}
> git clone https://github.com/zhfeng/test_jmx_ejb
> cd test_jmx_ejb
> mvn clean install
> {code}
> After starting the wildfly server, copy the test_jmx_ejb-1.0.jar to the deployment directory of the wildfly and you will see the exception
> {code}
> 11:39:30,064 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
> at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)
> at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:106) [wildfly-jmx-1.0.0.Alpha9.jar:1.0.0.Alpha9]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> {code}
> It looks like the JavaNamespaceSetup teardown happens before the WeldContextSetup so it throws NameNotFoundException in the WeldContextSetup teardown.
> The possible fix is to reverse calling the setupActions.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFCORE-449) MBeanRegistrationService throws NameNotFoundException "java:comp/BeanManager" when starting/stoping the MBean
by Amos Feng (JIRA)
Amos Feng created WFCORE-449:
--------------------------------
Summary: MBeanRegistrationService throws NameNotFoundException "java:comp/BeanManager" when starting/stoping the MBean
Key: WFCORE-449
URL: https://issues.jboss.org/browse/WFCORE-449
Project: WildFly Core
Issue Type: Bug
Affects Versions: 1.0.0.Alpha13
Reporter: Amos Feng
Assignee: Amos Feng
Fix For: 1.0.0.Alpha14
The steps to reproduce the issue is the following:
{code}
git clone https://github.com/zhfeng/test_jmx_ejb
cd test_jmx_ejb
mvn clean install
after starting the wildfly server, copy the test_jmx_ejb-1.0.jar to the deployment directory of the wildfly
{code}
you will see the exception
{code}
11:39:30,064 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager
at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:106) [wildfly-jmx-1.0.0.Alpha9.jar:1.0.0.Alpha9]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
{code}
It looks like the JavaNamespaceSetup teardown happens before the WeldContextSetup so it throws NameNotFoundException in the WeldContextSetup teardown.
The possible fix is to reverse calling the setupActions.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFLY-4011) Resource adapter config properties cannot be changed without two reloads
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-4011?page=com.atlassian.jira.plugin.... ]
Stefano Maestri commented on WFLY-4011:
---------------------------------------
Linked pull request makes config-property value attribure read-write instead of read-only. Of course it's a reload-required writable attribute
> Resource adapter config properties cannot be changed without two reloads
> ------------------------------------------------------------------------
>
> Key: WFLY-4011
> URL: https://issues.jboss.org/browse/WFLY-4011
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA
> Affects Versions: 8.1.0.Final
> Environment: Ubuntu 14.0.4 64-bit; JDK 1.8.0_25; Wildfly 8.1.0.Final standalone
> Reporter: Scott Van Wart
> Assignee: Stefano Maestri
> Priority: Minor
> Labels: cli, resource-adapter
> Attachments: remove-add.txt, remove-reload-add.txt
>
>
> I have a RAR deployed within an EAR file and it defines a config property "host" in the resource-adapter subsystem. I followed the binding instructions here:
> https://docs.jboss.org/author/display/WFLY8/Resource+adapters
> If I want to change the "host" configuration property, I need to do the following:
> 1. Remove the configuration property.
> 2. Reload
> 3. Add the configuration property back.
> 4. Reload
> The "value" attribute of the config property isn't writable (JCA doesn't communicate config property changes during runtime): https://issues.jboss.org/browse/WFLY-3729
> Trying to add the property again after removal results in an error as Wildfly believes the attribute still exists if you haven't reloaded since removal.
> This makes scripting a resource adapter property change difficult, as the "reload" command returns immediately and a script must wait an unknown amount of time for the management interface to become available before it can issue new commands.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (AS7-4443) Admin console hangs with "Loading..." icon spinning
by Hugo Baés Jr. (JIRA)
[ https://issues.jboss.org/browse/AS7-4443?page=com.atlassian.jira.plugin.s... ]
Hugo Baés Jr. commented on AS7-4443:
------------------------------------
I have a similar problem. When I access the admin console it hangs with the loading message.
My javascript shows the following exception:
2014-12-05 13:25:05,396 [FATAL] Uncaught JavaScript exception [Uncaught SyntaxError: Unexpected end of input] in , line 7449
1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:681 $e1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:788 df1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:729 Jf1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:496 Zf1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:559 bg1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:1 __gwtInstallCode1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:788 Sq1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:576 (anonymous function)1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:475 wp1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:740 zp1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:595 (anonymous function)
I'm using a custom module and some JNDI bindings (in standalone.xml). If I take the module and the bindings out, it works and I can access de Admin Console again.
I tested with only the module installed and with only the bindings configuration, either way the JavaScript Exception shows up again (besides the errors on jboss log with the bindings configurations alone)
These are my bindings configuration in standalone.xml:
<subsystem xmlns="urn:jboss:domain:naming:1.1">
<bindings>
<simple name="java:global/solr/home" value="solr/" type="java.lang.String"/>
<object-factory name="java:global/GoldenGateAPI" module="br.com.softplan.goldengate" class="br.com.softplan.goldengate.api.impl.GGAPIFactory"/>
<object-factory name="java:global/GoldenGateDIH" module="br.com.softplan.goldengate" class="br.com.softplan.goldengate.api.impl.GGDIHFactory"/>
</bindings>
</subsystem>
> Admin console hangs with "Loading..." icon spinning
> ---------------------------------------------------
>
> Key: AS7-4443
> URL: https://issues.jboss.org/browse/AS7-4443
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.1.Final
> Environment: Windows 7 Pro 64-bit, Java Version 1.7.0_02, BJoss 7.1.1 Final installed from .zip
> Reporter: Dean Schulze
> Assignee: Heiko Braun
>
> localhost:8080 works. When I click on Admin Console the screen comes up with the "loading..." icon spinning on the screen, but hangs there. I have created an administrative user with add-user.bat but I don't get prompted for credentials. I have successfully installed a REST application with maven and it is working.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months