[JBoss JIRA] (WFLY-6965) Audit @Ignore-d clustering integration tests
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6965?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-6965 at 8/19/16 6:44 AM:
---------------------------------------------------------------
Analyzed and enabled 4 cases in a PR https://github.com/wildfly/wildfly/pull/9131
RemoteFailoverTestCase already has PR submitted since 2015.
Fine/CoarseSessionPassivationTestCase fail intermittently probably due to Infinispan issue.
WFLY-835 is being fixed by Mike M.
was (Author: rhusar):
Analyzed and enabled 4 cases in a PR https://github.com/wildfly/wildfly/pull/9131
RemoteFailoverTestCase already has PR submitted since 2015.
Fine/CoarseSessionPassivationTestCase fail intermittently probably due to Infinispan issue.
> Audit @Ignore-d clustering integration tests
> --------------------------------------------
>
> Key: WFLY-6965
> URL: https://issues.jboss.org/browse/WFLY-6965
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 10.1.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 11.0.0.Alpha1
>
>
> Recently stumbling upon an @Ignore-d test which would have caught a regression, we need to audit ignored clustering tests, e.g. some are referencing already fixed issues.
> {noformat}
> [rhusar@syrah clustering]$ git grep @Ignore
> src/test/java/org/jboss/as/test/clustering/cluster/ejb/remote/RemoteFailoverTestCase.java: @Ignore("WFLY-3532")
> src/test/java/org/jboss/as/test/clustering/cluster/ejb/stateful/StatefulFailoverTestCase.java: @Ignore("WFLY-835 @Resource UserTransaction error when file passivation store is selected")
> src/test/java/org/jboss/as/test/clustering/cluster/web/passivation/CoarseSessionPassivationTestCase.java:@Ignore("WFLY-6624")
> src/test/java/org/jboss/as/test/clustering/cluster/web/passivation/FineSessionPassivationTestCase.java:@Ignore("WFLY-6624")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/passivation/ClusterPassivationTestCase.java: @Ignore("JBPAPP-8774")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/dd/RemoteEJB2ClientStatefulBeanFailoverDDTestCase.java: @Ignore("JBPAPP-8726")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/dd/RemoteEJB2ClientStatefulBeanFailoverDDTestCase.java: @Ignore("JBPAPP-8726")
> src/test/java/org/jboss/as/test/clustering/single/jdbcstore/TransactionalJdbcStoreTestCase.java:@Ignore("https://issues.jboss.org/browse/ISPN-604")
> src/test/java/org/jboss/as/test/clustering/xsite/XSiteSimpleTestCase.java: @Ignore("https://issues.jboss.org/browse/WFLY-5239")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6965) Audit @Ignore-d clustering integration tests
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6965?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6965:
---------------------------------
Fix Version/s: 11.0.0.Alpha1
> Audit @Ignore-d clustering integration tests
> --------------------------------------------
>
> Key: WFLY-6965
> URL: https://issues.jboss.org/browse/WFLY-6965
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 10.1.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 11.0.0.Alpha1
>
>
> Recently stumbling upon an @Ignore-d test which would have caught a regression, we need to audit ignored clustering tests, e.g. some are referencing already fixed issues.
> {noformat}
> [rhusar@syrah clustering]$ git grep @Ignore
> src/test/java/org/jboss/as/test/clustering/cluster/ejb/remote/RemoteFailoverTestCase.java: @Ignore("WFLY-3532")
> src/test/java/org/jboss/as/test/clustering/cluster/ejb/stateful/StatefulFailoverTestCase.java: @Ignore("WFLY-835 @Resource UserTransaction error when file passivation store is selected")
> src/test/java/org/jboss/as/test/clustering/cluster/web/passivation/CoarseSessionPassivationTestCase.java:@Ignore("WFLY-6624")
> src/test/java/org/jboss/as/test/clustering/cluster/web/passivation/FineSessionPassivationTestCase.java:@Ignore("WFLY-6624")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/passivation/ClusterPassivationTestCase.java: @Ignore("JBPAPP-8774")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/dd/RemoteEJB2ClientStatefulBeanFailoverDDTestCase.java: @Ignore("JBPAPP-8726")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/dd/RemoteEJB2ClientStatefulBeanFailoverDDTestCase.java: @Ignore("JBPAPP-8726")
> src/test/java/org/jboss/as/test/clustering/single/jdbcstore/TransactionalJdbcStoreTestCase.java:@Ignore("https://issues.jboss.org/browse/ISPN-604")
> src/test/java/org/jboss/as/test/clustering/xsite/XSiteSimpleTestCase.java: @Ignore("https://issues.jboss.org/browse/WFLY-5239")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6965) Audit @Ignore-d clustering integration tests
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6965?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-6965 at 8/19/16 6:42 AM:
---------------------------------------------------------------
Analyzed and enabled 4 cases in a PR https://github.com/wildfly/wildfly/pull/9131
RemoteFailoverTestCase already has PR submitted since 2015.
Fine/CoarseSessionPassivationTestCase fail intermittently probably due to Infinispan issue.
was (Author: rhusar):
Analyzed and enabled 5 cases in a PR https://github.com/wildfly/wildfly/pull/9131
RemoteFailoverTestCase already has PR submitted since 2015.
Fine/CoarseSessionPassivationTestCase fail intermittently probably due to Infinispan issue.
> Audit @Ignore-d clustering integration tests
> --------------------------------------------
>
> Key: WFLY-6965
> URL: https://issues.jboss.org/browse/WFLY-6965
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 10.1.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> Recently stumbling upon an @Ignore-d test which would have caught a regression, we need to audit ignored clustering tests, e.g. some are referencing already fixed issues.
> {noformat}
> [rhusar@syrah clustering]$ git grep @Ignore
> src/test/java/org/jboss/as/test/clustering/cluster/ejb/remote/RemoteFailoverTestCase.java: @Ignore("WFLY-3532")
> src/test/java/org/jboss/as/test/clustering/cluster/ejb/stateful/StatefulFailoverTestCase.java: @Ignore("WFLY-835 @Resource UserTransaction error when file passivation store is selected")
> src/test/java/org/jboss/as/test/clustering/cluster/web/passivation/CoarseSessionPassivationTestCase.java:@Ignore("WFLY-6624")
> src/test/java/org/jboss/as/test/clustering/cluster/web/passivation/FineSessionPassivationTestCase.java:@Ignore("WFLY-6624")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/passivation/ClusterPassivationTestCase.java: @Ignore("JBPAPP-8774")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/dd/RemoteEJB2ClientStatefulBeanFailoverDDTestCase.java: @Ignore("JBPAPP-8726")
> src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/dd/RemoteEJB2ClientStatefulBeanFailoverDDTestCase.java: @Ignore("JBPAPP-8726")
> src/test/java/org/jboss/as/test/clustering/single/jdbcstore/TransactionalJdbcStoreTestCase.java:@Ignore("https://issues.jboss.org/browse/ISPN-604")
> src/test/java/org/jboss/as/test/clustering/xsite/XSiteSimpleTestCase.java: @Ignore("https://issues.jboss.org/browse/WFLY-5239")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6975) Transformers for Undertow & securtiy
by Kabir Khan (JIRA)
Kabir Khan created WFLY-6975:
--------------------------------
Summary: Transformers for Undertow & securtiy
Key: WFLY-6975
URL: https://issues.jboss.org/browse/WFLY-6975
Project: WildFly
Issue Type: Task
Components: Security, Web (Undertow)
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Priority: Blocker
Fix For: 11.0.0.CR1
After majority of Eltryon integration is done we need to write & test transformers for all subsystems that ware affected by that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-4047) SLSB with WebService Annotation generates duplicate endpoint when JMS transport used
by Nikolay Boklaschuk (JIRA)
[ https://issues.jboss.org/browse/WFLY-4047?page=com.atlassian.jira.plugin.... ]
Nikolay Boklaschuk commented on WFLY-4047:
------------------------------------------
I have the same problem, trying to make work SOAP-over-JMS with JTA Transactions.
May be some one do this using manually configured JMSConfigFeature with Spring TransactionManager linked to jboss tx-manager?
> SLSB with WebService Annotation generates duplicate endpoint when JMS transport used
> ------------------------------------------------------------------------------------
>
> Key: WFLY-4047
> URL: https://issues.jboss.org/browse/WFLY-4047
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.Final
> Reporter: Wojciech Oczkowski
> Assignee: Alessio Soldano
> Attachments: TestWSJMS.zip
>
>
> When deploying Webservice with JMS transport as Stateless Session Bean, 2 endpoint's are published. One is ok JMSDefaultEndpoind and second is HTTPDefaultEndpoint which is treated as JMS endpoind somehow and fails to deploy with exception below. Simple project that reproduces this problem attached (it requires additional Spring libraries for CXF and JMS transport).
> 14:03:37,974 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."TestWSJMS-1.0-SNAPSHOT.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestWSJMS-1.0-SNAPSHOT.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "TestWSJMS-1.0-SNAPSHOT.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_72]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_72]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_72]
> Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Destination. Did you configure a <jms:destination name="{http://test.ctdp.pl/}NewSessionBeanPort.jms-destination"> and set the jndiConnectionFactoryName ?
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371)
> at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539)
> at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:117)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:67)
> at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:75)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
> ... 5 more
> Caused by: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Destination. Did you configure a <jms:destination name="{http://test.ctdp.pl/}NewSessionBeanPort.jms-destination"> and set the jndiConnectionFactoryName ?
> at org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:115)
> at org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:119)
> at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49)
> at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:95)
> at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:895)
> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:131)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362)
> ... 13 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1724) Resource.NoSuchResourceException managementResourceNotFound for native-interface and native-remoting-interface
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1724?page=com.atlassian.jira.plugi... ]
Chao Wang moved JBEAP-5682 to WFCORE-1724:
------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1724 (was: JBEAP-5682)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
Affects Version/s: 3.0.0.Alpha5
(was: 7.1.0.DR3)
> Resource.NoSuchResourceException managementResourceNotFound for native-interface and native-remoting-interface
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1724
> URL: https://issues.jboss.org/browse/WFCORE-1724
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha5
> Reporter: Chao Wang
> Assignee: Brian Stansberry
>
> management-interface {{native-interface}} and {{native-remoting-interface}} are listed under address:
> /core-service=management/management-interface=
> http-interface native-interface native-remoting-interface
> But the read-resource operation causes Resource.NoSuchResourceException
> {noformat}
> [wangc@dhcp-128-40 DR]$ sh jboss-eap-7.1-DR3/bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-server
> [standalone@embedded /] /core-service=management/management-interface=
> http-interface native-interface native-remoting-interface
> [standalone@embedded /] /core-service=management/management-interface=native-interface:read-resource
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"core-service\" => \"management\"),
> (\"management-interface\" => \"native-interface\")
> ]' not found",
> "rolled-back" => true
> }
> [standalone@embedded /] /core-service=management/management-interface=native-remoting-interface:read-resource
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"core-service\" => \"management\"),
> (\"management-interface\" => \"native-remoting-interface\")
> ]' not found",
> "rolled-back" => true
> }
> {noformat}
> It gives same error in standalone mode and ember-server mode since 7.1-DR2.
> 7.1-DR1 is fine when it's on Wildfly core 2.2.0.CR7
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6974) Transformers for Undertow & securtiy
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFLY-6974:
---------------------------------
Summary: Transformers for Undertow & securtiy
Key: WFLY-6974
URL: https://issues.jboss.org/browse/WFLY-6974
Project: WildFly
Issue Type: Task
Components: Security, Web (Undertow)
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Priority: Blocker
Fix For: 11.0.0.CR1
After majority of Eltryon integration is done we need to write & test transformers for all subsystems that ware affected by that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6971) MDB cannot be deployed after migration due to invalid cache configuration. Log a message in order to detect and reject any invalid configuration.
by Panagiotis Sotiropoulos (JIRA)
[ https://issues.jboss.org/browse/WFLY-6971?page=com.atlassian.jira.plugin.... ]
Panagiotis Sotiropoulos commented on WFLY-6971:
-----------------------------------------------
I have changed the title in order to describe better the proposed fix.
I have made some changes in order to log an error message about invalid cache configuration, while in parallel this invalid configuration is ignored (as the service is not registered).
I would appreciate any help for fixing this using the right approach.
> MDB cannot be deployed after migration due to invalid cache configuration. Log a message in order to detect and reject any invalid configuration.
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6971
> URL: https://issues.jboss.org/browse/WFLY-6971
> Project: WildFly
> Issue Type: Bug
> Components: EJB, JMS
> Affects Versions: 10.1.0.CR1
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
> Priority: Critical
> Attachments: mdb-1.0-SNAPSHOT.jar, standalone-full-ha.xml_eap6
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> If EAP 7 with (manually) migrated configuration from EAP 6.4.7.CP server is started then MDB deployment fails with:
> {code}
> 14:17:09,432 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".cache-dependencies-installer: org.jboss.msc.service.StartException in service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".cache-dependencies-installer: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_71]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_71]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.infinispan.ejb."mdb-1.0-SNAPSHOT.jar".config is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.as.ejb3.cache.distributable.DistributableCacheFactoryBuilderService.installDeploymentUnitDependencies(DistributableCacheFactoryBuilderService.java:93)
> at org.jboss.as.ejb3.deployment.processors.CacheDependenciesProcessor$1.start(CacheDependenciesProcessor.java:50)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> ... 3 more
> {code}
> Problem seems to be configuration of caches in ejb subsystem which looks like:
> {code}
> <subsystem xmlns="urn:jboss:domain:ejb3:4.0">
> ...
> <caches>
> <cache name="simple" aliases="NoPassivationCache"/>
> <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
> <cache name="clustered" passivation-store-ref="infinispan" aliases="StatefulTreeCache"/>
> </caches>
> ...
> </subsystem>
> {code}
> If any of lines:
> {code}
> <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
> <cache name="clustered" passivation-store-ref="infinispan"
> {code}
> is removed or I take default configuration from EAP 7:
> {code}
> <caches>
> <cache name="simple"/>
> <cache name="distributable" passivation-store-ref="infinispan" aliases="passivating clustered"/>
> </caches>
> {code}
> then MDB is deployed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months