[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on WFLY-1725 at 7/19/13 3:52 PM:
--------------------------------------------------------------------
I think at a minimum, the High Availability Guide should touch on all key aspects of AS8 clustering; if there are no significant changes, even a small mention and summary might well suffice. For subsystems/components/modules which may have changed significantly, more detail may be justified. In the end, the user should have a good overview of what is provided in terms of clustering features.
Some key aspects:
* changes since AS 7
* the major subsystems and their configuration options
* HA functionality provided, in overview (e.g. web session clustering, EJB clustering, Hibernate level clustering, HA-JNDI, load balancing/mod-cluster)
* modularity and class loading with regard to application deployment
was (Author: rachmato):
I think at a minimum, the High Availability Guide should touch on all key aspects of AS8 clustering; if there are no significant changes, even a small mention and summary might well suffice. For subsystems/components/modules which may have changed significantly, more detail may be justified. In the end, the user should have a good overview of what is provided in terms of clustering features.
Some key aspects:
- changes since AS 7
- the major subsystems and their configuration options
- HA functionality provided, in overview (e.g. web session clustering, EJB clustering, Hibernate level clustering, HA-JNDI, load balancing/mod-cluster)
- modularity and class loading with regard to application deployment
> Update The Wildfly High Availability Guide
> -------------------------------------------
>
> Key: WFLY-1725
> URL: https://issues.jboss.org/browse/WFLY-1725
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha3
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 8.0.0.Beta1
>
>
> The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org.
> Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering.
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on WFLY-1725 at 7/19/13 3:49 PM:
--------------------------------------------------------------------
I think the only thing we really need to agree on is what is in and what is not in with regard to content for the High Availability Guide.
For example, in the EAP docs (https://access.redhat.com/site/documentation/JBoss_Enterprise_Application...), the coverage of content is broken down into separate guides, and each guide has its own specific coverage:
* administration & configuration guide (starting/stopping/managing/deploying/configuring)
* api documentation (javadoc for all classes)
* development guide (key technologies: maven build/CDI/Hibernate/Web server/JTA/EJB/Clustering)
* installation guide (download/install/start/stop/upgrade)
* migration guide (migrate app from 5.1 to 6/migration changes/debugging migration problems)
* security guide (everything about configuring security)
Of course, we don't need this level of comprehensiveness.
My proposal would be like a section breakdown like this:
* introdction (brief overview of all features provided and how they relate to each other as a unified clustering subsystem)
* changes since AS7 (undertow, refactoring of apis/modules)
* individual subsystems and their configuration
** jgroups
** infinispan
** ejb
** undertow
** mod cluster
* functional areas (notes on configuring them, some developer related issues)
** web session clustering
** ejb clustering
** Hibernate 2LC
** load balancing
* modularity and class loading for app developers
was (Author: rachmato):
I think the only thing we really need to agree on is what is in and what is not in with regard to content for the High Availability Guide.
For example, in the EAP docs (https://access.redhat.com/site/documentation/JBoss_Enterprise_Application...), the coverage of content is broken down into separate guides, and each guide has its own specific coverage:
- administration & configuration guide (starting/stopping/managing/deploying/configuring)
- api documentation (javadoc for all classes)
- development guide (key technologies: maven build/CDI/Hibernate/Web server/JTA/EJB/Clustering)
- installation guide (download/install/start/stop/upgrade)
- migration guide (migrate app from 5.1 to 6/migration changes/debugging migration problems)
- security guide (everything about configuring security)
Of course, we don't need this level of comprehensiveness.
My proposal would be like a section breakdown like this:
- introdction (brief overview of all features provided and how they relate to each other as a unified clustering subsystem)
- changes since AS7 (undertow, refactoring of apis/modules)
- individual subsystems and their configuration
- jgroups
- infinispan
- ejb
- undertow
- mod cluster
- functional areas (notes on configuring them, some developer related issues)
- web session clustering
- ejb clustering
- Hibernate 2LC
- load balancing
- modularity and class loading for app developers
> Update The Wildfly High Availability Guide
> -------------------------------------------
>
> Key: WFLY-1725
> URL: https://issues.jboss.org/browse/WFLY-1725
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha3
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 8.0.0.Beta1
>
>
> The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org.
> Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering.
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-1725:
-------------------------------------------
I think the only thing we really need to agree on is what is in and what is not in with regard to content for the High Availability Guide.
For example, in the EAP docs (https://access.redhat.com/site/documentation/JBoss_Enterprise_Application...), the coverage of content is broken down into separate guides, and each guide has its own specific coverage:
- administration & configuration guide (starting/stopping/managing/deploying/configuring)
- api documentation (javadoc for all classes)
- development guide (key technologies: maven build/CDI/Hibernate/Web server/JTA/EJB/Clustering)
- installation guide (download/install/start/stop/upgrade)
- migration guide (migrate app from 5.1 to 6/migration changes/debugging migration problems)
- security guide (everything about configuring security)
Of course, we don't need this level of comprehensiveness.
My proposal would be like a section breakdown like this:
- introdction (brief overview of all features provided and how they relate to each other as a unified clustering subsystem)
- changes since AS7 (undertow, refactoring of apis/modules)
- individual subsystems and their configuration
- jgroups
- infinispan
- ejb
- undertow
- mod cluster
- functional areas (notes on configuring them, some developer related issues)
- web session clustering
- ejb clustering
- Hibernate 2LC
- load balancing
- modularity and class loading for app developers
> Update The Wildfly High Availability Guide
> -------------------------------------------
>
> Key: WFLY-1725
> URL: https://issues.jboss.org/browse/WFLY-1725
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha3
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 8.0.0.Beta1
>
>
> The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org.
> Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering.
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-1362) javax.transaction.xa.XAException thrown when using JTS transactions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1362?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1362:
-----------------------------------------------
Tom Ross <tom.ross(a)redhat.com> made a comment on [bug 981174|https://bugzilla.redhat.com/show_bug.cgi?id=981174]
I test this fix with Wildfly Alpha 2 ( this is the only build that currently startup without errors) and it seems to work. I don't see any exceptions any more only few warnings but I don't believe they have anything to do with the original issue. I will ask the JBossTM guys to look at them.
> javax.transaction.xa.XAException thrown when using JTS transactions
> -------------------------------------------------------------------
>
> Key: WFLY-1362
> URL: https://issues.jboss.org/browse/WFLY-1362
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Alpha1
> Environment: JBoss EAP 6.1 ER8
> Reporter: Tom Ross
> Assignee: jaikiran pai
> Fix For: 8.0.0.Alpha2
>
>
> When running the quick start ejb-multi-server example with JTS transactions the following exception is thrown:
> {noformat}
> 11:21:01,462 ERROR [stderr] (RequestProcessor-5) javax.transaction.xa.XAException
> 11:21:01,462 ERROR [stderr] (RequestProcessor-5) at com.arjuna.ats.internal.jta.transaction.jts.jca.XATerminatorImple.recover(XATerminatorImple.java:238)
> 11:21:01,462 ERROR [stderr] (RequestProcessor-5) at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.tryRecoveryForImportedTransaction(XidTransactionManagementTask.java:109)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionCommitTask.manageTransaction(XidTransactionCommitTask.java:62)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.run(XidTransactionManagementTask.java:68)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at java.lang.Thread.run(Thread.java:722)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at ...asynchronous invocation...(Unknown Source)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:99)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.sendCommit(RemotingConnectionEJBReceiver.java:327)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at org.jboss.ejb.client.EJBClientManagedTransactionContext$ResourceImpl.commit(EJBClientManagedTransactionContext.java:239)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at com.arjuna.ats.internal.jta.resources.jts.orbspecific.XAResourceRecord.commit(XAResourceRecord.java:455)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at com.arjuna.ArjunaOTS.OTSAbstractRecordPOA._invoke(OTSAbstractRecordPOA.java:201)
> 11:21:01,466 ERROR [stderr] (RequestProcessor-5) at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:306)
> 11:21:01,466 ERROR [stderr] (RequestProcessor-5) at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:626)
> 11:21:01,466 ERROR [stderr] (RequestProcessor-5) at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:769)
> 11:21:01,467 WARN [com.arjuna.ats.jtax] (RequestProcessor-5) ARJUNA024023: XAResourceRecord.commit caused an XA error: XAException.XAER_PROTO from resource ResourceImpl{transactionKey=0:ffffc0a80164:316a9a9d:5196046f:1a, ejbClientContext=org.jboss.ejb.client.EJBClientContext@216695c0, nodeName='master:app-oneB', state=null} in transaction < 131072, 30, 36, 0000000000-1-1-64-88110049106-102-9981-1064111000264849, 303030303030303030302929-34-583113079136-72-69111-7634141303030567879303030303030 >: javax.transaction.xa.XAException
> at com.arjuna.ats.internal.jta.transaction.jts.jca.XATerminatorImple.recover(XATerminatorImple.java:238) [jbossjts-jacorb-4.17.4.Final-redhat-2.jar:4.17.4.Final-redhat-2]
> at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.tryRecoveryForImportedTransaction(XidTransactionManagementTask.java:109)
> at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionCommitTask.manageTransaction(XidTransactionCommitTask.java:62)
> at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.run(XidTransactionManagementTask.java:68)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_21]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_21]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:99)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.sendCommit(RemotingConnectionEJBReceiver.java:327)
> at org.jboss.ejb.client.EJBClientManagedTransactionContext$ResourceImpl.commit(EJBClientManagedTransactionContext.java:239)
> at com.arjuna.ats.internal.jta.resources.jts.orbspecific.XAResourceRecord.commit(XAResourceRecord.java:455) [jbossjts-jacorb-4.17.4.Final-redhat-2.jar:4.17.4.Final-redhat-2]
> at com.arjuna.ArjunaOTS.OTSAbstractRecordPOA._invoke(OTSAbstractRecordPOA.java:201) [jbossjts-jacorb-4.17.4.Final-redhat-2.jar:4.17.4.Final-redhat-2]
> at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:306) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4]
> at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:626) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4]
> at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:769) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4]
> {noformat}
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-1725:
-------------------------------------------
Some other aspects:
I think adequate framing of sections is important together with well defined and ordered subsections (i.e. introduction and overview, followed by sections with more specific detail)
I also think that consistency of presentation across sections is important, as we move through
- different subsystems
- different collections of functionality
So, for example, touch on the same classes of points in each section (e.g. new features, configuration detail, example)
For an excellent example, I look to the ISPN docs.
> Update The Wildfly High Availability Guide
> -------------------------------------------
>
> Key: WFLY-1725
> URL: https://issues.jboss.org/browse/WFLY-1725
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha3
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 8.0.0.Beta1
>
>
> The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org.
> Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering.
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-1725:
-------------------------------------------
I think at a minimum, the High Availability Guide should touch on all key aspects of AS8 clustering; if there are no significant changes, even a small mention and summary might well suffice. For subsystems/components/modules which may have changed significantly, more detail may be justified. In the end, the user should have a good overview of what is provided in terms of clustering features.
Some key aspects:
- changes since AS 7
- the major subsystems and their configuration options
- HA functionality provided, in overview (e.g. web session clustering, EJB clustering, Hibernate level clustering, HA-JNDI, load balancing/mod-cluster)
- modularity and class loading with regard to application deployment
> Update The Wildfly High Availability Guide
> -------------------------------------------
>
> Key: WFLY-1725
> URL: https://issues.jboss.org/browse/WFLY-1725
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha3
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 8.0.0.Beta1
>
>
> The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org.
> Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering.
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-1725:
-------------------------------------------
We have a number of sources of documentation for AS clustering over recent versions:
- old but comprehensive clustering guides from legacy versions (AS 4, AS 5), reference from the JBoss Clustering community project documentation
- comprehensive clustering guides in EAP product documentation written by the docs team
- rather less comprehensive High Availability Guides for AS7 and Wildfly community documentation
The aim here is to update the project documentation in a way that makes sense and is useful to users of clustering features.
What should be the relationship between the comprehensive EAP product documentation and the Wildfly High Availability Guide project documentation? Some thoughts:
- the project documentation should concentrate on changes and new features of clustering, while at the same time providing a reasonable overview
- it should act as a source of upstream input for the subsequent EAP documentation, when required
- it should not aim to be comprehensive in the same way that the EAP documentation is; rather, be directed to experienced users who just need the minimal instruction to get a feature working
However, despite the fact that it may be less comprehensive, it must be well organized and well presented, with adequate framing of how covered topics related to each other.
> Update The Wildfly High Availability Guide
> -------------------------------------------
>
> Key: WFLY-1725
> URL: https://issues.jboss.org/browse/WFLY-1725
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha3
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 8.0.0.Beta1
>
>
> The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org.
> Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering.
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created WFLY-1725:
-----------------------------------------
Summary: Update The Wildfly High Availability Guide
Key: WFLY-1725
URL: https://issues.jboss.org/browse/WFLY-1725
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 8.0.0.Alpha3
Reporter: Richard Achmatowicz
Assignee: Paul Ferraro
Fix For: 8.0.0.Beta1
The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org.
Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering.
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-269) Updated infinispan management API
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-269?page=com.atlassian.jira.plugin.s... ]
Richard Achmatowicz commented on WFLY-269:
------------------------------------------
Heiko
Can you clarify what this issue concerns? The Infinispan management API will have undergone some changes between AS7 and AS8, such as adding addressable resources and operations, and these changes need to be reflected in the web console. This is what I expect WFLY-298 refers to. But what does this issue involve? Providing a list of those changes for you to concentrate on?
> Updated infinispan management API
> ---------------------------------
>
> Key: WFLY-269
> URL: https://issues.jboss.org/browse/WFLY-269
> Project: WildFly
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Richard Achmatowicz
> Fix For: 8.0.0.Beta1
>
>
> Expose updated management operations
--
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
12 years, 9 months