[JBoss JIRA] (AS7-3408) Classloading issue with HornetQLoggerFactory - possilbe problem with failback
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-3408:
-----------------------------------
Summary: Classloading issue with HornetQLoggerFactory - possilbe problem with failback
Key: AS7-3408
URL: https://issues.jboss.org/browse/AS7-3408
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.CR1
Reporter: Miroslav Novak
Assignee: Andy Taylor
Priority: Critical
Fix For: 7.1.0.Final
Attachments: console-log-backup-server.txt, console-log-live-server.txt, reproducer.zip
Test scenario:
1. Start two servers AS7/EAP6 servers - live and its backup in dedicated topology - each on different machine
2. Kill live server using "kill -9 ..."
3. Start live server again
In step 3. there are unexpected messages in console log of live and backup server.
>From backup server:
{code}
12:07:26,165 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-78) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [17700d86-45b2-11e1-a575-d48564b8e1e7] stopped
12:07:26,165 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-78) unable to restart server, please kill and restart manually: java.lang.IllegalArgumentException: Could not find class org.jboss.as.messaging.HornetQLoggerFactory
at org.hornetq.utils.ClassloadingUtil$1.run(ClassloadingUtil.java:42) [hornetq-core-2.2.7.Final.jar:]
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_22]
at org.hornetq.utils.ClassloadingUtil.safeInitNewInstance(ClassloadingUtil.java:16) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.instantiateInstance(HornetQServerImpl.java:1868) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.initialiseLogging(HornetQServerImpl.java:1301) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:541) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreBackupActivation$1FailbackChecker$1.run(HornetQServerImpl.java:430) [hornetq-core-2.2.7.Final.jar:]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
{code}
>From live server:
{code}
12:07:51,993 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test
12:07:52,007 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 31092ms - Started 155 of 263 services (103 services are passive or on-demand)
12:07:53,292 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying reconnection attempt 1
12:07:53,292 DEBUG [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Started Netty Connector version 3.2.3.Final-r${buildNumber}
12:07:53,292 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying to connect at the main server using connector :org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5446&host=192-168-10-4
12:07:53,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Main server is not up. Hopefully there's a backup configured now!
12:07:55,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying reconnection attempt 2
12:07:55,293 DEBUG [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Started Netty Connector version 3.2.3.Final-r${buildNumber}
12:07:55,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying to connect at the main server using connector :org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5446&host=192-168-10-4
12:07:55,294 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Main server is not up. Hopefully there's a backup
{code}
I'm not fully sure but it looks like that backup server did not manage to get to "waiting for live to fail" state and live server is not able to detect it.
There is set "DEBUG" level logging for "org.hornetq" in attached logs.
I've attached reproducer.zip - steps to use:
1. Download and unzip "reproducer.zip"
2. Prepare live and backup server - "sh prepare.sh"
3. Start live - "sh start-server1.sh server1_hostname"
4. Start backup - "sh start-server2.sh server2_hostname"
5. Kill live server using "kill -9 server1_process_id"
6. Start live server again - "sh start-server1.sh server1_hostname"
Note:
In reproducer.zip are configuration files standalone-ha-A.xml, standalone-ha-B.xml (A for live, B for backup).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-3317) ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-3317:
-----------------------------------
Summary: ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator
Key: AS7-3317
URL: https://issues.jboss.org/browse/AS7-3317
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.CR1
Reporter: Miroslav Novak
Assignee: Clebert Suconic
Fix For: 7.1.0.Final
When logging subsystem is set to DEBUG level for "org.hornetq" then ClassNotFoundException exception appears in console log:
{code}
12:45:01,163 DEBUG [org.hornetq.ra.Util] (MSC service thread 1-4) org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)]: java.lang.ClassNotFoundException: org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:473)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:461)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:403)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:125)
at org.hornetq.ra.Util.locateTM(Util.java:261) [hornetq-ra-2.2.7.Final.jar:]
at org.hornetq.ra.HornetQResourceAdapter.locateTM(HornetQResourceAdapter.java:1555) [hornetq-ra-2.2.7.Final.jar:]
at org.hornetq.ra.HornetQResourceAdapter.start(HornetQResourceAdapter.java:210) [hornetq-ra-2.2.7.Final.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_22]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_22]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_22]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:345) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2127) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1030) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:148) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1]
at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:94) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-4001) Bad reference to XSL transformation files in module jboss-as-testsuite-benchmark and jboss-as-testsuite-stress
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-4001?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek moved JBPAPP-8333 to AS7-4001:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4001 (was: JBPAPP-8333)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.1.Final
(was: EAP 6.0.0 ER 2)
Component/s: Test Suite
(was: Testsuite)
Security: (was: JBoss Internal)
Docs QE Status: (was: NEW)
> Bad reference to XSL transformation files in module jboss-as-testsuite-benchmark and jboss-as-testsuite-stress
> --------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4001
> URL: https://issues.jboss.org/browse/AS7-4001
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.1.Final
> Reporter: Pavel Janousek
> Assignee: Ondrej Zizka
> Priority: Blocker
>
> Transformation procedure is invoked, but it seems like bad configuration path or not correctly done clean-up in previous step. I caught this problem via warning:
> {code}
> [INFO] --- xml-maven-plugin:1.0:transform (ts.config-as.ip) @ jboss-as-testsuite-stress ---
> [WARNING] The directory /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/target/jbossas/standalone/configuration, which is a base directory of a ValidationSet or TransformationSet, does not exist.
> [WARNING] No files found for transformation by stylesheet /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/../integration/src/test/xslt/changeIPAddresses.xsl
> [WARNING] The directory /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/target/jbossas/standalone/configuration, which is a base directory of a ValidationSet or TransformationSet, does not exist.
> [WARNING] No files found for transformation by stylesheet /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/../integration/src/test/xslt/addJmsDestinations.xsl
> {code}
> Further investigation says /build/target/... isn't copied to these modules at all.
> You can see this problem [there|https://hudson.qa.jboss.com/hudson/job/AS7-TS-linux-ipv6-experiment...].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-3994) CLONE - Can't connect CLI to server on IPv6 address
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-3994?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry reassigned AS7-3994:
-------------------------------------
Assignee: Brian Stansberry (was: Alexey Loubyansky)
> CLONE - Can't connect CLI to server on IPv6 address
> ---------------------------------------------------
>
> Key: AS7-3994
> URL: https://issues.jboss.org/browse/AS7-3994
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.1.0.Final
> Reporter: Rostislav Svoboda
> Assignee: Brian Stansberry
> Priority: Critical
> Labels: eap6_LA
> Fix For: 7.1.1.Final
>
>
> Server started with:
> {code}
> bin/standalone.sh -b=::1 -bmanagement=::1 -Djava.net.preferIPv4Stack=false
> {code}
> CLI execution attempts:
> {code}
> $ bin/jboss-cli.sh --connect command=:shutdown
> The controller is not available at localhost:9999
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> $ bin/jboss-cli.sh --connect controller=::1 command=:shutdown
> The port must be a valid non-negative integer: 'controller=::1'
> $ bin/jboss-cli.sh --connect controller=[::1] command=:shutdown
> The port must be a valid non-negative integer: 'controller=[::1]'
> $ netstat -natup | grep java
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> tcp 0 0 ::1:9990 :::* LISTEN 21912/java
> tcp 0 0 ::1:9999 :::* LISTEN 21912/java
> tcp 0 0 ::1:8080 :::* LISTEN 21912/java
> tcp 0 0 ::1:4447 :::* LISTEN 21912/java
> $ bin/jboss-cli.sh --connect controller=[::1]:9999 command=:shutdown
> The port must be a valid non-negative integer: 'controller=[::1]:9999'
> $ bin/jboss-cli.sh --connect controller=[::1]#9999 command=:shutdown
> The port must be a valid non-negative integer: 'controller=[::1]#9999'
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-3997) Jacorb subsystem uses magic socket binding names
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-3997:
-------------------------------------
Summary: Jacorb subsystem uses magic socket binding names
Key: AS7-3997
URL: https://issues.jboss.org/browse/AS7-3997
Project: Application Server 7
Issue Type: Bug
Components: IIOP
Affects Versions: 7.1.0.Final
Reporter: Brian Stansberry
Assignee: Stefan Guilhen
In JacORBSubsystemAdd:
CorbaORBService orbService = new CorbaORBService(props);
final ServiceBuilder<ORB> builder = context.getServiceTarget().addService(
CorbaORBService.SERVICE_NAME, orbService);
// inject the socket bindings that specify the JacORB IIOP and IIOP/SSL ports.
builder.addDependency(SocketBinding.JBOSS_BINDING_NAME.append(JACORB_SOCKET_BINDING), SocketBinding.class,
orbService.getJacORBSocketBindingInjector());
builder.addDependency(SocketBinding.JBOSS_BINDING_NAME.append(JACORB_SSL_SOCKET_BINDING), SocketBinding.class,
orbService.getJacORBSSLSocketBindingInjector());
The JACORB_SOCKET_BINDING and JACORB_SSL_SOCKET_BINDING values should be coming from some configuration attributes, which perhaps have those constants as their default values. Users can name socket-binding configs whatever they want; the names we provide in our standard configs are just obvious defaults.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JASSIST-152) instrumentation fails when building stackmap for local var of array type : bad array type for AALOAD: null
by Yanic Inghelbrecht (JIRA)
Yanic Inghelbrecht created JASSIST-152:
------------------------------------------
Summary: instrumentation fails when building stackmap for local var of array type : bad array type for AALOAD: null
Key: JASSIST-152
URL: https://issues.jboss.org/browse/JASSIST-152
Project: Javassist
Issue Type: Bug
Affects Versions: 3.15.0-GA
Environment: Any
Reporter: Yanic Inghelbrecht
Assignee: Shigeru Chiba
When trying to instrument the attached org.hibernate.cfg.AbstractPropertyHolder (copied from the hibernate 4.0.1 final distribution), instrumentation fails with the following exception :
java.lang.RuntimeException: fatal error:
at javassist.bytecode.stackmap.TypeData$TypeName.getTypeData(TypeData.java:177)
at javassist.bytecode.stackmap.MapMaker.fillStackMap(MapMaker.java:410)
at javassist.bytecode.stackmap.MapMaker.toStackMapBody(MapMaker.java:393)
at javassist.bytecode.stackmap.MapMaker.toStackMap(MapMaker.java:323)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:98)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:417)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:399)
at javassist.expr.ExprEditor.doit(ExprEditor.java:113)
at javassist.CtBehavior.instrument(CtBehavior.java:672)
at test_abstractpropertyholder.SimpleTranslator.modify(SimpleTranslator.java:25)
at test_abstractpropertyholder.SimpleTranslator.onLoad(SimpleTranslator.java:19)
at test_abstractpropertyholder.JavassistInstrumenter.getInstrumentedClass(JavassistInstrumenter.java:21)
at test_abstractpropertyholder.Main.main(Main.java:32)transforming org.hibernate.cfg.AbstractPropertyHolder
Caused by: javassist.bytecode.BadBytecode: bad array type for AALOAD: null
at javassist.bytecode.stackmap.TypeData$ArrayElement.getName(TypeData.java:422)
at javassist.bytecode.stackmap.TypeData$TypeName.getExpected(TypeData.java:292)
at javassist.bytecode.stackmap.TypeData$TypeName.getTypeData(TypeData.java:175)
... 12 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-3994) CLONE - Can't connect CLI to server on IPv6 address
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-3994?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry moved JBPAPP-8324 to AS7-3994:
-----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-3994 (was: JBPAPP-8324)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.0.Final
(was: EAP 6.0.0 ER 2)
Component/s: CLI
(was: Scripts and Commands)
Security: (was: Public)
Fix Version/s: 7.1.1.Final
(was: EAP 6.0.0 ER 3)
Docs QE Status: (was: NEW)
> CLONE - Can't connect CLI to server on IPv6 address
> ---------------------------------------------------
>
> Key: AS7-3994
> URL: https://issues.jboss.org/browse/AS7-3994
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.1.0.Final
> Reporter: Rostislav Svoboda
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Labels: eap6_LA
> Fix For: 7.1.1.Final
>
>
> Server started with:
> {code}
> bin/standalone.sh -b=::1 -bmanagement=::1 -Djava.net.preferIPv4Stack=false
> {code}
> CLI execution attempts:
> {code}
> $ bin/jboss-cli.sh --connect command=:shutdown
> The controller is not available at localhost:9999
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> $ bin/jboss-cli.sh --connect controller=::1 command=:shutdown
> The port must be a valid non-negative integer: 'controller=::1'
> $ bin/jboss-cli.sh --connect controller=[::1] command=:shutdown
> The port must be a valid non-negative integer: 'controller=[::1]'
> $ netstat -natup | grep java
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> tcp 0 0 ::1:9990 :::* LISTEN 21912/java
> tcp 0 0 ::1:9999 :::* LISTEN 21912/java
> tcp 0 0 ::1:8080 :::* LISTEN 21912/java
> tcp 0 0 ::1:4447 :::* LISTEN 21912/java
> $ bin/jboss-cli.sh --connect controller=[::1]:9999 command=:shutdown
> The port must be a valid non-negative integer: 'controller=[::1]:9999'
> $ bin/jboss-cli.sh --connect controller=[::1]#9999 command=:shutdown
> The port must be a valid non-negative integer: 'controller=[::1]#9999'
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-3910) How to create server instances and then a cluster for JBoss AS 7.1.0 for Windows OS
by Mustafa Khambatta (JIRA)
Mustafa Khambatta created AS7-3910:
--------------------------------------
Summary: How to create server instances and then a cluster for JBoss AS 7.1.0 for Windows OS
Key: AS7-3910
URL: https://issues.jboss.org/browse/AS7-3910
Project: Application Server 7
Issue Type: Task
Components: Clustering
Affects Versions: 7.1.0.Final
Environment: Windows 2003 EE OS
32bit 4GB RAM
Reporter: Mustafa Khambatta
Assignee: Paul Ferraro
Fix For: No Release
I am unable to find any information on creating server instances on windows OS for JBoss AS7.1.0.
I have tried the other ways mentioned but nothing.
The admin console doesnot have any function of creating a server instance and I cant find any instruction for doing it through command prompt.
Also after creating the server instances how to you create the cluster and what are the steps for it. Then after that, what is the steps for creating a High Availability clustering
Thankyou in advance
Appreciate your help
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months