[JBoss JIRA] Created: (JBESB-1057) Deployment descriptors are not copied to management.esb
by Martin Vecera (JIRA)
Deployment descriptors are not copied to management.esb
-------------------------------------------------------
Key: JBESB-1057
URL: http://jira.jboss.com/jira/browse/JBESB-1057
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tooling
Affects Versions: 4.2.1 IR1
Environment: Sun JVM, ant 1.6.5
Reporter: Martin Vecera
Assigned To: Mark Little
Deployment descriptors (product/tools/console/management-esb/{jboss-esb.xml, jboss-service.xml, deployment.xml}) are not copied to management.esb because product/tools/console/management-esb/build.xml is being ran with wrong ${basedir} from product/tools/console/build.xml. I would suggest replace the line 216 in product/tools/console/build.xml to be like:
<ant dir="${console.dir}/management-esb/" antfile="${console.dir}/management-esb/build.xml" target="esb">
This corrects the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBESB-905) Increase Permgen: -XX:MaxPermSize=128m
by Burr Sutter (JIRA)
Increase Permgen: -XX:MaxPermSize=128m
--------------------------------------
Key: JBESB-905
URL: http://jira.jboss.com/jira/browse/JBESB-905
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Critical
Fix For: 4.2
On windows, modify the run.bat that is created for the ESB Server so that it has a larger than average MaxPermSize
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:MaxPermSize=128m
Otherwise, you'll eventually run out of PermGen space while performing numerous hot deploys/undeploys. It is especially noticeable while working with the BPM capabilites which use a substantial amount of Hibernate which generates classes for data access (persistence of the in-flight process state).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months