[JBoss JIRA] (WFCORE-993) Reload command on embed-host-controller fails
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-993?page=com.atlassian.jira.plugin... ]
Ken Wills reopened WFCORE-993:
------------------------------
Assignee: Ken Wills (was: Petr Kremensky)
This should have been reopened when JBEAP-1120 was. Sorry for the confusion.
> Reload command on embed-host-controller fails
> ---------------------------------------------
>
> Key: WFCORE-993
> URL: https://issues.jboss.org/browse/WFCORE-993
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.0.CR1
> Reporter: Petr Kremensky
> Assignee: Ken Wills
> Priority: Critical
> Fix For: 2.0.0.CR7
>
>
> Reload operation on embed-host-controller gives me an error.
> {noformat}
> [disconnected /] embed-host-controller
> [domain@embedded /] reload --host=master
> 13:25:30,019 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.CR1) stopped in 6ms
> 13:25:30,020 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.CR1) starting
> 13:25:30,115 ERROR [org.jboss.as.controller] (AeshProcess: 2) WFLYCTL0369: Required capabilities are not available:
> org.wildfly.domain.server-group.main-server-group in context 'server-config'; There are no known registration points which can provide this capability.
> org.wildfly.domain.server-group.main-server-group in context 'server-config'; There are no known registration points which can provide this capability.
> org.wildfly.domain.server-group.other-server-group in context 'server-config'; There are no known registration points which can provide this capability.
> 13:25:30,138 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'enabled' in the resource at address '/profile=default/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 13:25:30,150 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'enabled' in the resource at address '/profile=ha/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 13:25:30,166 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'enabled' in the resource at address '/profile=full/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 13:25:30,167 ERROR [org.jboss.as.controller] (AeshProcess: 2) WFLYCTL0369: Required capabilities are not available:
> org.wildfly.domain.server-group.main-server-group in context 'server-config'; There are no known registration points which can provide this capability.
> org.wildfly.domain.server-group.main-server-group in context 'server-config'; There are no known registration points which can provide this capability.
> org.wildfly.network.socket-binding.jgroups-mping in context 'profile=ha'; There are no known registration points which can provide this capability.
> org.wildfly.network.socket-binding.jgroups-udp-fd in context 'profile=ha'; There are no known registration points which can provide this capability.
> org.wildfly.network.socket-binding.http in context 'profile=ha'; There are no known registration points which can provide this capability.
> org.wildfly.network.socket-binding.jgroups-tcp in context 'profile=ha'; There are no known registration points which can provide this capability.
> org.wildfly.network.socket-binding.jgroups-tcp-fd in context 'profile=ha'; There are no known registration points which can provide this capability.
> org.wildfly.network.socket-binding.http in context 'profile=default'; There are no known registration points which can provide this capability.
> org.wildfly.network.socket-binding.ajp in context 'profile=ha'; There are no known registration points which can provide this capability.
> org.wildfly.network.socket-binding.jgroups-udp in context 'profile=ha'; There are no known registration points which can provide this capability.
> org.wildfly.domain.server-group.other-server-group in context 'server-config'; There are no known registration points which can provide this capability.
> 13:25:30,178 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'enabled' in the resource at address '/profile=full-ha/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 13:25:30,196 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/server-group=main-server-group' are not available:
> org.wildfly.domain.profile.full in context 'server-groups'; There are no known registration points which can provide this capability.
> 13:25:30,198 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 13:25:30,204 ERROR [org.jboss.as.protocol] (Thread-2) WFLYPRT0003: Failed to close resource org.jboss.as.cli.embedded.ThreadContextsModelControllerClient@713124ae: java.lang.IllegalStateException: WFLYEMB0023: The embedded server is stopping and invocations on the ModelControllerClient are not available
> at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl.getActiveModelControllerClient(EmbeddedHostControllerFactory.java:331)
> at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl.access$200(EmbeddedHostControllerFactory.java:225)
> at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl$3.getDelegate(EmbeddedHostControllerFactory.java:309)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.close(DelegatingModelControllerClient.java:103)
> at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.close(ThreadContextsModelControllerClient.java:139)
> at org.jboss.as.protocol.StreamUtils.safeClose(StreamUtils.java:66)
> at org.jboss.as.cli.impl.CommandContextImpl.disconnectController(CommandContextImpl.java:1181)
> at org.jboss.as.cli.impl.CommandContextImpl.terminateSession(CommandContextImpl.java:812)
> at org.jboss.as.cli.impl.CommandContextImpl$1.shutdown(CommandContextImpl.java:370)
> at org.jboss.as.cli.impl.CliShutdownHook$1.run(CliShutdownHook.java:50)
> at java.lang.Thread.run(Thread.java:745)
> 13:25:30,215 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.CR1) stopped in 11ms
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-4842) A resource packaged in a RAR file fails to call a native library packaged in the same RAR.
by Syed Mahdi (JIRA)
[ https://issues.jboss.org/browse/WFLY-4842?page=com.atlassian.jira.plugin.... ]
Syed Mahdi edited comment on WFLY-4842 at 10/26/15 7:55 PM:
------------------------------------------------------------
Hello David,
does this seem like a similar issue:
http://stackoverflow.com/questions/33250140/wildfly-class-loading-issue-w...
The only difference is that the Jira issue related to the library inside the RAR not able to be read within from RAR while my issue is an external EAR with an embedded EJB Jar that refrences the jar inside the RAR. and it cannot get the class inside the Jar inside the RAR.
It seems different but i am thinking if the root cause is the same for both.
Thanks
Syed
was (Author: armahdi):
Hello David,
does this seem like a similar issue:
http://stackoverflow.com/questions/33250140/wildfly-class-loading-issue-w...
The only difference is that the Jira issue related to the library inside the RAR while my issue is an external EAR where an embedded EJB Jar refrences the jar inside the RAR.
It seems different but i am thinking if the root cause is the same for both.
Thanks
Syed
> A resource packaged in a RAR file fails to call a native library packaged in the same RAR.
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-4842
> URL: https://issues.jboss.org/browse/WFLY-4842
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 8.2.0.Final, 9.0.0.CR2
> Environment: Windows 7, 64-bit
> Reporter: Alex Lashchuk
> Assignee: David Lloyd
>
> JSR322, section 20.2.0.2, specifies that native libraries, packaged at an arbitrary location in a resource adapter's RAR file, will be made available to resource adapter's managed code. In fact, section 20.2.0.1 requires that the platform-specific libraries be packaged with the resource adapter module instead of being placed on java.library.path. However, attempting to access a native library included in a RAR from resource adapter code on WildFly results in an UnsatisfiedLinkError.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-4842) A resource packaged in a RAR file fails to call a native library packaged in the same RAR.
by Syed Mahdi (JIRA)
[ https://issues.jboss.org/browse/WFLY-4842?page=com.atlassian.jira.plugin.... ]
Syed Mahdi commented on WFLY-4842:
----------------------------------
Hello David,
does this seem like a similar issue:
http://stackoverflow.com/questions/33250140/wildfly-class-loading-issue-w...
The only difference is that the Jira issue related to the library inside the RAR while my issue is an external EAR where an embedded EJB Jar refrences the jar inside the RAR.
It seems different but i am thinking if the root cause is the same for both.
Thanks
Syed
> A resource packaged in a RAR file fails to call a native library packaged in the same RAR.
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-4842
> URL: https://issues.jboss.org/browse/WFLY-4842
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 8.2.0.Final, 9.0.0.CR2
> Environment: Windows 7, 64-bit
> Reporter: Alex Lashchuk
> Assignee: David Lloyd
>
> JSR322, section 20.2.0.2, specifies that native libraries, packaged at an arbitrary location in a resource adapter's RAR file, will be made available to resource adapter's managed code. In fact, section 20.2.0.1 requires that the platform-specific libraries be packaged with the resource adapter module instead of being placed on java.library.path. However, attempting to access a native library included in a RAR from resource adapter code on WildFly results in an UnsatisfiedLinkError.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-601) Boot sometimes fails on restart when deployments are present in the deployments directory and the deployment scanner is in use
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-601?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-601:
-----------------------------------------
Perhaps there is both a wildfly-ee7.war.dodeploy and a wildfly-ee7.war.failed in the deployments dir, and it's trying to deploy it twice? The WFLYDS0015 message in the log indicates it found the .failed file, and the WFLYCTL0212 indicates two ops trying to add the deployment.
> Boot sometimes fails on restart when deployments are present in the deployments directory and the deployment scanner is in use
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-601
> URL: https://issues.jboss.org/browse/WFCORE-601
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
>
> I observed this today, looks to be some kind of race in the deployment scanner on boot
> {code}
> 21:52:08,618 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.1.Final
> 21:52:10,370 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final
> 21:52:10,440 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) starting
> 21:52:11,390 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 20) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version!
> 21:52:11,409 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment mysql-ds.xml
> 21:52:11,413 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment wildfly-ee7.war
> 21:52:11,488 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 3) WFLYDR0001: Content added at location /Users/stuart/workspace/wildfly/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/48/032d14f289775249a004205c059588ab0f44d4/content
> 21:52:11,504 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 3) WFLYDR0001: Content added at location /Users/stuart/workspace/wildfly/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/c6/7babde4791697ddc6509fbd43ba1ec25952d47/content
> 21:52:11,506 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 3) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "wildfly-ee7.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"wildfly-ee7.war\")]"
> 21:52:11,509 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem deployment-scanner boot operations"
> 21:52:11,512 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem deployment-scanner boot operations\""
> 21:52:11,514 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 21:52:11,514 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5584) Remove and deprecate profile concept for data-sources
by James Perkins (JIRA)
James Perkins created WFLY-5584:
-----------------------------------
Summary: Remove and deprecate profile concept for data-sources
Key: WFLY-5584
URL: https://issues.jboss.org/browse/WFLY-5584
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: James Perkins
Assignee: James Perkins
Priority: Blocker
Fix For: 10.0.0.Final
The datasource subsystem was given the concept of domain profiles in WFLY-3634. This doesn't appear to have been fully implemented as {{*-ds.xml}} deployments in domain mode don't work. During the deploy process the profile is passed as {{null}} which results in the profile named {{default}} being used. Essentially this means that {{*-ds.xml}} domain deployments would only ever work on a profile named {{default}}.
While debugging the issue it doesn't seem as if the profile concept is even needed for data sources. The subsystem is only registered on servers and a server shouldn't need to know about profiles.
In short the profile concept needs to be removed and the {{profile}} attribute on the result of the {{installed-drivers-list}} operation as well as the {{installed-drivers}} complex attribute needs to be deprecated. The attribute was added for the web console and per https://developer.jboss.org/message/941413#941413 it is not used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5584) Remove and deprecate profile concept for data-sources
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-5584?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-5584:
--------------------------------
Description:
The datasource subsystem was given the concept of domain profiles in WFLY-3634. This doesn't appear to have been fully implemented as {{-ds.xml}} deployments in domain mode don't work. During the deploy process the profile is passed as {{null}} which results in the profile named {{default}} being used. Essentially this means that {{-ds.xml}} domain deployments would only ever work on a profile named {{default}}.
While debugging the issue it doesn't seem as if the profile concept is even needed for data sources. The subsystem is only registered on servers and a server shouldn't need to know about profiles.
In short the profile concept needs to be removed and the {{profile}} attribute on the result of the {{installed-drivers-list}} operation as well as the {{installed-drivers}} complex attribute needs to be deprecated. The attribute was added for the web console and per https://developer.jboss.org/message/941413#941413 it is not used.
was:
The datasource subsystem was given the concept of domain profiles in WFLY-3634. This doesn't appear to have been fully implemented as {{*-ds.xml}} deployments in domain mode don't work. During the deploy process the profile is passed as {{null}} which results in the profile named {{default}} being used. Essentially this means that {{*-ds.xml}} domain deployments would only ever work on a profile named {{default}}.
While debugging the issue it doesn't seem as if the profile concept is even needed for data sources. The subsystem is only registered on servers and a server shouldn't need to know about profiles.
In short the profile concept needs to be removed and the {{profile}} attribute on the result of the {{installed-drivers-list}} operation as well as the {{installed-drivers}} complex attribute needs to be deprecated. The attribute was added for the web console and per https://developer.jboss.org/message/941413#941413 it is not used.
> Remove and deprecate profile concept for data-sources
> -----------------------------------------------------
>
> Key: WFLY-5584
> URL: https://issues.jboss.org/browse/WFLY-5584
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Blocker
> Fix For: 10.0.0.Final
>
>
> The datasource subsystem was given the concept of domain profiles in WFLY-3634. This doesn't appear to have been fully implemented as {{-ds.xml}} deployments in domain mode don't work. During the deploy process the profile is passed as {{null}} which results in the profile named {{default}} being used. Essentially this means that {{-ds.xml}} domain deployments would only ever work on a profile named {{default}}.
> While debugging the issue it doesn't seem as if the profile concept is even needed for data sources. The subsystem is only registered on servers and a server shouldn't need to know about profiles.
> In short the profile concept needs to be removed and the {{profile}} attribute on the result of the {{installed-drivers-list}} operation as well as the {{installed-drivers}} complex attribute needs to be deprecated. The attribute was added for the web console and per https://developer.jboss.org/message/941413#941413 it is not used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months