[JBoss jBPM] - Building from source
by onizuka82
Hi everyone,
I am facing problem when try to build from the source.
1. I use Eclipse to import the jbpm.3 and build class path to the repository.
2. When i run ant build in jbpm.3 \build folder, error occured.
The error message is a bit shorter than the orginal. I couldnt paste all in here as it will be too long.
Error message from the eclipse console
===================================================================
BUILD FAILED
C:\workspace\source\jbpm.3\build\build.xml:54: The following error occurred while executing this line:
C:\workspace\source\jbpm.3\jboss\db\build.xml:38: java.io.FileNotFoundException: JAR entry org/jbpm/ant/jbpm.ant.tasks.properties not found in C:\workspace\source\jbpm.3\jpdl\jar\target\jbpm-jpdl.jar
Total time: 1 minute 48 seconds
===================================================================
3. So i try to use the Ant to build it again without closing the eclipse but another error message show.
Error message from the eclipse console
===================================================================
check.project.dirs:
checkout.docs:
[cvs] Caught exception: CreateProcess: cvs -d:pserver:anonymous:@anoncvs.forge.jboss.com:/cvsroot/jbpm checkout -d C:\workspace\source\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build/target/projects/org.jbpm.gd.jpdl.docs -r jbpm_gpd_3_0_12_1 jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.docs error=2
checkout.site:
[cvs] Caught exception: CreateProcess: cvs -d:pserver:anonymous:@anoncvs.forge.jboss.com:/cvsroot/jbpm checkout -d C:\workspace\source\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build/target/projects/org.jbpm.gd.jpdl.site -r jbpm_gpd_3_0_12_1 jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.site error=2
checkout.feature:
[cvs] Caught exception: CreateProcess: cvs -d:pserver:anonymous:@anoncvs.forge.jboss.com:/cvsroot/jbpm checkout -d C:\workspace\source\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build/target/projects/org.jbpm.gd.jpdl.feature -r jbpm_gpd_3_0_12_1 jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.feature error=2
checkout.help:
[cvs] Caught exception: CreateProcess: cvs -d:pserver:anonymous:@anoncvs.forge.jboss.com:/cvsroot/jbpm checkout -d C:\workspace\source\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build/target/projects/org.jbpm.gd.jpdl.help -r jbpm_gpd_3_0_12_1 jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.help error=2
checkout.ui:
[cvs] Caught exception: CreateProcess: cvs -d:pserver:anonymous:@anoncvs.forge.jboss.com:/cvsroot/jbpm checkout -d C:\workspace\source\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build/target/projects/org.jbpm.gd.jpdl.ui -r jbpm_gpd_3_0_12_1 jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.ui error=2
checkout.core:
[cvs] Caught exception: CreateProcess: cvs -d:pserver:anonymous:@anoncvs.forge.jboss.com:/cvsroot/jbpm checkout -d C:\workspace\source\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build/target/projects/org.jbpm.gd.jpdl.core -r jbpm_gpd_3_0_12_1 jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.core error=2
get.projects:
all:
install.eclipse:
[delete] Deleting directory C:\eclipse
BUILD FAILED
C:\workspace\source\jbpm.3\build\build.xml:56: The following error occurred while executing this line:
C:\workspace\source\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\build.xml:57: The following error occurred while executing this line:
C:\workspace\source\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\build.xml:73: Unable to delete file C:\eclipse\configuration\org.eclipse.core.runtime\.extraData.7
Total time: 2 minutes 28 seconds
=====================================================================
4. After this error, i coudlnt open the eclipse again. The whole eclipse crashed.
Error message from the Eclipse log
=====================================================================
!MESSAGE Missing required bundle org.eclipse.ui.editors_0.0.0.
!SUBENTRY 2 org.jbpm.gd.jpdl.ui 2 0 2006-12-22 15:10:01.979
!MESSAGE Missing required bundle org.eclipse.ui.forms_0.0.0.
!SUBENTRY 2 org.jbpm.gd.jpdl.ui 2 0 2006-12-22 15:10:01.979
!MESSAGE Missing required bundle org.eclipse.jface.text_0.0.0.
!SUBENTRY 2 org.jbpm.gd.jpdl.ui 2 0 2006-12-22 15:10:01.979
!MESSAGE Missing required bundle org.eclipse.wst.common.ui_0.0.0.
!SUBENTRY 2 org.jbpm.gd.jpdl.ui 2 0 2006-12-22 15:10:01.979
!MESSAGE Missing required bundle org.eclipse.jdt.debug.ui_0.0.0.
!SUBENTRY 2 org.jbpm.gd.jpdl.ui 2 0 2006-12-22 15:10:01.979
!MESSAGE Missing required bundle org.eclipse.debug.core_0.0.0.
!SUBENTRY 2 org.jbpm.gd.jpdl.ui 2 0 2006-12-22 15:10:01.979
!MESSAGE Missing required bundle org.eclipse.core.variables_0.0.0.
====================================================================
Can anyone please tell me what is the problem behind this or provide any guide on how to overcome this.
Thank you.
Warmest regards,
Andrew
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990904#3990904
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990904
18 years, 1 month
[JBoss Seam] - Re: Excessive [could not destroy component] 1.1B1 to 1.1CR1
by lowecg2004
I had created this quick setup guide for our developers based on the information in this thread:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=93589
I hope this helps you out.
Chris.
There are a few important timeout values in the Seam environment that any Seam developer needs to be aware of.
The first one is obvious and it is the well known HTTP session-timeout value (the one that you set in web.xml). What catches most people out is that there also is a separate EJB3 SFSB timeout value. These SFSB timeout values must be set in 2 places.
Since Seam freely integrates these two environments, a difference in the two timeouts can cause apparently random exceptions like:
19:23:07,124 WARN [Contexts] Could not destroy component: login
| javax.ejb.EJBNoSuchObjectException: Could not find Stateful bean: 5r4m5v-man6m0-etofwmzy-1-etog131z-
| g
| at org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:268)
| at org.jboss.ejb3.stateful.StatefulRemoveInterceptor.removeSession(StatefulRemoveInterceptor
| .java:127)
| at org.jboss.ejb3.stateful.StatefulRemoveInterceptor.invoke(StatefulRemoveInterceptor.java:8
| 7)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.jav
| a:77)
| ...
It is worth mentioning that there is a @CacheConfig annotation that allows you to specify the SFSB timeout on a per class basis. This offers a fine grained level of control, however you often just need to set the value once and have done with it. So in order to align the HTTP session and the SFSB timeouts, you must amend configuration files. Also note that this example sets these values to be exactly the same. It is sometimes recommended that the SFSB timeouts are set to be longer than the HTTP session timeout.
1. HTTP Session Timeout
File: WEB-INF/web.xml
<session-config>
| <session-timeout>15</session-timeout>
| </session-config>
Note: Value is in minutes;
2. SFSB Timeout Part 1
File: PROJECT_HOME/embedded-ejb/conf/ejb3-interceptors-aop.xml
Find entry matching 'domain name="Stateful Bean" extends="Base Stateful Bean" inheritBindings="true">':
<domain name="Stateful Bean" extends="Base Stateful Bean" inheritBindings="true">
| ...
| <!-- OCSS: Align this value with session timeout in web.xml -->
| <annotation expr="!class((a)org.jboss.annotation.ejb.cache.simple.CacheConfig) AND !class((a)org.jboss.annotation.ejb.Clustered)">
| @org.jboss.annotation.ejb.cache.simple.CacheConfig (maxSize=100000, idleTimeoutSeconds=900)
| </annotation>
Set the idleTimeoutSeconds value.
Note: Value is in seconds;
3. SFSB Timeout Part 2
File: JBOSS_HOME\server\default\conf\standardjboss.xml
Find entry for '<container-name>Standard Stateful SessionBean</container-name>':
| <container-configuration>
| <container-name>Standard Stateful SessionBean</container-name>
| ...
| <container-cache-conf>
| ...
| <cache-policy-conf>
| <remover-period>900</remover-period>
| <max-bean-life>900</max-bean-life>
| ...
Note: Value is in seconds; Also this config is required for every server that the Seam code is deployed to.
That is all. Aligning these three timeout values will prevent those "Could not destroy component: XXXX" exceptions and prevent some strange behaviour in your apps.
Further information and discussion, see the thread referenced at the start of this post.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990903#3990903
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990903
18 years, 1 month