[ http://jira.jboss.com/jira/browse/JBMESSAGING-153?page=comments#action_12... ]
lepe commented on JBMESSAGING-153:
----------------------------------
Will this be done in 2.0?
/L
Redpill
> Support for very large messages
> -------------------------------
>
> Key: JBMESSAGING-153
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-153
> Project: JBoss Messaging
> Issue Type: Feature Request
> Components: Messaging Core
> Affects Versions: 1.0.0 alpha PR3
> Reporter: Karl de Boer
> Fix For: 2.0.0 Beta
>
> Original Estimate: 4 minutes
> Remaining Estimate: 4 minutes
>
> As dicussed during JBW Barcelona i want to ask to investigate if it is posible to reliably sent very big messages from one jboss messaging node to another one (most likely on top of HTTPS(S). The business case is: mulitple organisations working in one workflow on digitally signed documents where Quality of Service is extremely important for instance patent applications.
--
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
Investigate potential issue with long lived consumer
----------------------------------------------------
Key: JBMESSAGING-1228
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1228
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.4.0.SP3
Reporter: Tim Fox
Assigned To: Tim Fox
Need to investigate reported user issue on forum.
--
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
update jboss-remoting to 2.2.2sp5 and update configuration
----------------------------------------------------------
Key: JBMESSAGING-1238
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1238
Project: JBoss Messaging
Issue Type: Task
Components: Build System, Configuration and Management
Reporter: Jeff Mesnil
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP02, Stable branch
once jboss-remoting 2.2.2sp5 is released, we have to include it into jboss messaging and update the configuration related to JBREM-888 by adding:
<attribute name="stopLeaseOnFailure" isParam="true">false</attribute>
to server/default/deploy/jboss-messaging.sar/remoting-bisocket-service.xml configuration file
--
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
README.html not displayed properly by firefox on linux
------------------------------------------------------
Key: JBMESSAGING-1204
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1204
Project: JBoss Messaging
Issue Type: Task
Components: Documentation and Training
Affects Versions: 1.4.0.SP3
Reporter: Daniel Bevenius
Assigned To: Tim Fox
Priority: Trivial
Attachments: README.html
The docs/README.html contains <servername> which is causing the rest of the page to be displayed incorrectly with firefox on linux.
Just escaping them with "<" and ">:" will do.
--
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
Create TemplateFactory to keep ManagedComponent and Template properties in sync
-------------------------------------------------------------------------------
Key: JBAS-5258
URL: http://jira.jboss.com/jira/browse/JBAS-5258
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Mark Spritzler
--
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
coyote.RequestMap not storing all request properties in the Map.Entry set
-------------------------------------------------------------------------
Key: JBREM-810
URL: http://jira.jboss.com/jira/browse/JBREM-810
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: transport
Affects Versions: 2.2.1.GA
Reporter: Tom Fennelly
Assigned To: Trustin Lee
Priority: Minor
Small thing, but the RequestMap overrides the get method for some of the request properties e.g. "Path" and "HttpVersion". This is fine if the code using the request Map (from InvocationRequest) accesses the properties via the get method. However, if it iterates over the Map.Entry set, these values will come back as null because they're not actually stored in the map entry set.
--
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
Hibernate/JBoss Cache locking issues seem to be occurring in the HA setup
-------------------------------------------------------------------------
Key: JBPORTAL-1702
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1702
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.6.1 Final, 2.6 Final
Reporter: Sohil Shah
Assigned To: Sohil Shah
When the Portal is run in a clustered environment, I have noticed some locking issues in the Hibernate Cache which is using JBoss Cache as the caching engine.
So far, the locks have been detected on the HibernateUserModuleImpl in the Identity Module
Steps to Reproduce:
1/ Start up both cluster nodes
2/ Login in to node1 with admin user
3/ Login in to node2 with admin user
4/ Logout of node1
5/ Try to Logout of node2, and you see locking errors on node2
--
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
Duration not rendering correctly
--------------------------------
Key: JBRULES-1496
URL: http://jira.jboss.com/jira/browse/JBRULES-1496
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Decision tables
Affects Versions: 4.0.4
Reporter: Michael Neale
Assigned To: Michael Neale
Fix For: 5.0.0-M1
--
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
RealNetworks Hibernate/JBoss Cache Locking Combined Patch
---------------------------------------------------------
Key: JBPORTAL-1942
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1942
Project: JBoss Portal
Issue Type: Support Patch
Security Level: Public (Everyone can see)
Components: Portal CMS, Portal Core
Affects Versions: 2.6.1 Final
Reporter: Mike Millson
Assigned To: Mike Millson
--
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
Kernel tests which include annotation overrides fail with AOP configuration
---------------------------------------------------------------------------
Key: JBMICROCONT-250
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-250
Project: JBoss MicroContainer
Issue Type: Bug
Components: AOP
Affects Versions: JBossMC-2.0.0.Beta10
Reporter: Ales Justin
Assigned To: Kabir Khan
Priority: Critical
Fix For: JBossMC-2.0.0.CR1
When running MicrocontainerAllTestCase in aop-mc-int, the tests that include annotation overrides fail.
It looks like the proxy that is created for the bean doesn't get populated, but the changes reflect on the proxy's delegate.
See forum post for more details.
--
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