[JBoss JIRA] (WFLY-4794) Add logging deployment resource tests for a WAR and EAR deployment
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4794?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-4794:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Add logging deployment resource tests for a WAR and EAR deployment
> ------------------------------------------------------------------
>
> Key: WFLY-4794
> URL: https://issues.jboss.org/browse/WFLY-4794
> Project: WildFly
> Issue Type: Task
> Components: Logging, Test Suite
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 10.0.0.Final
>
>
> WildFly Core can only reliably test JAR deployments for logging configurations. Tests should be added to ensure WAR's and EAR's work as expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-4647) RemoteOutboundConnectionReconnectTestCase, EJBClientReconnectionTestCase configured as clustered test cases
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4647?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-4647:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> RemoteOutboundConnectionReconnectTestCase, EJBClientReconnectionTestCase configured as clustered test cases
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4647
> URL: https://issues.jboss.org/browse/WFLY-4647
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.Alpha1
> Reporter: Richard Achmatowicz
> Assignee: Michal Vinkler
> Fix For: 10.0.0.Final
>
>
> In the Wildfly integration testsuite, manual mode section, there are two test cases which are running in a clustered environment when they should not be:
> - RemoteOutboundConnectionReconnectTestCase
> - EJBClientReconnectionTestCase
> These two cases test outbound connections from one server A to another server B, and connection from a client to a server A when the server is stopped and started. There is no clustering functionality being tested.
> Two problems with this situation:
> - exceptions are generated in the logs which result from the fact that the test cases are not being run in the correct environment
> - the fact that the environment is incorrectly configured may also be preventing real bugs from otherwise being detected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-473) Get rid of external .index files
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-473?page=com.atlassian.jira.plugin.s... ]
Kabir Khan updated WFLY-473:
----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Get rid of external .index files
> --------------------------------
>
> Key: WFLY-473
> URL: https://issues.jboss.org/browse/WFLY-473
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: David Lloyd
> Fix For: 10.0.0.Final
>
>
> The external {{*.index}} files have become a problem for distribution. In 8 we should switch to using internal {{META-INF/PATHS.LIST}} files. These files should be embedded during build.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-2554) Start using wildcards for exclusions
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-2554?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-2554:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Start using wildcards for exclusions
> ------------------------------------
>
> Key: WFLY-2554
> URL: https://issues.jboss.org/browse/WFLY-2554
> Project: WildFly
> Issue Type: Enhancement
> Components: Build System
> Reporter: David Lloyd
> Assignee: Paul Gier
> Priority: Minor
> Fix For: 10.0.0.Final
>
>
> Maven 3 supports using * for group ID and artifact ID in exclusions. We should use them throughout the root pom.xml.
> In current Maven versions there's an annoying warning printed, but it can be ignored (the warning is a bug). See http://jira.codehaus.org/browse/MNG-3832 for discussion and info (the bug says "fix version 3.2" but that's just the version in which the warning was fixed, not the actual feature).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-4858) Add tests for permission assignment checking when security manager is enabled
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4858?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-4858:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Add tests for permission assignment checking when security manager is enabled
> -----------------------------------------------------------------------------
>
> Key: WFLY-4858
> URL: https://issues.jboss.org/browse/WFLY-4858
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Josef Cacek
> Assignee: Josef Cacek
> Fix For: 10.0.0.Final
>
>
> Extend test coverage for security manager permissions assignment (in {{permissions.xml}}) and their overrides (in {{jboss-permissions.xml}}).
> Add also tests which check permissions overrides in ear modules (subdeployments).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5003) AuthenticationTestCase fails was bind address is changed by -Dnode0 property
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5003?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5003:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> AuthenticationTestCase fails was bind address is changed by -Dnode0 property
> ----------------------------------------------------------------------------
>
> Key: WFLY-5003
> URL: https://issues.jboss.org/browse/WFLY-5003
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.Alpha5
> Reporter: Petr Kremensky
> Assignee: Jan Martiska
> Fix For: 10.0.0.Final
>
>
> org.jboss.as.test.integration.ejb.security.AuthenticationTestCase fails once -Dnode0 is used. On the first sight, *managementClient.getWebUri()* seems to be one to blame as "http://localhost:8080" is always used now.
> {noformat}
> Running org.jboss.as.test.integration.ejb.security.AuthenticationTestCase
> Tests run: 19, Failures: 1, Errors: 8, Skipped: 0, Time elapsed: 1.127 sec <<< FAILURE! - in org.jboss.as.test.integration.ejb.security.AuthenticationTestCase
> testAuthentication_ReAuth_ViaServlet(org.jboss.as.test.integration.ejb.security.AuthenticationTestCase) Time elapsed: 0.126 sec <<< ERROR!
> java.io.IOException: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at java.net.Socket.connect(Socket.java:538)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
> at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1168)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:932)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> at org.jboss.as.test.integration.ejb.security.AuthenticationTestCase.processResponse(AuthenticationTestCase.java:335)
> at org.jboss.as.test.integration.ejb.security.AuthenticationTestCase.access$000(AuthenticationTestCase.java:79)
> testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet(org.jboss.as.test.integration.ejb.security.AuthenticationTestCase) Time elapsed: 0.046 sec <<< FAILURE!
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.as.test.integration.ejb.security.AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet(AuthenticationTestCase.java:260)
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-4922) Add smoke test for <deny-uncovered-http-methods/> tag
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4922?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-4922:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Add smoke test for <deny-uncovered-http-methods/> tag
> -----------------------------------------------------
>
> Key: WFLY-4922
> URL: https://issues.jboss.org/browse/WFLY-4922
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Reporter: Jan Tymel
> Assignee: Jan Tymel
> Fix For: 10.0.0.Final
>
>
> With Java Servlet 3.1 specification [1] comes possibility to use <deny-uncovered-http-methods/> tag in web.xml file. This new feature should be tested by a basic smoke test in WildFly testsuite.
> Brief description of test case:
> * set some of HTTP methods secured
> * verify that these methods are accessible
> * when anyone tries to use other than specified (i.e. secured) HTTP methods, status code 403 should be returned (according to specification)
> [1] https://jcp.org/en/jsr/detail?id=340
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5527) "WFLYCTL0171 unsatisfied dependencies" when removing an xa-datasource-properties resource
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5527?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5527:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> "WFLYCTL0171 unsatisfied dependencies" when removing an xa-datasource-properties resource
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-5527
> URL: https://issues.jboss.org/browse/WFLY-5527
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 9.0.1.Final, 10.0.0.CR2
> Reporter: Peter Palaga
> Assignee: Stefano Maestri
> Priority: Critical
> Fix For: 10.0.0.Final
>
>
> Steps to reproduce, same fro WF 9.0.1.Final and 10.0.0.CR2:
> (1) create an XA Datasource:
> {code}
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs")
> ],
> "jndi-name" => "java:/testXaDs",
> "driver-name" => "h2",
> "xa-datasource-class" => "org.h2.jdbcx.JdbcDataSource",
> "user-name" => "sa",
> "password" => "sa",
> "new-connection-sql" => undefined,
> "url-delimiter" => undefined,
> "url-selector-strategy-class-name" => undefined,
> "use-java-context" => undefined,
> "max-pool-size" => undefined,
> "min-pool-size" => undefined,
> "initial-pool-size" => undefined,
> "pool-prefill" => undefined,
> "pool-use-strict-min" => undefined,
> "interleaving" => undefined,
> "capacity-incrementer-class" => undefined,
> "capacity-decrementer-class" => undefined,
> "no-tx-separate-pool" => undefined,
> "pad-xid" => undefined,
> "same-rm-override" => undefined,
> "wrap-xa-resource" => undefined,
> "security-domain" => undefined,
> "reauth-plugin-class-name" => undefined,
> "flush-strategy" => undefined,
> "allow-multiple-users" => undefined,
> "connection-listener-class" => undefined,
> "prepared-statements-cache-size" => undefined,
> "share-prepared-statements" => undefined,
> "track-statements" => undefined,
> "allocation-retry" => undefined,
> "allocation-retry-wait-millis" => undefined,
> "blocking-timeout-wait-millis" => undefined,
> "idle-timeout-minutes" => undefined,
> "query-timeout" => undefined,
> "use-try-lock" => undefined,
> "set-tx-query-timeout" => undefined,
> "transaction-isolation" => undefined,
> "check-valid-connection-sql" => undefined,
> "exception-sorter-class-name" => undefined,
> "stale-connection-checker-class-name" => undefined,
> "valid-connection-checker-class-name" => undefined,
> "background-validation-millis" => undefined,
> "background-validation" => undefined,
> "use-fast-fail" => undefined,
> "validate-on-match" => undefined,
> "xa-resource-timeout" => undefined,
> "spy" => undefined,
> "use-ccm" => undefined,
> "enabled" => undefined,
> "connectable" => undefined,
> "statistics-enabled" => undefined,
> "tracking" => undefined,
> "recovery-username" => undefined,
> "recovery-password" => undefined,
> "recovery-security-domain" => undefined,
> "recovery-plugin-class-name" => undefined,
> "no-recovery" => undefined,
> "url-property" => undefined,
> "reauth-plugin-properties" => undefined,
> "exception-sorter-properties" => undefined,
> "stale-connection-checker-properties" => undefined,
> "valid-connection-checker-properties" => undefined,
> "recovery-plugin-properties" => undefined,
> "connection-listener-property" => undefined,
> "capacity-incrementer-properties" => undefined,
> "capacity-decrementer-properties" => undefined
> },
> {
> "operation" => "add",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs"),
> ("xa-datasource-properties" => "URL")
> ],
> "value" => "jdbc:h2:mem:test"
> },
> {
> "operation" => "add",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs"),
> ("xa-datasource-properties" => "xaProp2")
> ],
> "value" => "xaVal2"
> }
> ]
> }
> {code}
> (2) Update or remove any of the {{xa-datasource-properties}}:
> {code}
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "remove",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs"),
> ("xa-datasource-properties" => "URL")
> ]
> },
> {
> "operation" => "add",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs"),
> ("xa-datasource-properties" => "URL")
> ],
> "value" => "jdbc:h2:mem:test;DB_CLOSE_DELAY=5000"
> },
> {
> "operation" => "remove",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs"),
> ("xa-datasource-properties" => "xaProp2")
> ]
> },
> {
> "operation" => "add",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs"),
> ("xa-datasource-properties" => "xaProp3")
> ],
> "value" => "xaVal3"
> }
> ]
> }
> {code}
> (3) NOT OK: the composite operation fails
> {code}
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
> Service jboss.xa-data-source-config.testXaDs.xa-datasource-properties.URL was depended upon by service jboss.xa-data-source-config.testXaDs",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "response-headers" => {"operation-requires-reload" => true},
> "rolled-back" => true
> },
> "step-3" => {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
> Service jboss.xa-data-source-config.testXaDs.xa-datasource-properties.xaProp2 was depended upon by service jboss.xa-data-source-config.testXaDs",
> "rolled-back" => true
> },
> "step-4" => {
> "outcome" => "failed",
> "response-headers" => {"operation-requires-reload" => true},
> "rolled-back" => true
> }
> },
> "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
> "Operation step-7" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
> Service jboss.xa-data-source-config.testXaDs.xa-datasource-properties.URL was depended upon by service jboss.xa-data-source-config.testXaDs",
> "Operation step-9" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
> Service jboss.xa-data-source-config.testXaDs.xa-datasource-properties.xaProp2 was depended upon by service jboss.xa-data-source-config.testXaDs"
> }},
> "rolled-back" => true,
> "response-headers" => {"process-state" => "reload-required"}
> }
> {code}
> EXPECTED: the operation should succeed
> Workaround: When the same request is sent once again, the second invocation succeeds.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-4756) jboss-ejb-iiop_1.0.xsd Should be removed from EAP code base and moved to metadata project
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4756?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-4756:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> jboss-ejb-iiop_1.0.xsd Should be removed from EAP code base and moved to metadata project
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-4756
> URL: https://issues.jboss.org/browse/WFLY-4756
> Project: WildFly
> Issue Type: Bug
> Components: EJB, IIOP
> Affects Versions: 10.0.0.Alpha2
> Environment: EAP default installations
> Reporter: Weston Price
> Assignee: Tomasz Adamski
> Fix For: 10.0.0.Final
>
>
> Currently the jboss-ejb-iiop_1.0.xsd file resides in the EAP project under:
> /Users/wmprice/projects/javaprojects/jboss-eap/ejb3/src/main/resources
> directory. The correct place for this file should be in the metadata project where the IIOPMetaDataParser and MetaData reside.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months