[JBoss JIRA] (WFCORE-2757) DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
by Radoslav Husar (JIRA)
Radoslav Husar created WFCORE-2757:
--------------------------------------
Summary: DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
Key: WFCORE-2757
URL: https://issues.jboss.org/browse/WFCORE-2757
Project: WildFly Core
Issue Type: Bug
Reporter: Radoslav Husar
Assignee: Radoslav Husar
{noformat}
20:11:08,590 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node1 elected as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
20:11:08,594 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
20:11:08,603 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel server: [node1|4] (1) [node1]
...
20:11:08,794 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started clusterbench-ee7-singleton-jbossall.ear/clusterbench-ee7-ejb.jar cache from ejb container
20:11:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
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)
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
at injection point [UnbackedAnnotatedField] @Inject private org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator
at org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator(ValidationInterceptor.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:362)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:539)
at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:78)
at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:76)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2757) DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2757?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFCORE-2757:
-----------------------------------
Affects Version/s: 3.0.0.Beta17
> DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2757
> URL: https://issues.jboss.org/browse/WFCORE-2757
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta17
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> {noformat}
> 20:11:08,590 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node1 elected as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
> 20:11:08,594 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
> 20:11:08,603 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel server: [node1|4] (1) [node1]
> ...
> 20:11:08,794 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started clusterbench-ee7-singleton-jbossall.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 20:11:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> 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)
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
> at injection point [UnbackedAnnotatedField] @Inject private org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator
> at org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator(ValidationInterceptor.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:362)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
> at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:539)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:78)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:76)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> 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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2756) Elytron Audit Logging's rotating-file-audit-log throws IllegalArgumentException if suffix property is not specified
by Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2756?page=com.atlassian.jira.plugi... ]
Jan Tymel moved WFLY-8689 to WFCORE-2756:
-----------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2756 (was: WFLY-8689)
Component/s: Security
(was: Security)
> Elytron Audit Logging's rotating-file-audit-log throws IllegalArgumentException if suffix property is not specified
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2756
> URL: https://issues.jboss.org/browse/WFCORE-2756
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jan Tymel
> Priority: Critical
>
> {{rotating-file-audit}} throws {{IllegalArgumentException}} if user tries to add a new {{rotating-audit-file}} and does not specify {{suffix}} property.
> Steps to reproduce: {{/subsystem=elytron/rotating-file-audit-log=rotating-audit:add(path=rotating-audit.log)}}
> Following output is given in jboss-cli
> {code}
> {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.security-event-listener.rotating-audit" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: Illegal pattern character 'n'"}},
> "rolled-back" => true
> }
> {code}
> and following one in server log:
> {code}
> 12:45:41,381 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.security.security-event-listener.rotating-audit: org.jboss.msc.service.StartException in service org.wildfly.security.security-event-listener.rotating-audit: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> 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)
> Caused by: java.lang.IllegalArgumentException: Illegal pattern character 'n'
> at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:826)
> at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:634)
> at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:605)
> at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:580)
> at org.wildfly.security.audit.RotatingFileAuditEndpoint$Builder.setSuffix(RotatingFileAuditEndpoint.java:289)
> at org.wildfly.extension.elytron.AuditResourceDefinitions$2.lambda$getValueSupplier$2(AuditResourceDefinitions.java:235)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> 12:45:41,382 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 5) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("rotating-file-audit-log" => "rotating-audit")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.security-event-listener.rotating-audit" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: Illegal pattern character 'n'"}}
> {code}
> Note: there is an easy workaround - if user specifies {{suffix}} property then adding a new {{rotating-audit-file}} works fine, e.g. {{/subsystem=elytron/rotating-file-audit-log=rotating-audit:add(path=rotating-audit.log,suffix=y-M-d)}} passes successfully.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2755) Elytron Audit Logging: rotating-file-audit-log's event timestamp lacks information about seconds
by Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2755?page=com.atlassian.jira.plugi... ]
Jan Tymel moved WFLY-8692 to WFCORE-2755:
-----------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2755 (was: WFLY-8692)
Component/s: Security
(was: Security)
> Elytron Audit Logging: rotating-file-audit-log's event timestamp lacks information about seconds
> ------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2755
> URL: https://issues.jboss.org/browse/WFCORE-2755
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jan Tymel
> Priority: Blocker
>
> The format of _rotating-file-audit-log's_ timestamp is insufficient. It lacks the information about seconds which might be a problem in an environment with thousands of active users.
> Furthermore the format of timestamp is inconsistent with the _file-audit-log_.
> _file-audit-log:_
> {code}
> 2017-05-03 13:44:07
> {code}
> _rotating-file-audit-log:_
> {code}
> 5/3/17 1:44 PM
> {code}
> Suggestions for improvement:
> Use the same format of timestamp in_rotating-file-audit-log_ as is already used in _file-audit-log_.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8692) Elytron Audit Logging: rotating-file-audit-log's event timestamp lacks information about seconds
by Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/WFLY-8692?page=com.atlassian.jira.plugin.... ]
Jan Tymel reassigned WFLY-8692:
-------------------------------
Assignee: (was: Darran Lofthouse)
> Elytron Audit Logging: rotating-file-audit-log's event timestamp lacks information about seconds
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-8692
> URL: https://issues.jboss.org/browse/WFLY-8692
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Jan Tymel
> Priority: Blocker
>
> The format of _rotating-file-audit-log's_ timestamp is insufficient. It lacks the information about seconds which might be a problem in an environment with thousands of active users.
> Furthermore the format of timestamp is inconsistent with the _file-audit-log_.
> _file-audit-log:_
> {code}
> 2017-05-03 13:44:07
> {code}
> _rotating-file-audit-log:_
> {code}
> 5/3/17 1:44 PM
> {code}
> Suggestions for improvement:
> Use the same format of timestamp in_rotating-file-audit-log_ as is already used in _file-audit-log_.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8692) Elytron Audit Logging: rotating-file-audit-log's event timestamp lacks information about seconds
by Jan Tymel (JIRA)
Jan Tymel created WFLY-8692:
-------------------------------
Summary: Elytron Audit Logging: rotating-file-audit-log's event timestamp lacks information about seconds
Key: WFLY-8692
URL: https://issues.jboss.org/browse/WFLY-8692
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Jan Tymel
Assignee: Darran Lofthouse
Priority: Blocker
The format of _rotating-file-audit-log's_ timestamp is insufficient. It lacks the information about seconds which might be a problem in an environment with thousands of active users.
Furthermore the format of timestamp is inconsistent with the _file-audit-log_.
_file-audit-log:_
{code}
2017-05-03 13:44:07
{code}
_rotating-file-audit-log:_
{code}
5/3/17 1:44 PM
{code}
Suggestions for improvement:
Use the same format of timestamp in_rotating-file-audit-log_ as is already used in _file-audit-log_.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years