[JBoss JIRA] (SWSQE-80) Automated deployment of Istio Traffice Management
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-80?page=com.atlassian.jira.plugin.s... ]
Matt Mahoney commented on SWSQE-80:
-----------------------------------
Possible sub-tasks:
* Deploy service-mesh
* Generate traffic to service-mesh
* Deploy Circuit Breaker
* Deploy RouteRules
* Jenkins Job(s) for above (aka: swsqe-88)
Open questions:
* Determine how to integrate with automation test cases
* Determine how to integrate into Pipeline
> Automated deployment of Istio Traffice Management
> -------------------------------------------------
>
> Key: SWSQE-80
> URL: https://issues.jboss.org/browse/SWSQE-80
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
>
> As a test engineer I want an automated way to deploy Istio Traffic Management such as Route Rules and Circuit Breakers into my test configuration.
> Istio documentation reference: [link title|https://istio.io/docs/tasks/traffic-management/]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-4096) Datasource Defined in web.xml Does Not Work with JPA Entity Manager
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-4096?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-4096:
------------------------------------
Makes sense to close, I'm guessing it was the datasource name, switching from java:/datasources/test to java:jboss/datasources/test might of helped.
> 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)
8 years, 1 month
[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)
8 years, 1 month
[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)
8 years, 1 month
[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)
8 years, 1 month