[JBoss JIRA] (WFLY-5040) DeltaSpike in WF 9.0.1 results in lots of warnings
by The Alchemist (JIRA)
The Alchemist created WFLY-5040:
-----------------------------------
Summary: DeltaSpike in WF 9.0.1 results in lots of warnings
Key: WFLY-5040
URL: https://issues.jboss.org/browse/WFLY-5040
Project: WildFly
Issue Type: Bug
Reporter: The Alchemist
Assignee: Jason Greene
{noformat}
21:59:01,315 INFO [org.jboss.weld.Event] (MSC service thread 1-2) WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.message.MessageBundleExtension.detectInterfaces(@Observes ProcessAnnotatedType<Object>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
21:59:01,323 INFO [org.jboss.weld.Event] (MSC service thread 1-2) WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension.vetoBeans(@Observes ProcessAnnotatedType<Object>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
21:59:01,324 INFO [org.jboss.weld.Event] (MSC service thread 1-2) WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.interceptor.GlobalInterceptorExtension.promoteInterceptors(@Observes ProcessAnnotatedType<Object>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
21:59:01,336 INFO [org.jboss.weld.Event] (MSC service thread 1-2) WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.security.impl.extension.SecurityExtension.processAnnotatedType(@Observes ProcessAnnotatedType<Object>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
21:59:01,352 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.jmx.MBeanExtension activated=true
21:59:01,353 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.message.MessageBundleExtension activated=true
21:59:01,353 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.interceptor.GlobalInterceptorExtension activated=true
21:59:01,356 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.config.ConfigurationExtension activated=true
21:59:01,356 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.exception.control.extension.ExceptionControlExtension activated=true
21:59:01,362 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension activated=true
21:59:01,362 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.exclude.CustomProjectStageBeanFilter activated=true
21:59:01,362 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.exclude.GlobalAlternative activated=true
21:59:01,363 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.core.impl.scope.DeltaSpikeContextExtension activated=true
21:59:01,363 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-2) class: org.apache.deltaspike.security.impl.extension.SecurityExtension activated=true
21:59:01,909 WARN [org.jboss.weld.Validator] (MSC service thread 1-2) WELD-001478: Interceptor class org.apache.deltaspike.security.impl.extension.SecurityInterceptor is enabled for the application and for the bean archive whatever.ear/whatever.war/WEB-INF/classes. It will only be invoked in the @Priority part of the chain.
21:59:01,910 WARN [org.jboss.weld.Validator] (MSC service thread 1-2) WELD-001478: Interceptor class org.apache.deltaspike.security.impl.extension.SecurityInterceptor is enabled for the application and for the bean archive whatever.ear/whatever.war/WEB-INF/lib/deltaspike-security-module-impl-1.4.2.jar. It will only be invoked in the @Priority part of the chain.
21:59:01,937 WARN [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-001125: Illegal bean type java.util.Comparator<javax.enterprise.inject.spi.AnnotatedConstructor<? super T>> ignored on [EnhancedAnnotatedTypeImpl] private static class org.apache.deltaspike.core.util.Annotateds$AnnotatedConstructorComparator
21:59:01,937 WARN [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-001125: Illegal bean type java.util.Comparator<javax.enterprise.inject.spi.AnnotatedCallable<? super T>> ignored on [EnhancedAnnotatedTypeImpl] private static class org.apache.deltaspike.core.util.Annotateds$AnnotatedCallableComparator
21:59:01,935 WARN [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-001125: Illegal bean type java.util.Comparator<javax.enterprise.inject.spi.AnnotatedField<? super T>> ignored on [EnhancedAnnotatedTypeImpl] private static class org.apache.deltaspike.core.util.Annotateds$AnnotatedFieldComparator
21:59:01,934 WARN [org.jboss.weld.Bootstrap] (weld-worker-1) WELD-001125: Illegal bean type java.util.Comparator<javax.enterprise.inject.spi.AnnotatedMethod<? super T>> ignored on [EnhancedAnnotatedTypeImpl] private static class org.apache.deltaspike.core.util.Annotateds$AnnotatedMethodComparator
21:59:01,945 WARN [org.jboss.weld.Bootstrap] (weld-worker-2) WELD-001125: Illegal bean type java.util.Comparator<org.apache.deltaspike.core.api.exception.control.HandlerMethod<?>> ignored on [EnhancedAnnotatedTypeImpl] public final class org.apache.deltaspike.core.impl.exception.control.ExceptionHandlerComparator
{noformat}
I'm not sure if these are meaningful or not. Is my app OK?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ]
Jason Greene commented on WFLY-4937:
------------------------------------
Hi [~tomjenkinson],
Do you mean pausing existing distributed transactions? That's an interesting point to consider. IMO it seems reasonable to allow an existing distributed transaction to prepare + commit/rollback. However, interesting things happen if additional data modification changes originating from the external node happen on the suspended node as part of the overall work of that distributed transaction. They won't be allowed to proceed, so I imagine the transaction will rollback.
More explicitly I mean something like:
server A starts transaction
server A writes to local resource AR
server A calls server B's ejb doStuff
server B's doStuff writes to local resource BR and returns
server B is suspended
server A calls server B's ejb doOtherStuff
server B rejects the call throwing an exception
server A rolls the transaction back
resource AR changes are reverted
resource BR changes are reverted, even though the node is suspended
> Implement graceful shutdown for transactions
> --------------------------------------------
>
> Key: WFLY-4937
> URL: https://issues.jboss.org/browse/WFLY-4937
> Project: WildFly
> Issue Type: Feature Request
> Components: Transactions
> Affects Versions: 10.0.0.Alpha5
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 11.0.0.Alpha1
>
>
> We will handle suspend for JTA and JTS by disallowing new transactions and then block the suspend thread until the count of active transactions drops to zero. We will also suspend the recovery manager.
> We will *not* do graceful shutdown for the optional XTS subsystem. For example an incoming XTS request for an existing transaction will be blocked.
> Question: should we
> - raise a new JIRA for this XTS case;
> - document the deficiency and see if there are complaints;
> - document the deficiency and fix it in a subsequent release
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4937:
-------------------------------
Parent: (was: WFLY-1247)
Issue Type: Feature Request (was: Sub-task)
> Implement graceful shutdown for transactions
> --------------------------------------------
>
> Key: WFLY-4937
> URL: https://issues.jboss.org/browse/WFLY-4937
> Project: WildFly
> Issue Type: Feature Request
> Components: Transactions
> Affects Versions: 10.0.0.Alpha5
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 10.0.0.Beta1
>
>
> We will handle suspend for JTA and JTS by disallowing new transactions and then block the suspend thread until the count of active transactions drops to zero. We will also suspend the recovery manager.
> We will *not* do graceful shutdown for the optional XTS subsystem. For example an incoming XTS request for an existing transaction will be blocked.
> Question: should we
> - raise a new JIRA for this XTS case;
> - document the deficiency and see if there are complaints;
> - document the deficiency and fix it in a subsequent release
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4937:
-------------------------------
Fix Version/s: 11.0.0.Alpha1
(was: 10.0.0.Beta1)
> Implement graceful shutdown for transactions
> --------------------------------------------
>
> Key: WFLY-4937
> URL: https://issues.jboss.org/browse/WFLY-4937
> Project: WildFly
> Issue Type: Feature Request
> Components: Transactions
> Affects Versions: 10.0.0.Alpha5
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 11.0.0.Alpha1
>
>
> We will handle suspend for JTA and JTS by disallowing new transactions and then block the suspend thread until the count of active transactions drops to zero. We will also suspend the recovery manager.
> We will *not* do graceful shutdown for the optional XTS subsystem. For example an incoming XTS request for an existing transaction will be blocked.
> Question: should we
> - raise a new JIRA for this XTS case;
> - document the deficiency and see if there are complaints;
> - document the deficiency and fix it in a subsequent release
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (WFLY-4634) Cannot start JDBC storage for Batch subsystem with the Driver in a deployment
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4634?page=com.atlassian.jira.plugin.... ]
James Perkins closed WFLY-4634.
-------------------------------
Resolution: Out of Date
This now works as part of WFLY-4811.
> Cannot start JDBC storage for Batch subsystem with the Driver in a deployment
> -----------------------------------------------------------------------------
>
> Key: WFLY-4634
> URL: https://issues.jboss.org/browse/WFLY-4634
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 9.0.0.CR1
> Reporter: Jan Martiska
> Assignee: James Perkins
> Priority: Critical
>
> Steps to reproduce:
> {noformat}
> - deploy JDBC driver as a deployment (postgresql93.jar in this case)
> - /subsystem=datasources/data-source=BatchProcessingDS:add(driver-name=postgresql93.jar, jndi-name="java:jboss/datasources/BatchProcessingDS", connection-url="some-url")
> - /subsystem=batch/job-repository=jdbc:write-attribute(name=jndi-name,value="java:jboss/datasources/BatchProcessingDS")
> - /subsystem=batch:write-attribute(name=job-repository-type,value=jdbc)
> - :reload
> {noformat}
> The reload fails with:
> {noformat}
> 11:45:44,391 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."postgresql93.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."postgresql93.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "postgresql93.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> 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: javax.batch.operations.BatchRuntimeException: JBERET000621: Failed to look up datasource by jndi name java:jboss/datasources/BatchProcessingDS.
> at org.jberet.repository.JdbcRepository.<init>(JdbcRepository.java:128)
> at org.jberet.repository.JdbcRepository.create(JdbcRepository.java:109)
> at org.wildfly.extension.batch.job.repository.JobRepositoryFactory.getJobRepository(JobRepositoryFactory.java:63)
> at org.wildfly.extension.batch.deployment.BatchEnvironmentProcessor.deploy(BatchEnvironmentProcessor.java:71)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> Caused by: javax.naming.NameNotFoundException: datasources/BatchProcessingDS [Root exception is java.lang.IllegalStateException]
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.doLookup(InitialContext.java:290)
> at org.jberet.repository.JdbcRepository.<init>(JdbcRepository.java:126)
> ... 9 more
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:138)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
> at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
> ... 19 more
> 11:45:44,396 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "postgresql93.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"postgresql93.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"postgresql93.jar\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"postgresql93.jar\"
> Caused by: javax.batch.operations.BatchRuntimeException: JBERET000621: Failed to look up datasource by jndi name java:jboss/datasources/BatchProcessingDS.
> Caused by: javax.naming.NameNotFoundException: datasources/BatchProcessingDS [Root exception is java.lang.IllegalStateException]
> Caused by: java.lang.IllegalStateException"}}
> 11:45:44,397 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "BatchProcessingDS")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.driver-demander.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]",
> "jboss.data-source.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]"
> ]}
> 11:45:44,398 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "BatchProcessingDS")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.driver-demander.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]",
> "jboss.data-source.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]",
> "jboss.data-source.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]"
> ]}
> {noformat}
> From reading the log, it looks to me like some sort of circular dependency problem: the JDBC driver won't start because there is a dependency on the datasource, but the datasource won't start because it has a dependency on the JDBC driver.
> This doesn't seem to happen when the JDBC driver is deployed as a module, only as a deployment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months