[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)
11 years, 7 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)
11 years, 7 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)
11 years, 7 months
[JBoss JIRA] (WFLY-4153) Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4153?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4153:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 900798|https://bugzilla.redhat.com/show_bug.cgi?id=900798] from POST to MODIFIED
> Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-4153
> URL: https://issues.jboss.org/browse/WFLY-4153
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.0.Alpha1
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
>
> {noformat}
> In case that you specify interface type for entity bean in ejb-jar.xml that does not correspond with definition in the class of the bean then just Null Pointer exception is shown without any other info what's happening.
> I mean when you define bean through interface as remote and the ejb-jar.xml describes bean interfaces as local
> {code}
> public interface SomeBean extends EJBObject {
> ...
> }
> public interface SomeBeanHome extends EJBHome {
> ...
> }
> {code}
> and the ejb-jar.xml looks like
> {code}
> <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1">
> <enterprise-beans>
> <entity>
> <ejb-name>SomeBean</ejb-name>
> <local-home>package.SomeBeanHome</local-home>
> <local>package.SomeBean</local>
> <ejb-class>package.SomeBeanBean</ejb-class>
> <persistence-type>Bean</persistence-type>
> <prim-key-class>java.lang.Integer</prim-key-class>
> <reentrant>true</reentrant>
> </entity>
> </enterprise-beans>
> </ejb-jar>
> {code}
> then NullPointerException is thrown
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "entitybeanbmp.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component SimpleBMPBean
> at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:102)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:108)
> at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:105)
> at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:139)
> at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95)
> ... 6 more
> {code}
> instead of some informative one.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-4156) WildFly is not able to parse ejb-jar.xml of version 2.0
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4156?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4156:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1057835|https://bugzilla.redhat.com/show_bug.cgi?id=1057835] from POST to MODIFIED
> WildFly is not able to parse ejb-jar.xml of version 2.0
> -------------------------------------------------------
>
> Key: WFLY-4156
> URL: https://issues.jboss.org/browse/WFLY-4156
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.0.Alpha1
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Fix For: 9.0.0.Beta1
>
>
> - While using "ejb-jar.xml" of version 2.0 as following EAP/WildFly throws the parsing error:
> {code}
> <?xml version="1.0"?>
> <!DOCTYPE ejb-jar
> PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
> "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
> <ejb-jar>
> <enterprise-beans>
> <message-driven>
> <ejb-name>ExampleMDB</ejb-name>
> <ejb-class>test.mdb.ExampleMDB</ejb-class>
> <transaction-type>Container</transaction-type>
> <message-driven-destination>
> <destination-type>javax.jms.Queue</destination-type>
> </message-driven-destination>
> <resource-ref>
> <res-ref-name>jms/QueueConnectionFactory</res-ref-name>
> <res-type>javax.jms.QueueConnectionFactory</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
> </message-driven>
> </enterprise-beans>
> </ejb-jar>
> {code}
> - The following error is encountered at the time of deployment:
> {code}
> 17:40:04,405 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."TestEJB.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestEJB.jar".PARSE: JBAS018733: Failed to process phase PARSE of deployment "TestEJB.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014185: Exception while parsing ejb-jar.xml: /content/TestEJB.jar/META-INF/ejb-jar.xml
> at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:250)
> at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:121)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> ... 5 more
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,10]
> Message: Unexpected element 'message-driven-destination' encountered
> at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
> at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElement(AbstractMetaDataParser.java:56)
> at org.jboss.metadata.ejb.parser.spec.AbstractNamedMetaDataWithDescriptionGroupParser.processElement(AbstractNamedMetaDataWithDescriptionGroupParser.java:67)
> at org.jboss.metadata.ejb.parser.spec.AbstractEnterpriseBeanMetaDataParser.processElement(AbstractEnterpriseBeanMetaDataParser.java:85)
> at org.jboss.metadata.ejb.parser.spec.AbstractMessageDrivenBeanParser.processElement(AbstractMessageDrivenBeanParser.java:94)
> at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(MessageDrivenBean31Parser.java:77)
> at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(MessageDrivenBean31Parser.java:37)
> at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69)
> at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.parse(MessageDrivenBean31Parser.java:44)
> at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:99)
> at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:40)
> at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69)
> at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:75)
> at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:68)
> at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:112)
> at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:39)
> at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69)
> at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parseDocument(EjbJarMetaDataParser.java:110)
> at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parse(EjbJarMetaDataParser.java:54)
> at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:247)
> ... 7 more
> 17:40:04,422 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TestEJB.jar" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"TestEJB.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"TestEJB.jar\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"TestEJB.jar\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014185: Exception while parsing ejb-jar.xml: /content/TestEJB.jar/META-INF/ejb-jar.xml
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,10]
> Message: Unexpected element 'message-driven-destination' encountered"}}
> {code}
> **NOTE:** According to the link [1] EJB2.0 is supported with EAP6 so ideally JBoss should be able to parse the "ejb-jar.xml" of version 2.0 DTDs.
> **NOTE:** there is a feature request seen for JBossAS7 for requesting support for ejb-jar.xml 2.0 DTDs [2]
> [1] https://access.redhat.com/site/articles/113373
> [2] https://issues.jboss.org/browse/JBMETA-354
> Version-Release number of selected component (if applicable):
> How reproducible:
> Steps to Reproduce:
> 1. Deploy an MDB based EJB jar in EAP6/WildFly and use the ejb-jar.xml as mentioned in the issue description.
> Actual results:
> - EAP6/WildFly should be able to parse the ejb-jar.xml properly and should deploy the MDB properly.
> Expected results:
> - Deployment should be successful.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months