[JBoss JIRA] (WFLY-8314) WFLY starts with errors and missing services for standalone xmls under examples directory
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-8314?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka edited comment on WFLY-8314 at 3/8/17 4:18 AM:
---------------------------------------------------------------
the trouble does not influence only the {{standalone-xts.xml}} but all these configs under examples directory
{code}
standalone-activemq-colocated.xml
standalone-genericjms.xml
standalone-jts.xml
standalone-rts.xml
standalone-xts.xml
{code}
was (Author: ochaloup):
the trouble does not influence only the {{standalone-xts.xml}} but all these configs under examples directory
{code}
standalone-activemq-colocated.xml
standalone-genericjms.xml
standalone-jts.xml
standalone-picketlink.xml
standalone-rts.xml
standalone-xts.xml
{code}
> WFLY starts with errors and missing services for standalone xmls under examples directory
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-8314
> URL: https://issues.jboss.org/browse/WFLY-8314
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Critical
>
> When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged:
> {code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("host" => "default-host"),
> ("setting" => "http-invoker")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"]
> }
> 09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker]
> 09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand)
> {code}
> This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8314) WFLY starts with errors and missing services for standalone xmls under examples directory
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-8314?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka commented on WFLY-8314:
---------------------------------------
the trouble does not influence only the {{standalone-xts.xml}} but all these configs under examples directory
{code}
standalone-activemq-colocated.xml
standalone-genericjms.xml
standalone-jts.xml
standalone-picketlink.xml
standalone-rts.xml
standalone-xts.xml
{code}
> WFLY starts with errors and missing services for standalone xmls under examples directory
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-8314
> URL: https://issues.jboss.org/browse/WFLY-8314
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Critical
>
> When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged:
> {code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("host" => "default-host"),
> ("setting" => "http-invoker")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"]
> }
> 09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker]
> 09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand)
> {code}
> This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8314) WFLY starts with errors and missing services for standalone xmls under examples directory
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-8314?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated WFLY-8314:
----------------------------------
Summary: WFLY starts with errors and missing services for standalone xmls under examples directory (was: WFLY starts with errors and missing services in standalone-xts and standalone-rts profile)
> WFLY starts with errors and missing services for standalone xmls under examples directory
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-8314
> URL: https://issues.jboss.org/browse/WFLY-8314
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Critical
>
> When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged:
> {code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("host" => "default-host"),
> ("setting" => "http-invoker")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"]
> }
> 09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker]
> 09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand)
> {code}
> This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8316) Mapping roles in legacy security domain is ignored when this domain is used as Elytron realm
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-8316?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-8316:
-------------------------------
Attachment: print-roles.war
> Mapping roles in legacy security domain is ignored when this domain is used as Elytron realm
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-8316
> URL: https://issues.jboss.org/browse/WFLY-8316
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
> Attachments: print-roles.war
>
>
> In case when legacy security domain is used as Elytron realm then roles assigned in mapping are unavailable in Elytron security realm.
> e.g. when UsersRoles login module, which assigns role JBossAdmin to user admin is used and then role User is assigned for user admin in SimpleRoles mapping module through:
> {code}
> <mapping>
> <mapping-module code="SimpleRoles" type="role">
> <module-option name="admin" value="User"/>
> </mapping-module>
> </mapping>
> {code}
> then only role JBossAdmin is available for Elytron. Following appears in server log:
> {code}
> Authorizing against the following attributes: [Roles, CallerPrincipal] => [JBossAdmin, admin]
> {code}
> In case when this legacy security domain is used directly as PicketBox security domain, then both roles, JBossAdmin and User, are assigned to user admin.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8316) Mapping roles in legacy security domain is ignored when this domain is used as Elytron realm
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-8316:
----------------------------------
Summary: Mapping roles in legacy security domain is ignored when this domain is used as Elytron realm
Key: WFLY-8316
URL: https://issues.jboss.org/browse/WFLY-8316
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Critical
In case when legacy security domain is used as Elytron realm then roles assigned in mapping are unavailable in Elytron security realm.
e.g. when UsersRoles login module, which assigns role JBossAdmin to user admin is used and then role User is assigned for user admin in SimpleRoles mapping module through:
{code}
<mapping>
<mapping-module code="SimpleRoles" type="role">
<module-option name="admin" value="User"/>
</mapping-module>
</mapping>
{code}
then only role JBossAdmin is available for Elytron. Following appears in server log:
{code}
Authorizing against the following attributes: [Roles, CallerPrincipal] => [JBossAdmin, admin]
{code}
In case when this legacy security domain is used directly as PicketBox security domain, then both roles, JBossAdmin and User, are assigned to user admin.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8306) Soap attachments are being truncated when moving from jboss 7 to wildfly9/10
by Einat Peretz (JIRA)
[ https://issues.jboss.org/browse/WFLY-8306?page=com.atlassian.jira.plugin.... ]
Einat Peretz commented on WFLY-8306:
------------------------------------
We use Axis2 messageReceivers with EJB, so the EJB method call is:
public DataHandler getPartsForPartsStatus(RequestDescriptor source, DataHandler attachment)
> Soap attachments are being truncated when moving from jboss 7 to wildfly9/10
> ----------------------------------------------------------------------------
>
> Key: WFLY-8306
> URL: https://issues.jboss.org/browse/WFLY-8306
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final
> Environment: Windows
> Reporter: Einat Peretz
> Assignee: Stuart Douglas
>
> Client access wildfly 9 or 10 web service (soap using Axis2) using https with zip attachment and the zip is received truncated on the server.
> The same deployed application with same client worked fine on Jboss 7.3.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8306) Soap attachments are being truncated when moving from jboss 7 to wildfly9/10
by Einat Peretz (JIRA)
[ https://issues.jboss.org/browse/WFLY-8306?page=com.atlassian.jira.plugin.... ]
Einat Peretz commented on WFLY-8306:
------------------------------------
Not big zip. There is no problem for zip sizes less than 891 bytes, more than 891 bytes and only 891 bytes are received.
This is the http coming from the client:
Host: localhost:8888
User-Agent: gSOAP/2.7
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 5674
Connection: keep-alive
Authorization: Basic dmFsb3I6dmFsb3J2cGw=
SOAPAction: "urn:getPartsForPartsStatus"
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:MentorApplicationsPartServices6="http://utils.services.domain.vpl.valor.com/xsd" xmlns:MentorApplicationsPartServices3="http://location.domain.vpl.valor.com/xsd" xmlns:MentorApplicationsPartServices2="http://utils.domain.vpl.valor.com/xsd" xmlns:MentorApplicationsPartServices5="http://exception.domain.vpl.valor.com/xsd" xmlns:MentorApplicationsPartServices4="http://config.domain.vpl.valor.com/xsd" xmlns:MentorApplicationsPartServices7="https://vplvalor.mentor.com/gateway2/services/MentorApplicationsPartServi..." xmlns:MentorApplicationsPartServices1="https://vplvalor.mentor.com/gateway2/services" xmlns:MentorApplicationsPartServices8="https://vplvalor.mentor.com/gateway2/services/MentorApplicationsPartServi..." xmlns:xop="http://www.w3.org/2004/08/xop/include"><SOAP-ENV:Body><MentorApplicationsPartServices1:getPartsForPartsStatus><MentorApplicationsPartServices1:param0><MentorApplicationsPartServices6:attachmentContentType>vNPI</MentorApplicationsPartServices6:attachmentContentType><MentorApplicationsPartServices6:binaryContentType>false</MentorApplicationsPartServices6:binaryContentType><MentorApplicationsPartServices6:clientDetails><MentorApplicationsPartServices4:build>AQAAAAEAAADASy85PjsXelbT/P7G++N0HLxem2xeQ9zso7w0/TurAd0DK9ahSEDLdtXwrQxknZVVD6FZPnsfduh/gJiHZNs/243f13AHbCTgEBb33LFPsQ==</MentorApplicationsPartServices4:build><MentorApplicationsPartServices4:transportVersion>AQAAAAEAAADASy85PjsXelbT/P7G++N0HLxem2xeQ9zso7w0/TurAbn+tE6Sx83y7Kh7PeibcAFrBt88j3UVYeJiF/vYsbGo</MentorApplicationsPartServices4:transportVersion><MentorApplicationsPartServices4:version>AQAAAAEAAADASy85PjsXelbT/P7G++N0HLxem2xeQ9zso7w0/TurAW2h2ghhjuSweQOktNKBPg5s6yo0BWcO91WQWCycJF1y</MentorApplicationsPartServices4:version><MentorApplicationsPartServices4:dongle>AQAAAAEAAADASy85PjsXelbT/P7G++N0HLxem2xeQ9zso7w0/TurAQfCb7GlzlBZ/7S3+GS1ybDdYtauFt3rZdxlMhdOCrXS</MentorApplicationsPartServices4:dongle></MentorApplicationsPartServices6:clientDetails><MentorApplicationsPartServices6:domainType>vNPI</MentorApplicationsPartServices6:domainType><MentorApplicationsPartServices6:initiator>vNPI</MentorApplicationsPartServices6:initiator><MentorApplicationsPartServices6:tXPDomain>true</MentorApplicationsPartServices6:tXPDomain><MentorApplicationsPartServices6:vPLDomain>false</MentorApplicationsPartServices6:vPLDomain><MentorApplicationsPartServices6:xStreamContentType>true</MentorApplicationsPartServices6:xStreamContentType></MentorApplicationsPartServices1:param0><MentorApplicationsPartServices1:param1>H4sIAAAAAAAAAO3dbW/ixhoG4L9irVSp1alhXjy2kSiSMebNGKhxWMg3TuJW6CQQYbpS/31nTHY3TttztjCPdD7c0ioiJBj20mgy88w9nu7D8bn1afd0PLU+vTy1Ho/Pu/2hVZWnT/uHstIPqmp/PLSWu1/LvKxejoeq7HVPr4+Sw3l/3peV8/C0q6qfPvzltX4775+q1svudNZXOZ1X5935t8rdnU673z/0ut/+kl73+eXQi3Puu5wx6Q7Tbts8031+OD6WvWg11d/XD7tPx4fdWX/sXnf/2JPdtv769bm1ebdu++vvPJbVw2n/8vWHzno5c1aaoNS/9/anb19VvX4ofW1+eYfD7ll/jOUyX6yTQbddf1tf/M2T9bfd9ucX/1tf7z/l4/B4ysvn47m8e3ncncveL7unquy2/+an3fY/QbsBePY/gZ1T+Ut5Kg8P5U8fWq22/vftb/fF8kP7s+ZNl7tcwlzs/1BVSCEC5vka1muyLsfbeJEtQXstbRbnTCb3y6FptA3afDHO4Hp9RxB/ZD6TjnZNh2kSNWzXk9U42kL3Wl0ju40589KoEE3aaL2B69Wt1sDWrl4exQ3XNMmSArLXyo7yjIdhHvBLq2V80NDN7vKoiMB79QhByNAJQt/hyvc6GCJYtw39QNtyBlvLw68xDy89borRl11WFemx1wCsFocHM876pq0uwvl83hwfrKJsdTcfAfcWXN0RsLgPXLK6DP+WwhdU/7kqql1WJ7dK9wSynty244wztQly84Ria0x2bU92NSsmuzST3XHdijHZJSuHC5TDycrhHDMH2zMHmWJwS7fWwFPGsNRANMZlGOPaHuNGnPEhFnBIlh29NHD+1BcM8mi2yCcxfG+dMwjMGWzLcsH82AvUvbeO4iBkDLpWdevqYpB1lmi3tue6Sum5boK5LlkpQcWmlKAHC+CliiVIidZLWggT4CXglTwbKl6PGzTvDLyWeUWS+2xqBg6JYOC1zduJFyPzh00xd1lA12aFwWNC1ItmYV+wZr+LMvnNkTAhgpDzThgIyFoP26lLkFFI2JKFRGFLtSbJsSZJRdsBLQmtF2AlnYjWD9EhUIQUHJNSMMs8SCmQpD8YXClcc7gSuPrvl8vgeovra1pJIK1Egiv50NRrF0ONmwDXMq6ITLX25zVwbeNOs1QK1a+r4ZnbLNcWW3c7mMP26ob75n4JOUKMVLp6oABdsvytHt0C1zZubFZy0nwT5GHfRMgbuttolCyAe33L5b5rss332BVpF9XszUFi3OZ6br0rUkqBW/7YdQ2ZUriVknVXE7jdDoTw4Wq3d60T+KYfQAKfQtYLZCoha1lWd7J1H4s2SxSwTUy7RcCWincsBPLLhLz1uBa81nkF71/S9/U9F5Fftsxbx8N5rEe5iIcTxr4kAjQktFIim0RF2xFotSS0HcGYD1mCHM14itgXSTxJ97NwpXDtCNykynLsy8zEEPsiSiaZcvhiimSSdVw9NKjvEVpPxQp31cwm1TfBBu1VtMlr6MvAIvRFFEvS4657pGYoZPXQC4EvOt1OKqBLFqdLEacjCScJwQSySQSlWoVSLRGtwL5yQlq0WiJaAVoiWo+JELQEtH6Ae3jQlWzF+zsmoWR7oysPteuUY2O53Xoi9zcqN6eV+mmBaqL1ygEXAeoydLoKpQM6XRGmAXSJdAX2P1Piol+gwxUpbIlsvZxhocE2bh6breXD3GVBfduJ5pwXW8tvxDUHukwvuKC12im8btTjUzXCdjK75QSHtZgvPzqXacR3Dg+D/N22hlkxQTHMrrKf8g6U7Sp/OZjosrk/DLE7x6Lu5+MFvDTA8QIUCxFOwDzH55KJmdN28ljgoAEiY1kbA5kQ2XeEYFiuJEvdYLmSKL/gSeQXaGglUjd0tB3QEqVuOh2cQUJDG3CFVktEq3ByDlFWzAtAaz/T5NTnu4ydobNx9BSYO+xH/hH5JgLi75c/1MoSyvbXKWac1csU2E9NgMt9FsZsxMdGuGCMzRHTIwiSIY1DqBsiBEkY08vFdA5cGlyJJBmlLk996JLpitSDLpluyjrQpdL1Ojl0yXSVSCV0qXT9ToiENJWu8NB0yXD1aBe9LhWuCT8Clwg34KkCLhWuwoGH1nHf7ErxAmycsEn75UCImDOFAyFs8/bv10q5sVgHDdb5ZumuYrBev4ymG61psDgw3T5uMdveccbC5t+wYrEaT/roCm4eIXAmxNBsaS8wRrDaarMt183WHa1YCFmbsvfZn/6AwfTGzqDesJrmG5UH/b4QCmNae7jDqWs2Wrv83b3J42w5L9w4RxDvatpJvAqVVNHI1TOFYUN3MsAu65tcA48xaWQFZC3mGqMN97mX3EX/as5so80EQcZbWH1fBFkBVpuss5/HUsRznrPs/TYzlGJuo50PE8mXBWc85sn7WyuA9hbaZTxlUw2bxTM+ah60M5/E40m8wIkw15cQIz3kQvXQqmghlAdSmz1AshrItVyJu6gArNVKN2d9Ibx0gQ0j9gexy3uzZWQlBH9X7MZOkVsqsaPL+sH3BfN+wCKC1TrBeLYUSqj+IMnNJIFxlGUJeOP7JJe5BK9d3tVETxJE7hbcTSRkLcpuYm893JjlLy6GwxHnSjTHCpvJbDLfAPh64I4SYbiZuUG8GomQgfe/kbVPZfVyPFRlcjjvz/uy+rvXV+Xp0/6hrPSDqtL/WX2VX8v89cW9PwDS0DAhTeIAAA==</MentorApplicationsPartServices1:param1></MentorApplicationsPartServices1:getPartsForPartsStatus></SOAP-ENV:Body></SOAP-ENV:Envelope>
> Soap attachments are being truncated when moving from jboss 7 to wildfly9/10
> ----------------------------------------------------------------------------
>
> Key: WFLY-8306
> URL: https://issues.jboss.org/browse/WFLY-8306
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final
> Environment: Windows
> Reporter: Einat Peretz
> Assignee: Stuart Douglas
>
> Client access wildfly 9 or 10 web service (soap using Axis2) using https with zip attachment and the zip is received truncated on the server.
> The same deployed application with same client worked fine on Jboss 7.3.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-2500) Elytron, changing http-server-mechanism-factory of http-authentication-factory ends in reload-required state
by Martin Choma (JIRA)
Martin Choma created WFCORE-2500:
------------------------------------
Summary: Elytron, changing http-server-mechanism-factory of http-authentication-factory ends in reload-required state
Key: WFCORE-2500
URL: https://issues.jboss.org/browse/WFCORE-2500
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Martin Choma
Assignee: Darran Lofthouse
Changing attribute changing http-server-mechanism-factory of http-authentication-factory ends in reload-required state even though header allow-resource-service-restart=true is used
{code}
[standalone@localhost:9990 /] /subsystem=elytron/http-authentication-factory=application-http-authentication:write-attribute(name=http-server-mechanism-factory, value=global){allow-resource-service-restart=true}
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{code}
Header should work as attribute is declared as {{"restart-required" => "resource-services"}}
{code}
"http-server-mechanism-factory" => {
"type" => STRING,
"description" => "The HttpServerAuthenticationMechanismFactory to associate with this resource",
"expressions-allowed" => false,
"required" => true,
"nillable" => false,
"capability-reference" => "org.wildfly.security.http-server-mechanism-factory",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
}
{code}
And according to documentation [1]:
resource-services – The operation can only immediately update the persistent configuration; applying the operation to the runtime will require a subsequent restart of some services associated with the resource. If the operation includes the request header "allow-resource-service-restart" => true, the handler for the operation will go ahead and restart the runtime service. Otherwise executing the operation will put the server into a "reload-required" state. (See the discussion of "all-services" above for more on the "reload-required" state.)
[1] https://docs.jboss.org/author/display/WFLY10/Description+of+the+Managemen...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months