[JBoss JIRA] (WFLY-3017) OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3017?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3017:
-----------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092206|https://bugzilla.redhat.com/show_bug.cgi?id=1092206] from ASSIGNED to POST
> OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-3017
> URL: https://issues.jboss.org/browse/WFLY-3017
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.1.0.CR1
>
>
> The readResourceForUpdate impl makes a few assumptions regarding the fact that a given Resource represents persistent config (i.e. Resource.isRuntime() == true):
> 1) It calls rejectUserDomainServerUpdates() which means an OSH running on a server could not call this.
> 2) It calls authorize(false, READ_WRITE_CONFIG) which means an OSH for an op available to the RBAC Operator role could not call this.
> Places this impacts include LogStoreProbeHandler and LogStoreTransactionDeleteHandler which should be calling readResourceForUpdate but aren't -- and can't because of this bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years
[JBoss JIRA] (AS7-4247) Server shutdown: Problems un-registering MBeans: CacheException: Failure while unregistering mbeans
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-4247?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-4247:
----------------------------------------------
Ladislav Thon <lthon(a)redhat.com> changed the Status of [bug 917010|https://bugzilla.redhat.com/show_bug.cgi?id=917010] from ON_QA to VERIFIED
> Server shutdown: Problems un-registering MBeans: CacheException: Failure while unregistering mbeans
> ---------------------------------------------------------------------------------------------------
>
> Key: AS7-4247
> URL: https://issues.jboss.org/browse/AS7-4247
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.1.Final
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Minor
> Labels: JBAS010282, eap6_prd_req
> Fix For: 7.1.2.Final (EAP)
>
>
> Just ran into this, implications not yet known.
> {noformat}
> [JBossINF] 15:02:54,085 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,null) ISPN000094: Received new cluster view: [perf18/ejb|12] [perf18/ejb, perf20/ejb, perf21/ejb]
> [JBossINF] 15:02:54,086 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-6,null) ISPN000094: Received new cluster view: [perf18/web|12] [perf18/web, perf20/web, perf21/web]
> [JBossINF] 15:02:58,127 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.lifecycle.web] (Incoming-5,null) JBAS010247: New cluster view for partition web (id: 13, delta: -1, merge: false) : [perf18/web, perf20/web]
> [JBossINF] 15:02:58,128 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-5,null) ISPN000094: Received new cluster view: [perf18/web|13] [perf18/web, perf20/web]
> [JBossINF] 15:02:58,135 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.lifecycle.ejb] (Incoming-4,null) JBAS010247: New cluster view for partition ejb (id: 13, delta: -1, merge: false) : [perf18/ejb, perf20/ejb]
> [JBossINF] 15:02:58,136 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-4,null) ISPN000094: Received new cluster view: [perf18/ejb|13] [perf18/ejb, perf20/ejb]
> [JBossINF] 15:03:02,476 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.lifecycle.web] (Incoming-2,null) JBAS010247: New cluster view for partition web (id: 14, delta: -1, merge: false) : [perf18/web]
> [JBossINF] 15:03:02,477 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,null) ISPN000094: Received new cluster view: [perf18/web|14] [perf18/web]
> [JBossINF] 15:03:02,494 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.lifecycle.ejb] (Incoming-16,null) JBAS010247: New cluster view for partition ejb (id: 14, delta: -1, merge: false) : [perf18/ejb]
> [JBossINF] 15:03:02,495 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-16,null) ISPN000094: Received new cluster view: [perf18/ejb|14] [perf18/ejb]
> 2012/03/20 15:03:05:785 EDT [DEBUG][RMI TCP Connection(18)-10.16.90.52] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JBossApplicationServerImpl: sfTerminateWith().
> 2012/03/20 15:03:05:785 EDT [DEBUG][RMI TCP Connection(18)-10.16.90.52] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - [JBossRuntime] sfTerminateWith() invoked.
> 2012/03/20 15:03:05:790 EDT [DEBUG][Thread-33] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JBossShutdown server host: perf18
> 2012/03/20 15:03:05:829 EDT [DEBUG][RMI TCP Connection(18)-10.16.90.52] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JBossShutdown command executed successfuly.
> 2012/03/20 15:03:05:830 EDT [DEBUG][RMI TCP Connection(18)-10.16.90.52] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Waiting for server to shutdown.
> [JBossINF] 15:03:05,850 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-3) ISPN000029: Passivating all entries to disk
> [JBossINF] 15:03:05,851 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-9) Pausing Coyote HTTP/1.1 on http-perf18-10.16.90.54-8080
> [JBossINF] 15:03:05,851 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-9) Stopping Coyote HTTP/1.1 on http-perf18-10.16.90.54-8080
> [JBossINF] 15:03:05,850 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-12) ISPN000029: Passivating all entries to disk
> [JBossINF] 15:03:05,851 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-3) ISPN000030: Passivated 0 entries in 0 milliseconds
> [JBossINF] 15:03:05,855 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-12) ISPN000030: Passivated 0 entries in 4 milliseconds
> [JBossINF] 15:03:05,858 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-12) JBAS010282: Stopped org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB cache from ejb container
> [JBossINF] 15:03:05,858 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-3) JBAS010282: Stopped org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSBImpl cache from ejb container
> [JBossINF] 15:03:05,879 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
> [JBossINF] 15:03:05,904 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000029: Passivating all entries to disk
> [JBossINF] 15:03:05,904 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000030: Passivated 0 entries in 0 milliseconds
> [JBossINF] 15:03:05,907 INFO [org.jboss.as.clustering.infinispan] JBAS010282: Stopped remote-connector-client-mappings cache from ejb container
> [JBossINF] 15:03:05,913 INFO [org.jboss.as.clustering.infinispan] JBAS010282: Stopped repl cache from ejb container
> [JBossINF] 15:03:05,939 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000029: Passivating all entries to disk
> [JBossINF] 15:03:05,940 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000030: Passivated 0 entries in 0 milliseconds
> [JBossINF] 15:03:05,941 WARN [org.infinispan.jmx.CacheJmxRegistration] ISPN000032: Problems un-registering MBeans: org.infinispan.CacheException: Failure while unregistering mbeans
> [JBossINF] at org.infinispan.jmx.ComponentsJmxRegistration.unregisterMBeans(ComponentsJmxRegistration.java:105)
> [JBossINF] at org.infinispan.jmx.AbstractJmxRegistration.unregisterMBeans(AbstractJmxRegistration.java:53)
> [JBossINF] at org.infinispan.jmx.CacheJmxRegistration.stop(CacheJmxRegistration.java:100)
> [JBossINF] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
> [JBossINF] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
> [JBossINF] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
> [JBossINF] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
> [JBossINF] at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:236)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:882)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:672)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:551)
> [JBossINF] at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:198)
> [JBossINF] at org.infinispan.CacheImpl.stop(CacheImpl.java:516)
> [JBossINF] at org.infinispan.DecoratedCache.stop(DecoratedCache.java:129)
> [JBossINF] at org.infinispan.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:291)
> [JBossINF] at org.infinispan.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:291)
> [JBossINF] at org.jboss.as.clustering.web.infinispan.DistributedCacheManager.stop(DistributedCacheManager.java:127)
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.stop(DistributableSessionManager.java:447) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> [JBossINF] at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3995) [jbossweb-7.0.13.Final.jar:]
> [JBossINF] at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:108) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> [JBossINF] Caused by: javax.management.InstanceNotFoundException: jboss.infinispan:type=Cache,name="//default-host//clusterbench(repl_async)",manager="web",component=Activation
> [JBossINF] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094) [rt.jar:1.6.0_30]
> [JBossINF] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:415) [rt.jar:1.6.0_30]
> [JBossINF] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:403) [rt.jar:1.6.0_30]
> [JBossINF] at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:506) [rt.jar:1.6.0_30]
> [JBossINF] at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.unregisterMBean(PluggableMBeanServerImpl.java:584)
> [JBossINF] at org.jboss.as.jmx.PluggableMBeanServerImpl.unregisterMBean(PluggableMBeanServerImpl.java:331)
> [JBossINF] at org.infinispan.jmx.JmxUtil.unregisterMBean(JmxUtil.java:109)
> [JBossINF] at org.infinispan.jmx.ComponentsJmxRegistration.unregisterMBeans(ComponentsJmxRegistration.java:101)
> [JBossINF] ... 24 more
> [JBossINF]
> [JBossINF] 15:03:05,955 INFO [org.jboss.as.clustering.infinispan] JBAS010282: Stopped //default-host//clusterbench cache from web container
> [JBossINF] 15:03:05,979 INFO [org.jboss.weld.deployer] JBAS016009: Stopping weld service for deployment clusterbench-ee6.ear
> [JBossINF] 15:03:05,992 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000029: Passivating all entries to disk
> [JBossINF] 15:03:05,993 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000030: Passivated 0 entries in 0 milliseconds
> [JBossINF] 15:03:06,016 INFO [org.jboss.as.clustering.infinispan] JBAS010282: Stopped repl cache from web container
> [JBossINF] 15:03:06,025 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
> [JBossINF] 15:03:06,025 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
> [JBossINF] 15:03:06,030 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment clusterbench-ee6-ejb.jar in 172ms
> [JBossINF] 15:03:06,032 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment clusterbench-ee6-web.war in 173ms
> [JBossINF] 15:03:06,052 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment clusterbench-ee6.ear in 197ms
> [JBossINF] 15:03:06,074 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher
> [JBossINF] 15:03:06,102 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher
> [JBossINF] 15:03:06,150 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" stopped in 290ms
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years
[JBoss JIRA] (WFLY-3104) datasource created with console cannot be enabled
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-3104?page=com.atlassian.jira.plugin.... ]
Stefano Maestri commented on WFLY-3104:
---------------------------------------
There is 2 different problem here. Because of changes introduced fixing WFLY-1460 jta attribute should be reload required. I'll change this as President for this issue, BUT the main problem here is on Web console setting jta to false, while default value is true. Jta false is only for special user's case or for what WFLY-1460 is describing. I'm opening an HAL issue on that
> datasource created with console cannot be enabled
> -------------------------------------------------
>
> Key: WFLY-3104
> URL: https://issues.jboss.org/browse/WFLY-3104
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Final
> Environment: Wildfly 8.0.0 Final
> Reporter: Gabriele Garuglieri
> Assignee: Stefano Maestri
>
> Consider the following cli file:
> {noformat}
> /subsystem=datasources/data-source=fai-bfsa:add( \
> driver-name=PostgresJDBCDriver, \
> driver-class="org.postgresql.Driver", \
> jndi-name=java:jboss/jdbc/fai-bfsa, \
> connection-url=jdbc:postgresql://tpg0001:5432/xfgb01, \
> max-pool-size=20, \
> min-pool-size=10, \
> new-connection-sql="select 1", \
> check-valid-connection-sql="select 1", \
> user-name=uuuuu, \
> password=uuuuu, \
> background-validation=false, \
> validate-on-match=false, \
> enabled=false, \
> jta=true, \
> use-ccm=true, \
> share-prepared-statements=false, \
> )
> {noformat}
> This is reflected into standalone-full.xml as:
> {code:xml}
> <datasource jta="true" jndi-name="java:jboss/jdbc/fai-bfsa" pool-name="fai-bfsa" enabled="false" use-ccm="true">
> <connection-url>jdbc:postgresql://tpg0001:5432/xfgb01</connection-url>
> <driver-class>org.postgresql.Driver</driver-class>
> <driver>PostgresJDBCDriver</driver>
> <new-connection-sql>select 1</new-connection-sql>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>20</max-pool-size>
> </pool>
> <security>
> <user-name>uuuuu</user-name>
> <password>uuuuu</password>
> </security>
> <validation>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <validate-on-match>false</validate-on-match>
> <background-validation>false</background-validation>
> </validation>
> <statement>
> <share-prepared-statements>false</share-prepared-statements>
> </statement>
> </datasource>
> {code}
> I can now enable and disable that datasource both via cli or console without problem.
> If i create the same datasource via console, with the very same attributes, producing the very same standalone-full.xml (i have diffed them), i cannot enable it nether via cli nor console because i get the following error:
> {noformat}
> 14:33:00,230 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-3) Error during the deployment of java:jboss/jdbc/fai-bfsa: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.getTransactionIntegration(AbstractDataSourceService.java:409)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.createMcf(AbstractDataSourceService.java:461)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:430)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:283)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:310)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:124)
> 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:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> 14:33:00,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.data-source.java:jboss/jdbc/fai-bfsa: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/jdbc/fai-bfsa: JBAS010433: Error during the deployment of fai-bfsa
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:131)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010432: Unable to start the ds because it generated more than one cf
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:126)
> ... 5 more
> 14:33:00,242 INFO [org.jboss.as.controller] (XNIO-4 task-2) JBAS014774: Servicestatus report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.data-source.reference-factory.fai-bfsa (missing) dependents:[service jboss.naming.context.java.jboss.jdbc.fai-bfsa]
> service jboss.data-source-config.fai-bfsa (missing) dependents: [service jboss.data-source.java:jboss/jdbc/fai-bfsa]
> JBAS014777: Services which failed to start: service jboss.data-source.java:jboss/jdbc/fai-bfsa
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years
[JBoss JIRA] (WFLY-3104) datasource created with console cannot be enabled
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-3104?page=com.atlassian.jira.plugin.... ]
Stefano Maestri commented on WFLY-3104:
---------------------------------------
There is 2 different problem here. Because of changes introduced fixing WFLY-1460 jta attribute should be reload required. I'll change this as President for this issue, BUT the main problem here is on Web console setting jta to false, while default value is true. Jta false is only for special user's case or for what WFLY-1460 is describing. I'm opening an HAL issue on that
> datasource created with console cannot be enabled
> -------------------------------------------------
>
> Key: WFLY-3104
> URL: https://issues.jboss.org/browse/WFLY-3104
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Final
> Environment: Wildfly 8.0.0 Final
> Reporter: Gabriele Garuglieri
> Assignee: Stefano Maestri
>
> Consider the following cli file:
> {noformat}
> /subsystem=datasources/data-source=fai-bfsa:add( \
> driver-name=PostgresJDBCDriver, \
> driver-class="org.postgresql.Driver", \
> jndi-name=java:jboss/jdbc/fai-bfsa, \
> connection-url=jdbc:postgresql://tpg0001:5432/xfgb01, \
> max-pool-size=20, \
> min-pool-size=10, \
> new-connection-sql="select 1", \
> check-valid-connection-sql="select 1", \
> user-name=uuuuu, \
> password=uuuuu, \
> background-validation=false, \
> validate-on-match=false, \
> enabled=false, \
> jta=true, \
> use-ccm=true, \
> share-prepared-statements=false, \
> )
> {noformat}
> This is reflected into standalone-full.xml as:
> {code:xml}
> <datasource jta="true" jndi-name="java:jboss/jdbc/fai-bfsa" pool-name="fai-bfsa" enabled="false" use-ccm="true">
> <connection-url>jdbc:postgresql://tpg0001:5432/xfgb01</connection-url>
> <driver-class>org.postgresql.Driver</driver-class>
> <driver>PostgresJDBCDriver</driver>
> <new-connection-sql>select 1</new-connection-sql>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>20</max-pool-size>
> </pool>
> <security>
> <user-name>uuuuu</user-name>
> <password>uuuuu</password>
> </security>
> <validation>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <validate-on-match>false</validate-on-match>
> <background-validation>false</background-validation>
> </validation>
> <statement>
> <share-prepared-statements>false</share-prepared-statements>
> </statement>
> </datasource>
> {code}
> I can now enable and disable that datasource both via cli or console without problem.
> If i create the same datasource via console, with the very same attributes, producing the very same standalone-full.xml (i have diffed them), i cannot enable it nether via cli nor console because i get the following error:
> {noformat}
> 14:33:00,230 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-3) Error during the deployment of java:jboss/jdbc/fai-bfsa: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.getTransactionIntegration(AbstractDataSourceService.java:409)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.createMcf(AbstractDataSourceService.java:461)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:430)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:283)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:310)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:124)
> 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:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> 14:33:00,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.data-source.java:jboss/jdbc/fai-bfsa: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/jdbc/fai-bfsa: JBAS010433: Error during the deployment of fai-bfsa
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:131)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010432: Unable to start the ds because it generated more than one cf
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:126)
> ... 5 more
> 14:33:00,242 INFO [org.jboss.as.controller] (XNIO-4 task-2) JBAS014774: Servicestatus report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.data-source.reference-factory.fai-bfsa (missing) dependents:[service jboss.naming.context.java.jboss.jdbc.fai-bfsa]
> service jboss.data-source-config.fai-bfsa (missing) dependents: [service jboss.data-source.java:jboss/jdbc/fai-bfsa]
> JBAS014777: Services which failed to start: service jboss.data-source.java:jboss/jdbc/fai-bfsa
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years
[JBoss JIRA] (DROOLS-473) Drools spawning a lot of JIT threads
by Frank Pavageau (JIRA)
Frank Pavageau created DROOLS-473:
-------------------------------------
Summary: Drools spawning a lot of JIT threads
Key: DROOLS-473
URL: https://issues.jboss.org/browse/DROOLS-473
Project: Drools
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 5.5.0.Final
Reporter: Frank Pavageau
Assignee: Mark Proctor
{{MvelConstraint}} submits JIT tasks to an {{Executor}} once it has been evaluated enough times, but that {{Executor}} created by {{ExecutorProviderImpl}} is a basic {{CachedThreadPool}} which can create an unbounded number of threads (though they die after idling for a minute).
Firing a lot of rules quickly can create several hundreds threads. If you have several JVMs on the same machine processing the same kind of load, it can saturate the OS and result in errors as the JVMs cannot create native threads anymore.
The maximum size of the thread pool should probably be limited to a more reasonable default, maybe with a configurable value.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years