[JBoss JIRA] Created: (JBMESSAGING-1137) Specifying Destination Paging Parameters in Megabytes
by Tyronne Wickramarathne (JIRA)
Specifying Destination Paging Parameters in Megabytes
-----------------------------------------------------
Key: JBMESSAGING-1137
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1137
Project: JBoss Messaging
Issue Type: Feature Request
Components: Configuration and Management
Affects Versions: 1.4.0.SP1
Environment: JBoss-4.2.1-GA -Xms1024m -Xmx1024m , JBM-1.4.0-SP1, Linux 2.6.22.1-41.fc7,i386
Reporter: Tyronne Wickramarathne
Assigned To: Tim Fox
a mechanism is required to configure the destination paging parameters, preferably in megabytes. IOW, the amount of memory to be used by the JBM for paging requires to be set in megabytes instead of specifying it by the number of messages.
at present, this is done via configuring the destination paging parameters by setting the number of messages for each destination (FullSize, PageSize, DownCacheSize) . but when you start receiving messages with varying sizes (1k, 10k 200k ), you can't have a control over the memory it requires to house those messages (message cache). with JBossMQ, you can configure the upper and lower limit values for the message cache. an approach is required to accommodate this feature in JBM.
--
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
16 years
[JBoss JIRA] Created: (JBRULES-1119) "ExpanderResolver was not set" when DSL and DRL in separate resource folders.
by Davy Toch (JIRA)
"ExpanderResolver was not set" when DSL and DRL in separate resource folders.
-----------------------------------------------------------------------------
Key: JBRULES-1119
URL: http://jira.jboss.com/jira/browse/JBRULES-1119
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Affects Versions: 3.0.5
Environment: - Eclipse 3.2.1
- WinXP
Reporter: Davy Toch
Assigned To: Mark Proctor
Priority: Minor
Attachments: jbossrulesproject_one_resource_folder.zip, jbossrulesproject_two_resource_folders.zip
1. jbossrulesproject_one_resource_folder.zip
- DRL and DSL in one resource folder
- no problem
2. jbossrulesproject_two_resource_folders.zip
- DRL and DSL in separate resource folders
- causes error message : "ExpanderResolver was not set"
We actually prefer two separate resource folders, because the rules are generated during the ANT
build from the decision tables (so in target/...), while the DSL isn't automatically generated (so
in src/...).
--
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
16 years