[JBoss JIRA] (WFCORE-450) Using parent system properties in child properties fails in domain server launch
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-450?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-450:
------------------------------------------------
Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1230980|https://bugzilla.redhat.com/show_bug.cgi?id=1230980] from VERIFIED to CLOSED
> Using parent system properties in child properties fails in domain server launch
> --------------------------------------------------------------------------------
>
> Key: WFCORE-450
> URL: https://issues.jboss.org/browse/WFCORE-450
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Samuli Saarinen
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Alpha15
>
> Attachments: domain.xml.patch, host-controller.log
>
>
> Using wildfly domain I would like to define some properties in domain.xml and then be able to use these properties when defining others in server-group or server level. Currently this leads to JBAS014802: Cannot resolve expression.
> More detailed example:
> {code:xml|title=domain.xml}
> <domain>
> <system-properties>
> <property name="foo" value="bar"/>
> </system-properties>
> ...
> <server-group name="g1">
> <system-properties>
> <property name="g1_foo" value="${foo}"/>
> </system-properties>
> </server-group>
> </domain>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-587) Wildfly does not log stack trace of an exception
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-587?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-587:
------------------------------------------------
Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1198186|https://bugzilla.redhat.com/show_bug.cgi?id=1198186] from VERIFIED to CLOSED
> Wildfly does not log stack trace of an exception
> ------------------------------------------------
>
> Key: WFCORE-587
> URL: https://issues.jboss.org/browse/WFCORE-587
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 1.0.0.Alpha19
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
>
> Copied from BZ 1198186:
> AbstractOperationContext.java line 1159 seems to be "swallowing" exceptions. It's possible to get NullPointerException without a stack trace. This makes it impossible to trace the cause of the NPE.
> https://github.com/jbossas/jboss-eap/blob/2292b0a8763683d0fab03efc3de6a29...
> 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-11) Finding class org.jboss.logging.DelegatingBasicLogger from Module "org.picketbox:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
> 2015-02-27 12:53:26,586 ERROR [|] [org.jboss.as.controller.client] (ServerService Thread Pool -- 29) JBAS014781: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@1e6a7c88 for operation {"operation" => "add","factory-class" => "org.hornetq.core.remoting.impl.netty.NettyConnectorFactory","param" => [("host" => "tp4.app.paypoint.net"),("port" => "6495"),("use-nio" => "true")],"address" => [("subsystem" => "messaging"),("hornetq-server" => "default"),("connector" => "tp4")],"socket-binding" => undefined} at address [
> ("subsystem" => "messaging"),
> ("hornetq-server" => "default"),
> ("connector" => "tp4")
> ] failed handling operation rollback -- java.lang.NullPointerException
> 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-4) Finding class org.jboss.remoting3.UnlockedReadHashMap$EntryIterator from Module "org.jboss.remoting3:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-3988) Authorization denied for authenticated users when @PermitAll is used on EJB JAX-WS endpoint
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3988?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3988:
-----------------------------------------------
Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1206657|https://bugzilla.redhat.com/show_bug.cgi?id=1206657] from VERIFIED to CLOSED
> Authorization denied for authenticated users when @PermitAll is used on EJB JAX-WS endpoint
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-3988
> URL: https://issues.jboss.org/browse/WFLY-3988
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.Final
> Reporter: Kyle Lape
> Assignee: Jim Ma
> Fix For: 9.0.0.Beta1
>
>
> Given this endpoint:
> {code:java}
> @Stateless
> @WebService(endpointInterface="com.redhat.gss.SecureEndpoint")
> @DeclareRoles({"a","b"})
> @WebContext(contextRoot="/endpoint",urlPattern="/e",authMethod="BASIC")
> public class SecureEndpointE implements SecureEndpoint {
> @RolesAllowed({"a"})
> public String a() {
> return "Success";
> }
> @RolesAllowed({"b"})
> public String b() {
> return "Success";
> }
> @PermitAll
> public String c() {
> return "Success";
> }
> }
> {code}
> One would expect any authenticated user to be able to invoke {{c()}}, but only users with a role found in {{@DelareRoles}} can invoke it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-4801) When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4801?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4801:
-----------------------------------------------
Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1232781|https://bugzilla.redhat.com/show_bug.cgi?id=1232781] from VERIFIED to CLOSED
> When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4801
> URL: https://issues.jboss.org/browse/WFLY-4801
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Alpha3
> Reporter: Chao Wang
> Assignee: Chao Wang
> Fix For: 9.0.0.Final, 10.0.0.Alpha4
>
>
> {noformat}
> Description of problem:
> ========================
> - Expression is added in the datasource JNDI name attribute as below:
> -----
> <datasource jndi-name="${ds}" pool-name="ExampleDS" enabled="true" use-java-context="true">
> -----
> - Value for the expression is passed to the JBoss server during the JBoss startup as below:
> -----
> ./standalone.sh -Dds=java:jboss/datasources/ExampleDS
> -----
> - In the server.log file below is the information regarding the datasource.
> -----
> INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [${ds}]
> -----
> - Test the datasource using the below command and here is the result:
> ----
> [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool()
> {
> "outcome" => "failed",
> "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:/${ds}",
> "rolled-back" => true
> }
> ----
> - Here is the information regarding the JNDI name attribute:
> ----
> [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-resource-description(recursive=true)
> {
> "outcome" => "success",
> "result" => {
> :
> "jndi-name" => {
> "type" => STRING,
> "description" => "Specifies the JNDI name for the datasource",
> "expressions-allowed" => true,
> "nillable" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> :
> }
> -----
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months