[JBoss JIRA] (WFLY-5442) stop-embedded-host-controller command is not available in non-modular environment
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-5442?page=com.atlassian.jira.plugin.... ]
Petr Kremensky updated WFLY-5442:
---------------------------------
Description:
stop-embedded-host-controller command for stopping the embed host controller instance is not available once the CLI is running in non-modular environment.
{noformat}
[pkremens@dhcp-10-40-5-17 client] $ java -jar jboss-cli-client.jar
WARN: can't find jboss-cli.xml. Using default configuration values.
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] embed-host-controller --jboss-home=~/workspace/jboss-eap-7.0/
Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
[domain@embedded /] stop-embedded-host-controller
The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable).
# only stop-embedded-server is available
[domain@embedded /] s
set stop-embedded-server
# stop-embedded-host-controller command should be used for this
[domain@embedded /] stop-embedded-server
[disconnected /]
{noformat}
was:
stop-embedded-host-controller command for stopping the embed host controller instance is not available once the CLI is running in non-modular environment.
{noformat}
[pkremens@dhcp-10-40-5-17 client] $ java -jar jboss-cli-client.jar
WARN: can't find jboss-cli.xml. Using default configuration values.
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] embed-host-controller --jboss-home=~/workspace/jboss-eap-7.0/
Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
# only stop-embedded-server is available
[domain@embedded /] s
set stop-embedded-server
# stop-embedded-host-controller command should be used for this
[domain@embedded /] stop-embedded-server
[disconnected /]
{noformat}
> stop-embedded-host-controller command is not available in non-modular environment
> ---------------------------------------------------------------------------------
>
> Key: WFLY-5442
> URL: https://issues.jboss.org/browse/WFLY-5442
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.CR2
> Reporter: Petr Kremensky
> Assignee: Ken Wills
>
> stop-embedded-host-controller command for stopping the embed host controller instance is not available once the CLI is running in non-modular environment.
> {noformat}
> [pkremens@dhcp-10-40-5-17 client] $ java -jar jboss-cli-client.jar
> WARN: can't find jboss-cli.xml. Using default configuration values.
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-host-controller --jboss-home=~/workspace/jboss-eap-7.0/
> Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
> [domain@embedded /] stop-embedded-host-controller
> The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable).
> # only stop-embedded-server is available
> [domain@embedded /] s
> set stop-embedded-server
> # stop-embedded-host-controller command should be used for this
> [domain@embedded /] stop-embedded-server
> [disconnected /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5442) stop-embedded-host-controller command is not available in non-modular environment
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-5442?page=com.atlassian.jira.plugin.... ]
Petr Kremensky moved JBEAP-1199 to WFLY-5442:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-5442 (was: JBEAP-1199)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
(was: CLI)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 10.0.0.CR2
(was: 7.0.0.DR11 (Alpha))
> stop-embedded-host-controller command is not available in non-modular environment
> ---------------------------------------------------------------------------------
>
> Key: WFLY-5442
> URL: https://issues.jboss.org/browse/WFLY-5442
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.CR2
> Reporter: Petr Kremensky
> Assignee: Ken Wills
>
> stop-embedded-host-controller command for stopping the embed host controller instance is not available once the CLI is running in non-modular environment.
> {noformat}
> [pkremens@dhcp-10-40-5-17 client] $ java -jar jboss-cli-client.jar
> WARN: can't find jboss-cli.xml. Using default configuration values.
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-host-controller --jboss-home=~/workspace/jboss-eap-7.0/
> Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
> # only stop-embedded-server is available
> [domain@embedded /] s
> set stop-embedded-server
> # stop-embedded-host-controller command should be used for this
> [domain@embedded /] stop-embedded-server
> [disconnected /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5441) Received unsolicited state from node X for segment Y of cache Z
by Richard Janík (JIRA)
[ https://issues.jboss.org/browse/WFLY-5441?page=com.atlassian.jira.plugin.... ]
Richard Janík updated WFLY-5441:
--------------------------------
Priority: Minor (was: Major)
> Received unsolicited state from node X for segment Y of cache Z
> ---------------------------------------------------------------
>
> Key: WFLY-5441
> URL: https://issues.jboss.org/browse/WFLY-5441
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Richard Janík
> Assignee: Paul Ferraro
> Priority: Minor
>
> Hi,
> we're occasionally seeing these warnings in the server logs:
> {code}
> [JBossINF] [0m[33m08:20:45,364 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t36) Received unsolicited state from node perf20 for segment 48 of cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar
> ...
> [JBossINF] [0m[33m08:21:02,793 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t22) Discarding received cache entries for segment 48 of cache dist because they do not belong to this node.
> {code}
> The warnings seem to be harmless.
> This is the equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=923789 which has been (with EAP6) followed by IllegalStateExceptions and has later been closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=922699. However, no IllegalStateExceptions occur with EAP7 and thus these two messages seem to be unrelated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5441) Received unsolicited state from node X for segment Y of cache Z
by Richard Janík (JIRA)
Richard Janík created WFLY-5441:
-----------------------------------
Summary: Received unsolicited state from node X for segment Y of cache Z
Key: WFLY-5441
URL: https://issues.jboss.org/browse/WFLY-5441
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Richard Janík
Assignee: Paul Ferraro
Hi,
we're occasionally seeing these warnings in the server logs:
{code}
[JBossINF] [0m[33m08:20:45,364 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t36) Received unsolicited state from node perf20 for segment 48 of cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar
...
[JBossINF] [0m[33m08:21:02,793 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t22) Discarding received cache entries for segment 48 of cache dist because they do not belong to this node.
{code}
The warnings seem to be harmless.
This is the equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=923789 which has been (with EAP6) followed by IllegalStateExceptions and has later been closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=922699. However, no IllegalStateExceptions occur with EAP7 and thus these two messages seem to be unrelated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5432) Wildfly SOAP webservice causes JVM crash
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-5432?page=com.atlassian.jira.plugin.... ]
Alessio Soldano commented on WFLY-5432:
---------------------------------------
To be honest, I've been thinking hardware was to be blamed too, just wanted to be sure I'm running the same test you are.
If you can try running on a different host, please let us know the findings.
> Wildfly SOAP webservice causes JVM crash
> ----------------------------------------
>
> Key: WFLY-5432
> URL: https://issues.jboss.org/browse/WFLY-5432
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 9.0.1.Final, 10.0.0.CR2
> Environment: Tested on Mac OSX 10.10.2, jdk 1.8.60, wildfly 9.0.1. Final / 10.cr2
> Also tested on Centos 6.5, jdk 1.7.51, wildfly 9.0.1. Final
> Reporter: Davide Marchetti
> Assignee: Alessio Soldano
> Priority: Blocker
> Labels: crash, jvm, soap, webservice
> Attachments: SOAPTest.war
>
>
> The JVM crashes with either a sigsegv or sigbus error when performing a SOAP load test.
> The error printed is:
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f5da922afb8, pid=75645, tid=140039627204352
> #
> # JRE version: OpenJDK Runtime Environment (7.0_51-b02) (build 1.7.0_51-mockbuild_2014_01_15_01_39-b00)
> # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # J org.apache.cxf.message.ExchangeImpl.get(Ljava/lang/Class;)Ljava/lang/Object;
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
>
> #
> # If you would like to submit a bug report, please include
> # instructions on how to reproduce the bug and visit:
> # 15:56:03,314 INFO [stdout] (default task-17) Submitted order request received with transId: <XXXXX>, opId: <SCO>, ...
> http://icedtea.classpath.org/bugzilla
> #
> The webservice does nothing, just a System.out.print("xxxxx").
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (DROOLS-934) Persistence unit tests - DB2 default schema not specified
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-934:
------------------------------------
Summary: Persistence unit tests - DB2 default schema not specified
Key: DROOLS-934
URL: https://issues.jboss.org/browse/DROOLS-934
Project: Drools
Issue Type: Bug
Reporter: Tibor Zimányi
Assignee: Mark Proctor
Priority: Minor
Unit tests in drools-persistence-jpa don't work on DB2 database system because there isn't specified DB schema in tests.
Things needed to be done:
- hibernate.default_schema property set in persistence.xml
- schema should be set in PersistenceUtil, when creating data source
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5440) undertow http misconfiguration is not correctly reported
by Ochieng Marembo (JIRA)
Ochieng Marembo created WFLY-5440:
-------------------------------------
Summary: undertow http misconfiguration is not correctly reported
Key: WFLY-5440
URL: https://issues.jboss.org/browse/WFLY-5440
Project: WildFly
Issue Type: Feature Request
Components: EJB, JMS, JMX, Remoting, Web (Undertow)
Affects Versions: 9.0.1.Final
Environment: - wildfly 9.0.1.Final
- oracle jdk8_u45
Reporter: Ochieng Marembo
Assignee: Jeff Mesnil
Priority: Minor
With a misconfigured http-listener, wildfly boot-up reports unrelated problem:
{noformat}
<http-listener name="non-default-listener" socket-binding="http" redirect-socket="https"/>
{noformat}
The following boot-up process does not reveal the underlying undertow issue of no 'default' http-listener:
{code:java}
11:06:43,307 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jsr77")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.jsr77.ejb"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
]
}}
11:06:43,315 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging"),
("hornetq-server" => "default")
]) - failure description: {
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.http-upgrade-registry.default]"],
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.messaging.default.jms.manager"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
]
}
}
11:06:43,317 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.ejb.default-local-ejb-receiver-service",
"jboss.ejb3.ejbClientContext.default",
"jboss.ejb3.localEjbReceiver.value"
],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
]
}}
11:06:43,318 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months