January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-680) Unit Testing: Added and modified methods in JDBCPersistenceManager

by Juha Lindfors (JIRA)

Unit Testing: Added and modified methods in JDBCPersistenceManager ------------------------------------------------------------------ Key: JBMESSAGING-680 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-680 Project: JBoss Messaging Issue Type: Sub-task Reporter: Juha Lindfors Assigned To: Juha Lindfors Fix For: 1.0.2.CR1 Add unit tests to the added and/or modified methods in JDBCPersistenceManager -- 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

19 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-446) Start the QA process in concert with QA team

by Ovidiu Feodorov (JIRA)

Start the QA process in concert with QA team -------------------------------------------- Key: JBMESSAGING-446 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-446 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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

19 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-626) Invalid JAXB API in jboss-messaging-client.jar

by Thomas Diesler (JIRA)

Invalid JAXB API in jboss-messaging-client.jar ---------------------------------------------- Key: JBMESSAGING-626 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-626 Project: JBoss Messaging Issue Type: Bug Reporter: Thomas Diesler Assigned To: Ovidiu Feodorov JAXB-1.0 api leaks from jboss-messaging-client into jbossall-client.jar, which breaks the CTS Messaging should have a dependency on jaxb-api.jar and not redistribute the jaxb api Please fix in jbossas/branches/JEE5_TCK -- 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

19 years, 1 month

5
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-454) InVM callbackserver

by Tim Fox (JIRA)

InVM callbackserver ------------------- Key: JBMESSAGING-454 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-454 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.0.1.CR3 Reporter: Tim Fox Fix For: 1.0.2 When running with both client and server invm and using the socket transport, a callbackserver is opened on the client and creates several sockets to listen for incoming requests. This uses up system resources (threads and sockets) which are never used for the invm case. -- 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

19 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-728) Clustering touch ups

by Ovidiu Feodorov (JIRA)

Clustering touch ups -------------------- Key: JBMESSAGING-728 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-728 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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

19 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (GPD-21) Add support for the process-state

by Koen Aers (JIRA)

Add support for the process-state --------------------------------- Key: GPD-21 URL: http://jira.jboss.com/jira/browse/GPD-21 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha2 Basic support is already provided. What still needs to be added is a way to configure. -- 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

19 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (GPD-42) Add script configuration on fork

by Koen Aers (JIRA)

Add script configuration on fork -------------------------------- Key: GPD-42 URL: http://jira.jboss.com/jira/browse/GPD-42 Project: JBoss jBPM GPD Issue Type: Task Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha2 -- 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

19 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-494) Add smoke test using ConnectionFactory

by Tim Fox (JIRA)

Add smoke test using ConnectionFactory -------------------------------------- Key: JBMESSAGING-494 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-494 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.0.1.CR4 Need to add a smoke test that uses /ConnectionFactory as opposed to /JmsXA. This is because there was a classloader bug that only manifests when sending a message from an ejb to a topic using /Connectionfactory. Really, the smoke tests should be refactored to have a more appropriate use of connection factories. -- 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

19 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-789) Non causality when using Remoting socket transport and one way invocations

by Tim Fox (JIRA)

Non causality when using Remoting socket transport and one way invocations -------------------------------------------------------------------------- Key: JBMESSAGING-789 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-789 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Priority: Critical Fix For: 1.2.0.CR1 The remoting socket transport uses an underlying pool of tcp connections, and subsequent invocations get a connection from the pool, use it and return it from the pool. This means that subsequent invocations can use a different underlying TCP connection, and later invocations can overtake earlier ones depending on how the OS schedules the read threads listening on the connections. Temporary work around is to use a pool size of 1, or completely serialize all invocations per VM by encloing in the synchronized block. This gives us effectively one TCP connection per VM. A better approach would be for the remoting Client object to be pinned to the actual TCP connection one to one. I.e. we don't want or need the pool. It is just a big PITA for us. -- 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

19 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1179) Create a special undeletable user for the administrator

by Thomas Heute (JIRA)

Create a special undeletable user for the administrator ------------------------------------------------------- Key: JBPORTAL-1179 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1179 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Reporter: Thomas Heute Fix For: 2.6.Beta1 The user with username "admin" is now mandatory at least for the CMS service (see JCRCMS.java). We should not be able to delete the admin user. Ultimately we should be able to give him any username. -- 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

19 years, 1 month

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007