[JBoss JIRA] (JGRP-1799) RpcDispatcher test fails when working with large values
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JGRP-1799?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JGRP-1799:
-----------------------------------------------
Paul Ferraro <paul.ferraro(a)redhat.com> changed the Status of [bug 1022413|https://bugzilla.redhat.com/show_bug.cgi?id=1022413] from NEW to CLOSED
> RpcDispatcher test fails when working with large values
> -------------------------------------------------------
>
> Key: JGRP-1799
> URL: https://issues.jboss.org/browse/JGRP-1799
> Project: JGroups
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.2.13
> Environment: RHEL, Win, Solaris
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> The two tests:
> * testLargeReturnValue
> * testLargeReturnValueUnicastCall
> make RPC calls with values which are increasingly large.
> The values used are in this range:
> {noformat}
> SIZES={10000, 20000, 40000, 80000, 100000, 200000, 400000, 800000,1000000, 2000000, 5000000}
> {noformat}
> The tests have been see to fail with the values 1000000, 2000000 and 5000000, always with the same error in each case.
> In the case of testLargeReturnValue, the test fails because one of the returned values from the RPC is null.
> In the case of testLargeReturnValueUnicastCall, the test fails due to a timeout while sending the RPC.
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil edited comment on WFLY-3791 at 8/29/14 10:28 AM:
--------------------------------------------------------------
Darran,
What tricks much more me, it is the fact via CLI console I can find security section.
Seems just Java API can not do it
Why?
C:\wildfly-8.1.0.Final\bin>jboss-cli.bat --connect --controller=localhost:9029
[standalone@localhost:9029 /] ./subsystem=security:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"deep-copy-subject-mode" => false,
"security-domain" => {
"pw_encrypted_MSSQL_CAS_DS" => {
"cache-type" => "default",
"acl" => undefined,
"audit" => undefined,
"authentication" => {"classic" => {
"login-modules" => [{
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}],
"login-module" => {"org.picketbox.datasource.security.SecureIdentityLoginModule" => {
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}}
}},
"authorization" => undefined,
"identity-trust" => undefined,
"jsse" => undefined,
was (Author: ofbizbrazil):
Darran,
What trickes much more me, is just the fact via CLI console I can find security section.
Seems just Java API can not do it
Why?
C:\wildfly-8.1.0.Final\bin>jboss-cli.bat --connect --controller=localhost:9029
[standalone@localhost:9029 /] ./subsystem=security:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"deep-copy-subject-mode" => false,
"security-domain" => {
"pw_encrypted_MSSQL_CAS_DS" => {
"cache-type" => "default",
"acl" => undefined,
"audit" => undefined,
"authentication" => {"classic" => {
"login-modules" => [{
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}],
"login-module" => {"org.picketbox.datasource.security.SecureIdentityLoginModule" => {
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}}
}},
"authorization" => undefined,
"identity-trust" => undefined,
"jsse" => undefined,
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Darran Lofthouse
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> final String section = response.get(ClientConstants.RESULT).get("security-domain")
> .get("pw_MSSQL_CAS_DS")
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil edited comment on WFLY-3791 at 8/29/14 10:25 AM:
--------------------------------------------------------------
Darran,
What trickes much more me, is just the fact via CLI console I can find security section.
Seems just Java API can not do it
Why?
C:\wildfly-8.1.0.Final\bin>jboss-cli.bat --connect --controller=localhost:9029
[standalone@localhost:9029 /] ./subsystem=security:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"deep-copy-subject-mode" => false,
"security-domain" => {
"pw_encrypted_MSSQL_CAS_DS" => {
"cache-type" => "default",
"acl" => undefined,
"audit" => undefined,
"authentication" => {"classic" => {
"login-modules" => [{
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}],
"login-module" => {"org.picketbox.datasource.security.SecureIdentityLoginModule" => {
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}}
}},
"authorization" => undefined,
"identity-trust" => undefined,
"jsse" => undefined,
was (Author: ofbizbrazil):
Darran,
What trickes much more me, is just the fact via CLI console I can find security section.
Seems just Java API can do it
Why?
C:\wildfly-8.1.0.Final\bin>jboss-cli.bat --connect --controller=localhost:9029
[standalone@localhost:9029 /] ./subsystem=security:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"deep-copy-subject-mode" => false,
"security-domain" => {
"pw_encrypted_MSSQL_CAS_DS" => {
"cache-type" => "default",
"acl" => undefined,
"audit" => undefined,
"authentication" => {"classic" => {
"login-modules" => [{
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}],
"login-module" => {"org.picketbox.datasource.security.SecureIdentityLoginModule" => {
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}}
}},
"authorization" => undefined,
"identity-trust" => undefined,
"jsse" => undefined,
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Darran Lofthouse
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> final String section = response.get(ClientConstants.RESULT).get("security-domain")
> .get("pw_MSSQL_CAS_DS")
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil commented on WFLY-3791:
------------------------------------
Darran,
What trickes much more me, is just the fact via CLI console I can find security section.
Seems just Java API can do it
Why?
C:\wildfly-8.1.0.Final\bin>jboss-cli.bat --connect --controller=localhost:9029
[standalone@localhost:9029 /] ./subsystem=security:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"deep-copy-subject-mode" => false,
"security-domain" => {
"pw_encrypted_MSSQL_CAS_DS" => {
"cache-type" => "default",
"acl" => undefined,
"audit" => undefined,
"authentication" => {"classic" => {
"login-modules" => [{
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}],
"login-module" => {"org.picketbox.datasource.security.SecureIdentityLoginModule" => {
"code" => "org.picketbox.datasource.security.SecureIdentityLoginModule",
"flag" => "required",
"module" => undefined,
"module-options" => {
"username" => "XXXX",
"password" => "XXXX",
"managedConnectionFactoryName" => "jboss.jca:service=TxCM,name=MSSQL_CAS_DS"
}
}}
}},
"authorization" => undefined,
"identity-trust" => undefined,
"jsse" => undefined,
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Darran Lofthouse
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> final String section = response.get(ClientConstants.RESULT).get("security-domain")
> .get("pw_MSSQL_CAS_DS")
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (WFLY-1631) Duplicated message ids in web, undertow, jsf and osgi subsystems
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1631?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1631:
-----------------------------------------------
Farah Juma <fjuma(a)redhat.com> changed the Status of [bug 980823|https://bugzilla.redhat.com/show_bug.cgi?id=980823] from NEW to ASSIGNED
> Duplicated message ids in web, undertow, jsf and osgi subsystems
> -----------------------------------------------------------------
>
> Key: WFLY-1631
> URL: https://issues.jboss.org/browse/WFLY-1631
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF, OSGi, Web (Undertow)
> Affects Versions: 8.0.0.Alpha2
> Reporter: Ivo Studensky
> Assignee: Tomaz Cerar
> Priority: Critical
> Fix For: 8.0.0.CR1
>
>
> There is a lot of duplicated or different messages in JBossWeb and Undertow subsystems which has the same ids.
> different messages:
> {noformat}
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12604, value = "JSF version slot '%s' is missing from module %s")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12604, value = "WildFlyConversationAwareViewHandler was improperly initialized. Expected ViewHandler parent.")
> {noformat}
> duplicated messages with the same content:
> {noformat}
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12600, value = "Could not load JSF managed bean class: %s")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12600, value = "Could not load JSF managed bean class: %s")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12601, value = "JSF managed bean class %s has no default constructor")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12601, value = "JSF managed bean class %s has no default constructor")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12602, value = "Failed to parse %s, managed beans defined in this file will not be available")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12602, value = "Failed to parse %s, managed beans defined in this file will not be available")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12603, value = "Unknown JSF version '%s'. Default version '%s' will be used instead.")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12603, value = "Unknown JSF version %s %s will be used instead")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12650, value = "Failed to load annotated class: %s")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12650, value = "Failed to load annotated class: %s")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12651, value = "Annotation %s in class %s is only allowed on classes")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12651, value = "Annotation %s in class %s is only allowed on classes")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12652, value = "Instance creation failed")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12652, value = "Instance creation failed")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12653, value = "Instance destruction failed")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12653, value = "Instance destruction failed")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12654, value = "Thread local injection container not set")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12654, value = "Thread local injection container not set")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12655, value = "@ManagedBean is only allowed at class level %s")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12655, value = "@ManagedBean is only allowed at class level %s")
> web/src/main/java/org/jboss/as/web/WebMessages.java: @Message(id = 18039, value = "Failed to create context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18039, value = "Failed to create context")
> web/src/main/java/org/jboss/as/web/WebMessages.java: @Message(id = 18040, value = "Failed to start context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18040, value = "Failed to start context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18200, value = "Failed to start welcome context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18200, value = "Failed to start welcome context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18201, value = "Failed to destroy welcome context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18201, value = "Failed to destroy welcome context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18202, value = "Error calling onStartup for servlet container initializer: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18202, value = "Error calling onStartup for servlet container initializer: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18203, value = "Error instantiating container component: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18203, value = "Error instantiating container component: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18204, value = "Clustering not supported, falling back to non-clustered session manager")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18204, value = "Clustering not supported, falling back to non-clustered session manager")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18205, value = "Cannot setup overlays for [%s] due to custom resources")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18205, value = "Cannot setup overlays for [%s] due to custom resources")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18206, value = "Webapp [%s] is unavailable due to startup errors")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18206, value = "Webapp [%s] is unavailable due to startup errors")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18208, value = "Failed to start context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18208, value = "Failed to start context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18208, value = "Failed to start context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18208, value = "Failed to start context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18208, value = "Failed to start context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18208, value = "Failed to start context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18210, value = "Register web context: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18210, value = "Register web context: %s")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18210, value = "Register web context: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18210, value = "Register web context: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18210, value = "Register web context: %s")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18210, value = "Register web context: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18214, value = "Error during login/password authenticate")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18214, value = "Error during login/password authenticate")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18215, value = "Error during certificate authenticate")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18215, value = "Error during certificate authenticate")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18216, value = "Error during digest authenticate")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18216, value = "Error during digest authenticate")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18217, value = "Error obtaining authorization helper")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18217, value = "Error obtaining authorization helper")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18218, value = "Exception in obtaining server authentication manager")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18218, value = "Exception in obtaining server authentication manager")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18219, value = "JASPI validation for unprotected request context %s failed")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18219, value = "JASPI validation for unprotected request context %s failed")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18220, value = "Caught Exception: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18220, value = "Caught Exception: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18221, value = "Error forwarding to login page: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18221, value = "Error forwarding to login page: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18222, value = "Error forwarding to error page: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18222, value = "Error forwarding to error page: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18224, value = "Unregister web context: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18224, value = "Unregister web context: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18226, value = "Skipped SCI for jar: %s.")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18226, value = "Skipped SCI for jar: %s.")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil edited comment on WFLY-3791 at 8/29/14 9:43 AM:
-------------------------------------------------------------
Hi Darran,
Is there any difference in standalone.xml that i need to put, because I migrated mine from jboss 7.1.1 to wildfly? Using the default file in Wildfly as base.
Take a look at my securtiy section
<subsystem xmlns="urn:jboss:domain:security:1.2">
<security-domains>
<security-domain name="pw_encrypted_MSSQL_CAS_DS" cache-type="default">
<authentication>
<login-module code="org.picketbox.datasource.security.SecureIdentityLoginModule" flag="required">
<module-option name="username" value="XXXX"/>
<module-option name="password" value="XXX"/>
<module-option name="managedConnectionFactoryName" value="jboss.jca:service=TxCM,name=MSSQL_CAS_DS"/>
</login-module>
</authentication>
</security-domain>
<security-domain name="other" cache-type="default">
<authentication>
<login-module code="Remoting" flag="optional">
<module-option name="password-stacking" value="useFirstPass"/>
</login-module>
<login-module code="RealmDirect" flag="required">
<module-option name="password-stacking" value="useFirstPass"/>
</login-module>
</authentication>
</security-domain>
<security-domain name="jboss-web-policy" cache-type="default">
<authorization>
<policy-module code="Delegating" flag="required"/>
</authorization>
</security-domain>
<security-domain name="jboss-ejb-policy" cache-type="default">
<authorization>
<policy-module code="Delegating" flag="required"/>
</authorization>
</security-domain>
</security-domains>
</subsystem>
Cheers,
was (Author: ofbizbrazil):
Hi Darran,
Is there any difference in standalone.xml that i need to put, because I migrated mine from jboss 7.1.1 to wildfly? Using the default file
Cheers,
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Darran Lofthouse
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> final String section = response.get(ClientConstants.RESULT).get("security-domain")
> .get("pw_MSSQL_CAS_DS")
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil commented on WFLY-3791:
------------------------------------
Hi Darran,
Is there any difference in standalone.xml that i need to put, because I migrated mine from jboss 7.1.1 to wildfly? Using the default file
Cheers,
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Darran Lofthouse
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> final String section = response.get(ClientConstants.RESULT).get("security-domain")
> .get("pw_MSSQL_CAS_DS")
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (AS7-3050) RESTEasy: Boolean configuration parameters don't reject non-sense content
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-3050?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-3050:
----------------------------------------------
Katerina Novotna <kanovotn(a)redhat.com> changed the Status of [bug 1121661|https://bugzilla.redhat.com/show_bug.cgi?id=1121661] from ON_QA to VERIFIED
> RESTEasy: Boolean configuration parameters don't reject non-sense content
> -------------------------------------------------------------------------
>
> Key: AS7-3050
> URL: https://issues.jboss.org/browse/AS7-3050
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Weinan Li
> Fix For: Awaiting Volunteers
>
>
> RESTEasy can be configured through several configuration options in WAR application deployment file WEB-INF/web.xml. These options which are type of Boolean (= true, false; maybe we should do support for 0 and 1 too), other invalid or non-sense setting should be rejected as invalid deployment description and a such application should not be deployed at all.
> Affected options are:
> - resteasy.scan
> - resteasy.scan.providers
> - resteasy.scan.resources
> - resteasy.use.builtin.providers
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months