April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by Stéphane Nicoll (Jira)

[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Stéphane Nicoll commented on DROOLS-1540: ----------------------------------------- Does that mean that instances must be loaded by the launcher classloader in order to be used by Drools? Would it be possible to alleviate this limitation, for instance by allowing to specify the {{ClassLoader}} to use rather than using an hardcoded one? > Drools does not work with spring-boot-devtools > ---------------------------------------------- > > Key: DROOLS-1540 > URL: https://issues.jboss.org/browse/DROOLS-1540 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final > Reporter: G Xiong > Assignee: Mario Fusco > Priority: Critical > Attachments: complete.zip > > > Drools does work with spring-boot-devtools. > If you add in pom.xml the following, no rules will be fired in Drools. > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-devtools</artifactId> > </dependency> > if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4448) Deprecate unused MultistepUtil methods

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4448?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4448: ------------------------------------- Fix Version/s: 9.0.0.Beta4 > Deprecate unused MultistepUtil methods > -------------------------------------- > > Key: WFCORE-4448 > URL: https://issues.jboss.org/browse/WFCORE-4448 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 9.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4449) Remove unused MultistepUtil methods

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4449: ---------------------------------------- Summary: Remove unused MultistepUtil methods Key: WFCORE-4449 URL: https://issues.jboss.org/browse/WFCORE-4449 Project: WildFly Core Issue Type: Task Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 9.0.0.Beta4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4449) Remove unused MultistepUtil methods

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4449?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4449: ------------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 9.0.0.Beta4) > Remove unused MultistepUtil methods > ----------------------------------- > > Key: WFCORE-4449 > URL: https://issues.jboss.org/browse/WFCORE-4449 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4448) Deprecate unused MultistepUtil methods

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4448: ---------------------------------------- Summary: Deprecate unused MultistepUtil methods Key: WFCORE-4448 URL: https://issues.jboss.org/browse/WFCORE-4448 Project: WildFly Core Issue Type: Task Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11986) HAL Console places <datasource-class> in <datasource> element in standalone.xml. It leads to Test Connection fail

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11986?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11986: ------------------------------------ Component/s: Web Console [~harald.pehl] FYI. I don't know if this is a console issue or a server-side issue. > HAL Console places <datasource-class> in <datasource> element in standalone.xml. It leads to Test Connection fail > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11986 > URL: https://issues.jboss.org/browse/WFLY-11986 > Project: WildFly > Issue Type: Bug > Components: JCA, Web Console > Affects Versions: 16.0.0.Final > Environment: Windows 10 Pro RU, MSSQL Server 2008 on remote machine, Microsoft JDBC driver. mssql-jdbc-6.2.2.jre7 > Reporter: Dmitry Lazarev > Assignee: Stefano Maestri > Priority: Major > > When Datasource for MSSQL is created through HAL Management console, it inserts tag <datasource-class>com.microsoft.sqlserver.jdbc.SQLServerDataSource</datasource-class> in <datasource> element in standalone.xml. > Then when I try to test connection it fails with error "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid" If i remove element <datasource-class> manualy from standalone.xml, Test Connection works properly. > 2019-04-12 17:01:15,500 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (External Management Request Threads -- 2) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1325) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:499) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:1067) > at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:93) > at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:240) > at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:97) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1412) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.jboss.as.controller.ModelControllerImpl$$Lambda$489/1626912192.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$491/1133081806.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler$$Lambda$541/1958155244.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$542/1328593333.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest(ElytronIdentityHandler.java:61) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Не удалось установить соединение TCP/IP к серверу localhost по порту 1433. Ошибка: "Connection refused: no further information. Проверьте свойства соединения. Убедитесь, что на сервере запущен экземпляр SQL Server и он принимает TCP/IP-соединения по порту. Убедитесь, что TCP-соединения по этому порту не блокируются брандмауэром.". > at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:227) > at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLServerException(SQLServerException.java:284) > at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:2435) > at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:635) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2010) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1687) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1528) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:866) > at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:968) > at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnection(SQLServerDataSource.java:78) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:314) > ... 39 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12021) Mixed domain testsuite should remove unneeded expanded dists as it goes

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12021?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12021: ------------------------------------ Description: OldVersionCopier unzips the legacy AS zip for the version requested. But there is no subsequent cleanup. Simplest is to have the method that unzips check for all the other versions besides the one being tested and remove any it finds. The tests execute grouped by version so when work on a new version begins the expanded dist for the previous version is not needed. That will leave one behind, but that's ok. The problem here is the overall disk utilization during CI jobs and getting this down to just one is ok. And after the last version runs, the CI jobs complete anyway. was: OldVersionCopier unzips the legacy AS zip for the version requested. But there is no subsequent cleanup. Simplest is to have the method that unzips check for all the other versions besides the one being tested and remove any it finds. That will leave one behind, but that's ok. The problem here is the overall disk utilization during CI jobs and getting this down to just one is fine. And after the last version runs, the CI jobs complete anyway. > Mixed domain testsuite should remove unneeded expanded dists as it goes > ----------------------------------------------------------------------- > > Key: WFLY-12021 > URL: https://issues.jboss.org/browse/WFLY-12021 > Project: WildFly > Issue Type: Enhancement > Components: Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > OldVersionCopier unzips the legacy AS zip for the version requested. But there is no subsequent cleanup. > Simplest is to have the method that unzips check for all the other versions besides the one being tested and remove any it finds. The tests execute grouped by version so when work on a new version begins the expanded dist for the previous version is not needed. > That will leave one behind, but that's ok. The problem here is the overall disk utilization during CI jobs and getting this down to just one is ok. And after the last version runs, the CI jobs complete anyway. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-667) Checklist for custom fields in order to support existing and future workflows for Jaeger

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-667?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy edited comment on SWSQE-667 at 4/26/19 11:13 PM: ----------------------------------------------------------------- [~pyadav] mentioned, this issue resolved. I am just updating status. [~pyadav] if it is not resolved, kindly reopen this issue was (Author: jkandasa): [~pyadav] mentioned, this issue resolved. I am just updating status. > Checklist for custom fields in order to support existing and future workflows for Jaeger > ---------------------------------------------------------------------------------------- > > Key: SWSQE-667 > URL: https://issues.jboss.org/browse/SWSQE-667 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > Attachments: Screenshot from 2019-04-16 18-19-46.png > > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-667) Checklist for custom fields in order to support existing and future workflows for Jaeger

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-667?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-667. ----------------------------------- Resolution: Done [~pyadav] mentioned, this issue resolved. I am just updating status. > Checklist for custom fields in order to support existing and future workflows for Jaeger > ---------------------------------------------------------------------------------------- > > Key: SWSQE-667 > URL: https://issues.jboss.org/browse/SWSQE-667 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > Attachments: Screenshot from 2019-04-16 18-19-46.png > > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-667) Checklist for custom fields in order to support existing and future workflows for Jaeger

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-667?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy updated SWSQE-667: ---------------------------------- Sprint: Kiali Sprint #21 (was: Kiali Sprint #22) > Checklist for custom fields in order to support existing and future workflows for Jaeger > ---------------------------------------------------------------------------------------- > > Key: SWSQE-667 > URL: https://issues.jboss.org/browse/SWSQE-667 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > Attachments: Screenshot from 2019-04-16 18-19-46.png > > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019