Bug 1017751
| Summary: | Multiple errors in hornetq-clustering example | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Vladimir Rastseluev <vrastsel> |
| Component: | Quickstarts | Assignee: | sgilda |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Vladimir Rastseluev <vrastsel> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | bsutter, jkudrnac, myarboro, pmuir, pslavice |
| Target Milestone: | ER7 | ||
| Target Release: | EAP 6.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-15 16:21:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1010473 | ||
We removed the '-as' from the module names, for example 'jboss-as-<quickstart-name>' became 'jboss-<quickstart-name>' and I neglected to modify the names in some of the scripts. This is fixed in this commit: https://github.com/jboss-developer/jboss-eap-quickstarts/commit/72170aab40767d81b7bbd8fd721e51f75b4ea9ac This quickstart was removed from the beta build so it should no longer be a beta blocking bug. However, this was fixed and the quickstart will be returned to the build for ER6 and this must remain open for verification. Tested on EAP 6.2 ER6.
Error in standalone mode still present:
[vrastsel@war hornetq-clustering]$ /home/vrastsel/jboss-eap-6.2/bin/jboss-cli.sh --connect --file=install-standalone.cli
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{
"outcome" => "failed",
"failure-description" => "JBAS011681: Attribute (connector) can not been undefined as the resource does not define any alternative to this attribute.",
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
Jess, I have a question about standalone mode. If you need to redeploy the application, you need to deploy it to the original server and the clone, correct? The same is true for the undeploy command? Mark, yes, it's a blocker. I am making progress, but now when I run the original and cloned servers at the same time, I get this warning: WARN [org.hornetq.core.client] (hornetq-discovery-group-thread-dg-group1) HQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=6d896380-3a4d-11e3-b2fb-31ba5bec2e12 Investigating. Note: This bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=1020859. Fixed in this commit: https://github.com/jboss-developer/jboss-eap-quickstarts/commit/00acdd6530071010e927cdf0860b5d5e076cb90c Verified on EAP 6.2 ER7 |
Description of problem: Following instruction from hornetq-clustering quickstart example README file I tried to execute installation CLI scripts on server in domain and standalone mode. Both scripts failed. Version-Release number of selected component (if applicable): EAP 6.2.0 ER5.1 How reproducible: easy Steps to Reproduce: IN DOMAIN MODE: 0. build helloworld-mdb example: mvn clean install 1. start server in domain mode JBOSS_HOME/bin/domain.sh 2. JBOSS_HOME/bin/jboss-cli.sh --connect --file=install-domain.cli { "outcome" => "success", "result" => undefined, "server-groups" => undefined } #1 /server-group=jdf-hornetq-clustering-group:add(profile=full-ha, socket-binding-group=full-ha-sockets) #2 /host=master/server-config=jdf-hornetqcluster-node1:add(group=jdf-hornetq-clustering-group, auto-start=true, socket-binding-port-offset=1000) #3 /host=master/server-config=jdf-hornetqcluster-node2:add(group=jdf-hornetq-clustering-group, auto-start=true, socket-binding-port-offset=1100) #4 /profile=full-ha/subsystem=messaging/hornetq-server=default:write-attribute(name=cluster-password, value=password) #5 /profile=full-ha/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector) #6 /profile=full-ha/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=discovery-group-name, value=dg-group1) Failed to add to batch 'deploy --server-groups=jdf-hornetq-clustering-group ../helloworld-mdb/target/jboss-as-helloworld-mdb.war': Path /home/vrastsel/jboss-eap-6.2-quickstarts/hornetq-clustering/../helloworld-mdb/target/jboss-as-helloworld-mdb.war doesn't exist. IN STANDALONE MODE 0. the same as above 1. JBOSS_HOME/bin/standalone.sh 2.JBOSS_HOME/bin/jboss-cli.sh --connect --file=install-standalone.cli { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } { "outcome" => "failed", "failure-description" => "JBAS011681: Attribute (connector) can not been undefined as the resource does not define any alternative to this attribute.", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} }