[jBPM] New message: "Re: Unable to set the mail configuration properties in JBPM 4.0"
by Anand Kumar
User development,
A new message was posted in the thread "Unable to set the mail configuration properties in JBPM 4.0":
http://community.jboss.org/message/521043#521043
Author : Anand Kumar
Profile : http://community.jboss.org/people/akstifr
Message:
--------------------------------------------------------------
And after number of trials with the configuration files, war files, jar files,soon i could thought of it for sending mail from my application i have do it.
Finally i am *able to send the mail* from my application to any email id as specified in it.
the solution for the previous error is that it was missing *from address* in the *xxx.jpdl.xml* file in mail tag i.e i have added to it as under
*<mail g="199,118,126,60" name="Send_approval_email">*
** ** *<from addresses="mailto:yyyyyyyyyy@tifr.res.in"/>*
** *<to addresses="mailto:xxxxxxxx@gmail.com"/>*
** *<subject>Test Mail</subject>*
** *<text>Reason:This is a test mail from JBPM application that we are working on...</text>*
* * ** *<transition g="-42,-18" name="reject" to="end"/>*
** ** *</mail>*
Finally it got working it....
Thank you Ronald for your commitment to help users towards JBPM and its development
Hoping to do more research in JBPM in comming days
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521043#521043
16 years, 3 months
[jBPM] New message: "Re: Obtaining all available transitions for a <wait state> node?"
by Ronald van Kuijk
User development,
A new message was posted in the thread "Obtaining all available transitions for a <wait state> node?":
http://community.jboss.org/message/521041#521041
Author : Ronald van Kuijk
Profile : http://community.jboss.org/people/kukeltje
Message:
--------------------------------------------------------------
Can you confirm it does not work (properly)?
And what is the exact usecase? Just the fact that there is something for tasks does not automatically mean there should be something for other nodes as well. Maybe modelling your process differently (on a technical level, not functional one) solves it to...
E.g. returning a value from an external system and having conditions on the transitions or just one transition and a decision can help instead of having an external system have knowledge of which transitions there are and signalling with an explicit transition..
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521041#521041
16 years, 3 months
[jBPM] New message: "Re: Unable to set the mail configuration properties in JBPM 4.0"
by Anand Kumar
User development,
A new message was posted in the thread "Unable to set the mail configuration properties in JBPM 4.0":
http://community.jboss.org/message/521030#521030
Author : Anand Kumar
Profile : http://community.jboss.org/people/akstifr
Message:
--------------------------------------------------------------
Thank you for your reply Ronald for the problem.
The *jbpm.mail.properties* file is EXACTELY in the same location as the *jbpm.hibernate.xml* file
I have tried to use a different name in the *jbpm.cfg.xml* to reference my specific properties file but it did not work it out still.
Later i tried to modify the configurations files of jbpm and jboss manually and it seems to be working a little bit at present i.e it is getting connected to mailserver as per properties file but it is raising an exception like
16:17:30,734 INFO [STDOUT] 220 mailhost.tifr.res.in ESMTP Postfix (2.2.10)
16:17:30,734 INFO [STDOUT] DEBUG SMTP: connected to host "mailhost.tifr.res.in", port: 25
16:17:30,734 INFO [STDOUT] EHLO anand
.........
........
16:17:30,781 INFO [STDOUT] DEBUG SMTP: Found extension "PIPELINING", arg ""
16:17:30,781 INFO [STDOUT] DEBUG SMTP: Found extension "SIZE", arg "20480000"
16:17:30,781 INFO [STDOUT] DEBUG SMTP: Found extension "VRFY", arg ""
16:17:30,781 INFO [STDOUT] DEBUG SMTP: Found extension "ETRN", arg ""
16:17:30,781 INFO [STDOUT]DEBUG SMTP: Found extension "8BITMIME", arg ""
16:17:30,781 INFO [STDOUT] DEBUG SMTP: use8bit false
16:17:30,781 INFO [STDOUT] javax.mail.MessagingException: can't determine local email address
16:17:30,781 INFO [STDOUT] at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:906)
16:17:30,781 INFO [STDOUT] at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.email.impl.MailSessionImpl.send(MailSessionImpl.java:51)
16:17:30,781 INFO [STDOUT] at org.jbpm.jpdl.internal.activity.MailActivity.perform(MailActivity.java:44)
16:17:30,781 INFO [STDOUT] at org.jbpm.jpdl.internal.activity.JpdlAutomaticActivity.execute(JpdlAutomaticActivity.java:15)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.model.op.ExecuteActivity.perform(ExecuteActivity.java:60)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:637)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperation(ExecutionImpl.java:597)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.model.ExecutionImpl.start(ExecutionImpl.java:201)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:64)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:37)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
16:17:30,781 INFO [STDOUT] at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.startProcessInstanceByKey(ExecutionServiceImpl.java:66)
16:17:30,781 INFO [STDOUT] at com.LeaveController.startNewProcessInstance(LeaveController.java:35)
16:17:30,781 INFO [STDOUT] at com.Leave.doPost(Leave.java:56)
16:17:30,781 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
16:17:30,781 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
16:17:30,781 INFO [STDOUT] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
16:17:30,781 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
16:17:30,781 INFO [STDOUT] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
16:17:30,781 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
16:17:30,781 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
16:17:30,781 INFO [STDOUT] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
16:17:30,781 INFO [STDOUT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
16:17:30,781 INFO [STDOUT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
16:17:30,781 INFO [STDOUT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
16:17:30,781 INFO [STDOUT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
16:17:30,781 INFO [STDOUT] at java.lang.Thread.run(Unknown Source)
16:17:30,781 INFO [STDOUT] QUIT
16:17:30,812 INFO [STDOUT] 221 Bye
16:17:30,828 INFO [DefaultCommandService] exception while executing command org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd@1908140
org.jbpm.api.JbpmException: could not send email: javax.mail.internet.MimeMessage@1947e20
at org.jbpm.pvm.internal.email.impl.MailSessionImpl.send(MailSessionImpl.java:60)
at org.jbpm.jpdl.internal.activity.MailActivity.perform(MailActivity.java:44)
at org.jbpm.jpdl.internal.activity.JpdlAutomaticActivity.execute(JpdlAutomaticActivity.java:15)
at org.jbpm.pvm.internal.model.op.ExecuteActivity.perform(ExecuteActivity.java:60)
at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:637)
at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperation(ExecutionImpl.java:597)
at org.jbpm.pvm.internal.model.ExecutionImpl.start(ExecutionImpl.java:201)
at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:64)
at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:37)
at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.startProcessInstanceByKey(ExecutionServiceImpl.java:66)
at com.LeaveController.startNewProcessInstance(LeaveController.java:35)
at com.Leave.doPost(Leave.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.mail.MessagingException: can't determine local email address
at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:906)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
at org.jbpm.pvm.internal.email.impl.MailSessionImpl.send(MailSessionImpl.java:51)
... 37 more
16:17:30,828 INFO [STDOUT] could not send email: javax.mail.internet.MimeMessage@1947e20
but still unable to send the mail from it....
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521030#521030
16 years, 3 months
[JBoss Tools] Document updated/added: "DevStudioReleaseProcess"
by Max Andersen
User development,
The document "DevStudioReleaseProcess", was updated Jan 20, 2010
by Max Andersen.
To view the document, visit:
http://community.jboss.org/docs/DOC-9570#cf
Document:
--------------------------------------------------------------
h3. JBoss Developer Studio and JBossTools Release Process
-
----
Prereqs for using this build
1. Install infozip
2. Have write access to download.jboss.org/jbosstools
3. Have file release permissions on sourceforge.net
-
----
1. Each component's repository must be tagged for release. Generally, we do a wide-sweeping tag for the entire jbosstools repository, while a few components (namely jBPM) have their own repositories and tags. You can easily tag a release by using the "make_tags.sh" script in releng's util directory.
TAG=jbosstools-2.1.2.GA BRANCH=branches/jbosstools-2.1.x ./make_tags.sh
0.1.
0.2. JBossIDE Core: IDE_CORE_RELEASENAME
0.3. JBossAOP Developer: IDE_AOP_DEVELOPER_RELEASENAME
0.4. EJB3 Tools: IDE_EJB3_TOOLS_RELEASENAME
0.5. Hibernate Tools: TOOLS_RELEASENAME
0.6. jBPM Designer: jbpm_gpd_releasename
2. After tagging is complete, an integration build is made on those tags.
3. Checkout the build system for JBossIDE
3.1. cvs co jbosside/releng/org.jboss.ide.eclipse.releng
5. From directory releng/org.jboss.ide.eclipse.releng execute the following:
5.1. ant -f customizeBuild.xml
7. This will launch a gui
7.1. Create temp dirs for the appropriate locations
7.2. You may need to execute 'ant -f customizeBuild.xml customize' to create a build.properties file.
9. Create a tags file, RELEASENAME.tag in the folder builders/product/versionTags
9.1. You can see an example tags file from the 1.5.1.GA release http://fisheye.jboss.com/viewrep/JBoss/jbosside/releng/org.jboss.ide.ecli...
9.2. You will need to know the sub version for each component.
9.3. The integration build is ran using this command in the builders directory of JBossIDE releng:
9.3.1. cd releng/org.jboss.ide.releng/builders
9.3.2. ./build-integration.sh product -tags tagsfile
9.3.3. See more info at the [JBossIDE Releng System
Docs|http://docs.jboss.com/jbosside/releng/user/build/en/html/index.html]
0.0.1. example: ./build-integration.sh product -tags product/versionTags/1.5.2.GA.tags
0.2. You will need to expand the eclipse-SDK which is downloaded into a an additional dir which you specify
0.3. Also, may need to modify global.properties updating as follows:
0.3.1. pdescriptdir=${clean.eclipse.home}/plugins/org.eclipse.pde.build_3.1.2/scripts
0.5. If the integration build breaks on compilation, the component lead responsible is notified and they re-tag their repository. We then re-initiate the integration build
2. Once the integration build is complete, each component lead is notified of the build and is responsible for doing any tests to their satisfaction on that build. (Note that this is usually outside the scope of unit tests).
2.1. If there are any fatal bugs / problems in the integration build, we give the responsible component leader time to fix those bugs, and re-start the process.
2.2. Once we receive the "thumbs-up" from all component leads, it's time to make a release build.
4. At this point, the tags file should be committed to Releng cvs.
5. If the release is "stable" (i.e. non beta/RC/etc) then you will run this command in the builders directory:
5.1. ./build-release.sh product stable RELEASENAME
7. Otherwise if the release is "development" (beta/RC/etc) then you will run this command:
7.1. ./build-release.sh product development RELEASENAME
9. The component leads are given a final chance to go over the release build before it will be published.
9.1. If there are any complaints, restart the process with the integration build
9.2. If all component leads give "thumbs-up", then it's time to upload and announce.
11. I first start by uploading all of the release files to sourceforge. Depending on the connection this can easily take a few hours. I have an ant script that automates this process for me that I've attached to this wiki. It's syntax is ./sf_upload.sh RELEASENAME (it probably needs to be changed to work on other systems)
12. While the files are uploading, I create the release in Sourceforge, and call it JBossIDE RELEASENAME.
13. I collect and enter the Changelog/ReleaseNotes from JIRA and various notes given to me from component leads.
14. After the files are done uploading, I add all of the appropriate files into the release, and describe them correctly using SF's interface (MD5 files get "Other", zips get ".zip", .tar.gz gets ".gz")
15. Now the only thing left to do is update the product download page and announce on the forums.
16. The "old" newest release is removed and replaced by the "new" newest release, including links to Sourceforge etc.
17. Release announcement is made on the JBossIDE http://jboss.com/index.html?module=bb&op=viewforum&f=201 and http://jboss.com/index.html?module=bb&op=viewforum&f=162. You can find an example announcement http://jboss.com/index.html?module=bb&op=viewtopic&t=78678
18. After the announcement is made, all of the people watching on Sourceforge are notified.
--------------------------------------------------------------
16 years, 3 months
[EJB 3.0] New message: "Problem configuring MDB to use HA JNDI"
by srinivaas venkat
User development,
A new message was posted in the thread "Problem configuring MDB to use HA JNDI":
http://community.jboss.org/message/521013#521013
Author : srinivaas venkat
Profile : http://community.jboss.org/people/sv_srinivaas
Message:
--------------------------------------------------------------
Hi, I'm unable to configure MDBs to use HA JNDI.
Environment details: Jboss 5.1.0, EJB3, HornetQ 2.0.0.GA
I'm new to EJB and not sure how to configure MDBs to use HA JNDI in JBoss. I've gone through the JBoss AS documentation on HA JNDI in this URL http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Cl...
but still not sure where to make the changes for my MDB to use HA JNDI.,
This is ouur application setup. We have a cluster of two queue nodes A and B. MDB is deployed in node C which is not part of the cluster.
Currently MDB is configured using JCA (ra.xml) to consume messages from node A and everything works fine as expected.
Issue is when the, node A goes down, MDB does not pick messages from nodeB and I read that HA JNDI is the solution for this issue.
Pls help me in configuring MDBs to use HA JNDI so that it can pick messages from any of active nodes in the queue cluster. I'd like to know which XMLs i need to change or if there is any sample code available elsewhere.
Thanks
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521013#521013
16 years, 3 months