[JBoss JIRA] (WFLY-7214) Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-7214?page=com.atlassian.jira.plugin.... ]
Lin Gao updated WFLY-7214:
--------------------------
Steps to Reproduce:
h2. Step 1. Try to add a data-source with missing information
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2, connection-url="jdbc:h2:test")
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.XXX" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.XXX: WFLYJCA0033: Error during the deployment of XXX
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.XXX"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
There will be exception in server log:
{code:}
23:47:24,962 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Error during the deployment of java:/XXX: javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: XXX
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createConnectionFactory(LocalManagedConnectionFactory.java:108)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:775)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:312)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:371)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:149)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
23:47:24,964 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.data-source.XXX: org.jboss.msc.service.StartException in service org.wildfly.data-source.XXX: WFLYJCA0033: Error during the deployment of XXX
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:151)
... 5 more
23:47:24,968 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "XXX")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.XXX" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.XXX: WFLYJCA0033: Error during the deployment of XXX
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.XXX"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
{code}
h2. Step 2. Fulfill the connection-url only:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
h2. Step 3. Call test-connection-in-pool() operation of this created data-source
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
There will be warning of exception in server log:
{code:}
10:30:39,185 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) 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:1320)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:496)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:1052)
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:234)
at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:90)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: javax.resource.ResourceException: IJ031087: Failed to register DriverClass for: org.h2.Driver
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getDriver(LocalManagedConnectionFactory.java:602)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:320)
... 28 more
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.driverClassLoader(AbstractDataSourceService.java:310)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.access$200(AbstractDataSourceService.java:103)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer$2.getClassLoader(AbstractDataSourceService.java:472)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getDriver(LocalManagedConnectionFactory.java:593)
... 29 more
{code}
{panel:title=NOTE}
Run a {{:reload()}} after Step 1 works fine
Same data-source name with different {{jndi-name}} works fine
Different data-source name with same {{jndi-name}} fails.
{panel}
was:
h2. Step 1. Try to add a data-source with missing information
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.XXX" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.XXX: WFLYJCA0033: Error during the deployment of XXX
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.XXX"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
},
"rolled-back" => true
}
{code}
There will be exception in server log:
{code:}
23:47:24,962 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Error during the deployment of java:/XXX: javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: XXX
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createConnectionFactory(LocalManagedConnectionFactory.java:108)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:775)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:312)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:371)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:149)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
23:47:24,964 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.data-source.XXX: org.jboss.msc.service.StartException in service org.wildfly.data-source.XXX: WFLYJCA0033: Error during the deployment of XXX
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:151)
... 5 more
23:47:24,968 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "XXX")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.XXX" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.XXX: WFLYJCA0033: Error during the deployment of XXX
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.XXX"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
{code}
h2. Step 2. Fulfill the missing information:
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
{"outcome" => "success"}
{code}
h2. Step 3. Call test-connection-in-pool() operation of this created data-source
{code:}
[standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:test-connection-in-pool()
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid",
"rolled-back" => true
}
{code}
There will be warning of exception in server log:
{code:}
10:30:39,185 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) 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:1320)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:496)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:1052)
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:234)
at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:90)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: javax.resource.ResourceException: IJ031087: Failed to register DriverClass for: org.h2.Driver
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getDriver(LocalManagedConnectionFactory.java:602)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:320)
... 28 more
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.driverClassLoader(AbstractDataSourceService.java:310)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.access$200(AbstractDataSourceService.java:103)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer$2.getClassLoader(AbstractDataSourceService.java:472)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getDriver(LocalManagedConnectionFactory.java:593)
... 29 more
{code}
{panel:title=NOTE}
Run a {{:reload()}} after Step 1 works fine
Same data-source name with different {{jndi-name}} works fine
Different data-source name with same {{jndi-name}} fails.
{panel}
> Warning of IllegalStateException on test-connection-pool for DataSources added after previous failure addition
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7214
> URL: https://issues.jboss.org/browse/WFLY-7214
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
>
> When a data-source was failed to be added either because of missing connection-properties:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2)
> {code}
> or missing of connection-url:
> {code:}
> /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2)
> {code}
> , it can be added by correcting the information, like:
> {code:}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:test")
> {"outcome" => "success"}
> {code}
> But the {{test-connection-in-pool()}} operation failed with {{IllegalStateException}} of the new created data-source.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-6149) Improve control over 'hibernate.id.new_generator_mappings' setting
by Arjun Kumar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6149?page=com.atlassian.jira.plugin.... ]
Arjun Kumar commented on WFLY-6149:
-----------------------------------
I don't think I have access to assign this issue to myself, but I am going to take a look at this.
> Improve control over 'hibernate.id.new_generator_mappings' setting
> ------------------------------------------------------------------
>
> Key: WFLY-6149
> URL: https://issues.jboss.org/browse/WFLY-6149
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 9.0.2.Final, 10.0.0.Final
> Reporter: Chris Poulsen
>
> It would be great if Wildfly offered better control over the properties used for configuring persistence units.
> For instance the 'hibernate.id.new_generator_mappings' setting has proven hard to control it currently requires one to change persistence.xml to turn it off.
> Hibernate supports specifying the properties in various ways, for example via system properties, but wildfly forces the new mappings to be enabled unless the persistence.xml says to disable them.
> There are some suggestions to how [~smarlow] imagines this to be implemented in the forum thread: https://developer.jboss.org/thread/267613
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7754) WELD o.j.w.e.IllegalStateException after saved session does not auto-recover
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7754?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-7754:
--------------------------------------
What shows up in the log when this happens?
> WELD o.j.w.e.IllegalStateException after saved session does not auto-recover
> ----------------------------------------------------------------------------
>
> Key: WFLY-7754
> URL: https://issues.jboss.org/browse/WFLY-7754
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Web (Undertow)
> Affects Versions: 10.0.0.Final
> Reporter: Darryl Miles
> Assignee: Stuart Douglas
>
> When modifying the WELD bean profile between starting/stopping WildFly with persistent session cookies over restart enabled.
> It is possible to get an unrecoverable o.j.w.e.IllegalStateException.
> What I mean by this is that if the AS knows the HTTP session cookie is a valid ID, but is unable to recover it from the persistence serialization over a restart (due to a change in the WELD BeanIdentifer instances changing to allow the optimization to work in this area). What the AS should do is simply log the problem and invalidate the session cookie completely. All this should happen in a transparent way to the WebApp, so it gets a null return or a brand new HttpSession.
> This will automatically allow the HTTP client to recover, by forcing the application to generate a new HTTP session as necessary / or force logout, etc..
> This is unrecoverable since the exception seems to be thrown at a level before it hits any WebApp application code. So it doesn't seem possible for the WebApp developer to correct the problem from the exception. Which makes sense since you need a HttpSession object to invoke #invalidate() on and it is recovering that that is.
> Everytime the user refreshes all they get is the error and a HTTP/500 Internal Server Error and the user has to either delete their cookie, or the WildFly admin shutdown and remove any persistent session cookie data.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7757) Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-7757?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-7757:
-------------------------------
Description:
In WF9, the following commands were valid:
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource)
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS)
In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF10, these operations should still work, and should return a value translated from the "data-source" attribute.
was:
In WF9, the following commands were valid:
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource)
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS)
In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute.
> Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-7757
> URL: https://issues.jboss.org/browse/WFLY-7757
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.Alpha1
>
>
> In WF9, the following commands were valid:
> /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource)
> /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS)
> In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF10, these operations should still work, and should return a value translated from the "data-source" attribute.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7757) Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-7757?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-7757:
-------------------------------
Description:
In WF9, the following commands were valid:
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource)
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS)
In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute.
was:
In WF10, the following commands were valid:
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource)
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS)
In WF11, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute.
> Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-7757
> URL: https://issues.jboss.org/browse/WFLY-7757
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.Alpha1
>
>
> In WF9, the following commands were valid:
> /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource)
> /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS)
> In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7757) Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-7757?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-7757:
-------------------------------
Affects Version/s: 10.1.0.Final
> Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-7757
> URL: https://issues.jboss.org/browse/WFLY-7757
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.Alpha1
>
>
> In WF9, the following commands were valid:
> /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource)
> /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS)
> In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFCORE-2089) Infinite wildfly boot on StartException in service start
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2089?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2089:
------------------------------------------
[~dlofthouse] I assigned this back to myself by mistake. But if what I suggest in my last comment sounds right to you, I'd be happy to take it on. I hear you are a bit busy. ;)
> Infinite wildfly boot on StartException in service start
> --------------------------------------------------------
>
> Key: WFCORE-2089
> URL: https://issues.jboss.org/browse/WFCORE-2089
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Jan Kalina
> Assignee: Brian Stansberry
> Priority: Blocker
> Attachments: threads-2.txt, threads.txt
>
>
> Following exception (and probably similar too) will cause wildfly frozing during start. Visible especially during integration tests (which will never ends), but reproducible directly too (see steps).
> {code:java}
> 15:59:37,252 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.security-realm.ManagementRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ManagementRealm: WFLYELY00025: Referenced property file is invalid: ELY01006: No realm name found in password property file
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:185)
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:164)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *Update:* This problem with infinite boot will occure everytime the start() method of some service throws StartException(). Not an Elytron problem.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-7758) Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-7758:
----------------------------------
Summary: Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes
Key: WFLY-7758
URL: https://issues.jboss.org/browse/WFLY-7758
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 11.0.0.Alpha1
In WF10, the following commands were valid:
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource)
/subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS)
In WF11, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFCORE-2094) HC is unaware when managed server's MSC is unstable
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-2094:
----------------------------------------
Summary: HC is unaware when managed server's MSC is unstable
Key: WFCORE-2094
URL: https://issues.jboss.org/browse/WFCORE-2094
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The HC should be aware if a managed server has a service container that cannot stabilize.
What it will do with this information can evolve over time, but it should at least log it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months