[jira] [Created] (VYSPER-347) Support HBase as a Vysper storage

Bernd Fondermann created VYSPER-347: --- Summary: Support HBase as a Vysper storage Key: VYSPER-347 URL: https://issues.apache.org/jira/browse/VYSPER-347 Project: VYSPER Issue Type: New

[jira] [Resolved] (VYSPER-347) Support HBase as a Vysper storage

[ https://issues.apache.org/jira/browse/VYSPER-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-347. - Resolution: Fixed Fix Version/s: 0.8 Support HBase as a Vysper storage

[jira] [Resolved] (VYSPER-345) Move storage provider implementations to separate maven module

[ https://issues.apache.org/jira/browse/VYSPER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-345. - Resolution: Fixed Move storage provider implementations to separate maven module

[jira] [Assigned] (VYSPER-346) Domain comparisons should be case-insensitive

[ https://issues.apache.org/jira/browse/VYSPER-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-346: --- Assignee: Bernd Fondermann Domain comparisons should be case-insensitive

[jira] [Created] (VYSPER-345) Move storage provider implementations to separate maven module

Bernd Fondermann created VYSPER-345: --- Summary: Move storage provider implementations to separate maven module Key: VYSPER-345 URL: https://issues.apache.org/jira/browse/VYSPER-345 Project: VYSPER

[jira] [Resolved] (VYSPER-329) Server To Server inbound messages in jabber:server namespace, delivery fails

[ https://issues.apache.org/jira/browse/VYSPER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-329. - Resolution: Fixed Fix Version/s: 0.8 Server To Server inbound messages in

[jira] [Resolved] (VYSPER-344) Server-to-server not working for Vysper to Vysper

[ https://issues.apache.org/jira/browse/VYSPER-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-344. - Resolution: Fixed Fix Version/s: 0.8 Server-to-server not working for Vysper

[jira] [Assigned] (VYSPER-329) Server To Server inbound messages in jabber:server namespace, delivery fails

[ https://issues.apache.org/jira/browse/VYSPER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-329: --- Assignee: Bernd Fondermann Server To Server inbound messages in jabber:server

[jira] [Created] (VYSPER-344) Server-to-server not working for Vysper to Vysper

Bernd Fondermann created VYSPER-344: --- Summary: Server-to-server not working for Vysper to Vysper Key: VYSPER-344 URL: https://issues.apache.org/jira/browse/VYSPER-344 Project: VYSPER Issue

[jira] [Created] (VYSPER-343) Spring-based distribution: allow to enable federation (s2s)

Bernd Fondermann created VYSPER-343: --- Summary: Spring-based distribution: allow to enable federation (s2s) Key: VYSPER-343 URL: https://issues.apache.org/jira/browse/VYSPER-343 Project: VYSPER

[jira] [Resolved] (VYSPER-343) Spring-based distribution: allow to enable federation (s2s)

[ https://issues.apache.org/jira/browse/VYSPER-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-343. - Resolution: Fixed Spring-based distribution: allow to enable federation (s2s)

[jira] [Closed] (VYSPER-343) Spring-based distribution: allow to enable federation (s2s)

[ https://issues.apache.org/jira/browse/VYSPER-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann closed VYSPER-343. --- Spring-based distribution: allow to enable federation (s2s)

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685471#comment-13685471 ] Bernd Fondermann commented on VYSPER-342: - thanks for the issue + contribution is

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685484#comment-13685484 ] Bernd Fondermann commented on VYSPER-342: - is it? ok, what about my Commit:

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685486#comment-13685486 ] Bernd Fondermann commented on VYSPER-342: - what kind of performance issues? at

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685504#comment-13685504 ] Bernd Fondermann commented on VYSPER-342: - yep, I roughly know what synchronized

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685508#comment-13685508 ] Bernd Fondermann commented on VYSPER-342: - @Mikko: ok, got it now. I'm reinstating

[jira] [Resolved] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-342. - Resolution: Fixed Fix Version/s: 0.8 patch applied. thanks for contributing!

[jira] [Assigned] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-342: --- Assignee: Bernd Fondermann Access to UTF-8 encoding and decoding is not thread

[jira] [Resolved] (VYSPER-336) is the status change right?

[ https://issues.apache.org/jira/browse/VYSPER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-336. - Resolution: Fixed fixed the state change to 'interested' is the status

[jira] [Resolved] (VYSPER-341) nbxml exception parsing multiple numeric character references

[ https://issues.apache.org/jira/browse/VYSPER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-341. - Resolution: Fixed nbxml exception parsing multiple numeric character references

[jira] [Commented] (VYSPER-341) nbxml exception parsing multiple numeric character references

[ https://issues.apache.org/jira/browse/VYSPER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673398#comment-13673398 ] Bernd Fondermann commented on VYSPER-341: - applied patch by Gene McCulley from the

[jira] [Updated] (VYSPER-341) nbxml exception parsing multiple numeric character references

[ https://issues.apache.org/jira/browse/VYSPER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann updated VYSPER-341: Summary: nbxml exception parsing multiple numeric character references (was: nbxml

[jira] [Created] (VYSPER-341) nbxml exception pasring multiple numeric character references

Bernd Fondermann created VYSPER-341: --- Summary: nbxml exception pasring multiple numeric character references Key: VYSPER-341 URL: https://issues.apache.org/jira/browse/VYSPER-341 Project: VYSPER

[jira] [Assigned] (VYSPER-341) nbxml exception pasring multiple numeric character references

[ https://issues.apache.org/jira/browse/VYSPER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-341: --- Assignee: Bernd Fondermann nbxml exception pasring multiple numeric character

[jira] [Commented] (VYSPER-340) Problems Performing WebSocket Handshake

[ https://issues.apache.org/jira/browse/VYSPER-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588317#comment-13588317 ] Bernd Fondermann commented on VYSPER-340: - General note: Please ask questions on

[jira] [Comment Edited] (VYSPER-340) Problems Performing WebSocket Handshake

[ https://issues.apache.org/jira/browse/VYSPER-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588317#comment-13588317 ] Bernd Fondermann edited comment on VYSPER-340 at 2/27/13 1:24 PM:

[jira] [Assigned] (VYSPER-74) Use the given bind resource from the client (if provided)

[ https://issues.apache.org/jira/browse/VYSPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-74: -- Assignee: (was: Bernd Fondermann) Use the given bind resource from the client

[jira] [Commented] (VYSPER-74) Use the given bind resource from the client (if provided)

[ https://issues.apache.org/jira/browse/VYSPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13539919#comment-13539919 ] Bernd Fondermann commented on VYSPER-74: sure, but it makes it much more difficult

[jira] [Assigned] (VYSPER-337) Sequential processing of stanzas per StanzaRelay

[ https://issues.apache.org/jira/browse/VYSPER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-337: --- Assignee: Bernd Fondermann Sequential processing of stanzas per StanzaRelay

[jira] [Created] (VYSPER-337) Sequential processing of stanzas per StanzaRelay

Bernd Fondermann created VYSPER-337: --- Summary: Sequential processing of stanzas per StanzaRelay Key: VYSPER-337 URL: https://issues.apache.org/jira/browse/VYSPER-337 Project: VYSPER Issue

[jira] [Updated] (VYSPER-337) Sequential processing of stanzas per StanzaRelay

[ https://issues.apache.org/jira/browse/VYSPER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann updated VYSPER-337: Description: Currently, StanzaRelays typically act as a stage, in that they queue and

[jira] [Updated] (VYSPER-333) Presence probes not properly handled for multiple sessions

[ https://issues.apache.org/jira/browse/VYSPER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann updated VYSPER-333: Component/s: (was: stanza routing) core protocol Description:

[jira] [Commented] (VYSPER-333) presence message should bring the resource information of one user;

[ https://issues.apache.org/jira/browse/VYSPER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501788#comment-13501788 ] Bernd Fondermann commented on VYSPER-333: - RFC6121; 4.3. is specifying presence

[jira] [Commented] (VYSPER-333) presence message should bring the resource information of one user;

[ https://issues.apache.org/jira/browse/VYSPER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501798#comment-13501798 ] Bernd Fondermann commented on VYSPER-333: - And, after a quick test, I see full

[jira] [Resolved] (VYSPER-335) NullPointerException in DefaultResourceRegistry

[ https://issues.apache.org/jira/browse/VYSPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-335. - Resolution: Fixed Fix Version/s: 0.8 NullPointerException in

[jira] [Commented] (VYSPER-333) presence message should bring the resource information of one user;

[ https://issues.apache.org/jira/browse/VYSPER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501863#comment-13501863 ] Bernd Fondermann commented on VYSPER-333: - Thanks for your bug report, but you are

[jira] [Commented] (VYSPER-334) Plain.java doesn't decode correctly, error appears in multi-byte character;

[ https://issues.apache.org/jira/browse/VYSPER-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500906#comment-13500906 ] Bernd Fondermann commented on VYSPER-334: - good catch. fixed in r1411574

[jira] [Commented] (VYSPER-332) Memory Leak in BoshBackedSessionContext

[ https://issues.apache.org/jira/browse/VYSPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490159#comment-13490159 ] Bernd Fondermann commented on VYSPER-332: - Thanks Emmanuel, interesting. In

[jira] [Commented] (VYSPER-331) Add Retrieve/Revoke Items

[ https://issues.apache.org/jira/browse/VYSPER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490473#comment-13490473 ] Bernd Fondermann commented on VYSPER-331: - Some files in the patch are missing the

[jira] [Commented] (VYSPER-332) Memory Leak in BoshBackedSessionContext

[ https://issues.apache.org/jira/browse/VYSPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13489978#comment-13489978 ] Bernd Fondermann commented on VYSPER-332: - I think handling 700K messages with 350

[jira] [Commented] (VYSPER-332) Memory Leak in BoshBackedSessionContext

[ https://issues.apache.org/jira/browse/VYSPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13489305#comment-13489305 ] Bernd Fondermann commented on VYSPER-332: - BOSH has been heavily reworked in

[jira] [Commented] (VYSPER-332) Memory Leak in BoshBackedSessionContext

[ https://issues.apache.org/jira/browse/VYSPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13489655#comment-13489655 ] Bernd Fondermann commented on VYSPER-332: - If the client is gone, his session will

[jira] [Commented] (VYSPER-331) Add Retrieve/Revoke Items

[ https://issues.apache.org/jira/browse/VYSPER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487185#comment-13487185 ] Bernd Fondermann commented on VYSPER-331: - Thanks for the patch. I think

[jira] [Created] (VYSPER-330) RequestWindow assumes PriorityQueue.iterator() is ordered

Bernd Fondermann created VYSPER-330: --- Summary: RequestWindow assumes PriorityQueue.iterator() is ordered Key: VYSPER-330 URL: https://issues.apache.org/jira/browse/VYSPER-330 Project: VYSPER

[jira] [Assigned] (VYSPER-330) RequestWindow assumes PriorityQueue.iterator() is ordered

[ https://issues.apache.org/jira/browse/VYSPER-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-330: --- Assignee: Bernd Fondermann RequestWindow assumes PriorityQueue.iterator() is

[jira] [Resolved] (VYSPER-330) RequestWindow assumes PriorityQueue.iterator() is ordered

[ https://issues.apache.org/jira/browse/VYSPER-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-330. - Resolution: Fixed RequestWindow assumes PriorityQueue.iterator() is ordered

[jira] [Closed] (VYSPER-323) (VYSPER-275) Race condition in stanza handling - How does this affect the BoshEndpoint ?

[ https://issues.apache.org/jira/browse/VYSPER-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann closed VYSPER-323. --- Resolution: Not A Problem Don't know what to do with this JIRA

[jira] [Commented] (VYSPER-329) Server To Server inbound messages in jabber:server namespace, delivery fails

[ https://issues.apache.org/jira/browse/VYSPER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13481870#comment-13481870 ] Bernd Fondermann commented on VYSPER-329: - Thanks for the patch. I find the patch

[jira] [Updated] (VYSPER-325) Non-ASCII chars get crippled

[ https://issues.apache.org/jira/browse/VYSPER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann updated VYSPER-325: Component/s: BOSH Assignee: Bernd Fondermann This is a problem in

[jira] [Commented] (VYSPER-325) Non-ASCII chars get crippled

[ https://issues.apache.org/jira/browse/VYSPER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471683#comment-13471683 ] Bernd Fondermann commented on VYSPER-325: - fixed in r1395682

[jira] [Updated] (VYSPER-325) Non-ASCII chars get crippled

[ https://issues.apache.org/jira/browse/VYSPER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann updated VYSPER-325: Fix Version/s: 0.8 Non-ASCII chars get crippled

[jira] [Resolved] (VYSPER-325) Non-ASCII chars get crippled

[ https://issues.apache.org/jira/browse/VYSPER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-325. - Resolution: Fixed Non-ASCII chars get crippled

[jira] [Commented] (VYSPER-329) Server To Server inbound messages in jabber:server namespace, delivery fails

[ https://issues.apache.org/jira/browse/VYSPER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471306#comment-13471306 ] Bernd Fondermann commented on VYSPER-329: - Justin, could you please provide us

[jira] [Commented] (VYSPER-329) Server To Server inbound messages in jabber:server namespace, delivery fails

[ https://issues.apache.org/jira/browse/VYSPER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471035#comment-13471035 ] Bernd Fondermann commented on VYSPER-329: - Looks like a valid suggestion. However,

[jira] [Commented] (VYSPER-327) Creating a room may be restricted as XEP-0045 says

[ https://issues.apache.org/jira/browse/VYSPER-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13467104#comment-13467104 ] Bernd Fondermann commented on VYSPER-327: - In TRUNK, this can already be achieved

[jira] [Updated] (VYSPER-328) Infinite loop in requestExpired()

[ https://issues.apache.org/jira/browse/VYSPER-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann updated VYSPER-328: Summary: Infinite loop in requestExpired() (was: One CPU goes to 100% ) Infinite

[jira] [Commented] (VYSPER-328) One CPU goes to 100%

[ https://issues.apache.org/jira/browse/VYSPER-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466436#comment-13466436 ] Bernd Fondermann commented on VYSPER-328: - This is probably due to a infinite loop

[jira] [Created] (VYSPER-328) One CPU goes to 100%

Bernd Fondermann created VYSPER-328: --- Summary: One CPU goes to 100% Key: VYSPER-328 URL: https://issues.apache.org/jira/browse/VYSPER-328 Project: VYSPER Issue Type: Bug

[jira] [Commented] (VYSPER-326) Synchronizing on the BoshSessionContext for both inbound and outbound processing can lead to deadlock.

[ https://issues.apache.org/jira/browse/VYSPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461336#comment-13461336 ] Bernd Fondermann commented on VYSPER-326: - ok, thanks. Since I wouldn't completely

[jira] [Commented] (VYSPER-326) Synchronizing on the BoshSessionContext for both inbound and outbound processing can lead to deadlock.

[ https://issues.apache.org/jira/browse/VYSPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461231#comment-13461231 ] Bernd Fondermann commented on VYSPER-326: - Sounds reasonable. However, in TRUNK,

[jira] [Created] (VYSPER-325) Non-ASCII chars get crippled

Bernd Fondermann created VYSPER-325: --- Summary: Non-ASCII chars get crippled Key: VYSPER-325 URL: https://issues.apache.org/jira/browse/VYSPER-325 Project: VYSPER Issue Type: Bug

[jira] [Assigned] (VYSPER-324) Thread pool leak: QueuedStanzaProcessor.executor

[ https://issues.apache.org/jira/browse/VYSPER-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-324: --- Assignee: Bernd Fondermann Thread pool leak: QueuedStanzaProcessor.executor

[jira] [Commented] (VYSPER-324) Thread pool leak: QueuedStanzaProcessor.executor

[ https://issues.apache.org/jira/browse/VYSPER-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13453334#comment-13453334 ] Bernd Fondermann commented on VYSPER-324: - Thanks for the patch. Currently we are

[jira] [Commented] (VYSPER-323) (VYSPER-275) Race condition in stanza handling - How does this affect the BoshEndpoint ?

[ https://issues.apache.org/jira/browse/VYSPER-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448638#comment-13448638 ] Bernd Fondermann commented on VYSPER-323: - Is this a question or a bug report?

[jira] [Resolved] (VYSPER-309) BOSH plugin does not always send or recieve messages from client

[ https://issues.apache.org/jira/browse/VYSPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-309. - Resolution: Fixed BOSH plugin does not always send or recieve messages from client

[jira] [Resolved] (VYSPER-322) Handle unresponded request having same RID

[ https://issues.apache.org/jira/browse/VYSPER-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-322. - Resolution: Fixed Handle unresponded request having same RID

[jira] [Assigned] (VYSPER-322) Handle unresponded request having same RID

[ https://issues.apache.org/jira/browse/VYSPER-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-322: --- Assignee: Bernd Fondermann Handle unresponded request having same RID

[jira] [Created] (VYSPER-322) Handle unresponded request having same RID

Bernd Fondermann created VYSPER-322: --- Summary: Handle unresponded request having same RID Key: VYSPER-322 URL: https://issues.apache.org/jira/browse/VYSPER-322 Project: VYSPER Issue Type:

[jira] [Created] (VYSPER-321) Record room creation and activity timestamps

Bernd Fondermann created VYSPER-321: --- Summary: Record room creation and activity timestamps Key: VYSPER-321 URL: https://issues.apache.org/jira/browse/VYSPER-321 Project: VYSPER Issue

[jira] [Resolved] (VYSPER-321) Record room creation and activity timestamps

[ https://issues.apache.org/jira/browse/VYSPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-321. - Resolution: Fixed Record room creation and activity timestamps

[jira] [Resolved] (VYSPER-14) Make the thread pool executors monitorable and configurable

[ https://issues.apache.org/jira/browse/VYSPER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-14. Resolution: Fixed Fix Version/s: 0.8 Make the thread pool executors monitorable

[jira] [Assigned] (VYSPER-14) Make the thread pool executors monitorable and configurable

[ https://issues.apache.org/jira/browse/VYSPER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-14: -- Assignee: Bernd Fondermann Make the thread pool executors monitorable and

[jira] [Work started] (VYSPER-14) Make the thread pool executors monitorable and configurable

[ https://issues.apache.org/jira/browse/VYSPER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on VYSPER-14 started by Bernd Fondermann. Make the thread pool executors monitorable and configurable ---

[jira] [Resolved] (VYSPER-185) Send unavailable on lost connection

[ https://issues.apache.org/jira/browse/VYSPER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-185. - Resolution: Fixed Fix Version/s: 0.8 this has been fixed when endSession() is now

[jira] [Resolved] (VYSPER-320) Make BOSH handler easily extensible

[ https://issues.apache.org/jira/browse/VYSPER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-320. - Resolution: Fixed Make BOSH handler easily extensible

[jira] [Closed] (VYSPER-224) Tests using Easymock not supported on Apache Harmony

[ https://issues.apache.org/jira/browse/VYSPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann closed VYSPER-224. --- Resolution: Won't Fix Apache Harmony is no longer releasing. No need to fix this, as sad as

[jira] [Created] (VYSPER-320) Make BOSH handler easily extensible

Bernd Fondermann created VYSPER-320: --- Summary: Make BOSH handler easily extensible Key: VYSPER-320 URL: https://issues.apache.org/jira/browse/VYSPER-320 Project: VYSPER Issue Type:

[jira] [Created] (VYSPER-318) Give Visitors voice in a room (as an option)

Bernd Fondermann created VYSPER-318: --- Summary: Give Visitors voice in a room (as an option) Key: VYSPER-318 URL: https://issues.apache.org/jira/browse/VYSPER-318 Project: VYSPER Issue

[jira] [Created] (VYSPER-319) Notify OccupantStorageProvider when occupants come or leave

Bernd Fondermann created VYSPER-319: --- Summary: Notify OccupantStorageProvider when occupants come or leave Key: VYSPER-319 URL: https://issues.apache.org/jira/browse/VYSPER-319 Project: VYSPER

[jira] [Resolved] (VYSPER-318) Give Visitors voice in a room (as an option)

[ https://issues.apache.org/jira/browse/VYSPER-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-318. - Resolution: Fixed Give Visitors voice in a room (as an option)

[jira] [Resolved] (VYSPER-319) Notify OccupantStorageProvider when occupants come or leave

[ https://issues.apache.org/jira/browse/VYSPER-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-319. - Resolution: Fixed Notify OccupantStorageProvider when occupants come or leave

[jira] [Resolved] (VYSPER-317) MUC doesn't send latest presence's inner elements

[ https://issues.apache.org/jira/browse/VYSPER-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-317. - Resolution: Fixed MUC doesn't send latest presence's inner elements

[jira] [Resolved] (VYSPER-305) Review BoshBackedSessionContext synchronization and queuing issues

[ https://issues.apache.org/jira/browse/VYSPER-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-305. - Resolution: Fixed Review BoshBackedSessionContext synchronization and queuing

[jira] [Created] (VYSPER-316) MUC not processing presence with explicitly set type available

Bernd Fondermann created VYSPER-316: --- Summary: MUC not processing presence with explicitly set type available Key: VYSPER-316 URL: https://issues.apache.org/jira/browse/VYSPER-316 Project: VYSPER

[jira] [Resolved] (VYSPER-316) MUC not processing presence with explicitly set type available

[ https://issues.apache.org/jira/browse/VYSPER-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-316. - Resolution: Fixed MUC not processing presence with explicitly set type available

[jira] [Resolved] (VYSPER-315) Support Cross-Origin-Resource-Sharing HTTP Headers

[ https://issues.apache.org/jira/browse/VYSPER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-315. - Resolution: Not A Problem BoshServlet already returns the headers for OPTIONS. Beyond

[jira] [Closed] (VYSPER-314) /crossdomain.xml is not served when BoshServlet is mapped to /foo/bosh/, not root

[ https://issues.apache.org/jira/browse/VYSPER-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann closed VYSPER-314. --- Resolution: Fixed /crossdomain.xml is not served when BoshServlet is mapped to

[jira] [Resolved] (VYSPER-313) Make MUC history accessible from outside

[ https://issues.apache.org/jira/browse/VYSPER-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-313. - Resolution: Fixed Make MUC history accessible from outside

[jira] [Created] (VYSPER-314) /crossdomain.xml is not served when BoshServlet is mapped to /foo/bosh/, not root

Bernd Fondermann created VYSPER-314: --- Summary: /crossdomain.xml is not served when BoshServlet is mapped to /foo/bosh/, not root Key: VYSPER-314 URL: https://issues.apache.org/jira/browse/VYSPER-314

[jira] [Created] (VYSPER-315) Support Cross-Origin-Resource-Sharing HTTP Headers

Bernd Fondermann created VYSPER-315: --- Summary: Support Cross-Origin-Resource-Sharing HTTP Headers Key: VYSPER-315 URL: https://issues.apache.org/jira/browse/VYSPER-315 Project: VYSPER

[jira] [Resolved] (VYSPER-312) Make some MUC features configurable

[ https://issues.apache.org/jira/browse/VYSPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-312. - Resolution: Fixed Make some MUC features configurable

[jira] [Created] (VYSPER-313) Make MUC history accessible from outside

Bernd Fondermann created VYSPER-313: --- Summary: Make MUC history accessible from outside Key: VYSPER-313 URL: https://issues.apache.org/jira/browse/VYSPER-313 Project: VYSPER Issue Type:

[jira] [Created] (VYSPER-312) Make some MUC features configurable

Bernd Fondermann created VYSPER-312: --- Summary: Make some MUC features configurable Key: VYSPER-312 URL: https://issues.apache.org/jira/browse/VYSPER-312 Project: VYSPER Issue Type: New

[jira] [Created] (VYSPER-311) Respond with error when session id not matching

Bernd Fondermann created VYSPER-311: --- Summary: Respond with error when session id not matching Key: VYSPER-311 URL: https://issues.apache.org/jira/browse/VYSPER-311 Project: VYSPER Issue

[jira] [Assigned] (VYSPER-311) Respond with error when session id not matching

[ https://issues.apache.org/jira/browse/VYSPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-311: --- Assignee: Bernd Fondermann Respond with error when session id not matching

[jira] [Resolved] (VYSPER-311) Respond with error when session id not matching

[ https://issues.apache.org/jira/browse/VYSPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-311. - Resolution: Fixed Respond with error when session id not matching

[jira] [Commented] (VYSPER-309) BOSH plugin does not always send or recieve messages from client

[ https://issues.apache.org/jira/browse/VYSPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276865#comment-13276865 ] Bernd Fondermann commented on VYSPER-309: - What is your hold value? Educated

[jira] [Resolved] (VYSPER-302) Log chat messages

[ https://issues.apache.org/jira/browse/VYSPER-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-302. - Resolution: Fixed Log chat messages - Key:

[jira] [Commented] (VYSPER-310) XEP-0047 IBB usablility

[ https://issues.apache.org/jira/browse/VYSPER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273565#comment-13273565 ] Bernd Fondermann commented on VYSPER-310: - as far as I can tell, in-band

  1   2   3   4   >