[JBoss JIRA] (WFLY-4699) Expose EJB3 deployment information at runtime
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-4699?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-4699:
-----------------------------------
Fix Version/s: 20.0.0.Beta1
(was: 19.0.0.Beta1)
> Expose EJB3 deployment information at runtime
> ---------------------------------------------
>
> Key: WFLY-4699
> URL: https://issues.redhat.com/browse/WFLY-4699
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Bilgehan Ozpeynirci
> Assignee: Cheng Fang
> Priority: Minor
> Fix For: 20.0.0.Beta1
>
>
> User will be able to get EJB Deployment Information at runtime for the following areas:
> - Class name
> - Local JNDI name
> - Remote JNDI name
> - Security roles
> - Bean statistics (beans in use, access count, idle count, ...)
> - Destination JNDI (for MDBs)
> - Activation config properties
> - EJB timeout (Stateful Timeouts , and Stateless Instance timeout)
> A lot of this information were previously (EAP 5) obtained from the deployment descriptor that was published by the bean ("deploymentDescriptor" attribute). In the past, this metadata could be retrieved from EAP 5 via jmx which no longer exists in EAP 6+ (JBoss AS 7+). Now with EJB 3, users provide that information through annotations (and also through the Deployment Descriptor file), so users need means to get those informations at runtime.
> The goal of this is not only for MDB but for all kinds of EJB (session, stateful, MDB, ...)
> MORE INFO:
> The local and remote JNDI are related to Session EJBs.
> However we need to access the JNDI of the destination configured for the MDB.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-8136) Allow JAX-RS annotations in CDI @Stereotype
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-8136?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-8136:
-----------------------------------
Fix Version/s: 20.0.0.Beta1
(was: 19.0.0.Beta1)
> Allow JAX-RS annotations in CDI @Stereotype
> -------------------------------------------
>
> Key: WFLY-8136
> URL: https://issues.redhat.com/browse/WFLY-8136
> Project: WildFly
> Issue Type: Feature Request
> Components: CDI / Weld, REST
> Affects Versions: 9.0.1.Final, 15.0.0.Final
> Environment: Windows 7, JDK 1.8.0_60
> Reporter: Andreas Klemp
> Assignee: Martin Stefanko
> Priority: Major
> Fix For: 20.0.0.Beta1
>
>
> A simple JAX-RS REST service can be annotated with @Produces to define the resulting mime-type. However, it is not working anymore, when the annotation is moved to a stereotype. The default application/octet-stream is used.
> {code}
> @Stereotype
> @Produces(MediaType.APPLICATION_JSON)
> @Target(ElementType.TYPE)
> @Retention(RetentionPolicy.RUNTIME)
> public @interface RestService {
> }
> @Path("/some")
> @RestService
> public class SomeRestService {
> @GET
> @Path("/")
> public Response getSome() {
> return Response.ok().entity("{\"x\" : 42, \"y\" : \"foo\"}").build();
> }
> }
> {code}
> Using the following dependencies in Gradle project.
> {noformat}
> providedCompile(
> [group: 'javax.enterprise', name: 'cdi-api', version: '1.2'],
> [group: 'org.jboss.spec.javax.ws.rs', name: 'jboss-jaxrs-api_2.0_spec', version: '1.0.0.Final'],
> [group: 'com.fasterxml.jackson.core', name: 'jackson-databind', version: '2.7.4']
> )
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-12680) Ability to configure default global stateful timeout for Stateful Session Beans (SFSB)
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12680?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12680:
------------------------------------
Fix Version/s: 20.0.0.Beta1
(was: 19.0.0.Beta1)
> Ability to configure default global stateful timeout for Stateful Session Beans (SFSB)
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12680
> URL: https://issues.redhat.com/browse/WFLY-12680
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
> Labels: EAP-CD19, Previous_RFE
> Fix For: 20.0.0.Beta1
>
>
> SFSB expiration can be configured by using the {{@StatefulTimeout}} annotation in the SFSB java source code or by specifying {{<stateful-timeout>}} in the {{ejb-jar.xml}} file. However, it can be only set on a per-bean basis.
> There is no default stateful timeout and we do not have a way to configure the default stateful timeout globally. So, it is troublesome for users who have many stateful session beans and want to set the same stateful-timeout value for every bean.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-6892) Access logging for EJBs
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-6892?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-6892:
-----------------------------------
Fix Version/s: 20.0.0.Beta1
(was: 19.0.0.Beta1)
> Access logging for EJBs
> -----------------------
>
> Key: WFLY-6892
> URL: https://issues.redhat.com/browse/WFLY-6892
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Cheng Fang
> Priority: Major
> Labels: affects-model, affects_elytron
> Fix For: 20.0.0.Beta1
>
>
> Access logging for EJB requests similar to Web access logging would be very useful.
> Possibly something like:
> {code}
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received ...
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting Invocation ...
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished Invocation ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4764) Availability of web console during the startup of the Domain Controller
by Yeray Borges (Jira)
[ https://issues.redhat.com/browse/WFCORE-4764?page=com.atlassian.jira.plug... ]
Yeray Borges updated WFCORE-4764:
---------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4058
> Availability of web console during the startup of the Domain Controller
> -----------------------------------------------------------------------
>
> Key: WFCORE-4764
> URL: https://issues.redhat.com/browse/WFCORE-4764
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Affects Versions: 11.0.0.Beta3
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Minor
>
> The customer asking why the web console is only available after all servers are registered in the Domain.
> If the customer starts a domain controller using the host.xml file for example and enables all servers to auto-start="true" the web console is not available until all servers are registered and the browser prompts to add a new interface.
> In the log file, the HTTP management interface is enable in the end of the events:
> ~~~
> [Host Controller] 18:41:29,247 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting
> [Host Controller] 18:41:30,208 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:30,210 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:30,284 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1
> [Host Controller] 18:41:30,342 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.5.4.Final-redhat-1
> [Host Controller] 18:41:30,356 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 18:41:30,383 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.4.Final-redhat-1
> [Host Controller] 18:41:30,478 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.5.Final-redhat-1
> [Host Controller] 18:41:30,603 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
> [Host Controller] 18:41:30,647 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /opt/jboss-eap-7.1/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> [Host Controller] 18:41:30,705 INFO [org.jboss.as.remoting] (MSC service thread 1-8) WFLYRMT0001: Listening on 127.0.0.1:9999
> [Host Controller] 18:41:32,922 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:32,990 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,046 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,112 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,612 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one
> 18:41:33,665 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one'
> [Host Controller] 18:41:35,496 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 348b688d (inbound) of Remoting connection 0f97728d to localhost/127.0.0.1:53171 of endpoint "master:MANAGEMENT" <46167ef2>]
> [Host Controller] 18:41:35,562 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two
> [Host Controller] 18:41:35,582 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one
> 18:41:35,606 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two'
> [Host Controller] 18:41:38,901 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 114e3864 (inbound) of Remoting connection 30f65708 to localhost/127.0.0.1:42083 of endpoint "master:MANAGEMENT" <46167ef2>]
> [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management
> [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1
> [Host Controller] 18:41:38,970 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) (Host Controller) started in 10487ms - Started 77 of 79 services (23 services are lazy, passive or on-demand)
> ~~~
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4764) Availability of web console during the startup of the Domain Controller
by Yeray Borges (Jira)
[ https://issues.redhat.com/browse/WFCORE-4764?page=com.atlassian.jira.plug... ]
Yeray Borges commented on WFCORE-4764:
--------------------------------------
Hello [~harald.pehl], I hope you can help with this.
I opened HAL-1653 as a consequence of enabling the console before the domain is complete up. There could be more issues, sometimes I get errors clicking on the server and server groups when the domain is starting, I haven't found a pattern yet, when you have a chance, could you take a look to HAL with the PR of this issue merged in your local WildFly version? Thanks
> Availability of web console during the startup of the Domain Controller
> -----------------------------------------------------------------------
>
> Key: WFCORE-4764
> URL: https://issues.redhat.com/browse/WFCORE-4764
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Affects Versions: 11.0.0.Beta3
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Minor
>
> The customer asking why the web console is only available after all servers are registered in the Domain.
> If the customer starts a domain controller using the host.xml file for example and enables all servers to auto-start="true" the web console is not available until all servers are registered and the browser prompts to add a new interface.
> In the log file, the HTTP management interface is enable in the end of the events:
> ~~~
> [Host Controller] 18:41:29,247 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting
> [Host Controller] 18:41:30,208 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:30,210 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:30,284 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1
> [Host Controller] 18:41:30,342 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.5.4.Final-redhat-1
> [Host Controller] 18:41:30,356 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 18:41:30,383 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.4.Final-redhat-1
> [Host Controller] 18:41:30,478 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.5.Final-redhat-1
> [Host Controller] 18:41:30,603 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
> [Host Controller] 18:41:30,647 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /opt/jboss-eap-7.1/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> [Host Controller] 18:41:30,705 INFO [org.jboss.as.remoting] (MSC service thread 1-8) WFLYRMT0001: Listening on 127.0.0.1:9999
> [Host Controller] 18:41:32,922 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:32,990 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,046 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,112 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,612 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one
> 18:41:33,665 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one'
> [Host Controller] 18:41:35,496 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 348b688d (inbound) of Remoting connection 0f97728d to localhost/127.0.0.1:53171 of endpoint "master:MANAGEMENT" <46167ef2>]
> [Host Controller] 18:41:35,562 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two
> [Host Controller] 18:41:35,582 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one
> 18:41:35,606 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two'
> [Host Controller] 18:41:38,901 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 114e3864 (inbound) of Remoting connection 30f65708 to localhost/127.0.0.1:42083 of endpoint "master:MANAGEMENT" <46167ef2>]
> [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management
> [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1
> [Host Controller] 18:41:38,970 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) (Host Controller) started in 10487ms - Started 77 of 79 services (23 services are lazy, passive or on-demand)
> ~~~
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-12836) Large allocations in EJBContextImpl#isCallerInRole
by Ashley Abdel-Sayed (Jira)
[ https://issues.redhat.com/browse/WFLY-12836?page=com.atlassian.jira.plugi... ]
Ashley Abdel-Sayed commented on WFLY-12836:
-------------------------------------------
I don't think it would be possible to add a roles field to the SecurityIdentity as there wouldn't be a way of telling when it should be updated, so I think we need to stick with mapping everytime getRoles is called. As a lot of the allocations were coming from creating a HashSet every time here: https://github.com/wildfly-security/wildfly-elytron/blob/de462529f5c5f49e..., I tried adding a {{HashMap<Attributes.Entry, HashSet>}} to map the entry to a HashSet if its already been created. While this did reduce the allocations from creating the HashSet, this increased the allocations from searching the HashMap more significantly. This is due to {{HashMap#get}} calling {{MapAttributes#size}} which calls {{MapAttributes#get}}:
!screenshot-1.png|thumbnail!
Before my changes, the total allocations from this 526KiB for the test I ran.
[~dlofthouse] I was wondering if you had any thoughts or suggestions for this isssue. Thanks!
> Large allocations in EJBContextImpl#isCallerInRole
> --------------------------------------------------
>
> Key: WFLY-12836
> URL: https://issues.redhat.com/browse/WFLY-12836
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security
> Affects Versions: 18.0.1.Final
> Reporter: Philippe Marschall
> Assignee: Ashley Abdel-Sayed
> Priority: Major
> Attachments: elytron_allocations_redacted.PNG, screenshot-1.png
>
>
> In our application we have the need to know the roles of the current user. We would like to do this using Java / Jakarta EE APIs rather than rely on WildFly implementation classes. We do this by iterating over all roles, which we know statically, and calling {{EJBContext#isCallerInRole}} for each one. This seem to be a common technique, see [How to get user roles in a JSP / Servlet|https://stackoverflow.com/questions/344117/how-to-get-user-roles-...].
> That's about 100 roles for us. We were expecting that would be a lookup into a {{HashMap}} or similar with O(1) complexity and almost no allocations.
> This however does not seem to be case as {{EJBContextImpl#isCallerInRole}} seems to do the role mapping for every call. This results in a large amount of allocations. In our case this completely dominates our allocation profile. See attached screenshot from JFR.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months