[JBoss JIRA] (WFLY-1701) Race condition during server start-up - RA not deployed
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1701?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1701:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 984855|https://bugzilla.redhat.com/show_bug.cgi?id=984855] from MODIFIED to ON_QA
> Race condition during server start-up - RA not deployed
> -------------------------------------------------------
>
> Key: WFLY-1701
> URL: https://issues.jboss.org/browse/WFLY-1701
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Alpha2
> Environment: JBoss EAP 6.1, MS Windows server
> Reporter: Tom Ross
> Assignee: Stefano Maestri
> Priority: Blocker
> Fix For: 8.0.0.Final
>
>
> A custom RA is not being deployed every during server restart even though it is linked to a MDB via @ResourceAdpater annotation. This only happens during server startup. The RA can be deployed successfully via jboss cli every time. When the deployment fails the following message appear in the log file:
> 11:30:45,303 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.ra.cdd-ra (missing) dependents: [service jboss.deployment.unit."dmgapp.jar".component.CddListenerClientMDB.CREATE]
> When comparing the log file from a successful startup with one from a failed one the only difference seems to be the absence of any output from RaXmlDeployer. See below:
> Successful startup:
> {noformat}
> 11:29:24,991 DEBUG [org.jboss.as.connector.logging] (MSC service thread 1-6) starting Inactive:InactiveResourceAdapterDeployment{module=Module "deployment.cdd-ra.rar:main" from Service Module Loader, connectorXmlDescriptor=org.jboss.as.connector.metadata.xmldescriptors.ConnectorXmlDescriptor@23322e4, deployment='cdd-ra', deploymentUnitName='cdd-ra.rar', registration=org.jboss.as.controller.registry.ConcreteResourceRegistration@6b37a7dc, serviceTarget=org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget@12ed9382}
> 11:29:24,991 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-6) DEPLOYMENT name = cdd-ra
> 11:29:24,994 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) Connector=<?xml version="1.0" encoding="UTF-8"?><connector version="1.5"><display-name>DMG CDD Resource Adapter</display-name><vendor-name>Cassidian</vendor-name><eis-type>CDD Server</eis-type><resourceadapter-version>1.0</resourceadapter-version><resourceadapter><resourceadapter-class>com.xx-yy.dmg.jca.eis.CddResourceAdapter</resourceadapter-class><outbound-resourceadapter><connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition><transaction-support>NoTransaction</transaction-support><reauthentication-support>false</reauthentication-support></outbound-resourceadapter><inbound-resourceadapter><messageadapter><messagelistener><messagelistener-type>javax.resource.cci.MessageListener</messagelistener-type><activationspec><activationspec-class>com.xx-yy.dmg.jca.eis.CddActivationSpec</activationspec-class><required-config-property><config-property-name>hostname</config-property-name></required-config-property><required-config-property><config-property-name>port</config-property-name></required-config-property><required-config-property><config-property-name>timeout</config-property-name></required-config-property></activationspec></messagelistener></messageadapter></inbound-resourceadapter></resourceadapter></connector>
> 11:29:24,995 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) IronJacamar=null
> 11:29:24,996 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) RaXML=null
> 11:29:24,996 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) ActivateDeployment=false
> 11:29:24,998 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) CdMeta: <connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition>
> 11:29:25,000 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) No activation: com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory
> 11:29:25,001 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-6) Registering ResourceAdapter cdd-ra
> 11:29:25,005 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) Activated: file:/C:/jboss-eap-6.1_test/standalone/tmp/vfs/temp7ab26b3b80d7102a/cdd-ra.rar-eb8a8dd4a3f65805/contents/
> 11:29:25,005 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-6) Not activating: cdd-ra
> 11:29:25,009 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) Connector=<?xml version="1.0" encoding="UTF-8"?><connector version="1.5"><display-name>DMG CDD Resource Adapter</display-name><vendor-name>Cassidian</vendor-name><eis-type>CDD Server</eis-type><resourceadapter-version>1.0</resourceadapter-version><resourceadapter><resourceadapter-class>com.xx-yy.dmg.jca.eis.CddResourceAdapter</resourceadapter-class><outbound-resourceadapter><connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition><transaction-support>NoTransaction</transaction-support><reauthentication-support>false</reauthentication-support></outbound-resourceadapter><inbound-resourceadapter><messageadapter><messagelistener><messagelistener-type>javax.resource.cci.MessageListener</messagelistener-type><activationspec><activationspec-class>com.xx-yy.dmg.jca.eis.CddActivationSpec</activationspec-class><required-config-property><config-property-name>hostname</config-property-name></required-config-property><required-config-property><config-property-name>port</config-property-name></required-config-property><required-config-property><config-property-name>timeout</config-property-name></required-config-property></activationspec></messagelistener></messageadapter></inbound-resourceadapter></resourceadapter></connector>
> 11:29:25,010 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) IronJacamar=null
> 11:29:25,010 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) RaXML=<resource-adapter><archive>cdd-ra.rar</archive><transaction-support>NoTransaction</transaction-support><connection-definitions><connection-definition class-name="com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory" jndi-name="java:jboss/ra/cdd-connector" enabled="true" use-java-context="true" pool-name="ra/cdd-connector" use-ccm="false"><config-property name="port">42006</config-property><config-property name="probeTimeout">10</config-property><config-property name="timeout">45</config-property><config-property name="hostname">localhost</config-property><pool><min-pool-size>0</min-pool-size><max-pool-size>1</max-pool-size><prefill>false</prefill><use-strict-min>false</use-strict-min><flush-strategy>FailingConnectionOnly</flush-strategy></pool><timeout><blocking-timeout-millis>60000</blocking-timeout-millis></timeout><validation><background-validation>false</background-validation><use-fast-fail>false</use-fast-fail></validation></connection-definition></connection-definitions></resource-adapter>
> 11:29:25,012 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) ActivateDeployment=true
> 11:29:25,014 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) ResourceAdapter: com.xx-yy.dmg.jca.eis.CddResourceAdapter
> 11:29:25,014 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) ResourceAdapter defined in classloader: ModuleClassLoader for Module "deployment.cdd-ra.rar:main" from Service Module Loader
> 11:29:25,014 DEBUG [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) CdMeta: <connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition>
> 11:29:25,015 DEBUG [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) ConnectionDefinitions: 1
> 11:29:25,017 DEBUG [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) Activating: <connection-definition class-name="com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory" jndi-name="java:jboss/ra/cdd-connector" enabled="true" use-java-context="true" pool-name="ra/cdd-connector" use-ccm="false"><config-property name="port">42006</config-property><config-property name="probeTimeout">10</config-property><config-property name="timeout">45</config-property><config-property name="hostname">localhost</config-property><pool><min-pool-size>0</min-pool-size><max-pool-size>1</max-pool-size><prefill>false</prefill><use-strict-min>false</use-strict-min><flush-strategy>FailingConnectionOnly</flush-strategy></pool><timeout><blocking-timeout-millis>60000</blocking-timeout-millis></timeout><validation><background-validation>false</background-validation><use-fast-fail>false</use-fast-fail></validation></connection-definition>
> 11:29:25,018 INFO [com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory] (MSC service thread 1-6) setPort() called.
> 11:29:25,019 INFO [com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory] (MSC service thread 1-6) setProbeTiemout() called.
> 11:29:25,021 INFO [com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory] (MSC service thread 1-6) setTimeout() called.
> 11:29:25,021 INFO [com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory] (MSC service thread 1-6) setHostname() called.
> {noformat}
> Failed startup:
> {noformat}
> 11:30:44,391 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-5) DEPLOYMENT name = cdd-ra
> 11:30:44,402 TRACE [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-8) DataSource=<datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true" spy="false" use-ccm="true" jta="true"><connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url><driver>h2</driver><pool><min-pool-size>0</min-pool-size><max-pool-size>20</max-pool-size><prefill>false</prefill><use-strict-min>false</use-strict-min><flush-strategy>FailingConnectionOnly</flush-strategy></pool><security><user-name>sa</user-name><password>sa</password></security><validation><validate-on-match>false</validate-on-match><background-validation>false</background-validation><use-fast-fail>false</use-fast-fail></validation><timeout></timeout><statement><track-statements>nowarn</track-statements></statement></datasource>
> 11:30:44,408 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) Connector=<?xml version="1.0" encoding="UTF-8"?><connector version="1.5"><display-name>DMG CDD Resource Adapter</display-name><vendor-name>Cassidian</vendor-name><eis-type>CDD Server</eis-type><resourceadapter-version>1.0</resourceadapter-version><resourceadapter><resourceadapter-class>com.xx-yy.dmg.jca.eis.CddResourceAdapter</resourceadapter-class><outbound-resourceadapter><connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition><transaction-support>NoTransaction</transaction-support><reauthentication-support>false</reauthentication-support></outbound-resourceadapter><inbound-resourceadapter><messageadapter><messagelistener><messagelistener-type>javax.resource.cci.MessageListener</messagelistener-type><activationspec><activationspec-class>com.xx-yy.dmg.jca.eis.CddActivationSpec</activationspec-class><required-config-property><config-property-name>hostname</config-property-name></required-config-property><required-config-property><config-property-name>port</config-property-name></required-config-property><required-config-property><config-property-name>timeout</config-property-name></required-config-property></activationspec></messagelistener></messageadapter></inbound-resourceadapter></resourceadapter></connector>
> 11:30:44,410 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) IronJacamar=null
> 11:30:44,410 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) RaXML=null
> 11:30:44,410 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) ActivateDeployment=false
> 11:30:44,445 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) CdMeta: <connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition>
> 11:30:44,450 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) No activation: com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory
> 11:30:44,452 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-5) Registering ResourceAdapter cdd-ra
> 11:30:44,453 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) Activated: file:/C:/jboss-eap-6.1_test/standalone/tmp/vfs/temp3cf601edad306224/cdd-ra.rar-5ec7930ccabd45d/contents/
> 11:30:44,454 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-5) Not activating: cdd-ra
> 11:30:44,468 DEBUG [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-8) Adding management datasource: DataSource@1f69b08 xa=false jndiName=java:jboss/datasources/ExampleDS pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@653c2b39 poolconfiguration=PoolConfiguration@5139df1b[minSize=0 maxSize=20 blockingTimeout=30000 idleTimeoutMinutes=30 backgroundValidation=false backgroundValidationMillis=0 prefill=false strictMin=false useFastFail=false] statistics=org.jboss.jca.adapters.jdbc.statistics.JdbcStatisticsPlugin@2e668f46]
> 11:30:44,482 DEBUG [org.jboss.as.connector.deployer.dsdeployer] (MSC service thread 1-8) Adding datasource: java:jboss/datasources/ExampleDS
> 11:30:44,485 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 11:30:44,578 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221034: Waiting to obtain live lock
> {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
12 years, 5 months
[JBoss JIRA] (WFLY-406) Redesign web session clustering
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-406?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on WFLY-406:
----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1039585|https://bugzilla.redhat.com/show_bug.cgi?id=1039585] from MODIFIED to ON_QA
> Redesign web session clustering
> -------------------------------
>
> Key: WFLY-406
> URL: https://issues.jboss.org/browse/WFLY-406
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Clustering
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Alpha2
>
>
> The current web session replication code has been around for ages and suffers from a number of issues:
> * By maintaining a separate local map of sessions in conjunction with the session data stored in the distributed cache, stale data is inevitable - a number of issues have cropped up in EAP testing.
> * Extra concurrency measures are required to ensure synchronicity of the local session map with the distributed cache.
> * Extra logic/locking is required to invalidate the local session map is required per request
> * AtomicMaps, on which the current implementation relies, have proven buggy
> * Session access outside of the scope of the replication valve is possible and problematic
> * Maintaining sessions locally means that the clustering code needs to implement passivation and expiration manually - instead of leveraging Infinispan full capabilities.
> * The current code base is tightly coupled to JBoss Web. Migrating the code to support Undertow will inevitably introduce issues and code duplication.
> The new design will incorporate a proper SPI for the servlet container. Thus the logic to integrate with Undertow vs JBoss Web will be relatively thin.
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2697) Domain Mode does not start with the IBM JDK
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2697?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2697:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1047515|https://bugzilla.redhat.com/show_bug.cgi?id=1047515] from MODIFIED to ON_QA
> Domain Mode does not start with the IBM JDK
> -------------------------------------------
>
> Key: WFLY-2697
> URL: https://issues.jboss.org/browse/WFLY-2697
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.CR1
> Environment: Windows (OS), IBM JDK 7
> Reporter: Eric Rich
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Final
>
>
> When starting domain mode with the IBM JDK the following is produced 3 out of 4 times.
> [Host Controller] 16:44:06,419 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("start") failed - address: ([
> [Host Controller] ("host" => "master"),
> [Host Controller] ("server-config" => "server-one")
> [Host Controller] ]): java.lang.IllegalStateException: JBAS010986: Host-Controller is already shutdown.
> [Host Controller] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:175)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.startServer(DomainModelControllerService.java:781)
> [Host Controller] at org.jboss.as.host.controller.operations.ServerStartHandler$1.execute(ServerStartHandler.java:107)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:607) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:485) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282)
> [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277) [jbo
> ss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:231) [jboss-as-contr
> oller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:137) [jboss-as-controller-7.
> 3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(Mode
> lControllerClientOperationHandler.java:173) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(Mod
> elControllerClientOperationHandler.java:105) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelC
> ontrollerClientOperationHandler.java:125) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelC
> ontrollerClientOperationHandler.java:121) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at java.security.AccessController.doPrivileged(AccessController.java:366) [vm.jar:1.7.0]
> [Host Controller] at javax.security.auth.Subject.doAs(Subject.java:572) [rt.jar:1.7.0]
> [Host Controller] at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.3.0.Fi
> nal-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(Mode
> lControllerClientOperationHandler.java:121) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283) [jboss-a
> s-protocol-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504) [j
> boss-as-protocol-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) [rt.jar:1.7.0]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626) [rt.jar:1.7.0]
> [Host Controller] at java.lang.Thread.run(Thread.java:804) [vm.jar:1.7.0]
> [Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Fin
> al-redhat-1]
> [Host Controller]
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-898) SharedLocalYieldingLockManager.LocalLock
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-898?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on WFLY-898:
----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1039585|https://bugzilla.redhat.com/show_bug.cgi?id=1039585] from MODIFIED to ON_QA
> SharedLocalYieldingLockManager.LocalLock
> ----------------------------------------
>
> Key: WFLY-898
> URL: https://issues.jboss.org/browse/WFLY-898
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Reporter: MJ Kim
> Assignee: Paul Ferraro
>
> Hi,
>
> Recently my system has been in the QA. (includes Stress test, Endurance test)
> During the endurance test, I found that the heap space was getting exausted, and not removed after full gc.
> When the heap space got close to 90%, the gabage collection was happend every 2 min, and my system was stopped reponding.
> The heap space was not cleaned up, nevertheless I ended the test (no request during a few hours)
>
>
> I downloaded some heap dumps, and found that the SharedLocalYieldingLockManage.LocalLock() resided much of heap space. (above 60%)
> I think the session expiration doesn't operate porperly.
>
> If the SessionBasesClusteredSession class raises the expiration signals with "LocalOnly=True", the lock would not be removed.
>
> Addionally, I reviewed our source code and did a leakage discory test, anything was matter.
>
> Here is my environment. If you want to see my standalone.xml, please post a reply thread.
>
> <Cluster>
> - 8 JVM (4 machine, each 2)
> - JDK : 1.6u31
> - OS : Amazon Linux 64bit
> - JGroups : FILE_PING (The shared storage is GlusterFS volume)
> - Infinispan operation mode : L1 + Distribution / ASYNC / expiration 1min
> - Session handling : web.xml (expiration every 1min)
> (Originally our setting was 30 min. Beacuse the load generator was sending too many requests with new session, I lowered the threshold to 1min)
> - Source code : 7.1.3 Final tag (downloaded from Github)
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2840) @Schedule EJB Timer not using timezone when calculating next timeout
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2840?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2840:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1059911|https://bugzilla.redhat.com/show_bug.cgi?id=1059911] from MODIFIED to ON_QA
> @Schedule EJB Timer not using timezone when calculating next timeout
> --------------------------------------------------------------------
>
> Key: WFLY-2840
> URL: https://issues.jboss.org/browse/WFLY-2840
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Affects Versions: 8.0.0.CR1
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: 8.0.0.Final
>
>
> With a system running in Central Timezone, if it uses the annotation below specifying the timezone as Eastern timezone, with the hour set to the current hour.
> The timer will fire once, and it will calculate the next timeout to be in the next hour CST, where as it should take in consideration the timezone specified on @Schedule which is Eastern. If it did, then the timer should continue to fire every minute.
> {code}
> @Schedule(persistent = false, timezone = "America/New_York", dayOfMonth = "*", dayOfWeek = "*", month = "*", hour = "22", minute = "*", second = "0", year = "*")
> {code}
> 21:53:00,006 INFO [stdout] (EJB default - 1) ScheduleTest: nextTimeout:Wed Jan 29 22:00:00 CST 2014
> {code}
> import javax.ejb.Schedule;
> import javax.ejb.Singleton;
> import javax.ejb.Startup;
> @Startup
> @Singleton
> public class ScheduleTest {
> @Schedule(persistent = false, timezone = "America/New_York", dayOfMonth = "*", dayOfWeek = "*", month = "*", hour = "22", minute = "*", second = "0", year = "*")
> public void helloWorld(Timer time) {
> System.out.println("ScheduleTest: timer:" + time.getClass().getName() + " " + time.getNextTimeout() + " " + time.getInfo());
> }
> }
> {code}
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2851) Can't validate jboss-deployment-structure.xml due to incorrect schema
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2851?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2851:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1060719|https://bugzilla.redhat.com/show_bug.cgi?id=1060719] from MODIFIED to ON_QA
> Can't validate jboss-deployment-structure.xml due to incorrect schema
> ---------------------------------------------------------------------
>
> Key: WFLY-2851
> URL: https://issues.jboss.org/browse/WFLY-2851
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.0.0.CR1
> Reporter: Harald Wellmann
> Assignee: Stuart Douglas
> Fix For: 8.0.0.Final
>
>
> The following deployment structure cannot be validated against the XML schema:
> {code:xml}
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <dependencies>
> <module name="foo"/>
> </dependencies>
> </deployment>
> </jboss-deployment-structure>
> {code}
> This looks like a glitch in the schema where the {{module-alias}} element in {{deploymentType}} is missing a {{minOccurs="0"}}.
> The same holds for the {{filter}} element of {{resource-root}}, which should be optional according to the schema documentation.
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2633) Cannot use deployments with same runtime-name in a domain
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2633?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2633:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1040621|https://bugzilla.redhat.com/show_bug.cgi?id=1040621] from MODIFIED to ON_QA
> Cannot use deployments with same runtime-name in a domain
> ---------------------------------------------------------
>
> Key: WFLY-2633
> URL: https://issues.jboss.org/browse/WFLY-2633
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.CR1
>
>
> The check for duplicate runtime-name in a server group on startup is too aggressive. It is incorrectly throwing an error on startup if there are any duplicate runtime-names in the whole domain, instead of just in a single server group.
> Steps to Reproduce:
> 1. Start a single HC/DC
> 2. deploy --name=foo1 --runtime-name=bar --disabled testfile
> 3. deploy --name=foo2 --runtime-name=bar --disabled testfile
> 4. restart the DC/HC
> Actual results:
> JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> ...
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1348,9]
> ...
> Message: JBAS014664: An element of this type named 'bar' has already been declared
> Expected results:
> No errors
--
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
12 years, 5 months
[JBoss JIRA] (JBWEB-281) Inconsistent use of genStringAsCharArray.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBWEB-281?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBWEB-281:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1050225|https://bugzilla.redhat.com/show_bug.cgi?id=1050225] from MODIFIED to ON_QA
> Inconsistent use of genStringAsCharArray.
> -----------------------------------------
>
> Key: JBWEB-281
> URL: https://issues.jboss.org/browse/JBWEB-281
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Tomcat
> Affects Versions: JBossWeb-7.2.1.GA
> Environment: All environments.
> Reporter: Jeremy Whiting
> Assignee: Remy Maucherat
> Fix For: JBossWeb-7.3.0.GA
>
>
> The JSP configuration property "genStringAsCharArray" is inconsistently named in jbossweb. This means the enabling of the feature for using char array type rather than String in generated Servlet code is not enabled.
> This issue has been fixed upstream in the 7.0 branch of Tomcat hosted at Apache.
> Can this patch be ported to jbossweb so that the 6.2 version of EAP includes this fix ?
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2593) Memory leak in JBoss AS / Hibernate JPA integration
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2593?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2593:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1040733|https://bugzilla.redhat.com/show_bug.cgi?id=1040733] from MODIFIED to ON_QA
> Memory leak in JBoss AS / Hibernate JPA integration
> ---------------------------------------------------
>
> Key: WFLY-2593
> URL: https://issues.jboss.org/browse/WFLY-2593
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JPA / Hibernate
> Affects Versions: No Release
> Environment: JBoss 7.1.1
> JBoss EAP 6.2 beta
> Reporter: Michael Kozak
> Assignee: Scott Marlow
> Priority: Critical
> Fix For: No Release
>
> Attachments: jmxp.ear.ear, jmxp.tar.gz
>
>
> The leak exists in AS integration code with Hibernate JPA.
> When a persistence unit is deployed which has 2nd level cache and statistics enabled each query for "query-cache" elements produces new elements.
> The issue lies in org.jboss.as.jpa.hibernate4.management.HibernateStatisticsResource. getQueryNames() method requests query names from Hibernate and applies QueryName.queryName(query).getDisplayName() to change names. Then for all queries hasQuery() is called which invokes stats.getQueryStatistics(). Within this method Hibernate creates a new object to track the statistics because the name is not found.
> Possible solution is to reverse the work done by getDisplayName() but I'm not sure if it's the right thing to do.
> This issue arised when we deployed jmxproxy application which was queried from Zabbix installation. For some MBean queries the implementation visits all MBeans deployed on the server. This kills the JVM after about 7 days.
--
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
12 years, 5 months