April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12029) Update Checkstyl Config to 1.0.8.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12029: --------------------------------------- Summary: Update Checkstyl Config to 1.0.8.Final Key: WFLY-12029 URL: https://issues.jboss.org/browse/WFLY-12029 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 17.0.0.Beta1 Also remove the checkstyle plug-in version override. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12028) Upgrade JBoss Parent to version 35

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12028: --------------------------------------- Summary: Upgrade JBoss Parent to version 35 Key: WFLY-12028 URL: https://issues.jboss.org/browse/WFLY-12028 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 17.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 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 Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-11986?page=com.atlassian.jira.plugin... ] Harald Pehl commented on WFLY-11986: ------------------------------------ I'll check what operations HAL uses to create the datasource. > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3948) Testing of the HACEP

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3948?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-3948: --------------------------------------- Summary: Testing of the HACEP (was: testing of the HACEP) > Testing of the HACEP > -------------------- > > Key: DROOLS-3948 > URL: https://issues.jboss.org/browse/DROOLS-3948 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3948) testing of the HACEP

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-3948: ------------------------------------------ Summary: testing of the HACEP Key: DROOLS-3948 URL: https://issues.jboss.org/browse/DROOLS-3948 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3916) Create a "delta" of the events between the startup of a pod and the last snapshot

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3916?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-3916. ---------------------------------------- Resolution: Done > Create a "delta" of the events between the startup of a pod and the last snapshot > --------------------------------------------------------------------------------- > > Key: DROOLS-3916 > URL: https://issues.jboss.org/browse/DROOLS-3916 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2299) LockService does not work correctly if unlock/lock is called in immediate succession

by David White (Jira)

[ https://issues.jboss.org/browse/JGRP-2299?page=com.atlassian.jira.plugin.... ] David White commented on JGRP-2299: ----------------------------------- In my case we are using TCP, not UDP. > LockService does not work correctly if unlock/lock is called in immediate succession > ------------------------------------------------------------------------------------ > > Key: JGRP-2299 > URL: https://issues.jboss.org/browse/JGRP-2299 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Environment: Windows 10 Oracle JDK 1.8 131 > AIX IBM Java 8 > Reporter: Mirko Streckenbach > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.1 > > Attachments: JGroupsExample.java, udp+lock.xml > > > In our application we have encountered occasional cases of LockService allowing 2 processes to hold the same lock at the same time. I could reproduce this with a simple program (see atttachment) and it happens if for a lock "unlock" is called and immediately afterwards "lock". If there is a small delay (e.g. 1 second) between the two operations everything works as expected. > This can be produced with the attached program. The program does lock/unlock/lock on a lock and then tries to lock the same lock from a different JChannel and is awarded the lock. If you place a small sleep() after the unlock, everything works as expected and the parallel lock is not awarded. > If you turn on debugging you'll see no output between unlock and lock, so it looks to me like the lock is awarded without passing GRANT_LOCK messages to the stack. Using a conditional break point you can see that ClientLock.acquired is still true even after the unlock(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4453) Clean up left curly placement in files triggering checkstyle failures.

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4453: ---------------------------------------- Summary: Clean up left curly placement in files triggering checkstyle failures. Key: WFCORE-4453 URL: https://issues.jboss.org/browse/WFCORE-4453 Project: WildFly Core Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.Beta4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4452) Update WildFly Checkstyle Config to 1.0.8.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4452: ---------------------------------------- Summary: Update WildFly Checkstyle Config to 1.0.8.Final Key: WFCORE-4452 URL: https://issues.jboss.org/browse/WFCORE-4452 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.Beta4 Additionally drop the checkstyle plug-in version override and use the version from jboss-parent. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4451) Upgrade JBoss Parent to version 35

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4451: ---------------------------------------- Summary: Upgrade JBoss Parent to version 35 Key: WFCORE-4451 URL: https://issues.jboss.org/browse/WFCORE-4451 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.Beta4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019