[JBoss JIRA] (WFLY-6954) Binding Wildfly's management interface to IP address fails
by Eduard Dedu (JIRA)
Eduard Dedu created WFLY-6954:
---------------------------------
Summary: Binding Wildfly's management interface to IP address fails
Key: WFLY-6954
URL: https://issues.jboss.org/browse/WFLY-6954
Project: WildFly
Issue Type: Bug
Reporter: Eduard Dedu
Assignee: Jason Greene
Attachments: Screen Shot 2016-08-15 at 12.34.42.png
Binding management interface to a remote IPV4 address causes the server to start with errors :
Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: WFLYSRV0082: failed to resolve interface management
The error occurs if the server is started with the -b switch:
./standalone.sh -bmanagement=my_IPV4_address
... or if I edit the configuration standalone.xml:
<interface name="management">
<inet-address value="${jboss.bind.address.management:my_IPV4_address}"/>
</interface>
The remote host located at the IPV4 address is up and running and responds to PING signals.
TCP is enabled on port 9990.
Wildfly starts w/o errors if I enable remote access from any host:
./standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 &
Perhaps I'm missing something, but this behaviour looks like a bug in a core WF feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-761) Not possible to overlay non existing file in WAR
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-761?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-761:
------------------------------------------------
Matej Novotny <manovotn(a)redhat.com> changed the Status of [bug 1287732|https://bugzilla.redhat.com/show_bug.cgi?id=1287732] from ON_QA to VERIFIED
> Not possible to overlay non existing file in WAR
> ------------------------------------------------
>
> Key: WFCORE-761
> URL: https://issues.jboss.org/browse/WFCORE-761
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Bartosz Baranowski
> Assignee: Lin Gao
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 3.0.0.Alpha5
>
>
> It is either bug in how deployments are treated or how overlay/vfs work.
> Steps to reproduce:
> 1. deploy undexploded war with jar inside
> 2. add overlay that will add non existing file in jar
> Result: exception:
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt
> Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}}
> at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
> at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
> at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76)
> at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67)
> Expectation:
> should work. It actually does work, if war is really exploded or
> 'if(exploded)' part in overlay is removed from overlay processor and everything is handled via: https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1714) Tab completion doesn't offer more options once prefix match some value
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1714?page=com.atlassian.jira.plugi... ]
Petr Kremensky moved JBEAP-5625 to WFCORE-1714:
-----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1714 (was: JBEAP-5625)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Affects Version/s: 3.0.0.Alpha5
(was: 7.1.0.DR2)
> Tab completion doesn't offer more options once prefix match some value
> ----------------------------------------------------------------------
>
> Key: WFCORE-1714
> URL: https://issues.jboss.org/browse/WFCORE-1714
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha5
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
>
> Tab completion for CLI variables doesn't offer more values once the variable to be completed match some value.
> *reproduce*
> {noformat}
> set foo=/subsystem=logging
> set foobar=/subsystem=logging/console-handler=CONSOLE
> {noformat}
> *actual*
> {noformat}
> $foo<TAB>
> / :
> {noformat}
> *expected*
> {noformat}
> $foo<TAB>
> / : foo foobar
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1253) configure DSL files adding order in kie-maven-plugin
by Toshiya Kobayashi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1253?page=com.atlassian.jira.plugi... ]
Toshiya Kobayashi updated DROOLS-1253:
--------------------------------------
Description:
When we use DSL, we need to follow "the most specific sentences must be up in the order" principal. If we use multiple DSL files, adding order matters.
But in case of kie-maven-plugin,
https://github.com/droolsjbpm/drools/blob/master/drools-compiler/src/main...
{code:java}
for (Asset asset : assets) {
asset.kmodule.addResourceToCompiler(ckbuilder, kBaseModel, asset.name);
}
{code}
the order is decided by HashSet iterator hence it's beyond control.
So this feature request is a capability to configure the DSL files adding order for kie-maven-plugin. For example, listing up all DLS file names in pom.xml to specify the adding order.
was:
When we use DSL, we need to follow "the most specific sentences must be up in the order" principal. If we use multiple DSL files, adding order matters.
But in case of kie-maven-plugin,
https://github.com/droolsjbpm/drools/blob/master/drools-compiler/src/main...
{code:java}
for (Asset asset : assets) {
asset.kmodule.addResourceToCompiler(ckbuilder, kBaseModel, asset.name);
}
{code}
the order is decided by HashSet iterator hence it's beyond control.
So this feature request is a capability to configure the DSL files adding order for kie-maven-plugin. For example, listing up all DLS file names in pom.xml.
> configure DSL files adding order in kie-maven-plugin
> ----------------------------------------------------
>
> Key: DROOLS-1253
> URL: https://issues.jboss.org/browse/DROOLS-1253
> Project: Drools
> Issue Type: Feature Request
> Components: integration
> Affects Versions: 7.0.0.Beta1
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
>
> When we use DSL, we need to follow "the most specific sentences must be up in the order" principal. If we use multiple DSL files, adding order matters.
> But in case of kie-maven-plugin,
> https://github.com/droolsjbpm/drools/blob/master/drools-compiler/src/main...
> {code:java}
> for (Asset asset : assets) {
> asset.kmodule.addResourceToCompiler(ckbuilder, kBaseModel, asset.name);
> }
> {code}
> the order is decided by HashSet iterator hence it's beyond control.
> So this feature request is a capability to configure the DSL files adding order for kie-maven-plugin. For example, listing up all DLS file names in pom.xml to specify the adding order.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1253) configure DSL files adding order in kie-maven-plugin
by Toshiya Kobayashi (JIRA)
Toshiya Kobayashi created DROOLS-1253:
-----------------------------------------
Summary: configure DSL files adding order in kie-maven-plugin
Key: DROOLS-1253
URL: https://issues.jboss.org/browse/DROOLS-1253
Project: Drools
Issue Type: Feature Request
Components: integration
Affects Versions: 7.0.0.Beta1
Reporter: Toshiya Kobayashi
Assignee: Mario Fusco
When we use DSL, we need to follow "the most specific sentences must be up in the order" principal. If we use multiple DSL files, adding order matters.
But in case of kie-maven-plugin,
https://github.com/droolsjbpm/drools/blob/master/drools-compiler/src/main...
{code:java}
for (Asset asset : assets) {
asset.kmodule.addResourceToCompiler(ckbuilder, kBaseModel, asset.name);
}
{code}
the order is decided by HashSet iterator hence it's beyond control.
So this feature request is a capability to configure the DSL files adding order for kie-maven-plugin. For example, listing up all DLS file names in pom.xml.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-6953) Wildfly 10.1.0.CR1 does not start as a windows service
by Anton Yudin (JIRA)
Anton Yudin created WFLY-6953:
---------------------------------
Summary: Wildfly 10.1.0.CR1 does not start as a windows service
Key: WFLY-6953
URL: https://issues.jboss.org/browse/WFLY-6953
Project: WildFly
Issue Type: Bug
Affects Versions: 10.1.0.CR1
Environment: Windows 8/Windows Server 2012
Oracle Java 8
Reporter: Anton Yudin
Assignee: Jason Greene
Wildfly fails to start as a windows service.
Installation works fine:
bq. .\service.bat install
bq. Using the X86-64bit version of prunsrv
bq.
bq. "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfl
bq. y --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --Lo
bq. gPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOu
bq. tput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPat
bq. h="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standal
bq. one.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--serve
bq. r-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wi
bq. ldfly-10.1.0.CR1-test\bin" ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --c
bq. onnect --command=:shutdown"
bq. Service Wildfly installed
bq.
Windows reports this error:
{{Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1.
}}
Event log report:
The Wildfly service terminated with the following service-specific error:
Incorrect function.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7024</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z" />
<EventRecordID>196500</EventRecordID>
<Correlation />
<Execution ProcessID="668" ThreadID="10184" />
<Channel>System</Channel>
<Computer>ITPC7.intra.rfgh.net</Computer>
<Security />
</System>
- <EventData>
<Data Name="param1">Wildfly</Data>
<Data Name="param2">%%1</Data>
<Binary>570069006C00640066006C0079000000</Binary>
</EventData>
</Event>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months