[
https://jira.jboss.org/jira/browse/WELD-398?page=com.atlassian.jira.plugi...
]
Martin Gencur updated WELD-398:
-------------------------------
Description:
When I try to go to
http://localhost:8080/weld-translator after deploying the translator
example to JBossAS 6.0.0.M1, exceptions are thrown both at server.log and web browser. The
exception are attached as separated files.
Steps to reproduce:
1) add <distributable/> tag to web.xml as it's first tag (at
WELD/examples/jsf/translator/war/src/main/webapp/WEB-INF/web.xml)
2) add this content to jboss.xml file at
WELD/examples/jsf/translator/ejb/src/main/resources/META-INF/jboss.xml :
<?xml version="1.0" encoding="UTF-8"?>
<jboss
xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
jboss_5_0.xsd"
version="5.0">
<enterprise-beans>
<session>
<!-- stateless bean -->
<ejb-name>SentenceTranslator</ejb-name>
<clustered>true</clustered>
</session>
<session>
<!-- stateful bean -->
<ejb-name>TranslatorControllerBean</ejb-name>
<clustered>true</clustered>
</session>
</enterprise-beans>
</jboss>
3) download jboss-6.0.0.M1 (for example from
http://reports.qa.atl.jboss.com/release_tests/binaries/JBossAS/jboss-6.0....)
4) unzip it twice to different folders
5) now you have to update both the JBoss AS instances with current version of WELD core
(from WELD/core)
6) run the first instance from its bin directory: ./run.sh -c all -g DocsPartition -u
239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=1
-Djboss.service.binding.set=ports-default
7) run the second instance from its bin directory: ./run.sh -c all -g DocsPartition -u
239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=2
-Djboss.service.binding.set=ports-01
8) clean and build the application: run mvn clean package in examples/jsf/translator
9) copy resulting ear file (weld-numberguess.war) from translator/ear/target/ directory to
serve/all/farm directory at first jbossAS instance
10) go to
http://localhost:8080/weld-translator
11) now you can see both exception in server.log and web browser
When i try to set <clustered>false</clustered> in jboss.xml, the application
shows properly when I go to web browser. But then the application is not working in
cluster (EJBs' state is not replicated between nodes of cluster).
was:
When I try to go to
http://localhost:8080/weld-translator after deploying the translator
example to JBossAS 6.0.0.M1, exceptions are thrown both at server.log and web browser. The
exception are attached as separated files.
Steps to reproduce:
1) add <distributable/> tag to web.xml as it's first tag (at
WELD/examples/jsf/translator/war/src/main/webapp/WEB-INF/web.xml)
2) add this content to jboss.xml file at
WELD/examples/jsf/translator/ejb/src/main/resources/META-INF/jboss.xml :
<?xml version="1.0" encoding="UTF-8"?>
<jboss
xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
jboss_5_0.xsd"
version="5.0">
<enterprise-beans>
<session>
<!-- stateless bean -->
<ejb-name>SentenceTranslator</ejb-name>
<clustered>true</clustered>
</session>
<session>
<!-- stateful bean -->
<ejb-name>TranslatorControllerBean</ejb-name>
<clustered>true</clustered>
</session>
</enterprise-beans>
</jboss>
3) download jboss-6.0.0.M1 (for example from
http://reports.qa.atl.jboss.com/release_tests/binaries/JBossAS/jboss-6.0....)
4) unzip it twice to different folders
5) now you have to update both the JBoss AS instances with current version of WELD core
(from WELD/core)
6) run the first instance from its bin directory: ./run.sh -c all -g DocsPartition -u
239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=1
-Djboss.service.binding.set=ports-default
7) run the second instance from its bin directory: ./run.sh -c all -g DocsPartition -u
239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=2
-Djboss.service.binding.set=ports-01
8) clean and build the application: run mvn clean package in examples/jsf/translator
9) copy resulting ear file (weld-numberguess.war) from translator/ear/target/ directory to
serve/all/farm directory at first jbossAS instance
10) go to
http://localhost:8080/weld-translator
11) now you can see both exception in server.log and web browser
Unable to run translator example with settings for cluster
----------------------------------------------------------
Key: WELD-398
URL:
https://jira.jboss.org/jira/browse/WELD-398
Project: Weld
Issue Type: Bug
Reporter: Martin Gencur
Attachments: jboss-server-log.txt, web-browser-report.txt
When I try to go to
http://localhost:8080/weld-translator after deploying the translator
example to JBossAS 6.0.0.M1, exceptions are thrown both at server.log and web browser. The
exception are attached as separated files.
Steps to reproduce:
1) add <distributable/> tag to web.xml as it's first tag (at
WELD/examples/jsf/translator/war/src/main/webapp/WEB-INF/web.xml)
2) add this content to jboss.xml file at
WELD/examples/jsf/translator/ejb/src/main/resources/META-INF/jboss.xml :
<?xml version="1.0" encoding="UTF-8"?>
<jboss
xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
jboss_5_0.xsd"
version="5.0">
<enterprise-beans>
<session>
<!-- stateless bean -->
<ejb-name>SentenceTranslator</ejb-name>
<clustered>true</clustered>
</session>
<session>
<!-- stateful bean -->
<ejb-name>TranslatorControllerBean</ejb-name>
<clustered>true</clustered>
</session>
</enterprise-beans>
</jboss>
3) download jboss-6.0.0.M1 (for example from
http://reports.qa.atl.jboss.com/release_tests/binaries/JBossAS/jboss-6.0....)
4) unzip it twice to different folders
5) now you have to update both the JBoss AS instances with current version of WELD core
(from WELD/core)
6) run the first instance from its bin directory: ./run.sh -c all -g DocsPartition -u
239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=1
-Djboss.service.binding.set=ports-default
7) run the second instance from its bin directory: ./run.sh -c all -g DocsPartition -u
239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=2
-Djboss.service.binding.set=ports-01
8) clean and build the application: run mvn clean package in examples/jsf/translator
9) copy resulting ear file (weld-numberguess.war) from translator/ear/target/ directory
to serve/all/farm directory at first jbossAS instance
10) go to
http://localhost:8080/weld-translator
11) now you can see both exception in server.log and web browser
When i try to set <clustered>false</clustered> in jboss.xml, the application
shows properly when I go to web browser. But then the application is not working in
cluster (EJBs' state is not replicated between nodes of cluster).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira