[JBoss JIRA] (WFLY-324) xinclude support in the management model
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-324?page=com.atlassian.jira.plugin.s... ]
Jason Greene commented on WFLY-324:
-----------------------------------
I have a prototype for this, but it requires further discussion. Deferring to 9
> xinclude support in the management model
> ----------------------------------------
>
> Key: WFLY-324
> URL: https://issues.jboss.org/browse/WFLY-324
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Jason Greene
> Fix For: 9.0.0.CR1
>
>
> Ability to use xinclude in the domain/xml/host.xml/standalone.xml documents. Not necessarily anywhere, but where the model supports storing the information. Upon changes to the model, persistence of the relevant elements would be to the specified file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (WFLY-324) xinclude support in the management model
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-324?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-324:
------------------------------
Fix Version/s: 9.0.0.CR1
(was: 8.0.0.CR1)
(was: 8.0.0.Final)
> xinclude support in the management model
> ----------------------------------------
>
> Key: WFLY-324
> URL: https://issues.jboss.org/browse/WFLY-324
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Jason Greene
> Fix For: 9.0.0.CR1
>
>
> Ability to use xinclude in the domain/xml/host.xml/standalone.xml documents. Not necessarily anywhere, but where the model supports storing the information. Upon changes to the model, persistence of the relevant elements would be to the specified file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (WFLY-2821) Intermittent failures in EE resource injection tests
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2821?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2821:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 8.0.0.Final)
> Intermittent failures in EE resource injection tests
> ----------------------------------------------------
>
> Key: WFLY-2821
> URL: https://issues.jboss.org/browse/WFLY-2821
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EE
> Affects Versions: 8.0.0.CR1
> Reporter: Brian Stansberry
> Assignee: David Lloyd
> Fix For: 9.0.0.CR1
>
>
> The set of 5 failures shown below are recurring intermittently in the WF testsuite:
> http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=8698&buildType...
> org.jboss.as.test.integration.ee.injection.resource.enventry
> EnvEntryInjectionTestCase.testNonExistantResourceCannotBeLookedUp
> org.jboss.as.test.integration.ee.injection.resource.noncomponent
> NonComponentResourceInjectionTestCase.testBindingDoesNotExist
> org.jboss.as.test.integration.ee.injection.resource.persistencecontextref
> PersistenceContextRefTestCase.testCorrectPersistenceUnitInjectedFromAnnotation2
> PersistenceContextRefTestCase.testCorrectPersistenceUnitInjectedFromPersistenceUnitRef
> PersistenceContextRefTestCase.testCorrectPersistenceUnitInjectedFromRefInjectionTarget2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (WFLY-2774) Non-distributed, stateful web applications cannot be load balanced using sticky sessions
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2774?page=com.atlassian.jira.plugin.... ]
Jason Greene commented on WFLY-2774:
------------------------------------
This should be resolved once CR2 of undertow is included
> Non-distributed, stateful web applications cannot be load balanced using sticky sessions
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-2774
> URL: https://issues.jboss.org/browse/WFLY-2774
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
> Fix For: 8.0.0.Final
>
>
> In AS7, one could configure a load balancer with sticky sessions to support load balancing for non-distributed web applications.
> While the distributed session manager supports parsing and formatting of the instance-id from/to the session id, the in-memory session manager does not.
> The use case for this are stateful web applications that do not require high-availability of state (e.g. a stateless web-app that uses container managed authentication), but would also like to scale beyond the capacity of a single server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (WFLY-2641) ARQ upgrade likely to cause test failures
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2641?page=com.atlassian.jira.plugin.... ]
Jason Greene reassigned WFLY-2641:
----------------------------------
Assignee: Jason Greene (was: Aslak Knutsen)
> ARQ upgrade likely to cause test failures
> ------------------------------------------
>
> Key: WFLY-2641
> URL: https://issues.jboss.org/browse/WFLY-2641
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
> Assignee: Jason Greene
> Priority: Blocker
> Fix For: 9.0.0.CR1
>
>
> {code}
> testSimpleBundleWithWabExtension(org.jboss.test.osgi.example.webapp.WebAppTestCase) Time elapsed: 0.028 sec <<< ERROR!
> java.lang.NullPointerException: null
> at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:290)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (WFLY-2592) A server-to-server communication via outbound connection is not working
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2592?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2592:
-------------------------------
Priority: Critical (was: Blocker)
> A server-to-server communication via outbound connection is not working
> -----------------------------------------------------------------------
>
> Key: WFLY-2592
> URL: https://issues.jboss.org/browse/WFLY-2592
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB, Remoting
> Affects Versions: 8.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: David Lloyd
> Priority: Critical
> Labels: ejb, remoting
> Attachments: networktraffic, server-client.log, server-server.log
>
>
> A ejb invocation from a SLSB is configured similar to AS7 (EAP6) to call a remote server fail in WildFly with the ERROR message " EJBCLIENT000025: No EJB receiver available for handling".
> The logfiles of client(server) and remote-server are attached, also a WireShark dump of the related network traffic.
> A standalone client at the same machine is able to call the remote application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (WFLY-2641) ARQ upgrade likely to cause test failures
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2641?page=com.atlassian.jira.plugin.... ]
Jason Greene commented on WFLY-2641:
------------------------------------
We will revisit our test suite in WF9, including whether or not we stick with Arquillian.
> ARQ upgrade likely to cause test failures
> ------------------------------------------
>
> Key: WFLY-2641
> URL: https://issues.jboss.org/browse/WFLY-2641
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
> Assignee: Aslak Knutsen
> Priority: Blocker
> Fix For: 9.0.0.CR1
>
>
> {code}
> testSimpleBundleWithWabExtension(org.jboss.test.osgi.example.webapp.WebAppTestCase) Time elapsed: 0.028 sec <<< ERROR!
> java.lang.NullPointerException: null
> at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:290)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months