[JBoss JIRA] (WFLY-7189) UT000010: Session not found
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-7189?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-7189.
----------------------------
> UT000010: Session not found
> ---------------------------
>
> Key: WFLY-7189
> URL: https://issues.jboss.org/browse/WFLY-7189
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.2.Final
> Environment: Production
> Reporter: Alpesh B
> Assignee: Jason Greene
> Priority: Critical
> Labels: wildfly
>
> In my application I am using 4 different database connection with spring,
> Before upgrading to wildfly 9.0.2 Final it was working fine, but yesterday from production I came to know that one database is not able to connect. and giving following exception
> {code:java}
> Caused by: java.lang.IllegalStateException: UT000010: Session not found ONaa4NC8R3y3WuYRhMjp5kD0__MXIkMtHbginKOx
> INFO | jvm 1 | 2016/09/21 05:53:09 | at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:430)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:123)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.util.WebUtils.getSessionMutex(WebUtils.java:328)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.context.request.ServletRequestAttributes.getSessionMutex(ServletRequestAttributes.java:191)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.context.request.SessionScope.get(SessionScope.java:88)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:285)
> {code}
> While, I was able to connect to other databases through the application, only facing issues for accessing one of the database.
> After restart of wildfly server issue is resolved, Even I am not able to reproduce it
> [OpenIssue|[#https://developer.jboss.org/message/949465#949465]]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-6967) Client connection are not balanced across cluster with any load balancing policy
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6967?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-6967:
----------------------------------
[~ataylor] [~martyn-taylor] is this old issue still relevant? If not please close it
> Client connection are not balanced across cluster with any load balancing policy
> --------------------------------------------------------------------------------
>
> Key: WFLY-6967
> URL: https://issues.jboss.org/browse/WFLY-6967
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.1.0.CR1
> Reporter: Chen Maoqian
> Assignee: Andy Taylor
> Priority: Critical
>
> *Scenario*
> There two nodes in cluster. Nodes in cluster are connected and both nodes have same jms destinations and connection factory defined like the following one
> {noformat}
> <connection-factory name="RemoteConnectionFactory" connectors="http-connector" entries="java:jboss/exported/jms/RemoteConnectionFactory" ha="true" connection-ttl="120000" call-timeout="60000" block-on-acknowledge="true" retry-interval="1000" reconnect-attempts="-1" connection-load-balancing-policy-class-name="org.apache.activemq.artemis.api.core.client.loadbalance.RandomConnectionLoadBalancingPolicy"/>
> {noformat}
> There are clients connecting to cluster. With _RandomConnectionLoadBalancingPolicy_, I would expect that connections are randomly distributed among the nodes in cluster. However, when I list connections on both nodes (/subsystem=messaging-activemq/server=default:list-connection-ids), all connections are on one server.
> Method {{private TransportConfiguration selectConnector()}} in class {{ServerLocatorImpl}} checks whether the {{topologyArray}} is null and makes decision between choosing connector to other node in topology or initial connector of connection factory. In method {{private TransportConfiguration selectConnector()}} {{topologyArray}} is still null, so clients make connection using initial connector. It seems like {{topologyArray}} is only updated during {{notifyNodeUp/Down}} methods.
> Could you please explain how is this client connection balancing supposed to work?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-7189) UT000010: Session not found
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-7189?page=com.atlassian.jira.plugin.... ]
Kabir Khan resolved WFLY-7189.
------------------------------
Resolution: Out of Date
> UT000010: Session not found
> ---------------------------
>
> Key: WFLY-7189
> URL: https://issues.jboss.org/browse/WFLY-7189
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.2.Final
> Environment: Production
> Reporter: Alpesh B
> Assignee: Jason Greene
> Priority: Critical
> Labels: wildfly
>
> In my application I am using 4 different database connection with spring,
> Before upgrading to wildfly 9.0.2 Final it was working fine, but yesterday from production I came to know that one database is not able to connect. and giving following exception
> {code:java}
> Caused by: java.lang.IllegalStateException: UT000010: Session not found ONaa4NC8R3y3WuYRhMjp5kD0__MXIkMtHbginKOx
> INFO | jvm 1 | 2016/09/21 05:53:09 | at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:430)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:123)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.util.WebUtils.getSessionMutex(WebUtils.java:328)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.context.request.ServletRequestAttributes.getSessionMutex(ServletRequestAttributes.java:191)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.context.request.SessionScope.get(SessionScope.java:88)
> INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:285)
> {code}
> While, I was able to connect to other databases through the application, only facing issues for accessing one of the database.
> After restart of wildfly server issue is resolved, Even I am not able to reproduce it
> [OpenIssue|[#https://developer.jboss.org/message/949465#949465]]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-6849) Duplicate messages in replicated HA topology when backup is shutdowned
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6849?page=com.atlassian.jira.plugin.... ]
Kabir Khan resolved WFLY-6849.
------------------------------
Fix Version/s: 11.0.0.Final
Resolution: Done
> Duplicate messages in replicated HA topology when backup is shutdowned
> ----------------------------------------------------------------------
>
> Key: WFLY-6849
> URL: https://issues.jboss.org/browse/WFLY-6849
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Bartosz Baranowski
> Assignee: Clebert Suconic
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 11.0.0.Final
>
>
> Scenario
> # Configure 2 nodes in replicated dedicated topology
> # Start live (node-1) and backup (node-2)
> # Start producer
> # Shut down node-2
> # Stop producer
> # Check if there are some duplicates on node-1 using CLI operation list-messages
> Expectation: there is no duplications
> Actual state: there are 10 messages with the same _AMQ_DUPL_ID twice
> After that Backup is shut downed, the Live is not able to replicate its data to Backup. It waits 30 seconds until timeouts expire. Meanwhile producer does not get response from Live and it gets TimeoutException on commit. It retries to send the same batch of messages and then commit them again. I think that problem is at this point. The Live does not detect duplicate messages.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-6263) Apostrophe in an attribute with multiple EL parts breaks function lookup
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6263?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-6263:
-----------------------------
Fix Version/s: 12.0.0.Final
> Apostrophe in an attribute with multiple EL parts breaks function lookup
> ------------------------------------------------------------------------
>
> Key: WFLY-6263
> URL: https://issues.jboss.org/browse/WFLY-6263
> Project: WildFly
> Issue Type: Bug
> Components: EE, Web (Undertow)
> Affects Versions: 10.0.0.Final
> Reporter: Paul Pogonyshev
> Assignee: Tomaz Cerar
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 12.0.0.Final
>
> Attachments: jastow-bug.war.zip, jastow.diff
>
>
> Certain EL pieces result in unexplained org.apache.jasper.JasperException "contains invalid expression(s)" (the exception _does not_ explain what is invalid). After lots of tries, I have narrowed it down: 1) there must be several EL pieces in one string; 2) there must be an apostrophe in between.
> This looks very similar to bug WFLY-4455. It breaks several pages in our application, blocking upgrade to WildFly 10.
> Example is attached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-4096) Datasource Defined in web.xml Does Not Work with JPA Entity Manager
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4096?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4096.
----------------------------
Resolution: Out of Date
> Datasource Defined in web.xml Does Not Work with JPA Entity Manager
> -------------------------------------------------------------------
>
> Key: WFLY-4096
> URL: https://issues.jboss.org/browse/WFLY-4096
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Web (Undertow)
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Environment: Windows 7
> Java 8u25
> WildFly 8.1.0.Final
> Reporter: shinzey shinzey
> Assignee: Scott Marlow
> Priority: Critical
> Labels: datasource, deployment, jpa, persistence.xml, persistenceUnit
>
> The datasource defined in web.xml:
> {quote}
> <data-source>
> <name>java:/datasources/test</name>
> <class-name>org.apache.derby.jdbc.ClientDataSource</class-name>
> <database-name>test</database-name>
> <url>jdbc:derby://localhost:1527/test</url>
> <user>test</user>
> <password>test</password>
> </data-source>
> {quote}
> The persistence unit:
> {quote}
> <persistence-unit name="wtpu" transaction-type="JTA">
> <jta-data-source>java:/datasources/test</jta-data-source>
> </persistence-unit>
> {quote}
> The deployment error:
> {quote}
> 17:57:10,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "WebTest.war" (runtime-name: "WebTest.war")
> 17:57:11,078 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for wtpu
> 17:57:11,172 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "WebTest.war")]) - failure description: ("JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"WebTest.war#wtpu\".__FIRST_PHASE__ is missing [jboss.naming.context.java.datasources.test]"])
> 17:57:11,187 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "WebTest.war" (runtime-name : "WebTest.war")
> 17:57:11,187 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.naming.context.java.datasources.test (missing) dependents: [service jboss.persistenceunit."WebTest.war#wtpu".__FIRST_PHASE__]
> {quote}
> If I remove the persistence unit, the datasource can be successfully bound:
> {quote}
> 17:55:47,851 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/datasources/test]
> {quote}
> The same code works as expected in GlassFish 4.1, and the @DataSourceDefinition annotation has the same issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-4212) REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4212?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4212.
----------------------------
Resolution: Out of Date
> REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
> -------------------------------------------------------------
>
> Key: WFLY-4212
> URL: https://issues.jboss.org/browse/WFLY-4212
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Jason Greene
> Priority: Critical
> Attachments: 8.1.0-cluster_logs.2014-12-31T04-01-53.tar.gz, 8.2.0-cluster_logs.2014-12-31T04-19-06.tar.gz
>
>
> While testing an upgrade to 8.2.0 a multi-component integration test that worked on 8.1.0 failed to deploy.
> A distilled clean-room test case reproducing the problem is located here: https://github.com/arcivanov/misc/tree/WFCORE-488/WFCORE-488
> This bug is also accompanied by the failure to undeploy partial deployment in WFCORE-488, although at present the above test case not yet reproduces the behavior.
> The deployment error on 8.2.0 is as follows:
> {noformat}
> 2014-12-31 04:17:11,877 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:372)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:293)
> at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:531)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_25]
> ... 3 more
> 2014-12-31 04:17:11,886 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "bf40aa60-1792-473b-bc2c-344adf89790c.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> 2014-12-31 04:17:11,889 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 66) JBAS015870: Deploy of deployment "bf40aa60-1792-473b-bc2c-344adf89790c.ear" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-4096) Datasource Defined in web.xml Does Not Work with JPA Entity Manager
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4096?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-4096:
----------------------------------
[~smarlow] [~shinzey] I am closing this because it is so old and I don't think it is being looked at
> Datasource Defined in web.xml Does Not Work with JPA Entity Manager
> -------------------------------------------------------------------
>
> Key: WFLY-4096
> URL: https://issues.jboss.org/browse/WFLY-4096
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Web (Undertow)
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Environment: Windows 7
> Java 8u25
> WildFly 8.1.0.Final
> Reporter: shinzey shinzey
> Assignee: Scott Marlow
> Priority: Critical
> Labels: datasource, deployment, jpa, persistence.xml, persistenceUnit
>
> The datasource defined in web.xml:
> {quote}
> <data-source>
> <name>java:/datasources/test</name>
> <class-name>org.apache.derby.jdbc.ClientDataSource</class-name>
> <database-name>test</database-name>
> <url>jdbc:derby://localhost:1527/test</url>
> <user>test</user>
> <password>test</password>
> </data-source>
> {quote}
> The persistence unit:
> {quote}
> <persistence-unit name="wtpu" transaction-type="JTA">
> <jta-data-source>java:/datasources/test</jta-data-source>
> </persistence-unit>
> {quote}
> The deployment error:
> {quote}
> 17:57:10,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "WebTest.war" (runtime-name: "WebTest.war")
> 17:57:11,078 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for wtpu
> 17:57:11,172 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "WebTest.war")]) - failure description: ("JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"WebTest.war#wtpu\".__FIRST_PHASE__ is missing [jboss.naming.context.java.datasources.test]"])
> 17:57:11,187 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "WebTest.war" (runtime-name : "WebTest.war")
> 17:57:11,187 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.naming.context.java.datasources.test (missing) dependents: [service jboss.persistenceunit."WebTest.war#wtpu".__FIRST_PHASE__]
> {quote}
> If I remove the persistence unit, the datasource can be successfully bound:
> {quote}
> 17:55:47,851 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/datasources/test]
> {quote}
> The same code works as expected in GlassFish 4.1, and the @DataSourceDefinition annotation has the same issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months