[JBoss JIRA] (WFLY-11970) SFSB memory leak due to Date() usage
by Ilia Vassilev (Jira)
[ https://issues.jboss.org/browse/WFLY-11970?page=com.atlassian.jira.plugin... ]
Ilia Vassilev updated WFLY-11970:
---------------------------------
Labels: downstream_dependency (was: )
> SFSB memory leak due to Date() usage
> ------------------------------------
>
> Key: WFLY-11970
> URL: https://issues.jboss.org/browse/WFLY-11970
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Dennis Reed
> Assignee: Paul Ferraro
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 17.0.0.Beta1
>
>
> SFSB tracks expiration with "new Date().getTime()" and "System.currentTimeMillis()".
> But the expiration threads are scheduled (inside JDK classes) with System.nanoTime().
> If the expiration task runs before the bean is considered expired, the expiration check fails and the bean is never expired.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11784) App classloader leaked by IIOP WorkCacheManager cache
by Ilia Vassilev (Jira)
[ https://issues.jboss.org/browse/WFLY-11784?page=com.atlassian.jira.plugin... ]
Ilia Vassilev updated WFLY-11784:
---------------------------------
Labels: downstream_dependency (was: )
> App classloader leaked by IIOP WorkCacheManager cache
> -----------------------------------------------------
>
> Key: WFLY-11784
> URL: https://issues.jboss.org/browse/WFLY-11784
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Affects Versions: 16.0.0.Beta1
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 17.0.0.Beta1
>
>
> After redeploys, application ear module classloaders are left in org.wildfly.iiop.openjdk.rmi.WorkCacheManager's classesByLoader map:
> {code}
> com.sun.corba.se.impl.transport.SelectorImpl @ 0xc12234b8 SelectorThread Thread
> '- contextClassLoader org.jboss.modules.ModuleClassLoader @ 0xc075bea0
> '- classes java.util.Vector @ 0xc075c4a8
> '- elementData java.lang.Object[160] @ 0xc1afb200
> '- [58] class org.wildfly.iiop.openjdk.rmi.ValueAnalysis @ 0xc180e4b0 |
> '- cache org.wildfly.iiop.openjdk.rmi.WorkCacheManager @ 0xc180e520
> |- classesByLoader java.util.HashMap @ 0xc180e730
> | '- table java.util.HashMap$Node[16] @ 0xc1ba2ff8
> | |- [14] java.util.HashMap$Node @ 0xc37b01e0
> | | '- key org.jboss.modules.ModuleClassLoader @ 0xc3677958
> {code}
> This was previously a weak map, but we switched to strong caching with explicit clean up on undeploy. It looks like that clean up is missed in some case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFCORE-3995) Deployer or Maintainer RBAC role unable to write datasource credential after setting sensitive-classification credential requires-write=false
by Ilia Vassilev (Jira)
[ https://issues.jboss.org/browse/WFCORE-3995?page=com.atlassian.jira.plugi... ]
Ilia Vassilev updated WFCORE-3995:
----------------------------------
Labels: downstream_dependency (was: )
> Deployer or Maintainer RBAC role unable to write datasource credential after setting sensitive-classification credential requires-write=false
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3995
> URL: https://issues.jboss.org/browse/WFCORE-3995
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 6.0.0.Alpha5
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
> Labels: downstream_dependency
> Fix For: 9.0.0.Beta3
>
>
> 1) Start the EAP in standalone or domain mode and connect to CLI and create a user with Deployer or Maintainer role
> ~~~
> - Create a user named "maintainer" using adduser.sh, then follow below steps to add it to the maintainer role
> /core-service=management/access=authorization/role-mapping=Maintainer:add()
> /core-service=management/access=authorization/role-mapping=Maintainer/include=maintainer:add(name=maintainer, type=user)
> /core-service=management/access=authorization:write-attribute(name=provider, value=rbac)
> reload
> ~~~
> 2) Apply application constraint to data-sources
> ~~~
> /core-service=management/access=authorization/constraint=application-classification/type=datasources/classification=data-source:write-attribute(name=configured-application,value=true)
> /core-service=management/access=authorization/constraint=application-classification/type=datasources/classification=xa-data-source:write-attribute(name=configured-application,value=true)
> ~~~
> 3) Set sensitivity-constraints to false for security credential requires-write
> ~~~
> /core-service=management/access=authorization/constraint=sensitivity-classification/type=core/classification=credential:write-attribute(name=configured-requires-write,value=false)
> /core-service=management/access=authorization/constraint=sensitivity-classification/type=core/classification=security-domain-ref:write-attribute(name=configured-requires-write,value=false)
> /core-service=management/access=authorization/constraint=sensitivity-classification/type=datasources/classification=data-source-security:write-attribute(name=configured-requires-write,value=false)
> /core-service=management/access=authorization/constraint=sensitivity-classification/type=datasources/classification=data-source-security:write-attribute(name=configured-requires-read,value=false)
> ~~~
> 4) Try to read / write the datasource's user-name and password:
> {code}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:write-attribute(name=user-name, sa)
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "WFLYCTL0313: Unauthorized to execute operation 'write-attribute' for resource '[
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\")
> ]' -- \"WFLYCTL0332: Permission denied\"",
> "rolled-back" => true
> }
> {code}
> {code}
> <access-control provider="rbac">
> <role-mapping>
> <role name="SuperUser">
> <include>
> <user name="$local"/>
> </include>
> </role>
> <role name="Maintainer">
> <include>
> <user alias="maintainer" name="maintainer"/>
> </include>
> </role>
> </role-mapping>
> <constraints>
> <sensitive-classifications>
> <sensitive-classification type="core" name="credential" requires-write="false"/>
> <sensitive-classification type="core" name="security-domain-ref" requires-write="false"/>
> <sensitive-classification type="datasources" name="data-source-security" requires-addressable="false" requires-read="false" requires-write="false"/>
> </sensitive-classifications>
> <application-classifications>
> <application-classification type="datasources" name="data-source" application="true"/>
> <application-classification type="datasources" name="xa-data-source" application="true"/>
> </application-classifications>
> </constraints>
> </access-control>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11974) resource adapter configured as module not finding validation provider
by Ilia Vassilev (Jira)
[ https://issues.jboss.org/browse/WFLY-11974?page=com.atlassian.jira.plugin... ]
Ilia Vassilev updated WFLY-11974:
---------------------------------
Labels: downstream_dependency (was: )
> resource adapter configured as module not finding validation provider
> ---------------------------------------------------------------------
>
> Key: WFLY-11974
> URL: https://issues.jboss.org/browse/WFLY-11974
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Major
> Labels: downstream_dependency
> Fix For: 17.0.0.Beta1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> resource adapter configured as module not finding validation provider
> {code}
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0215: Failed to resume activity org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent$1@3f9a21a1. To resume normal operation it is recommended that you restart the server.: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:273)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.access$300(MessageDrivenComponent.java:63)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent$1.resume(MessageDrivenComponent.java:109)
> at org.jboss.as.server.suspend.SuspendController.resume(SuspendController.java:126)
> at org.jboss.as.server.ServerService.finishBoot(ServerService.java:430)
> at org.jboss.as.server.ServerService.boot(ServerService.java:398)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:177)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:271)
> ... 7 more
> Caused by: javax.validation.ValidationException: Unable to create a Configuration, because no Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath.
> at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:271)
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidatorFactory(BeanValidationUtil.java:51)
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidator(BeanValidationUtil.java:63)
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:165)
> ... 8 more
> {code}
> It looks like the hibernate validator module should have services=import:
> {code}
> <module name="org.jboss.ironjacamar.impl" xmlns="urn:jboss:module:1.5">
> ...
> <dependencies>
> ...
> <module name="javax.validation.api"/>
> <module name="org.hibernate.validator"/>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-6918) Unnecessary NoSuchMethodException during JSF app deployment
by Ilia Vassilev (Jira)
[ https://issues.jboss.org/browse/WFLY-6918?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev updated WFLY-6918:
--------------------------------
Labels: downstream_dependency (was: )
> Unnecessary NoSuchMethodException during JSF app deployment
> ------------------------------------------------------------
>
> Key: WFLY-6918
> URL: https://issues.jboss.org/browse/WFLY-6918
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 10.0.0.Final, 10.1.0.CR1, 16.0.0.Final
> Environment: it's same at current master
> Reporter: Tomas Remes
> Assignee: Farah Juma
> Priority: Minor
> Labels: downstream_dependency
>
> When you turn on TRACE logging for {{javax.enterprise.resource}} then you can notice following exception during JSF app deployment:
> {noformat}
> [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 69) java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider): java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider)
> at java.lang.Class.getConstructor0(Class.java:3082)
> at java.lang.Class.getDeclaredConstructor(Class.java:2178)
> at com.sun.faces.spi.ServiceFactoryUtils.getProviderFromEntry(ServiceFactory.java:83)
> at com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:70)
> at com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:931)
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:385)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:227)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:200)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:171)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:234)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> Problem is that {{org.jboss.as.jsf.injection.JandexAnnotationProvider}} doesn't have corresponding constructor (with two params - javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11897) SFSB expiration failures cause memory leak
by Ilia Vassilev (Jira)
[ https://issues.jboss.org/browse/WFLY-11897?page=com.atlassian.jira.plugin... ]
Ilia Vassilev updated WFLY-11897:
---------------------------------
Labels: downstream_dependency (was: )
> SFSB expiration failures cause memory leak
> ------------------------------------------
>
> Key: WFLY-11897
> URL: https://issues.jboss.org/browse/WFLY-11897
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Dennis Reed
> Assignee: Paul Ferraro
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 17.0.0.Beta1
>
> Attachments: WFLY-11897.btm, test.ear
>
>
> There is a timing bug where SFSB expiration can run while the SFSB is still locked, causing the expiration to fail and never retry, leaving the SFSB active indefinitely.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11864) Only one JSF Validator is invoked when defined via annotation @FacesValidator
by Ilia Vassilev (Jira)
[ https://issues.jboss.org/browse/WFLY-11864?page=com.atlassian.jira.plugin... ]
Ilia Vassilev updated WFLY-11864:
---------------------------------
Labels: downstream_dependency (was: )
> Only one JSF Validator is invoked when defined via annotation @FacesValidator
> -----------------------------------------------------------------------------
>
> Key: WFLY-11864
> URL: https://issues.jboss.org/browse/WFLY-11864
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 16.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
> Labels: downstream_dependency
>
> Only one JSF Validator is invoked when defined via annotation @FacesValidator
> {code}
> @FacesValidator(value = "validator.CustomValidator1", managed = true)
> public class CustomValidator1 implements Validator<String> {
> ...
> }
> @FacesValidator(value = "validator.CustomValidator2", managed = true)
> public class CustomValidator2 implements Validator<String> {
> ...
> }
> {code}
> {code}
> <h:inputText id="input-value" value="#{customBean.inputValue}">
> <f:validator validatorId="validator.CustomValidator2" />
> <f:validator validatorId="validator.CustomValidator1" />
> </h:inputText>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11866) Cannot get exception as pass-by-reference
by Ilia Vassilev (Jira)
[ https://issues.jboss.org/browse/WFLY-11866?page=com.atlassian.jira.plugin... ]
Ilia Vassilev updated WFLY-11866:
---------------------------------
Labels: downstream_dependency (was: )
> Cannot get exception as pass-by-reference
> -----------------------------------------
>
> Key: WFLY-11866
> URL: https://issues.jboss.org/browse/WFLY-11866
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 16.0.0.Final, 17.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Major
> Labels: downstream_dependency
> Fix For: 17.0.0.Beta1
>
>
> Despite of <in-vm-remote-interface-invocation pass-by-value="false"/>, an exception is not thrown by reference, which results in java.io.NotSerializableException if the exception doesn't implement Serializable. This is a blocker of a large migration project from WebLogic because it throws by reference even if that doesn't implement Serializable.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months