May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2667) Support application-level batch configuration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2667?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2667: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Support application-level batch configuration > --------------------------------------------- > > Key: WFLY-2667 > URL: https://issues.jboss.org/browse/WFLY-2667 > Project: WildFly > Issue Type: Feature Request > Components: Batch > Affects Versions: 8.0.0.Beta1 > Reporter: Cheng Fang > Assignee: James Perkins > Fix For: 9.0.0.CR2 > > > Applications should be able to override certain batch configuration in WildFly batch subsystem with application deployment descriptors. In particular, applications may want to specify their own datasource jndi-name for batch job repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2652) Add/remove load metric operations should not require service restart

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2652?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2652: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Add/remove load metric operations should not require service restart > -------------------------------------------------------------------- > > Key: WFLY-2652 > URL: https://issues.jboss.org/browse/WFLY-2652 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2900: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Performance issue with Xalan transformer and very large text nodes > ------------------------------------------------------------------ > > Key: WFLY-2900 > URL: https://issues.jboss.org/browse/WFLY-2900 > Project: WildFly > Issue Type: Bug > Components: XML Frameworks > Reporter: Kyle Lape > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.CR2 > > > It has been observed that when using the {{Transfomer}} to convert a {{StreamSource}} to {{DOMResult}}, the performance of Transform gets worse as the size of the > character data increases. If you have a 50MB text blob in XML, this will take a very long time to finish. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2876) Add mod_cluster support for all Undertow servers, not only the default-server

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2876?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2876: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Add mod_cluster support for all Undertow servers, not only the default-server > ----------------------------------------------------------------------------- > > Key: WFLY-2876 > URL: https://issues.jboss.org/browse/WFLY-2876 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2 > > > Currently only the default host is registered with the proxy. > This will require: > * configuration change for listener<>host mapping > * instance-id be configured per server, instead of per whole undertow subsystem (or just appended to the unique server name) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2858) JPA doesn't parse for "urn:jboss:jpa" namespace in jboss-all.xml

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2858?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2858: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > JPA doesn't parse for "urn:jboss:jpa" namespace in jboss-all.xml > ---------------------------------------------------------------- > > Key: WFLY-2858 > URL: https://issues.jboss.org/browse/WFLY-2858 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 8.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Scott Marlow > Priority: Minor > Fix For: 9.0.0.CR2 > > > Looks like the parser is only parsing for "http://www.jboss.com/xml/ns/javaee" and never for "urn:jboss:jpa". This makes the schema less useful. > https://github.com/wildfly/wildfly/blob/master/build/src/main/resources/d... > Example file: > https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basi... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3188) Optimize use of Infinispan listeners

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3188?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3188: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Optimize use of Infinispan listeners > ------------------------------------ > > Key: WFLY-3188 > URL: https://issues.jboss.org/browse/WFLY-3188 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR2 > > > Typically, when we use an Infinispan cache listener, we only need it to be invoked on one node in the cluster. Infinispan 6/7 have added several mechanisms to filter when listeners are invoked. For example, we can leverage @Listener(primaryOnly = true) in many places. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3044) Mojarra's @ViewScoped implementation is not cluster-aware resulting in NotSerializableException

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3044?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3044: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Mojarra's @ViewScoped implementation is not cluster-aware resulting in NotSerializableException > ----------------------------------------------------------------------------------------------- > > Key: WFLY-3044 > URL: https://issues.jboss.org/browse/WFLY-3044 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 9.0.0.CR2 > > > The problem is in ViewScopeContextManager, namely > {code} > getContextMap(facesContext).put(contextual, new ViewScopeContextObject(contextual, creational, name)); > {code} > probably it needs an artificial ID generated to serve as a key. > Also the ViewScopeContextObject needs to be serializable as well among other things > {code} > class ViewScopeContextObject { > {code} > Issue manifests as > {noformat}[Server:server-one] 19:22:41,564 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-15) ISPN000136: Execution error: org.infinispan.commons.CacheException: java.lang.RuntimeException: Failure to marshal argument(s) > [Server:server-one] at org.infinispan.commons.util.Util.rewrapAsCacheException(Util.java:581) > ... > [Server:server-one] at org.infinispan.transaction.tm.DummyTransaction.notifyAfterCompletion(DummyTransaction.java:263) > [Server:server-one] at org.infinispan.transaction.tm.DummyTransaction.runCommitTx(DummyTransaction.java:312) > [Server:server-one] at org.infinispan.transaction.tm.DummyTransaction.commit(DummyTransaction.java:69) > [Server:server-one] at org.infinispan.transaction.tm.DummyBaseTransactionManager.commit(DummyBaseTransactionManager.java:80) > [Server:server-one] at org.infinispan.batch.BatchContainer.resolveTransaction(BatchContainer.java:101) > [Server:server-one] at org.infinispan.batch.BatchContainer.endBatch(BatchContainer.java:83) > [Server:server-one] at org.infinispan.batch.BatchContainer.endBatch(BatchContainer.java:64) > [Server:server-one] at org.infinispan.CacheImpl.endBatch(CacheImpl.java:777) > [Server:server-one] at org.infinispan.AbstractDelegatingCache.endBatch(AbstractDelegatingCache.java:53) > [Server:server-one] at org.wildfly.clustering.web.infinispan.InfinispanBatcher$1.end(InfinispanBatcher.java:56) > [Server:server-one] at org.wildfly.clustering.web.infinispan.InfinispanBatcher$1.close(InfinispanBatcher.java:46) > [Server:server-one] at org.wildfly.clustering.web.undertow.session.DistributableSession.requestDone(DistributableSession.java:72) > [Server:server-one] at io.undertow.servlet.spec.ServletContextImpl.updateSessionAccessTime(ServletContextImpl.java:704) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > [Server:server-one] at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:522) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > [Server:server-one] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:287) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > [Server:server-one] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > [Server:server-one] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > [Server:server-one] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > [Server:server-one] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > [Server:server-one] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > [Server:server-one] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > [Server:server-one] Caused by: java.lang.RuntimeException: Failure to marshal argument(s) > [Server:server-one] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.marshallCall(CommandAwareRpcDispatcher.java:333) > [Server:server-one] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:352) > [Server:server-one] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:167) > [Server:server-one] ... 76 more > [Server:server-one] Caused by: org.infinispan.commons.marshall.NotSerializableException: org.jboss.weld.bean.ManagedBean > [Server:server-one] Caused by: an exception which occurred: > [Server:server-one] in object java.util.HashMap@b37422bb > [Server:server-one] in object org.jboss.as.clustering.marshalling.SimpleMarshalledValue@b37422bb > [Server:server-one] in object org.infinispan.commands.write.PutKeyValueCommand@db517a36 > [Server:server-one] in object org.infinispan.commands.tx.PrepareCommand@6fa34718 > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2990) Forward port EAP 6.2/6.3 xml schemas

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2990?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2990: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Forward port EAP 6.2/6.3 xml schemas > ------------------------------------ > > Key: WFLY-2990 > URL: https://issues.jboss.org/browse/WFLY-2990 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Priority: Blocker > Fix For: 9.0.0.CR2 > > > EAP 6.3 will be introducing new versions of domain configuration xml schemas. These will basically be schemas containing some subset of the diff between the AS 7.2 schemas and the WF 9 schemas. > These schemas and parsing thereof need to be forward ported into WF. > Hopefully the schemas used for EAP 6.2 are already forward ported and this is mostly about 6.3. > This is a parent task to capture the overall requirement and the task of analyzing what areas need the forward port. Subtasks or linked issues should be used for the specific porting tasks (e.g. one per subsystem) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2982) refactor two phase persistence unit services (PhaseOnePersistenceUnitServiceImpl + PersistenceUnitServiceImpl) into one service

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2982?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2982: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > refactor two phase persistence unit services (PhaseOnePersistenceUnitServiceImpl + PersistenceUnitServiceImpl) into one service > ------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2982 > URL: https://issues.jboss.org/browse/WFLY-2982 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 8.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.CR2 > > > Related feedback from https://github.com/wildfly/wildfly/pull/4722: > {quote} > This is asymetrical, so if this service , and phase one are stopped, and then phase 1 is started again, phase 2 will appear started. The side effects seem minor though > {quote} > {quote} > We have a long term goal to somehow verify every service can be stopped and started with the expected effect. Right now many of our services are not restartable which makes potential new features like partial deployment standby hard to achieve. So Im just offering pointers whenever I see lifecycle symmetry issues. > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3449) Add a unit test that verifies that Hibernate ORM 4.3.5 jars can be included with an application

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3449?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3449: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Add a unit test that verifies that Hibernate ORM 4.3.5 jars can be included with an application > ----------------------------------------------------------------------------------------------- > > Key: WFLY-3449 > URL: https://issues.jboss.org/browse/WFLY-3449 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.CR2 > > > Unit test should get the classloader for one of the Hibernate classes and verify that its the application classloader. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2015