[JBoss JIRA] (WFCORE-4724) SyslogAuditLogTestCase Test Failures
by Darran Lofthouse (Jira)
Darran Lofthouse created WFCORE-4724:
----------------------------------------
Summary: SyslogAuditLogTestCase Test Failures
Key: WFCORE-4724
URL: https://issues.jboss.org/browse/WFCORE-4724
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 11.0.0.Beta2
This test is dependent on a bad host address triggering a UDP write failure, however later Linux Kernel updates are more tolerant to this bad address - overall the Java APIs can not be relied upon in this situation so the test will be removed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFCORE-4723) SyslogAuditLogTestCase Test Failures
by Darran Lofthouse (Jira)
Darran Lofthouse created WFCORE-4723:
----------------------------------------
Summary: SyslogAuditLogTestCase Test Failures
Key: WFCORE-4723
URL: https://issues.jboss.org/browse/WFCORE-4723
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 10.0.3.Final, 11.0.0.Beta2
This test is dependent on a bad host address triggering a UDP write failure, however later Linux Kernel updates are more tolerant to this bad address - overall the Java APIs can not be relied upon in this situation so the test will be removed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (JGRP-2391) BindException on Windows
by Mark Latham (Jira)
[ https://issues.jboss.org/browse/JGRP-2391?page=com.atlassian.jira.plugin.... ]
Mark Latham commented on JGRP-2391:
-----------------------------------
I'm also seeing exactly the same symptoms as reported above. Bela could you either post a link to the ML suggestions here or could the suggestions be listed here. Thanks.
> BindException on Windows
> ------------------------
>
> Key: JGRP-2391
> URL: https://issues.jboss.org/browse/JGRP-2391
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6
> Environment: Openjdk 13
> Microsoft Windows 10
> Reporter: Thorsten Marx
> Assignee: Bela Ban
> Priority: Major
>
> After updating to jgroups 4.1.6 i get the following BindException
> {code}
> java.net.BindException: Cannot assign requested address: Cannot bind
> at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind0(Native Method)
> at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind0(TwoStacksPlainDatagramSocketImpl.java:114)
> at java.base/java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:117)
> at java.base/java.net.TwoStacksPlainDatagramSocketImpl.bind(TwoStacksPlainDatagramSocketImpl.java:98)
> at java.base/java.net.DatagramSocket.bind(DatagramSocket.java:395)
> at java.base/java.net.MulticastSocket.<init>(MulticastSocket.java:176)
> at org.jgroups.util.DefaultSocketFactory.createMulticastSocket(DefaultSocketFactory.java:92)
> at org.jgroups.stack.DiagnosticsHandler.startUDP(DiagnosticsHandler.java:180)
> at org.jgroups.stack.DiagnosticsHandler.start(DiagnosticsHandler.java:122)
> at org.jgroups.protocols.TP.startDiagnostics(TP.java:1031)
> at org.jgroups.protocols.TP.start(TP.java:938)
> at org.jgroups.protocols.UDP.start(UDP.java:295)
> at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:888)
> at org.jgroups.JChannel.startStack(JChannel.java:980)
> at org.jgroups.JChannel._preConnect(JChannel.java:844)
> at org.jgroups.JChannel.connect(JChannel.java:349)
> at org.jgroups.JChannel.connect(JChannel.java:343)
> at com.thorstenmarx.webtools.cluster.JGroupsTest.simple(JGroupsTest.java:43)
> {code}
> It seems to be caused by https://stackoverflow.com/questions/14086740/how-to-create-a-new-multicas...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (ELY-1847) WildFlyElytronProvider Loading wrong class for Bearer
by Lennart Jörelid (Jira)
[ https://issues.jboss.org/browse/ELY-1847?page=com.atlassian.jira.plugin.s... ]
Lennart Jörelid edited comment on ELY-1847 at 10/23/19 8:15 AM:
----------------------------------------------------------------
Seems to be a good solution for when Keycloak supports Wildfly 18.
Until then, however, we have to run on top of Wildfly 17, which basically refuses to accept the token emitted by Keycloak 7.0.1 (latest release). I believe that the Token from Keycloak is not accepted due to this bug (but I could be wrong about that). Since the fix is not too complex, however, we only need to know how to configure the Elytron subsystem to use a custom provider for the Bearer Token Authentication mechanism.
Or would you recommend installing Elytron 1.10 on top of Wildfly 17 instead?
was (Author: lennartj):
Seems to be a good solution for when Keycloak supports Wildfly 18.
Until then, however, we have to run on top of Wildfly 17, which basically refuses to accept the token emitted by Keycloak 7.0.1 (latest release). Since the fix is not too complex, we only need to know how to configure the Elytron subsystem to use a custom provider for the Bearer Token Authentication mechanism.
Or would you recommend installing Elytron 1.10 on top of Wildfly 17 instead?
> WildFlyElytronProvider Loading wrong class for Bearer
> -----------------------------------------------------
>
> Key: ELY-1847
> URL: https://issues.jboss.org/browse/ELY-1847
> Project: WildFly Elytron
> Issue Type: Bug
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 2.0.0.Alpha5, 1.10.0.CR4
>
>
> {noformat}
> Caused by: java.lang.NoSuchMethodException: org.wildfly.security.http.bearer.BearerTokenAuthenticationMechanism.<init>(java.security.Provider)
> at java.lang.Class.getConstructor0(Class.java:3082)
> at java.lang.Class.getConstructor(Class.java:1825)
> at org.wildfly.security.WildFlyElytronProvider$ProviderService.newInstance(WildFlyElytronProvider.java:339)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (ELY-1847) WildFlyElytronProvider Loading wrong class for Bearer
by Lennart Jörelid (Jira)
[ https://issues.jboss.org/browse/ELY-1847?page=com.atlassian.jira.plugin.s... ]
Lennart Jörelid commented on ELY-1847:
--------------------------------------
Seems to be a good solution for when Keycloak supports Wildfly 18.
Until then, however, we have to run on top of Wildfly 17, which basically refuses to accept the token emitted by Keycloak 7.0.1 (latest release). Since the fix is not too complex, we only need to know how to configure the Elytron subsystem to use a custom provider for the Bearer Token Authentication mechanism.
Or would you recommend installing Elytron 1.10 on top of Wildfly 17 instead?
> WildFlyElytronProvider Loading wrong class for Bearer
> -----------------------------------------------------
>
> Key: ELY-1847
> URL: https://issues.jboss.org/browse/ELY-1847
> Project: WildFly Elytron
> Issue Type: Bug
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 2.0.0.Alpha5, 1.10.0.CR4
>
>
> {noformat}
> Caused by: java.lang.NoSuchMethodException: org.wildfly.security.http.bearer.BearerTokenAuthenticationMechanism.<init>(java.security.Provider)
> at java.lang.Class.getConstructor0(Class.java:3082)
> at java.lang.Class.getConstructor(Class.java:1825)
> at org.wildfly.security.WildFlyElytronProvider$ProviderService.newInstance(WildFlyElytronProvider.java:339)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12703) Error populating DB schema with PostgreSQL as JDBC store
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFLY-12703?page=com.atlassian.jira.plugin... ]
Tommasso Borgato deleted WFLY-12703:
------------------------------------
> Error populating DB schema with PostgreSQL as JDBC store
> --------------------------------------------------------
>
> Key: WFLY-12703
> URL: https://issues.jboss.org/browse/WFLY-12703
> Project: WildFly
> Issue Type: Bug
> Reporter: Tommasso Borgato
> Assignee: Paul Ferraro
> Priority: Blocker
>
> The scenario is a 4 nodes WildFly cluster where Web Sessions are stored in an invalidation cache backed by PostgreSQL DB; this is the cli script used to configure all 4 nodes:
> {noformat}
> embed-server --server-config=standalone-ha.xml
> /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload:add()
> /subsystem=infinispan/cache-container=web/invalidation-cache==offload/component=transaction:write-attribute(name=mode, value=BATCH)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
> data-source add --name=testDS --jndi-name=java:jboss/datasources/testDS --driver-name=postgresql-connector.jar --connection-url=jdbc:postgresql://postgres-115.mwqe.upshift.rdu2.redhat.com:5432/dballo03 --enabled=true --jta=true --use-java-context=true --transaction-isolation=TRANSACTION_READ_COMMITTED --min-pool-size=1 --max-pool-size=5 --pool-prefill=true --user-name=dballo03 --password=dballo03 --prepared-statements-cache-size=32 --share-prepared-statements=true
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc:add(data-source=testDS,fetch-state=false,passivation=false,purge=false,shared=true,dialect=POSTGRES){allow-resource-service-restart=true}
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=prefix,value=s)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.name,value=id)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.type,value=VARCHAR(255))
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.name,value=datum)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.type,value=BYTEA)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.name,value=version)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.type,value=BIGINT)
> /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=offload)
> /subsystem=transactions:write-attribute(name=node-identifier,value=wildfly2)
> {noformat}
> Note that the Database schema was empty before running the tests;
> This is the sequence that produces the error:
> - Node 1 is started
> - App clusterbench is deployed on Node 1
> - Database tables are created:
> - "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war"
> - "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war"
> - "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_war"
> - Node 2 is started
> - App clusterbench is deployed on Node 2 ---> ERROR
> The error is:
> {noformat}
> ERROR o.j.e.c.i.i.u.WildFlyServiceInstrumentationProviderSunstone - could not deploy /home/hudson/static_build_env/clustering/clusterbench/clusterbench-ee8.ear via management client to service WildFly Service 2, result is not a success:
> {
> "outcome" : "failed",
> "failure-description" : {"WFLYCTL0080: Failed services" : {
> "org.wildfly.clustering.infinispan.cache.web.clusterbench-ee8.ear.clusterbench-ee8-web-granular.war" : "org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to start cache loaders\n Caused by: org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore\n Caused by: org.infinispan.persistence.spi.PersistenceException: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war_timest\" already exists\n Caused by: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war_timest\" already exists",
> "org.wildfly.clustering.infinispan.cache.web.clusterbench-ee8.ear.clusterbench-ee8-web-passivating.war" : "org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to start cache loaders\n Caused by: org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore\n Caused by: org.infinispan.persistence.spi.PersistenceException: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war_tim\" already exists\n Caused by: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war_tim\" already exists"
> }},
> "rolled-back" : true
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12703) Error populating DB schema with PostgreSQL as JDBC store
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFLY-12703?page=com.atlassian.jira.plugin... ]
Tommasso Borgato closed WFLY-12703.
-----------------------------------
Resolution: Done
> Error populating DB schema with PostgreSQL as JDBC store
> --------------------------------------------------------
>
> Key: WFLY-12703
> URL: https://issues.jboss.org/browse/WFLY-12703
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 18.0.0.Final
> Reporter: Tommasso Borgato
> Assignee: Paul Ferraro
> Priority: Blocker
>
> The scenario is a 4 nodes WildFly cluster where Web Sessions are stored in an invalidation cache backed by PostgreSQL DB; this is the cli script used to configure all 4 nodes:
> {noformat}
> embed-server --server-config=standalone-ha.xml
> /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload:add()
> /subsystem=infinispan/cache-container=web/invalidation-cache==offload/component=transaction:write-attribute(name=mode, value=BATCH)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
> data-source add --name=testDS --jndi-name=java:jboss/datasources/testDS --driver-name=postgresql-connector.jar --connection-url=jdbc:postgresql://postgres-115.mwqe.upshift.rdu2.redhat.com:5432/dballo03 --enabled=true --jta=true --use-java-context=true --transaction-isolation=TRANSACTION_READ_COMMITTED --min-pool-size=1 --max-pool-size=5 --pool-prefill=true --user-name=dballo03 --password=dballo03 --prepared-statements-cache-size=32 --share-prepared-statements=true
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc:add(data-source=testDS,fetch-state=false,passivation=false,purge=false,shared=true,dialect=POSTGRES){allow-resource-service-restart=true}
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=prefix,value=s)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.name,value=id)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.type,value=VARCHAR(255))
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.name,value=datum)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.type,value=BYTEA)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.name,value=version)
> /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.type,value=BIGINT)
> /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=offload)
> /subsystem=transactions:write-attribute(name=node-identifier,value=wildfly2)
> {noformat}
> Note that the Database schema was empty before running the tests;
> This is the sequence that produces the error:
> - Node 1 is started
> - App clusterbench is deployed on Node 1
> - Database tables are created:
> - "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war"
> - "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war"
> - "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_war"
> - Node 2 is started
> - App clusterbench is deployed on Node 2 ---> ERROR
> The error is:
> {noformat}
> ERROR o.j.e.c.i.i.u.WildFlyServiceInstrumentationProviderSunstone - could not deploy /home/hudson/static_build_env/clustering/clusterbench/clusterbench-ee8.ear via management client to service WildFly Service 2, result is not a success:
> {
> "outcome" : "failed",
> "failure-description" : {"WFLYCTL0080: Failed services" : {
> "org.wildfly.clustering.infinispan.cache.web.clusterbench-ee8.ear.clusterbench-ee8-web-granular.war" : "org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to start cache loaders\n Caused by: org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore\n Caused by: org.infinispan.persistence.spi.PersistenceException: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war_timest\" already exists\n Caused by: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war_timest\" already exists",
> "org.wildfly.clustering.infinispan.cache.web.clusterbench-ee8.ear.clusterbench-ee8-web-passivating.war" : "org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to start cache loaders\n Caused by: org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore\n Caused by: org.infinispan.persistence.spi.PersistenceException: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war_tim\" already exists\n Caused by: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war_tim\" already exists"
> }},
> "rolled-back" : true
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12703) Error populating DB schema with PostgreSQL as JDBC store
by Tommasso Borgato (Jira)
Tommasso Borgato created WFLY-12703:
---------------------------------------
Summary: Error populating DB schema with PostgreSQL as JDBC store
Key: WFLY-12703
URL: https://issues.jboss.org/browse/WFLY-12703
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.0.Final
Reporter: Tommasso Borgato
Assignee: Paul Ferraro
The scenario is a 4 nodes WildFly cluster where Web Sessions are stored in an invalidation cache backed by PostgreSQL DB; this is the cli script used to configure all 4 nodes:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload:add()
/subsystem=infinispan/cache-container=web/invalidation-cache==offload/component=transaction:write-attribute(name=mode, value=BATCH)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
data-source add --name=testDS --jndi-name=java:jboss/datasources/testDS --driver-name=postgresql-connector.jar --connection-url=jdbc:postgresql://postgres-115.mwqe.upshift.rdu2.redhat.com:5432/dballo03 --enabled=true --jta=true --use-java-context=true --transaction-isolation=TRANSACTION_READ_COMMITTED --min-pool-size=1 --max-pool-size=5 --pool-prefill=true --user-name=dballo03 --password=dballo03 --prepared-statements-cache-size=32 --share-prepared-statements=true
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc:add(data-source=testDS,fetch-state=false,passivation=false,purge=false,shared=true,dialect=POSTGRES){allow-resource-service-restart=true}
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=prefix,value=s)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.name,value=id)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.type,value=VARCHAR(255))
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.name,value=datum)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.type,value=BYTEA)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.name,value=version)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.type,value=BIGINT)
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=offload)
/subsystem=transactions:write-attribute(name=node-identifier,value=wildfly2)
{noformat}
Note that the Database schema was empty before running the tests;
This is the sequence that produces the error:
- Node 1 is started
- App clusterbench is deployed on Node 1
- Database tables are created:
- "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war"
- "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war"
- "public"."s_clusterbench_ee8_ear_clusterbench_ee8_web_war"
- Node 2 is started
- App clusterbench is deployed on Node 2 ---> ERROR
The error is:
{noformat}
ERROR o.j.e.c.i.i.u.WildFlyServiceInstrumentationProviderSunstone - could not deploy /home/hudson/static_build_env/clustering/clusterbench/clusterbench-ee8.ear via management client to service WildFly Service 2, result is not a success:
{
"outcome" : "failed",
"failure-description" : {"WFLYCTL0080: Failed services" : {
"org.wildfly.clustering.infinispan.cache.web.clusterbench-ee8.ear.clusterbench-ee8-web-granular.war" : "org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to start cache loaders\n Caused by: org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore\n Caused by: org.infinispan.persistence.spi.PersistenceException: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war_timest\" already exists\n Caused by: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_granular_war_timest\" already exists",
"org.wildfly.clustering.infinispan.cache.web.clusterbench-ee8.ear.clusterbench-ee8-web-passivating.war" : "org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl\n Caused by: org.infinispan.commons.CacheException: Unable to start cache loaders\n Caused by: org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore\n Caused by: org.infinispan.persistence.spi.PersistenceException: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war_tim\" already exists\n Caused by: org.postgresql.util.PSQLException: ERROR: relation \"s_clusterbench_ee8_ear_clusterbench_ee8_web_passivating_war_tim\" already exists"
}},
"rolled-back" : true
}
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months