March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6409) Update default domain configuration to use http-remoting

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6409?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved WFCORE-1443 to WFLY-6409: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-6409 (was: WFCORE-1443) Component/s: Domain Management (was: Domain Management) Affects Version/s: (was: 2.0.3.Final) Fix Version/s: 11.0.0.Alpha1 (was: 3.0.0.Alpha1) > Update default domain configuration to use http-remoting > -------------------------------------------------------- > > Key: WFLY-6409 > URL: https://issues.jboss.org/browse/WFLY-6409 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > Our default domain configuration still use the native remote protocol on port 9999 for DC-HC communication. Update those files so that we use http-remoting on port 9990. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1443) Update default domain configuration to use http-remoting

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1443: ---------------------------------------- Summary: Update default domain configuration to use http-remoting Key: WFCORE-1443 URL: https://issues.jboss.org/browse/WFCORE-1443 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 2.0.3.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Priority: Minor Fix For: 3.0.0.Alpha1 Our default domain configuration still use the native remote protocol on port 9999 for DC-HC communication. Update those files so that we use http-remoting on port 9990. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1443) Update default domain configuration to use http-remoting

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1443?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1443: ------------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/1282) > Update default domain configuration to use http-remoting > -------------------------------------------------------- > > Key: WFCORE-1443 > URL: https://issues.jboss.org/browse/WFCORE-1443 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 2.0.3.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Minor > Fix For: 3.0.0.Alpha1 > > > Our default domain configuration still use the native remote protocol on port 9999 for DC-HC communication. Update those files so that we use http-remoting on port 9990. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2033) Replace Java serialization with JGroups marshalling

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2033?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2033: -------------------------------- Replaced all occurrences of {{Message.getObject()}} in: * NAKACK2 * UNICAST3 * FlowControl * Locking Skipped {{Executing}} as this will probably get removed in 4.0 anyway. > Replace Java serialization with JGroups marshalling > --------------------------------------------------- > > Key: JGRP-2033 > URL: https://issues.jboss.org/browse/JGRP-2033 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.9, 4.0 > > > In some cases, even JGroups internal code still uses Java serialization. Replace this with marshalling (using {{Streamable}}) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1099) Couldn't access any web service of drools or kie which run in docker container

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1099?page=com.atlassian.jira.plugi... ] Petr Široký commented on DROOLS-1099: ------------------------------------- I've just tried {{docker run -p 8080:8080 -p 8001:8001 -d --name drools-workbench jboss/drools-workbench:6.3.0.Final}} and it works as expected. I can see the login page at {{http://localhost:8080/drools-wb}}. It takes a while for the application to start up though. Could it be that it just was not yet deployed when you were accessing the page? If that is not the case, could you post the output of {{docker logs drools-workbench}} (preferably as attachment)? > Couldn't access any web service of drools or kie which run in docker container > ------------------------------------------------------------------------------ > > Key: DROOLS-1099 > URL: https://issues.jboss.org/browse/DROOLS-1099 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 6.2.0.Final, 6.4.0.CR1 > Environment: Ubuntu 15.04, Docker 1.10.3 > Reporter: Jackey Lee > Assignee: Mario Fusco > > I followed the instructions to run drools and KIE workbenches in docker. But the browser shows "404-Not Found" when I tried to access http://localhost:8080/drools-wb. > It shows "Forbidden" when I tried to access http://localhost:32769/kie-server -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2033) Replace Java serialization with JGroups marshalling

by Bela Ban (JIRA)

Bela Ban created JGRP-2033: ------------------------------ Summary: Replace Java serialization with JGroups marshalling Key: JGRP-2033 URL: https://issues.jboss.org/browse/JGRP-2033 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.6.9, 4.0 In some cases, even JGroups internal code still uses Java serialization. Replace this with marshalling (using {{Streamable}}) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1099) Couldn't access any web service of drools or kie which run in docker container

by Jackey Lee (JIRA)

Jackey Lee created DROOLS-1099: ---------------------------------- Summary: Couldn't access any web service of drools or kie which run in docker container Key: DROOLS-1099 URL: https://issues.jboss.org/browse/DROOLS-1099 Project: Drools Issue Type: Bug Components: tools Affects Versions: 6.4.0.CR1, 6.2.0.Final Environment: Ubuntu 15.04, Docker 1.10.3 Reporter: Jackey Lee Assignee: Mario Fusco I followed the instructions to run drools and KIE workbenches in docker. But the browser shows "404-Not Found" when I tried to access http://localhost:8080/drools-wb. It shows "Forbidden" when I tried to access http://localhost:32769/kie-server -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1201) Could not upload new deployment

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1201?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1201: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > Could not upload new deployment > ------------------------------- > > Key: WFCORE-1201 > URL: https://issues.jboss.org/browse/WFCORE-1201 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.2.Final > Environment: 2 different machines > Linux Debian Squeeze & Jessie > Oracle Java SE 8 > Reporter: Claudio Weiler > Assignee: Harald Pehl > Fix For: 2.1.0.Final > > > WildFly stop to accept deployments via interface upload with following stacktrace: > ERROR [io.undertow.request] (XNIO-1 task-2) Undertow request failed HttpServerExchange{ POST /management-upload}: java.io.IOException: UT000036: Connection terminated parsing multipart data > at io.undertow.server.handlers.form.MultiPartParserDefinition$MultiPartUploadHandler.parseBlocking(MultiPartParserDefinition.java:203) > at org.jboss.as.domain.http.server.DomainApiGenericOperationHandler.handleRequest(DomainApiGenericOperationHandler.java:104) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:87) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Same artifact was used before with success, nothing changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1320) Dead local store - ManagementHttpServer

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1320?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1320: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > Dead local store - ManagementHttpServer > --------------------------------------- > > Key: WFCORE-1320 > URL: https://issues.jboss.org/browse/WFCORE-1320 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Rostislav Svoboda > Assignee: Tomaz Cerar > Fix For: 2.1.0.Final > > > https://github.com/wildfly/wildfly-core/blame/master/domain-http/interfac... > Lines 130 - 136 seem not need, originally came from https://github.com/wildfly/wildfly-core/commit/c5cab49048c1509f7773fc88f8... > But probably forgotten after some refactoring -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1436) Undertow 1.3.19.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1436?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1436: ------------------------------------- Fix Version/s: 2.1.0.Final (was: 2.1.0.CR2) > Undertow 1.3.19.Final > --------------------- > > Key: WFCORE-1436 > URL: https://issues.jboss.org/browse/WFCORE-1436 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2016