[JBoss Tools] - Re: JBoss Server Full publish - WeldPhaseListener cannot be cast to PhaseListener
by Max Rydahl Andersen
Max Rydahl Andersen [https://community.jboss.org/people/maxandersen] created the discussion
"Re: JBoss Server Full publish - WeldPhaseListener cannot be cast to PhaseListener"
To view the discussion, visit: https://community.jboss.org/message/755077#755077
--------------------------------------------------------------
Does not look like a tooling bug - looks like a JBoss 6/Weld issue - have you asked in those forums ?
p.s. if you are using CDI, try AS7 or EAP6 instead; much better ;)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755077#755077]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 2 months
- 2
- 1
[jBPM] - jBPM-5.3.0.Final Manual Deployment Guide for Beginner
by quangtin3
quangtin3 [https://community.jboss.org/people/quangtin3] modified the document:
"jBPM-5.3.0.Final Manual Deployment Guide for Beginner"
To view the document, visit: https://community.jboss.org/docs/DOC-21179
--------------------------------------------------------------
**
#1_Overview_of_jBPM 1. Overview of jBPM
***
#jBPM_Components jBPM Components
***
#Separation_deployment Separation deployment
**
#2_Common_bugs_fix_after_jBPM530Final_release 2. Common bugs fix after jBPM-5.3.0.Final release
***
#Building_from_sourcecode Building from source-code
****
#a_Configure_your_git_username_and_email a. Configure your git username and email
****
#b_Clone_jbpm_repository_from_githubcom b. Clone jbpm repository from github.com
****
#c_Working_with_local_repository c. Working with local repository
*****
#List_all_jBPM_tags_ List all jBPM tags
*****
#Switch_to_530Final_revision_tag Switch to 5.3.0.Final revision tag.
*****
#View_prehistory_just_before_jBPM_team_released_jBPM530Final View pre-history just before jBPM team released jBPM.5.3.0.Final
***
#Apply_bug_fix Apply bug fix
****
#Bug_Could_not_locate_named_parameter_userId Bug: Could not locate named parameter [userId]
****
#Bug_No_result_or_connection_timeout Bug: No result, or connection timeout
****
#Bug_Must_be_positive Bug: Must be positive
****
#Bug_HornetQ_binding_only_to_local_address Bug: HornetQ binding only to local address.
**
#3_Manual_jBPM_components_deployment 3. Manual jBPM components deployment
***
#Environment Environment
****
#Check_your_JDK_installation Check your JDK installation
****
#Check_apache_maven Check apache maven
****
#Check_apache_ant Check apache ant
***
#Deployment_parameters Deployment parameters
***
#MySQL_database_deployment_just_verify MySQL database deployment (just verify).
**
#4_Drools_guvnor_designer_and_formbuilder_deployment_with_verify 4. Drools guvnor, designer, and form-builder deployment (with verify)
***
#Step_41Extract_a_clean_copy_of_jbossas702Finalzip_to_GUVNOR_JBOSS Step 4.1:Extract a clean copy of jboss-as-7.0.2.Final.zip to GUVNOR_JBOSS
***
#Step_42_Jboss_configuration Step 4.2: Jboss configuration.
***
#Step_43_droolsguvnor_configuration Step 4.3: drools-guvnor configuration
****
#a_Update_GUVNOR_JBOSSpreferencesproperties_to_our_will_be_deployed_designer_and_formbuilder a. Update GUVNOR_JBOSS/preferences.properties to our will be deployed designer and form-builder
****
#b_Place_a_copy_of_GUVNOR_JBOSSpreferencesproperties_to_droolsguvnorwartargetWEBINFclassespreferencesproperties b. Place a copy of GUVNOR_JBOSS/preferences.properties to drools-guvnor.war/target/WEB-INF/classes/preferences.properties
***
#Step_44_Deploy_and_verify_droolsguvnor_component_installation Step 4.4: Deploy and verify drools-guvnor component installation
****
#a_Deploy_droolsguvnor a. Deploy drools-guvnor
****
#b_Verify_that_we_have_the_following_message_in_the_console b. Verify that we have the following message in the console
****
#c_Verify_that_we_can_access_the_droolsguvnor c. Verify that we can access the drools-guvnor
***
#Step_45_Deploy_designer Step 4.5: Deploy designer
****
#a_Apply_the_change_for_Designer_as_following_article_httpbpmgeekcomblogmakingjbpm5workremotehost_ a. Apply the change for Designer as following article http://bpmgeek.com/blog/making-jbpm5-work-remote-host
****
#b_Deploy_designer b. Deploy designer
****
#c_Verify_designer c. Verify designer
***
#Step_46_Deploy_formbuilder Step 4.6: Deploy form-builder
****
#a_Add_usersroles_configuration_to_GUVNOR_JBOSS a. Add users/roles configuration to GUVNOR_JBOSS
****
#b_Add_security_domain_for_jbpmformbuilder_in_file_standaloneconfigurationstandalonexml b. Add security domain for jbpm-form-builder in file standalone/configuration/standalone.xml
****
#c_Add_usersroles_to_jbpmformbuilderwarWEBINFclasses c. Add users/roles to jbpm-form-builder.war/WEB-INF/classes
****
#d_Deploy_formbuilder_and_verify_like_we_already_did_with_designer d. Deploy form-builder and verify like we already did with designer
****
#e_Verify_that_you_have e. Verify that you have
**
#5_TaskService_or_Human_Task_deployment_with_verify 5. Task-Service or Human Task deployment (with verify).
***
#Step_51Extract_a_clean_copy_of_jbossas702Finalzip_to_HUMAN_TASK_JBOSS Step 5.1:Extract a clean copy of jboss-as-7.0.2.Final.zip to HUMAN_TASK_JBOSS
***
#Step_52_Copy_your_custom_build_humantask_ Step 5.2: Copy your custom build human-task
***
#Step_53_Jboss_standalonexml_configuration_ Step 5.3: Jboss standalone.xml configuration
****
#a_Remove_pojo_module a. Remove pojo module
****
#b_Change_port_for_management_interface b. Change port for management interface.
****
#c_Add_datasource_for_taskservice c. Add datasource for task-service
****
#d_Bind_to_HUMAN_TASK_IP_For_example d. Bind to HUMAN_TASK_IP. For example
****
#e_Set_offsetport e. Set offset-port
***
#Step_54_MySQL_driver_for_jboss Step 5.4: MySQL driver for jboss
****
#a_Create_MySQL_module_directory a. Create MySQL module directory
****
#bCopy_module_declaration_file b.Copy module declaration file
****
#c_Download_and_install_mysql_driver_to_jBoss c. Download and install mysql driver to jBoss
****
#d_Start_your_HUMAN_TASK_JBOSS_now d. Start your HUMAN_TASK_JBOSS now
***
#Step_54_jbpmhumantaskwarwar_configuration Step 5.4: jbpm-human-task-war.war configuration
****
#a_In_your_jbpmhumantaskwarwar_file_make_following_modification_with_your_current_archive_manager a. In your jbpm-human-task-war.war file, make following modification with your current archive manager
****
#b_Configure_your_WEBINFwebxml_as_following b. Configure your WEB-INF/web.xml as following
*****
#Make_HornetQ_as_active_transport Make HornetQ as active transport
*****
#Set_HornetQ_binding_address_and_port_Remember_our_fix_at_the_end_of_part_2_to_HUMAN_TASK_IP_and_HORNETQ_PORT Set HornetQ binding address and port (Remember our fix at the end of part 2) to HUMAN_TASK_IP and HORNETQ_PORT
*****
#Optional_Task_service_persistence_unit_name_we_will_use_default_value_so_you_can_keep_it_blank Optional: Task service persistence unit name, we will use default value so you can keep it blank
*****
#User_demo_usergroup_callback_implementation User demo user/group call-back implementation
*****
#Using_demo_user_and_group_provider Using demo user and group provider
****
#c_Configure_persistencexml_ c. Configure persistence.xml
*****
#Change_jbpmDS_to_taskDS Change jbpmDS to taskDS
*****
#Modify_properties_to_your_MySQL_IP_and_MySQL_PORT Modify properties to your MySQL_IP and MySQL_PORT
****
#d_Update_jpbmhumantaskwarwarWEBINFclassesMETAINFpersistencexml d. Update jpbm-human-task-war.war/WEB-INF/classes/META-INF/persistence.xml
****
#b_Place_a_copy_of_HUMAN_TASK_JBOSS b. Place a copy of HUMAN_TASK_JBOSS
**
#6_jBPMConsole_deployment_with_verify 6. jBPM-Console deployment (with verify).
*Disclaimer:* First, Almost material in this article I borrowed form all over the public web. Some of most borrowed source are (in order):
* Extract from jbpm-install/build.xml Ant script.
* jBPM official user-guide: http://docs.jboss.org/jbpm/v5.3/userguide/ http://docs.jboss.org/jbpm/v5.3/userguide/
* jBPM community user forum: https://community.jboss.org/community/jbpm?view=discussions https://community.jboss.org/en/jbpm?view=discussions
* BPM Geek: http://bpmgeek.com/blog/making-jbpm5-work-remote-host http://bpmgeek.com/blog/making-jbpm5-work-remote-host
Second, This article only provides a way of step by step manually deployment of each jBPM-5.3.0.Final components. It was written by a jBPM beginner. For a official document please refer to: http://docs.jboss.org/jbpm/v5.3/userguide/ http://docs.jboss.org/jbpm/v5.3/userguide/
Third,this article example is in Linux. Mabe I will add ant scripts (again, heavily extracts from jbpm-install/build.xml) for faster deployment and Windows friendlier.
h2. 1. Overview of jBPM
h3. jBPM Components
Download a copy of jbpm-5.3.0.Final-installer-full.zip ( http://sourceforge.net/projects/jbpm/files/jBPM%205/jbpm-5.3.0.Final/ http://sourceforge.net/projects/jbpm/files/jBPM%205/jbpm-5.3.0.Final/) and extract it to a location, from now on we call it JBPM_INSTALL. JBPM_INSTALL contains all core jBPM components.
|| *Components
* || *File in JBPM_INSTALL/lib*
|| *Description
* ||
| jbpm-runtime | jbpm-5.3.0.Final-bin.zip | jBPM Runtime, if you are willing to build a stand alone Java application you will need this. |
| drools-guvnor | guvnor-distribution-wars-5.4.0-20120516.war | Drools-Guvnor provides process repository. |
| designer | designer-2.2.Final-jboss7.war | JBPM2 process designer. It's integrated with drools-guvnor. |
| form-builder | jbpm-5.3.0.Final-form-builder.war | Form builder. It's going to be integrated with the designer. http://blog.athico.com/2012/07/jbpm-form-builder-state-of-art.html |
| gwt-console and gwt-console-server | jbpm-5.3.0.Final-gwt-console.zip |
|
| human-task | jbpm-5.3.0.Final-human-task-war.zip |
|
Table 01: jBPM.5.3.0.Final components and their binary file
https://community.jboss.org/servlet/JiveServlet/showImage/19247/jBPM+-+In... https://community.jboss.org/servlet/JiveServlet/downloadImage/19247/jBPM+...
Figure 01: jBPM-Internal components communication
The communication between component as described in Figure-01, this article use MySQL. But by default, jbpm-install with "ant start.demo" will run with H2 database. From this communication view we can separate each component deployment. Event on each application server.
https://community.jboss.org/servlet/JiveServlet/showImage/19248/jBPM+-+Ec... https://community.jboss.org/servlet/JiveServlet/downloadImage/19248/jBPM+...
Figure 02: The communication with Eclipse IDE
h3. Separation deployment
For a beginner, with all jBPM components are twisted together:
* It's hard to tell which message of what components. When something go wrong, which one to focus, which one to just ignore.
* Need a way to check each component is up and running.
* Just a way to learn and experience with jBPM.
Purely from this experience and conclusion, this article will provides a manual installation of each jBPM-5.3.0.Final component.
h2. 2. Common bugs fix after jBPM-5.3.0.Final release
h3. Building from source-code
As a beginner I occasionally meet this kind of error {userId parameter, no result, must be positive, hornetq remote ..}. Some are must apply the fix before you can go on further. The commits after jBPM-5.3.0.Final does fix the bug but also introduces incompatible with other jBPM.5.3.0.Final. So this part will describes how to checkout Original jBPM-5.3.0.Final release source code; find the Fixed patch and apply to your local branch.
For more detailed git document, please refer to other document. This article only using related git commands.
h4. a. Configure your git username and email
# For your local branche
git config --global user.name "Your Name"
git config --global user.email "your_email(a)addr.ess"
h4. b. Clone jbpm repository from github.com
# We only need jbpm.git, because in version 5.3.0.Final all component on the same git repository.
git clone https://github.com/droolsjbpm/jbpm.git
# We have local git reposistory. We will call its directory path as jBPM_SRC
cd jbpm/
mvn clean install -U -Dfull -DskipTests
Optional: in "mvn clean install -U -Dfull -DskipTests" abover, We can add -nsu (no snapshot update) for faster build. Because we're only aware specific on 5.3.0.Final revision and its dependencies.
mvn clean install -U -Dfull -DskipTests -nsu
This command really takes a while, especially for the first time and your empty maven local repository.
h4. c. Working with local repository
The jbpm is a typical maven parent project with multiple module. Two of theme {human-task; gwt-console} are parent project too. From now on, you can use your favorite IDE with JavaEE profile to work with this checked out repository, showing diff and applying patch. Otherwise you can using git command as following example:
h5. List all jBPM tags
# From your jBPM_SOURCE, show tags
git tag
The output will be something like this:
5.0-CR1
5.0.0
5.1.0.CR1
5.1.0.Final
5.1.0.M1
5.1.1.Final
5.1.2.Final
5.2.0.Final
5.2.1.Final
5.2.2.Final
5.3.0.CR1
5.3.0.Final
h5. Switch to 5.3.0.Final revision tag.
Chose your local branch name, for example: update.after.5.3.0.final
git checkout 5.3.0.Final -b update.after.5.3.0.final
Result message
Switched to a new branch 'update.after.5.3.0.final'
h5. View pre-history just before jBPM team released jBPM.5.3.0.Final
git log
Example output
***@***:~/Tutorial/jbpm$ git log
commit d7640b9c0ba87d771862e8534cc607ca0f4d1aff
Author: Toni Rikkola <toni(a)rikkola.net>
Date: Mon May 14 13:25:30 2012 +0300
change to 5.4.0.Final version
commit 88440fe1430170458981c2752192df2c64c83636
Author: Maciej Swiderski <mswiders(a)redhat.com>
Date: Wed May 9 19:22:35 2012 +0200
BZ820210 - Could not initialize stateful knowledge session: loader constraint violation when using HornetQ task service strategy
commit 80f940e2e860ac640a75114ab2780f6c2b7a865c
Author: salaboy <salaboy(a)gmail.com>
Date: Wed May 9 15:04:54 2012 +0100
- mvel workaround
...
Build your own jBPM.5.3.0.Final for the first time
mvn clean install -U -Dfull -DskipTests -nsu
Now you can working with your local git repository, update the 5.3.0.Final tag with the patch you need. All your commit will be stored on update.after.5.3.0.final branches.
h3. Apply bug fix
h4. Bug: Could not locate named parameter [userId]
Full message
java.lang.IllegalArgumentException: org.hibernate.QueryParameterException: could not locate named parameter [userId]
Community thread:
https://community.jboss.org/message/738335#738335 https://community.jboss.org/message/738335#738335
https://community.jboss.org/thread/200361 https://community.jboss.org/thread/200361
Fix commit: 4a47527163854b233cdb9599f54c9320e945a372
h4. Bug: No result, or connection timeout
Message
java.lang.RuntimeException: Timeout : unable to retrieve results
Treatment: With this particular deployment {separating components deployment, using MySQL} I haven't meet this error yet.
h4. Bug: Must be positive
Full message:
2011-07-18 18:46:35,546 [FATAL] Uncaught Exception:
java.lang.IllegalArgumentException:
must be positive
at Unknown.cKb(Unknown source:0)
Fix: Not yet. (I think) this comes from GWT bug. GWT is the Google Web Toolkit that jBPM-Console are using. Just ignore it and continue with your work.
h4. Bug: HornetQ binding only to local address.
There aren't any configuration for Human-Task-War to bind on particular address. And by default it only listen on local address so Gwt-Console-Server cannot connect to it. Our separating deployment needs Gwt-Console-Server to connect to Human-Task, so apply the change-set below:
Bug track link: https://issues.jboss.org/browse/JBPM-3720?page=com.atlassian.jira.plugin.... https://issues.jboss.org/browse/JBPM-3720?page=com.atlassian.jira.plugin....
Change set: https://source.jboss.org/changelog/jBPM?cs=e115680b023ce0747608625f0cd616... https://source.jboss.org/changelog/jBPM?cs=e115680b023ce0747608625f0cd616...
h2. 3. Manual jBPM components deployment
h3. Environment
h4. Check your JDK installation
# Check JAVA_HOME environment variable arcording to your operating system. In linux
echo $JAVA_HOME
# JDK Java version 1.6 or newer
java -version
h4. Check apache maven
Download and installation instruction: http://maven.apache.org/download.html http://maven.apache.org/download.html
# Check M2 and M2_HOME environment variables acording to your operating system. In linux
echo $M2
echo $M2_HOME
# Check Apache Maven installation
mvn -version
h4. Check apache ant
Download: http://ant.apache.org/bindownload.cgi http://ant.apache.org/bindownload.cgi and manual: http://ant.apache.org/manual/index.html http://ant.apache.org/manual/index.html
# Check ANT_HOME environment variables acording to your operating system. In linux
echo $ANT_HOME
# And ANT_OPTS if it's nessessary. For example proxy configuration
echo $ANT_OPTS
-Dhttp.proxyHost=192.168.193.12 -Dhttp.proxyPort=3128
# Check Apache Ant installation
ant -version
h3. Deployment parameters
|| *Name
* || *Variables
* || *Example values* ||
| Jbpm-install | JBPM_INSTALL | /opt/download/jbpm-install |
| MySQL username/password and schema | MySQL_JBPM
MySQL_TASK | jbpm,jbpmpassword and schema name is jbpm
task,taskpassword and schema name is task |
| MySQL server IP/PORT | MySQL_IP:MySQL_PORT | 192.168.140.39:3306 |
| Group-01 components: {Drool-guvnor, Designer, Form-Builder} | GUVNOR_JBOSS
GUVNOR_IP
GUVNOR_HTTP_PORT
GUVNOR_MANAGEMENT_PORT | /opt/guvnor_jboss
192.168.140.39
8080
9999 and 9990 |
| Group-02: Human-task |
HUMAN_TASK_JBOSS
HUMAN_TASK_IP
HUMAN_TASK_HTTP_PORT
HUMAN_TASK_MANAGEMENT_PORT
HUMAN_TASK_PORT-OFFSET
HORNETQ_PORT | /opt/human_task_jboss
192.168.140.39
8180
10099 and 10090
port-offset="100"
1234 (Don't use default value, because we want to know if this configuratio affect or not)
|
| Group-03: Gwt-Console and Gwt-Console-Server | CONSOLE_JBOSS
CONSOLE_IP
CONSOLE_HTTP_PORT
CONSOLE_MANAGEMENT_POR
CONSOLE_PORT_OFFSET | /opt/console_jboss
192.168.140.39
8280
10199 and 10190
port-offset="200" |
Table 02 - Deployment parameters
The "example value column" in Table 02 are values from a real deployment with all jboss instances running on the same machine. https://community.jboss.org/docs/DOC-16705 https://community.jboss.org/wiki/MultipleInstancesOfJBossAS7OnTheSameMachine (Approach#1)
h3. MySQL database deployment (just verify).
Verify that you can connect and login to MySQL:
# From server HUMAN_TASK_IP to MySQL_IP:MySQL_PORT
mysql -h MySQL_IP -P MySQL_Port -u MySQL_TASK -pMySQL_TASK_PASSWORD
# From server JBPM_IP to MYSQL_IP:MySQL_PORT
mysql -h MySQL_IP -P MySQL_Port -u MySQL_JBPM -pMySQL_JBPM_PASSWORD
# Note: -P (capitalized) for port; and -p (lowercase) for password.
# No space between -p and MySQL_TASK_PASSWORD. For example:
# mysql -h 192.168.140.39 -P 3306 -u task -ptaskpassword
# mysql -h 192.168.140.39 -P 3306 -u jbpm -pjbpmpassword
After this, We can just forget about firewall, network routing, MySQL permission issues incase our persistence not work. For MySQL related document http://dev.mysql.com/doc/refman/5.0/en/connecting.html http://dev.mysql.com/doc/refman/5.0/en/connecting.html
h2. 4. Drools guvnor, designer, and form-builder deployment (with verify)
Login to server on GUVNOR_IP and place a copy of jbpm-install and start the installation:
h3. Step 4.1:Extract a clean copy of jboss-as-7.0.2.Final.zip to GUVNOR_JBOSS
# Set our GUVNOR_JBOSS to this example path
export GUVNOR_JBOSS=/opt/guvnor_jboss
echo $GUVNOR_JBOSS
# Go to JBPM_INSTALL directory
cd /opt/download/
unzip jbpm-5.3.0.Final-installer-full.zip
cd /opt/download/jbpm-installer
# Extract a clean copy of jboss application server. To move to /opt we need root permission.
unzip lib/jboss-as-7.0.2.Final.zip
sudo mv jboss-as-7.0.2.Final $GUVNOR_JBOSS
# Copy guvnor, designer, form-builder
cp lib/guvnor-distribution-wars-5.4.0-20120516.war $GUVNOR_JBOSS/drools-guvnor.war
cp lib/designer-2.2.Final-jboss7.war $GUVNOR_JBOSS/designer.war
cp lib/jbpm-5.3.0.Final-form-builder.war $GUVNOR_JBOSS/jbpm-form-builder.war
# And their configurations file
cp conf/guvnor.preferences.properties $GUVNOR_JBOSS/preferences.properties
cp auth/users.properties $GUVNOR_JBOSS/
cp auth/roles.properties $GUVNOR_JBOSS/
cd $GUVNOR_JBOSS
h3. Step 4.2: Jboss configuration.
# Change GUVNOR_JBOSS/standalone/configuration/standalone.xml to bind to GUVNOR_IP. For example
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:192.168.140.39}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:192.168.140.39}"/>
</interface>
</interfaces>
h3. Step 4.3: drools-guvnor configuration
h4. a. Update GUVNOR_JBOSS/preferences.properties to our will be deployed designer and form-builder
...
#Designer configuration
designer.url=http://192.168.140.39:8080
#Do not change this unless you know what are you doing
designer.context=designer
designer.profile=jbpm
#FormBuilder configuration
#Do not change this unless you know what are you doing
formbuilder.url=http://192.168.140.39:8080
formbuilder.context=jbpm-form-builder
formbuilder.profile=guvnor
h4. b. Place a copy of GUVNOR_JBOSS/preferences.properties to drools-guvnor.war/target/WEB-INF/classes/preferences.properties
# User your favorist archive manager.
Using "Open with Archive Manager" in Ubuntu Linux
h3. Step 4.4: Deploy and verify drools-guvnor component installation
h4. a. Deploy drools-guvnor
# Set our GUVNOR_JBOSS to this example path
export GUVNOR_JBOSS=/opt/guvnor_jboss
cd $GUVNOR_JBOSS
# Deploy drools-guvnor
cp drools-guvnor.war standalone/deployments/
# Verify drools-guvnor by start GUVNOR_JBOSS
bin/standalone.sh
h4. b. Verify that we have the following message in the console
...
11:55:46,779 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /drools-guvnor
11:55:46,844 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "drools-guvnor.war
h4. c. Verify that we can access the drools-guvnor
Access the http://GUVNOR_IP:8080/drools-guvnor http://GUVNOR_IP:8080/drools-guvnor (In our example is http://192.168.140.39:8080 http://192.168.140.39:8080/drools-guvnor) with the browser from GUVNOR_IP and CONSOLE_IP
h3. Step 4.5: Deploy designer
h4. a. Apply the change for Designer as following article http://bpmgeek.com/blog/making-jbpm5-work-remote-host
Lock for the section +"Saving and reloading process in designer could cause failures"+ at the end of that post, we need to make following change:
<externalloadurl protocol="http" host="GUVNOR_IP:8080" subdomain="drools-guvnor/org.drools.guvnor.Guvnor/oryxeditor" usr="admin" pwd="admin"/>
In our example
<externalloadurl protocol="http" host="192.168.140.39:8080" subdomain="drools-guvnor/org.drools.guvnor.Guvnor/oryxeditor" usr="admin" pwd="admin"/>
h4. b. Deploy designer
Simple by copy to jboss deployment directory, or with our example in Linux
# Set our GUVNOR_JBOSS to this example path
export GUVNOR_JBOSS=/opt/guvnor_jboss
cd $GUVNOR_JBOSS
# Deploy designer
cp designer.war standalone/deployments/
h4. c. Verify designer
Start jboss and verify that we have something like this
09:47:56,841 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "designer.war"
09:47:56,841 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "drools-guvnor.war"
https://community.jboss.org/servlet/JiveServlet/showImage/19266/Screensho... https://community.jboss.org/servlet/JiveServlet/downloadImage/19266/Scree...
Figure 02: Verify designer installation
User your browser to connect to http://GUVNOR_IP:8080/drools-guvnor http://GUVNOR_IP:8080/drools-guvnor (or http://192.168.140.39:8080/drools-guvnor http://192.168.140.39:8080/drools-guvnor in our example), on Left side bar, select "Knowledge Base" \ "Packages" , then select "Create New" \ "New BPMN2 Process" as Figure 02 above, note that if you can create/edit and save your process.
h3. Step 4.6: Deploy form-builder
h4. a. Add users/roles configuration to GUVNOR_JBOSS
# Set our GUVNOR_JBOSS to this example path
export GUVNOR_JBOSS=/opt/guvnor_jboss
cd $GUVNOR_JBOSS
cp users.properties standalone/configuration/
cp roles.properties standalone/configuration/
h4. b. Add security domain for jbpm-form-builder in file standalone/configuration/standalone.xml
<subsystem xmlns="urn:jboss:domain:security:1.0">
<security-domains>
..
<security-domain name="jbpm-form-builder" cache-type="default">
<authentication>
<login-module code="UsersRoles" flag="required">
<module-option name="usersProperties" value="${jboss.server.config.dir}/users.properties"/>
<module-option name="rolesProperties" value="${jboss.server.config.dir}/roles.properties"/>
</login-module>
</authentication>
</security-domain>
..
</security-domains>
</subsystem>
h4. c. Add users/roles to jbpm-form-builder.war/WEB-INF/classes
Using your current Archive Manager to add users.properties and roles.properties to jbpm-form-builder.war/WEB-INF/classes
h4. d. Deploy form-builder and verify like we already did with designer
cp jbpm-form-builder.war standalone/deployments/
# Start GUVNOR_JBOSS
bin/standalone.sh
h4. e. Verify that you have
10:36:52,907 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "drools-guvnor.war"
And use your browser to verify that http://GUVNOR_IP:8080/jbpm-form-builder http://GUVNOR_IP:8080/jbpm-form-builder ( http://192.168.140.39:8080/jbpm-form-builder http://192.168.140.39:8080/jbpm-form-builder) works.
h2. 5. Task-Service or Human Task deployment (with verify).
Login to server on HUMAN_TASK_IP and place a copy of jbpm-install and start the installation:
h3. Step 5.1:Extract a clean copy of jboss-as-7.0.2.Final.zip to HUMAN_TASK_JBOSS
# Set our HUMAN_TASK_JBOSS to this example path
export HUMAN_TASK_JBOSS=/opt/human_task_jboss
echo $HUMAN_TASK_JBOSS
# Go to JBPM_INSTALL directory
cd /opt/download/
unzip jbpm-5.3.0.Final-installer-full.zip
cd /opt/download/jbpm-installer
# Extract a clean copy of jboss application server. To move to /opt we need root permission.
unzip lib/jboss-as-7.0.2.Final.zip
sudo mv jboss-as-7.0.2.Final $HUMAN_TASK_JBOSS
# And jbpm transactin manager library
cp jbpm-tm.jar $HUMAN_TASK_JBOSS/
# Task persistence.xml
cp task-service/resources/war/persistence.xml $HUMAN_TASK_JBOSS/
# MySQL module configuration
cp db/driver_jar_module.xml $HUMAN_TASK_JBOSS/module.xml
cd $HUMAN_TASK_JBOSS
h3. Step 5.2: Copy your custom build human-task
>From JBPM_SOURCE/jbpm-human-task/jbpm-human-task-war/target
To $HUMAN_TASK_JBOSS/jbpm-human-task-war.war
h3. Step 5.3: Jboss standalone.xml configuration
Change HUMAN_TASK_JBOSS/standalone/configuration/standalone.xml as following
h4. a. Remove pojo module
<extension module="org.jboss.as.osgi"/>
<!-- Remove this line extension module="org.jboss.as.pojo"/-->
<extension module="org.jboss.as.remoting"/>
And
<subsystem xmlns="urn:jboss:domain:naming:1.0" />
<!--subsystem xmlns="urn:jboss:domain:pojo:1.0" /-->
<subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="lazy">
h4. b. Change port for management interface.
<management-interfaces>
<native-interface interface="management" port="10099" />
<http-interface interface="management" port="10090"/>
</management-interfaces>
h4. c. Add datasource for task-service
<subsystem xmlns="urn:jboss:domain:datasources:1.0">
<datasources>
<datasource jndi-name="java:jboss/datasources/taskDS" pool-name="MysqlTaskDSPool" enabled="true" jta="true" use-java-context="true" use-ccm="true">
<connection-url>
jdbc:mysql://192.168.140.39:3306/task
</connection-url>
<driver>
mysql
</driver>
<pool>
<prefill>
false
</prefill>
<use-strict-min>
false
</use-strict-min>
<flush-strategy>
FailingConnectionOnly
</flush-strategy>
</pool>
<security>
<user-name>
task
</user-name>
<password>
taskpassword
</password>
</security>
</datasource>
<drivers>
<driver name="mysql" module="com.mysql">
<xa-datasource-class>
com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
</xa-datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
h4. d. Bind to HUMAN_TASK_IP. For example
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:192.168.140.39}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:192.168.140.39}"/>
</interface>
</interfaces>
h4. e. Set offset-port
For our example to running on the same server as in https://community.jboss.org/docs/DOC-16705 https://community.jboss.org/wiki/MultipleInstancesOfJBossAS7OnTheSameMachine (Approach#1)
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="100">
h3. Step 5.4: MySQL driver for jboss
h4. a. Create MySQL module directory
mkdir modules/com/mysql
mkdir modules/com/mysql/main
h4. b.Copy module declaration file
cp module.xml modules/com/mysql/main/
h4. c. Download and install mysql driver to jBoss
wget https://repository.jboss.org/nexus/service/local/repositories/central/con...
cp mysql-connector-java-5.1.18.jar modules/com/mysql/main/mysql-connector-java.jar
h4. d. Start your HUMAN_TASK_JBOSS now
bin/standalone.sh
To verify your configuration
* Does it start Ok?
* MySQL driver loaded?
* Can you see taskDS datasource on jBoss admin console at http://HUMAN_TASK_IP:10099/ http://HUMAN_TASK_IP:10090/ (In our example http://192.168.140.39:10090/)?
https://community.jboss.org/servlet/JiveServlet/showImage/19269/human_tas... https://community.jboss.org/servlet/JiveServlet/downloadImage/19269/human... Figure 03: Veriry DataSource configuration of HUMAN_TASK_JBOSS
h3. Step 5.4: jbpm-human-task-war.war configuration
h4. a. In your jbpm-human-task-war.war file, make following modification with your current archive manager
Remove WEB-INF/lib/netty-3.2.0.Final.jar
Add jbpm-tm.jar to WEB-INF/lib/
h4. b. Configure your WEB-INF/web.xml as following
h5. Make HornetQ as active transport
<!-- active configuration on of hornetq|mina|jms (defauls to hornetq) -->
<init-param>
<param-name>active.config</param-name>
<param-value>hornetq</param-value>
</init-param>
h5. Set HornetQ binding address and port (Remember our fix at the end of part 2) to HUMAN_TASK_IP and HORNETQ_PORT
<!-- HornetQ configuration parameters -->
<init-param>
<param-name>hornetq.host</param-name>
<param-value>192.168.140.39</param-value>
</init-param>
<init-param>
<param-name>hornetq.port</param-name>
<param-value>1234</param-value>
</init-param>
h5. Optional: Task service persistence unit name, we will use default value so you can keep it blank
<!-- Task Service configuration independent of transport -->
<init-param>
<param-name>task.persistence.unit</param-name>
<param-value>org.jbpm.task</param-value>
</init-param>
h5. User demo user/group call-back implementation
<!-- use org.jbpm.task.service.DefaultUserGroupCallbackImpl to configure sample user group callback for demo purpose-->
<init-param>
<param-name>user.group.callback.class</param-name>
<param-value>org.jbpm.task.service.DefaultUserGroupCallbackImpl</param-value>
</init-param>
h5. Using demo user and group provider
<!-- use classpath:/org/jbpm/task/servlet/SampleUsers.mvel to configure sample users for demo purpose-->
<!-- DefaultUsers.mvel is used to insert Administrator as it is required for task server to operate -->
<init-param>
<param-name>load.users</param-name>
<param-value>classpath:/org/jbpm/task/servlet/SampleUsers.mvel</param-value>
</init-param>
<!-- use classpath:/org/jbpm/task/servlet/SampleGroups.mvel to configure sample users for demo purpose-->
<init-param>
<param-name>load.groups</param-name>
<param-value>classpath:/org/jbpm/task/servlet/SampleGroups.mvel</param-value>
</init-param>
Look at attachement for the file jbpm_human_task_web.xml, a full copy of our example jbpm-human-task-war/WEB-INF/web.xml
h4. c. Configure persistence.xml
h5. Change jbpmDS to taskDS
<non-jta-data-source>java:jboss/datasources/taskDS</non-jta-data-source>
h5. Modify properties to your MySQL_IP and MySQL_PORT
<properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
<property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/>
<property name="hibernate.connection.url" value="jdbc:mysql://MySQL_IP:MySQL_PORT/task" />
<property name="hibernate.connection.username" value="task"/>
<property name="hibernate.connection.password" value="taskpassword"/>
<property name="hibernate.connection.autocommit" value="false" />
<property name="hibernate.max_fetch_depth" value="3"/>
<property name="hibernate.hbm2ddl.auto" value="create" />
<property name="hibernate.show_sql" value="true" />
</properties>
In our example:
<properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
<property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/>
<property name="hibernate.connection.url" value="jdbc:mysql://192.168.140.39:3306/task" />
<property name="hibernate.connection.username" value="task"/>
<property name="hibernate.connection.password" value="taskpassword"/>
<property name="hibernate.connection.autocommit" value="false" />
<property name="hibernate.max_fetch_depth" value="3"/>
<property name="hibernate.hbm2ddl.auto" value="create" />
<property name="hibernate.show_sql" value="true" />
</properties>
Look at attachment for the file jbpm_human_task_persistence.xml, a full copy of our example jbpm-human-task-war/WEB-INF/classes/META-INF/persistence.xml
h4. d. Update jpbm-human-task-war.war/WEB-INF/classes/META-INF/persistence.xml
With the modified persistence.xml in the Step c above.
h4. b. Place a copy of HUMAN_TASK_JBOSS
h2. 6. jBPM-Console deployment (with verify).
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-21179]
Create a new document in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 2 months
- 1
- 0
[JBoss Web Services] - jaxb version used by JBoss AS 7.0Final (date issue/timezone issue)
by Peter Fry
Peter Fry [https://community.jboss.org/people/peterfry] created the discussion
"jaxb version used by JBoss AS 7.0Final (date issue/timezone issue)"
To view the discussion, visit: https://community.jboss.org/message/754884#754884
--------------------------------------------------------------
I seem to be re-encountering an issue in JBoss AS 7.0 that we first encountered in JBoss 5.
A previous developer described the problem thus:
JAXB 2.1.x DatatypeConverter implementation does not correctly apply timezone offset when printing xs:dateTime string representation of a java.util.Date. The complementary method in DatatypeConverter that parses the string representation into a java.util.Date does apply the current timezone offset. The issue has manifested itself now because we are in BST (GMT + 1).
JAXB 2.1.x DatatypeConverter.printDateTime() outputs:
"1970-01-01T00:00:00Z"
JAXB 2.2.x DatatypeConverter.printDateTime() outputs:
"1970-01-01T00:00:00+01:00"
Solution is to ensure that JAXB 2.2.1 version of jaxb-api.jar is present in JBoss server's endorsed library folder for both the web service client jboss instance and the web service
server instance.
I have replicated the issue with the following client code
XMLGregorianCalendar cal = null;
try {
cal = DatatypeFactory.newInstance()
.newXMLGregorianCalendar(
new GregorianCalendar(1970,0,1));
} catch (DatatypeConfigurationException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
service.doSomething( cal )
In the webservice implementation the string received in the SOAP payload is:
1970-01-01T00:00:00Z
Which corresponds to the JAXB 2.1 behaviour .
What I can't fathom is that the modules repository for the JBoss 7.0 only has the JAXB 2.2 implementation.
With JBoss 5.0 we had to put JAXB 2.2 in the endorsed directory (specified via the system property java.endorsed.dirs) .
Do we have to do a similar thing with JBoss 7.0? Why do we have to do this even though the version in the modules repository is JAXB 2.2?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/754884#754884]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 2 months
- 1
- 1
[JBoss Tools] - Summer time with new release, SOA tools and a bit of Juno and Fedora news
by Max Rydahl Andersen
Max Rydahl Andersen [https://community.jboss.org/people/maxandersen] created the blog post:
"Summer time with new release, SOA tools and a bit of Juno and Fedora news"
To view the blog post, visit: https://community.jboss.org/community/tools/blog/2012/08/22/summer-time-w...
--------------------------------------------------------------
We released back in July a new version of JBoss Tools 3.3.1 and JBoss Developer Studio 5.0.1 which fixes the problem of installing on Eclipse 3.7.0 (Indigo) and makes it possible, but not recommended to install on Eclipse 4.x (Juno).
The SOA Tools are also now available from JBoss Central and we got news from the Fedora Java spin which includes parts of JBoss Tools. More below...
h2. SOA Tools
The SOA Tools (jbpm, drools, modeshape, teiid, etc.) are available from JBoss Central in both JBoss Tools 3.3+ and Developer Studio 5+.
https://community.jboss.org/servlet/JiveServlet/showImage/38-5016-19268/s... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5016-192...
To get them open JBoss Central and go to the Software/Update tab and they should be listed, ready to be installed.
The plugins have been updated to work with the latest release of http://www.redhat.com/about/news/archive/2012/6/new-versions-of-jboss-ent... JBoss SOA Platform and its components.
h2. Eclipse 3.7.0 - you still use that ?
JBoss Tools 3.3.0 came out requiring Eclipse 3.7.1 because there was some rather nasty bugs we wanted to avoid to expose to users and we naively belived most would be on 3.7.1+ by now - but oh boy we were wrong.
It turns out that when we released the final version of JBoss Tools 3.3.0 our success install rate went up significantly (Yay!) but we also saw a skyrocketing level of errored installs (Not good). Looking at those error logs showed us that majority of Eclipse 3.7 (Indigo) users are still on the very first version, i.e. 3.7.0.
In a perfect world Eclipse P2 update mechanisim would let you update to Eclipse 3.7.1+ at the same time as installing plugins that requires/suggest to use a bugfixed version, but unfortunately Eclipse mechanism does not allow for this.
Therefore in this update we allowed JBoss Tools to depend on Eclipse 3.7.0 to make it installable, but Eclipse 3.7.0 users will now get a warning dialog on startup suggesting they should update their Eclipse to have a better experience.
h2. How about Eclipse 4.x/Juno ?
JBoss Tools 3.3.x and Developer Studio is tested and supported on Eclipse 3.7/Indigo - but what if I want to use Juno ?
There are two options:
A) You can *try* use JBoss Tools 3.3.x on Juno - but we do not recommend this.
B) You can use the http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ JBoss Tools 3.4.x nightly builds updatesite - this have been updated/adjusted to work with Juno and is the basis for the next major update of tools and Developer Studio.
In both cases your mileage will vary, but if you are up for it please do try out the nightly builds and report any issues found while using Juno with JBoss Tools.
h2. Fedora Java Spin
https://twitter.com/grdryn Gerard Ryan have been doing his Google Summer of Code project about creating a Fedora Spin that would be good for Java developers. In that progress he took on the task on trying to package JBoss Tools, or at https://apps.fedoraproject.org/packages/s/eclipse-jbosstools least parts of it so it could be installed "the Fedora way".
http://fedoraproject.org/static/images/fedora-logo.png http://fedoraproject.org/static/images/fedora-logo.png
He actually succeded in making this happen and you can see his final report about this at his http://blog.grdryn.me/2012/08/20/fedora-java-remix-gsoc-update-13-final/ GSOC blog.
You can try out the full Fedora Java spin by downloading the ISO images from http://ryan.lt/fedora-java-remix/ Gerard or if you are already running Fedora 17 or newer, you can try it out by running:
yum install eclipse-jbosstools
This will actually be installed into Fedora's version of Eclipse Juno, so that is third way to try Juno out with parts of JBoss Tools.
Hope you like that and if you find issues report it in our jra, but please mention if you are using the Fedora package since there are some slight differences.
Have fun,
Max
h2.
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/community/tools/blog/2012/08/22/summer-time-w...]
12 years, 2 months
- 1
- 0
[jBPM] - the reassignment and the notification are invalid under the human task
by sandy yang
sandy yang [https://community.jboss.org/people/forrest43] created the discussion
"the reassignment and the notification are invalid under the human task"
To view the discussion, visit: https://community.jboss.org/message/755065#755065
--------------------------------------------------------------
I have created a process, defined notification and reassignment under task1, as per below picture,：
https://community.jboss.org/servlet/JiveServlet/showImage/2-755065-19270/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-755065-19...
When the process stayed at task1 over 10 seconds, it didn’t do the reassignment, and the notification did not work either. But in the database, there were new records created in the deadline and the notification_recipients table, refer to below picture:
https://community.jboss.org/servlet/JiveServlet/showImage/2-755065-19275/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-755065-19...
https://community.jboss.org/servlet/JiveServlet/showImage/2-755065-19276/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-755065-19...
The coding under the task server as followed：
https://community.jboss.org/servlet/JiveServlet/showImage/2-755065-19272/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-755065-19...
Use the human task handler:
https://community.jboss.org/servlet/JiveServlet/showImage/2-755065-19274/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-755065-19...
The version of the JBPM is 5.3.0 Final
The details of the process definition file as followed:
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755065#755065]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 2 months
- 1
- 0
[jBPM] - how to user the jbpm web designer ?
by qi jian
qi jian [https://community.jboss.org/people/air_is_me] created the discussion
"how to user the jbpm web designer ?"
To view the discussion, visit: https://community.jboss.org/message/755047#755047
--------------------------------------------------------------
I had downloaded the jbpm5.2 and it worked. but when i type the url http://localhost:8080/designer http://localhost:8080/designer
it return the 400 error. here is the wars in my jboss deployments
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755047#755047]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 2 months
- 1
- 0
[jBPM] - Remove/delete human task
by gvallangca
gvallangca [https://community.jboss.org/people/gvallangca] created the discussion
"Remove/delete human task"
To view the discussion, visit: https://community.jboss.org/message/752760#752760
--------------------------------------------------------------
To whom it may concern,
I had successfully created a human task in jbpm 5.3. I saw it in the jbpm database that it already has a record and its status was 'Reserved'.
After successfully creating a task, the next was to create a record in my database but suddenly it produced an sqlException. Due to
that reason, I would like to delete the jbpm task that was created. I've tried to execute this line:
taskClient.remove(taskId, userId, responseHandler);
Unfortunately it generated an exception:
java.lang.RuntimeException: Couldn't remove user gvallangca since it isn't a notification recipient
at org.jbpm.task.service.TaskServiceSession.taskRemoveOperation(TaskServiceSession.java:760)
at org.jbpm.task.service.TaskServiceSession.taskOperation(TaskServiceSession.java:410)
at org.jbpm.task.service.TaskServerHandler.messageReceived(TaskServerHandler.java:84)
at org.jbpm.task.service.mina.MinaTaskServerHandler.messageReceived(MinaTaskServerHandler.java:41)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:713)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:793)
at org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:375)
at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:229)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:793)
at org.apache.mina.filter.logging.LoggingFilter.messageReceived(LoggingFilter.java:176)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:793)
at org.apache.mina.core.filterchain.IoFilterAdapter.messageReceived(IoFilterAdapter.java:119)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageReceived(DefaultIoFilterChain.java:426)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:638)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:598)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:587)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:61)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:969)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I hope someone could help or give other ideas how to remove the jbpm task I have created. Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/752760#752760]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 2 months
- 3
- 3
[jBPM] - jBPM-5.3.0.Final Manual Deployment Guide for Beginner
by quangtin3
quangtin3 [https://community.jboss.org/people/quangtin3] modified the document:
"jBPM-5.3.0.Final Manual Deployment Guide for Beginner"
To view the document, visit: https://community.jboss.org/docs/DOC-21179
--------------------------------------------------------------
**
#1_Overview_of_jBPM 1. Overview of jBPM
***
#jBPM_Components jBPM Components
***
#Separation_deployment Separation deployment
**
#2_Common_bugs_fix_after_jBPM530Final_release 2. Common bugs fix after jBPM-5.3.0.Final release
***
#Building_from_sourcecode Building from source-code
****
#a_Configure_your_git_username_and_email a. Configure your git username and email
****
#b_Clone_jbpm_repository_from_githubcom b. Clone jbpm repository from github.com
****
#c_Working_with_local_repository c. Working with local repository
*****
#List_all_jBPM_tags_ List all jBPM tags
*****
#Switch_to_530Final_revision_tag Switch to 5.3.0.Final revision tag.
*****
#View_prehistory_just_before_jBPM_team_released_jBPM530Final View pre-history just before jBPM team released jBPM.5.3.0.Final
***
#Apply_bug_fix Apply bug fix
****
#Bug_Could_not_locate_named_parameter_userId Bug: Could not locate named parameter [userId]
****
#Bug_No_result_or_connection_timeout Bug: No result, or connection timeout
****
#Bug_Must_be_positive Bug: Must be positive
****
#Bug_HornetQ_binding_only_to_local_address Bug: HornetQ binding only to local address.
**
#3_Manual_jBPM_components_deployment 3. Manual jBPM components deployment
***
#Environment Environment
****
#Check_your_JDK_installation Check your JDK installation
****
#Check_apache_maven Check apache maven
****
#Check_apache_ant Check apache ant
***
#Deployment_parameters Deployment parameters
***
#MySQL_database_deployment_just_verify MySQL database deployment (just verify).
**
#4_Drools_guvnor_designer_and_formbuilder_deployment_with_verify 4. Drools guvnor, designer, and form-builder deployment (with verify)
***
#Step_41Extract_a_clean_copy_of_jbossas702Finalzip_to_GUVNOR_JBOSS Step 4.1:Extract a clean copy of jboss-as-7.0.2.Final.zip to GUVNOR_JBOSS
***
#Step_42_Jboss_configuration Step 4.2: Jboss configuration.
***
#Step_43_droolsguvnor_configuration Step 4.3: drools-guvnor configuration
****
#a_Update_GUVNOR_JBOSSpreferencesproperties_to_our_will_be_deployed_designer_and_formbuilder a. Update GUVNOR_JBOSS/preferences.properties to our will be deployed designer and form-builder
****
#b_Place_a_copy_of_GUVNOR_JBOSSpreferencesproperties_to_droolsguvnorwartargetWEBINFclassespreferencesproperties b. Place a copy of GUVNOR_JBOSS/preferences.properties to drools-guvnor.war/target/WEB-INF/classes/preferences.properties
***
#Step_44_Deploy_and_verify_droolsguvnor_component_installation Step 4.4: Deploy and verify drools-guvnor component installation
****
#a_Deploy_droolsguvnor a. Deploy drools-guvnor
****
#b_Verify_that_we_have_the_following_message_in_the_console b. Verify that we have the following message in the console
****
#c_Verify_that_we_can_access_the_droolsguvnor c. Verify that we can access the drools-guvnor
***
#Step_45_Deploy_designer Step 4.5: Deploy designer
****
#a_Apply_the_change_for_Designer_as_following_article_httpbpmgeekcomblogmakingjbpm5workremotehost_ a. Apply the change for Designer as following article http://bpmgeek.com/blog/making-jbpm5-work-remote-host
****
#b_Deploy_designer b. Deploy designer
****
#c_Verify_designer c. Verify designer
***
#Step_46_Deploy_formbuilder Step 4.6: Deploy form-builder
****
#a_Add_usersroles_configuration_to_GUVNOR_JBOSS a. Add users/roles configuration to GUVNOR_JBOSS
****
#b_Add_security_domain_for_jbpmformbuilder_in_file_standaloneconfigurationstandalonexml b. Add security domain for jbpm-form-builder in file standalone/configuration/standalone.xml
****
#c_Add_usersroles_to_jbpmformbuilderwarWEBINFclasses c. Add users/roles to jbpm-form-builder.war/WEB-INF/classes
****
#d_Deploy_formbuilder_and_verify_like_we_already_did_with_designer d. Deploy form-builder and verify like we already did with designer
****
#e_Verify_that_you_have e. Verify that you have
**
#5_TaskService_or_Human_Task_deployment_with_verify 5. Task-Service or Human Task deployment (with verify).
***
#Step_51Extract_a_clean_copy_of_jbossas702Finalzip_to_HUMAN_TASK_JBOSS Step 5.1:Extract a clean copy of jboss-as-7.0.2.Final.zip to HUMAN_TASK_JBOSS
***
#Step_52_Copy_your_custom_build_humantask_ Step 5.2: Copy your custom build human-task
***
#Step_53_Jboss_standalonexml_configuration_ Step 5.3: Jboss standalone.xml configuration
****
#a_Remove_pojo_module a. Remove pojo module
****
#b_Change_port_for_management_interface b. Change port for management interface.
****
#c_Add_datasource_for_taskservice c. Add datasource for task-service
****
#d_Bind_to_HUMAN_TASK_IP_For_example d. Bind to HUMAN_TASK_IP. For example
****
#e_Set_offsetport e. Set offset-port
***
#Step_54_MySQL_driver_for_jboss Step 5.4: MySQL driver for jboss
****
#a_Create_MySQL_module_directory a. Create MySQL module directory
****
#bCopy_module_declaration_file b.Copy module declaration file
****
#c_Download_and_install_mysql_driver_to_jBoss c. Download and install mysql driver to jBoss
****
#d_Start_your_HUMAN_TASK_JBOSS_now d. Start your HUMAN_TASK_JBOSS now
***
#Step_54_jbpmhumantaskwar_configuration_TODO Step 5.4: jbpm-human-task.war configuration (//TODO)
****
#a_Update_HUMAN_TASK_JBOSS a. Update HUMAN_TASK_JBOSS
****
#b_Place_a_copy_of_HUMAN_TASK_JBOSS b. Place a copy of HUMAN_TASK_JBOSS
**
#6_jBPMConsole_deployment_with_verify 6. jBPM-Console deployment (with verify).
*Disclaimer:* First, Almost material in this article I borrowed form all over the public web. Some of most borrowed source are (in order):
* Extract from jbpm-install/build.xml Ant script.
* jBPM official user-guide: http://docs.jboss.org/jbpm/v5.3/userguide/ http://docs.jboss.org/jbpm/v5.3/userguide/
* jBPM community user forum: https://community.jboss.org/community/jbpm?view=discussions https://community.jboss.org/en/jbpm?view=discussions
* BPM Geek: http://bpmgeek.com/blog/making-jbpm5-work-remote-host http://bpmgeek.com/blog/making-jbpm5-work-remote-host
Second, This article only provides a way of step by step manually deployment of each jBPM-5.3.0.Final components. It was written by a jBPM beginner. For a official document please refer to: http://docs.jboss.org/jbpm/v5.3/userguide/ http://docs.jboss.org/jbpm/v5.3/userguide/
Third,this article example is in Linux. Mabe I will add ant scripts (again, heavily extracts from jbpm-install/build.xml) for faster deployment and Windows friendlier.
h2. 1. Overview of jBPM
h3. jBPM Components
Download a copy of jbpm-5.3.0.Final-installer-full.zip ( http://sourceforge.net/projects/jbpm/files/jBPM%205/jbpm-5.3.0.Final/ http://sourceforge.net/projects/jbpm/files/jBPM%205/jbpm-5.3.0.Final/) and extract it to a location, from now on we call it JBPM_INSTALL. JBPM_INSTALL contains all core jBPM components.
|| *Components
* || *File in JBPM_INSTALL/lib*
|| *Description
* ||
| jbpm-runtime | jbpm-5.3.0.Final-bin.zip | jBPM Runtime, if you are willing to build a stand alone Java application you will need this. |
| drools-guvnor | guvnor-distribution-wars-5.4.0-20120516.war | Drools-Guvnor provides process repository. |
| designer | designer-2.2.Final-jboss7.war | JBPM2 process designer. It's integrated with drools-guvnor. |
| form-builder | jbpm-5.3.0.Final-form-builder.war | Form builder. It's going to be integrated with the designer. http://blog.athico.com/2012/07/jbpm-form-builder-state-of-art.html |
| gwt-console and gwt-console-server | jbpm-5.3.0.Final-gwt-console.zip |
|
| human-task | jbpm-5.3.0.Final-human-task-war.zip |
|
Table 01: jBPM.5.3.0.Final components and their binary file
https://community.jboss.org/servlet/JiveServlet/showImage/19247/jBPM+-+In... https://community.jboss.org/servlet/JiveServlet/downloadImage/19247/jBPM+...
Figure 01: jBPM-Internal components communication
The communication between component as described in Figure-01, this article use MySQL. But by default, jbpm-install with "ant start.demo" will run with H2 database. From this communication view we can separate each component deployment. Event on each application server.
https://community.jboss.org/servlet/JiveServlet/showImage/19248/jBPM+-+Ec... https://community.jboss.org/servlet/JiveServlet/downloadImage/19248/jBPM+...
Figure 02: The communication with Eclipse IDE
h3. Separation deployment
For a beginner, with all jBPM components are twisted together:
* It's hard to tell which message of what components. When something go wrong, which one to focus, which one to just ignore.
* Need a way to check each component is up and running.
* Just a way to learn and experience with jBPM.
Purely from this experience and conclusion, this article will provides a manual installation of each jBPM-5.3.0.Final component.
h2. 2. Common bugs fix after jBPM-5.3.0.Final release
h3. Building from source-code
As a beginner I occasionally meet this kind of error {userId parameter, no result, must be positive, hornetq remote ..}. Some are must apply the fix before you can go on further. The commits after jBPM-5.3.0.Final does fix the bug but also introduces incompatible with other jBPM.5.3.0.Final. So this part will describes how to checkout Original jBPM-5.3.0.Final release source code; find the Fixed patch and apply to your local branch.
For more detailed git document, please refer to other document. This article only using related git commands.
h4. a. Configure your git username and email
# For your local branche
git config --global user.name "Your Name"
git config --global user.email "your_email(a)addr.ess"
h4. b. Clone jbpm repository from github.com
# We only need jbpm.git, because in version 5.3.0.Final all component on the same git repository.
git clone https://github.com/droolsjbpm/jbpm.git
# We have local git reposistory. We will call its directory path as jBPM_SRC
cd jbpm/
mvn clean install -U -Dfull -DskipTests
Optional: in "mvn clean install -U -Dfull -DskipTests" abover, We can add -nsu (no snapshot update) for faster build. Because we're only aware specific on 5.3.0.Final revision and its dependencies.
mvn clean install -U -Dfull -DskipTests -nsu
This command really takes a while, especially for the first time and your empty maven local repository.
h4. c. Working with local repository
The jbpm is a typical maven parent project with multiple module. Two of theme {human-task; gwt-console} are parent project too. From now on, you can use your favorite IDE with JavaEE profile to work with this checked out repository, showing diff and applying patch. Otherwise you can using git command as following example:
h5. List all jBPM tags
# From your jBPM_SOURCE, show tags
git tag
The output will be something like this:
5.0-CR1
5.0.0
5.1.0.CR1
5.1.0.Final
5.1.0.M1
5.1.1.Final
5.1.2.Final
5.2.0.Final
5.2.1.Final
5.2.2.Final
5.3.0.CR1
5.3.0.Final
h5. Switch to 5.3.0.Final revision tag.
Chose your local branch name, for example: update.after.5.3.0.final
git checkout 5.3.0.Final -b update.after.5.3.0.final
Result message
Switched to a new branch 'update.after.5.3.0.final'
h5. View pre-history just before jBPM team released jBPM.5.3.0.Final
git log
Example output
***@***:~/Tutorial/jbpm$ git log
commit d7640b9c0ba87d771862e8534cc607ca0f4d1aff
Author: Toni Rikkola <toni(a)rikkola.net>
Date: Mon May 14 13:25:30 2012 +0300
change to 5.4.0.Final version
commit 88440fe1430170458981c2752192df2c64c83636
Author: Maciej Swiderski <mswiders(a)redhat.com>
Date: Wed May 9 19:22:35 2012 +0200
BZ820210 - Could not initialize stateful knowledge session: loader constraint violation when using HornetQ task service strategy
commit 80f940e2e860ac640a75114ab2780f6c2b7a865c
Author: salaboy <salaboy(a)gmail.com>
Date: Wed May 9 15:04:54 2012 +0100
- mvel workaround
...
Build your own jBPM.5.3.0.Final for the first time
mvn clean install -U -Dfull -DskipTests -nsu
Now you can working with your local git repository, update the 5.3.0.Final tag with the patch you need. All your commit will be stored on update.after.5.3.0.final branches.
h3. Apply bug fix
h4. Bug: Could not locate named parameter [userId]
Full message
java.lang.IllegalArgumentException: org.hibernate.QueryParameterException: could not locate named parameter [userId]
Community thread:
https://community.jboss.org/message/738335#738335 https://community.jboss.org/message/738335#738335
https://community.jboss.org/thread/200361 https://community.jboss.org/thread/200361
Fix commit: 4a47527163854b233cdb9599f54c9320e945a372
h4. Bug: No result, or connection timeout
Message
java.lang.RuntimeException: Timeout : unable to retrieve results
Treatment: With this particular deployment {separating components deployment, using MySQL} I haven't meet this error yet.
h4. Bug: Must be positive
Full message:
2011-07-18 18:46:35,546 [FATAL] Uncaught Exception:
java.lang.IllegalArgumentException:
must be positive
at Unknown.cKb(Unknown source:0)
Fix: Not yet. (I think) this comes from GWT bug. GWT is the Google Web Toolkit that jBPM-Console are using. Just ignore it and continue with your work.
h4. Bug: HornetQ binding only to local address.
There aren't any configuration for Human-Task-War to bind on particular address. And by default it only listen on local address so Gwt-Console-Server cannot connect to it. Our separating deployment needs Gwt-Console-Server to connect to Human-Task, so apply the change-set below:
Bug track link: https://issues.jboss.org/browse/JBPM-3720?page=com.atlassian.jira.plugin.... https://issues.jboss.org/browse/JBPM-3720?page=com.atlassian.jira.plugin....
Change set: https://source.jboss.org/changelog/jBPM?cs=e115680b023ce0747608625f0cd616... https://source.jboss.org/changelog/jBPM?cs=e115680b023ce0747608625f0cd616...
h2. 3. Manual jBPM components deployment
h3. Environment
h4. Check your JDK installation
# Check JAVA_HOME environment variable arcording to your operating system. In linux
echo $JAVA_HOME
# JDK Java version 1.6 or newer
java -version
h4. Check apache maven
Download and installation instruction: http://maven.apache.org/download.html http://maven.apache.org/download.html
# Check M2 and M2_HOME environment variables acording to your operating system. In linux
echo $M2
echo $M2_HOME
# Check Apache Maven installation
mvn -version
h4. Check apache ant
Download: http://ant.apache.org/bindownload.cgi http://ant.apache.org/bindownload.cgi and manual: http://ant.apache.org/manual/index.html http://ant.apache.org/manual/index.html
# Check ANT_HOME environment variables acording to your operating system. In linux
echo $ANT_HOME
# And ANT_OPTS if it's nessessary. For example proxy configuration
echo $ANT_OPTS
-Dhttp.proxyHost=192.168.193.12 -Dhttp.proxyPort=3128
# Check Apache Ant installation
ant -version
h3. Deployment parameters
|| *Name
* || *Variables
* || *Example values* ||
| Jbpm-install | JBPM_INSTALL | /opt/download/jbpm-install |
| MySQL username/password and schema | MySQL_JBPM
MySQL_TASK | jbpm,jbpmpassword and schema name is jbpm
task,taskpassword and schema name is task |
| MySQL server IP/PORT | MySQL_IP:MySQL_PORT | 192.168.140.39:3306 |
| Group-01 components: {Drool-guvnor, Designer, Form-Builder} | GUVNOR_JBOSS
GUVNOR_IP
GUVNOR_HTTP_PORT
GUVNOR_MANAGEMENT_PORT | /opt/guvnor_jboss
192.168.140.39
8080
9999 and 9990 |
| Group-02: Human-task | HUMAN_TASK_JBOSS
HUMAN_TASK_IP
HUMAN_TASK_HTTP_PORT
HUMAN_TASK_MANAGEMENT_PORT
HUMAN_TASK_PORT-OFFSET | /opt/human_task_jboss
192.168.140.39
8180
10099 and 10090
port-offset="100" |
| Group-03: Gwt-Console and Gwt-Console-Server | CONSOLE_JBOSS
CONSOLE_IP
CONSOLE_HTTP_PORT
CONSOLE_MANAGEMENT_POR
CONSOLE_PORT_OFFSET | /opt/console_jboss
192.168.140.39
8280
10199 and 10190
port-offset="200" |
Table 02 - Deployment parameters
The "example value column" in Table 02 are values from a real deployment with all jboss instances running on the same machine. https://community.jboss.org/docs/DOC-16705 https://community.jboss.org/wiki/MultipleInstancesOfJBossAS7OnTheSameMachine (Approach#1)
h3. MySQL database deployment (just verify).
Verify that you can connect and login to MySQL:
# From server HUMAN_TASK_IP to MySQL_IP:MySQL_PORT
mysql -h MySQL_IP -P MySQL_Port -u MySQL_TASK -pMySQL_TASK_PASSWORD
# From server JBPM_IP to MYSQL_IP:MySQL_PORT
mysql -h MySQL_IP -P MySQL_Port -u MySQL_JBPM -pMySQL_JBPM_PASSWORD
# Note: -P (capitalized) for port; and -p (lowercase) for password.
# No space between -p and MySQL_TASK_PASSWORD. For example:
# mysql -h 192.168.140.39 -P 3306 -u task -ptaskpassword
# mysql -h 192.168.140.39 -P 3306 -u jbpm -pjbpmpassword
After this, We can just forget about firewall, network routing, MySQL permission issues incase our persistence not work. For MySQL related document http://dev.mysql.com/doc/refman/5.0/en/connecting.html http://dev.mysql.com/doc/refman/5.0/en/connecting.html
h2. 4. Drools guvnor, designer, and form-builder deployment (with verify)
Login to server on GUVNOR_IP and place a copy of jbpm-install and start the installation:
h3. Step 4.1:Extract a clean copy of jboss-as-7.0.2.Final.zip to GUVNOR_JBOSS
# Set our GUVNOR_JBOSS to this example path
export GUVNOR_JBOSS=/opt/guvnor_jboss
echo $GUVNOR_JBOSS
# Go to JBPM_INSTALL directory
cd /opt/download/
unzip jbpm-5.3.0.Final-installer-full.zip
cd /opt/download/jbpm-installer
# Extract a clean copy of jboss application server. To move to /opt we need root permission.
unzip lib/jboss-as-7.0.2.Final.zip
sudo mv jboss-as-7.0.2.Final $GUVNOR_JBOSS
# Copy guvnor, designer, form-builder
cp lib/guvnor-distribution-wars-5.4.0-20120516.war $GUVNOR_JBOSS/drools-guvnor.war
cp lib/designer-2.2.Final-jboss7.war $GUVNOR_JBOSS/designer.war
cp lib/jbpm-5.3.0.Final-form-builder.war $GUVNOR_JBOSS/jbpm-form-builder.war
# And their configurations file
cp conf/guvnor.preferences.properties $GUVNOR_JBOSS/preferences.properties
cp auth/users.properties $GUVNOR_JBOSS/
cp auth/roles.properties $GUVNOR_JBOSS/
cd $GUVNOR_JBOSS
h3. Step 4.2: Jboss configuration.
# Change GUVNOR_JBOSS/standalone/configuration/standalone.xml to bind to GUVNOR_IP. For example
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:192.168.140.39}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:192.168.140.39}"/>
</interface>
</interfaces>
h3. Step 4.3: drools-guvnor configuration
h4. a. Update GUVNOR_JBOSS/preferences.properties to our will be deployed designer and form-builder
...
#Designer configuration
designer.url=http://192.168.140.39:8080
#Do not change this unless you know what are you doing
designer.context=designer
designer.profile=jbpm
#FormBuilder configuration
#Do not change this unless you know what are you doing
formbuilder.url=http://192.168.140.39:8080
formbuilder.context=jbpm-form-builder
formbuilder.profile=guvnor
h4. b. Place a copy of GUVNOR_JBOSS/preferences.properties to drools-guvnor.war/target/WEB-INF/classes/preferences.properties
# User your favorist archive manager.
Using "Open with Archive Manager" in Ubuntu Linux
h3. Step 4.4: Deploy and verify drools-guvnor component installation
h4. a. Deploy drools-guvnor
# Set our GUVNOR_JBOSS to this example path
export GUVNOR_JBOSS=/opt/guvnor_jboss
cd $GUVNOR_JBOSS
# Deploy drools-guvnor
cp drools-guvnor.war standalone/deployments/
# Verify drools-guvnor by start GUVNOR_JBOSS
bin/standalone.sh
h4. b. Verify that we have the following message in the console
...
11:55:46,779 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /drools-guvnor
11:55:46,844 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "drools-guvnor.war
h4. c. Verify that we can access the drools-guvnor
Access the http://GUVNOR_IP:8080/drools-guvnor http://GUVNOR_IP:8080/drools-guvnor (In our example is http://192.168.140.39:8080 http://192.168.140.39:8080/drools-guvnor) with the browser from GUVNOR_IP and CONSOLE_IP
h3. Step 4.5: Deploy designer
h4. a. Apply the change for Designer as following article http://bpmgeek.com/blog/making-jbpm5-work-remote-host
Lock for the section +"Saving and reloading process in designer could cause failures"+ at the end of that post, we need to make following change:
<externalloadurl protocol="http" host="GUVNOR_IP:8080" subdomain="drools-guvnor/org.drools.guvnor.Guvnor/oryxeditor" usr="admin" pwd="admin"/>
In our example
<externalloadurl protocol="http" host="192.168.140.39:8080" subdomain="drools-guvnor/org.drools.guvnor.Guvnor/oryxeditor" usr="admin" pwd="admin"/>
h4. b. Deploy designer
Simple by copy to jboss deployment directory, or with our example in Linux
# Set our GUVNOR_JBOSS to this example path
export GUVNOR_JBOSS=/opt/guvnor_jboss
cd $GUVNOR_JBOSS
# Deploy designer
cp designer.war standalone/deployments/
h4. c. Verify designer
Start jboss and verify that we have something like this
09:47:56,841 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "designer.war"
09:47:56,841 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "drools-guvnor.war"
https://community.jboss.org/servlet/JiveServlet/showImage/19266/Screensho... https://community.jboss.org/servlet/JiveServlet/downloadImage/19266/Scree...
Figure 02: Verify designer installation
User your browser to connect to http://GUVNOR_IP:8080/drools-guvnor http://GUVNOR_IP:8080/drools-guvnor (or http://192.168.140.39:8080/drools-guvnor http://192.168.140.39:8080/drools-guvnor in our example), on Left side bar, select "Knowledge Base" \ "Packages" , then select "Create New" \ "New BPMN2 Process" as Figure 02 above, note that if you can create/edit and save your process.
h3. Step 4.6: Deploy form-builder
h4. a. Add users/roles configuration to GUVNOR_JBOSS
# Set our GUVNOR_JBOSS to this example path
export GUVNOR_JBOSS=/opt/guvnor_jboss
cd $GUVNOR_JBOSS
cp users.properties standalone/configuration/
cp roles.properties standalone/configuration/
h4. b. Add security domain for jbpm-form-builder in file standalone/configuration/standalone.xml
<subsystem xmlns="urn:jboss:domain:security:1.0">
<security-domains>
..
<security-domain name="jbpm-form-builder" cache-type="default">
<authentication>
<login-module code="UsersRoles" flag="required">
<module-option name="usersProperties" value="${jboss.server.config.dir}/users.properties"/>
<module-option name="rolesProperties" value="${jboss.server.config.dir}/roles.properties"/>
</login-module>
</authentication>
</security-domain>
..
</security-domains>
</subsystem>
h4. c. Add users/roles to jbpm-form-builder.war/WEB-INF/classes
Using your current Archive Manager to add users.properties and roles.properties to jbpm-form-builder.war/WEB-INF/classes
h4. d. Deploy form-builder and verify like we already did with designer
cp jbpm-form-builder.war standalone/deployments/
# Start GUVNOR_JBOSS
bin/standalone.sh
h4. e. Verify that you have
10:36:52,907 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "drools-guvnor.war"
And use your browser to verify that http://GUVNOR_IP:8080/jbpm-form-builder http://GUVNOR_IP:8080/jbpm-form-builder ( http://192.168.140.39:8080/jbpm-form-builder http://192.168.140.39:8080/jbpm-form-builder) works.
h2. 5. Task-Service or Human Task deployment (with verify).
Login to server on HUMAN_TASK_IP and place a copy of jbpm-install and start the installation:
h3. Step 5.1:Extract a clean copy of jboss-as-7.0.2.Final.zip to HUMAN_TASK_JBOSS
# Set our HUMAN_TASK_JBOSS to this example path
export HUMAN_TASK_JBOSS=/opt/human_task_jboss
echo $HUMAN_TASK_JBOSS
# Go to JBPM_INSTALL directory
cd /opt/download/
unzip jbpm-5.3.0.Final-installer-full.zip
cd /opt/download/jbpm-installer
# Extract a clean copy of jboss application server. To move to /opt we need root permission.
unzip lib/jboss-as-7.0.2.Final.zip
sudo mv jboss-as-7.0.2.Final $HUMAN_TASK_JBOSS
# And jbpm transactin manager library
cp jbpm-tm.jar $HUMAN_TASK_JBOSS/
# MySQL module configuration
cp db/driver_jar_module.xml $HUMAN_TASK_JBOSS/module.xml
cd $HUMAN_TASK_JBOSS
h3. Step 5.2: Copy your custom build human-task
>From JBPM_SOURCE/jbpm-human-task/jbpm-human-task-war/target
To $HUMAN_TASK_JBOSS/jbpm-human-task-war.war
h3. Step 5.3: Jboss standalone.xml configuration
Change HUMAN_TASK_JBOSS/standalone/configuration/standalone.xml as following
h4. a. Remove pojo module
<extension module="org.jboss.as.osgi"/>
<!-- Remove this line extension module="org.jboss.as.pojo"/-->
<extension module="org.jboss.as.remoting"/>
And
<subsystem xmlns="urn:jboss:domain:naming:1.0" />
<!--subsystem xmlns="urn:jboss:domain:pojo:1.0" /-->
<subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="lazy">
h4. b. Change port for management interface.
<management-interfaces>
<native-interface interface="management" port="10099" />
<http-interface interface="management" port="10090"/>
</management-interfaces>
h4. c. Add datasource for task-service
<subsystem xmlns="urn:jboss:domain:datasources:1.0">
<datasources>
<datasource jndi-name="java:jboss/datasources/taskDS" pool-name="MysqlTaskDSPool" enabled="true" jta="true" use-java-context="true" use-ccm="true">
<connection-url>
jdbc:mysql://192.168.140.39:3306/task
</connection-url>
<driver>
mysql
</driver>
<pool>
<prefill>
false
</prefill>
<use-strict-min>
false
</use-strict-min>
<flush-strategy>
FailingConnectionOnly
</flush-strategy>
</pool>
<security>
<user-name>
task
</user-name>
<password>
taskpassword
</password>
</security>
</datasource>
<drivers>
<driver name="mysql" module="com.mysql">
<xa-datasource-class>
com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
</xa-datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
h4. d. Bind to HUMAN_TASK_IP. For example
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:192.168.140.39}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:192.168.140.39}"/>
</interface>
</interfaces>
h4. e. Set offset-port
For our example to running on the same server as in https://community.jboss.org/docs/DOC-16705 https://community.jboss.org/wiki/MultipleInstancesOfJBossAS7OnTheSameMachine (Approach#1)
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="100">
h3. Step 5.4: MySQL driver for jboss
h4. a. Create MySQL module directory
mkdir modules/com/mysql
mkdir modules/com/mysql/main
h4. b.Copy module declaration file
cp module.xml modules/com/mysql/main/
h4. c. Download and install mysql driver to jBoss
wget https://repository.jboss.org/nexus/service/local/repositories/central/con...
cp mysql-connector-java-5.1.18.jar modules/com/mysql/main/mysql-connector-java.jar
h4. d. Start your HUMAN_TASK_JBOSS now
bin/standalone.sh
To verify your configuration
* Does it start Ok?
* MySQL driver loaded?
* Can you see taskDS datasource on jBoss admin console at http://HUMAN_TASK_IP:10099/ http://HUMAN_TASK_IP:10090/ (In our example http://192.168.140.39:10090/)?
https://community.jboss.org/servlet/JiveServlet/showImage/19269/human_tas... https://community.jboss.org/servlet/JiveServlet/downloadImage/19269/human... Figure 03: Veriry DataSource configuration of HUMAN_TASK_JBOSS
h3. Step 5.4: jbpm-human-task.war configuration (//TODO)
h4. a. Update HUMAN_TASK_JBOSS
h4. b. Place a copy of HUMAN_TASK_JBOSS
h2. 6. jBPM-Console deployment (with verify).
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-21179]
Create a new document in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 2 months
- 1
- 0
[JBoss Tools] - JBoss Server Full publish - WeldPhaseListener cannot be cast to PhaseListener
by dasago
dasago [https://community.jboss.org/people/dasago] created the discussion
"JBoss Server Full publish - WeldPhaseListener cannot be cast to PhaseListener"
To view the discussion, visit: https://community.jboss.org/message/755032#755032
--------------------------------------------------------------
Hello,
if I make a full publish in JBoss 6 Server i get the exception below.
I use Eclipse Helios and jdk 1.6.24. I think i configured sth. wrong. What i have to do?
10:17:03,590 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/test-webapp
10:17:04,028 INFO [javax.enterprise.resource.webcontainer.jsf.config] Mojarra 2.1.10 (-SNAPSHOT 20120625-1354) für Kontext '/test-webapp' wird initialisiert.
10:17:16,278 SCHWERWIEGEND [javax.enterprise.resource.webcontainer.jsf.config] Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! org.jboss.weld.jsf.WeldPhaseListener cannot be cast to javax.faces.event.PhaseListener
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:377) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225) [:2.1.10-SNAPSHOT]
at org.jboss.web.jsf.integration.config.JBossMojarraConfigureListener.contextInitialized(JBossMojarraConfigureListener.java:58) [:1.0.3]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3369) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3828) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA]
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA]
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA]
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA]
at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.GA]
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2.2.0.GA]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_24]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: java.lang.ClassCastException: org.jboss.weld.jsf.WeldPhaseListener cannot be cast to javax.faces.event.PhaseListener
at com.sun.faces.config.processor.LifecycleConfigProcessor.addPhaseListeners(LifecycleConfigProcessor.java:148) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:111) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:222) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:362) [:2.1.10-SNAPSHOT]
... 60 more
10:17:16,313 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/test-webapp]] Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossMojarra20ConfigureListener: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! org.jboss.weld.jsf.WeldPhaseListener cannot be cast to javax.faces.event.PhaseListener
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:292) [:2.1.10-SNAPSHOT]
at org.jboss.web.jsf.integration.config.JBossMojarraConfigureListener.contextInitialized(JBossMojarraConfigureListener.java:58) [:1.0.3]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3369) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3828) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA]
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA]
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA]
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA]
at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.GA]
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2.2.0.GA]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_24]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! org.jboss.weld.jsf.WeldPhaseListener cannot be cast to javax.faces.event.PhaseListener
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:377) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225) [:2.1.10-SNAPSHOT]
... 59 more
Caused by: java.lang.ClassCastException: org.jboss.weld.jsf.WeldPhaseListener cannot be cast to javax.faces.event.PhaseListener
at com.sun.faces.config.processor.LifecycleConfigProcessor.addPhaseListeners(LifecycleConfigProcessor.java:148) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:111) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:222) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:362) [:2.1.10-SNAPSHOT]
... 60 more
10:17:16,329 ERROR [org.apache.catalina.core.StandardContext] Error listenerStart
10:17:16,329 ERROR [org.apache.catalina.core.StandardContext] Context [/test-webapp] startup failed due to previous errors
10:17:16,340 SCHWERWIEGEND [javax.faces] Die Anwendung wurde bei Systemstart nicht einwandfrei initialisiert, Factory konnte nicht gefunden werden: javax.faces.application.ApplicationFactory. Rügriff versucht.
10:17:16,341 SCHWERWIEGEND [javax.enterprise.resource.webcontainer.jsf.config] Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.IllegalStateException: Kein Rügriff für javax.faces.application.ApplicationFactory gefunden.
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:1011) [:2.1.10-SNAPSHOT]
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:343) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:131) [:2.1.10-SNAPSHOT]
at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:328) [:2.1.10-SNAPSHOT]
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3466) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3975) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3895) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA]
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA]
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA]
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA]
at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.GA]
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2.2.0.GA]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_24]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
10:17:16,348 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.web.deployment:war=/test-webapp state=Create mode=Manual requiredState=Installed: org.jboss.deployers.spi.DeploymentException: URL file:/D:/Dev/Workspaces/dragon/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1343827371884/deploy/test-webapp.war/ deployment failed
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:325) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA]
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA]
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA]
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA]
at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.GA]
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2.2.0.GA]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_24]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
10:17:16,363 WARN [org.jboss.profileservice.deployment.hotdeploy.HDScanner] Scan failed: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS IN ERROR:
Deployment "jboss.web.deployment:war=/test-webapp" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/D:/Dev/Workspaces/dragon/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1343827371884/deploy/test-webapp.war/ deployment failed
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:82) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.checkComplete(ProfileControllerContext.java:138) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:246) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_24]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755032#755032]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 2 months
- 1
- 0
Re: [jboss-user] [jBPM] - jBPM-5.3.0.Final Manual Deployment Guide for Beginner
by quangtin3
quangtin3 [https://community.jboss.org/people/quangtin3] commented on the document
"jBPM-5.3.0.Final Manual Deployment Guide for Beginner"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-21179#comment-10531
--------------------------------------------------
Dear Mauricio Salatino,
Sorry, I don't know why and how I put a copy of entire article in a reply. I did try to empty it, but didn't work. Please help me to delete above reply and this one too.
Thanks,
- Quang.
--------------------------------------------------
12 years, 2 months
- 1
- 0