September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-751) ignoreModifications cache loader flag to be extended to all cache loaders, not just ones configured in a chaining cache loader

by Manik Surtani (JIRA)

ignoreModifications cache loader flag to be extended to all cache loaders, not just ones configured in a chaining cache loader ------------------------------------------------------------------------------------------------------------------------------ Key: JBCACHE-751 URL: http://jira.jboss.com/jira/browse/JBCACHE-751 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0, 1.3.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0 -- 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, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3441) Request to include log4j version 1.2.13 in next JBoss AS release

by Khiem Tang (JIRA)

Request to include log4j version 1.2.13 in next JBoss AS release ---------------------------------------------------------------- Key: JBAS-3441 URL: http://jira.jboss.com/jira/browse/JBAS-3441 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-4.0.4.GA Environment: All OS's. Reporter: Khiem Tang Assigned To: Scott M Stark We have one component that depends on log4j-1.2.13 but the one that ships with JBoss is older. We currently use this log4j version in our JBoss stack and it seems to work fine. It would help us if JBoss put the same version (1.2.13) in the packages. -- 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, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-553) Run AS (4.x and 5.x) integration tests with Messaging

by Ovidiu Feodorov (JIRA)

Run AS (4.x and 5.x) integration tests with Messaging ----------------------------------------------------- Key: JBMESSAGING-553 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-553 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Richard Achmatowicz Priority: Critical Fix For: 1.2.0.Beta1 This is the container task for everthing required to run JBoss AS JMS integration tests with JBoss Messaging. The existing integration test framework should be modified in such a manner to allow interchangeably running the same JMS tests with JBossMQ and JBoss Messaging. None of the existing JBossMQ tests should be removed, they must be at most refactored so the JBossMQ-specific tests will be executed with JBossMQ only (as part of the JBossMQ functional testsuite) and generic JMS tests will be executed with both JBossMQ and JBoss Messaging. More details in the sub-tasks. -- 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

18 years

5
14
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-509) JMS DDL should be made public and available as a script.

by Joel Lindheimer (JIRA)

JMS DDL should be made public and available as a script. -------------------------------------------------------- Key: JBMESSAGING-509 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-509 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: All Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov JMS DDL should be made public and available as a script. Other jboss projects like jbpm have the option of generating ddl at server startup, or not, also supply ddl generation capability. Recently (CR4) there was a release that made schema changes and problems occured from said changes. Had there been ddl files available diffs could have been done easily and the problem would have been apparent right away. -- 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

18 years

4
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-524) Introduce data schema backward compatibility tests

by Ovidiu Feodorov (JIRA)

Introduce data schema backward compatibility tests -------------------------------------------------- Key: JBMESSAGING-524 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-524 Project: JBoss Messaging Issue Type: Task Components: Messaging Core Persistence Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.1 Fill the database with messages using the old version and then start the new version in top of it. -- 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

18 years

3
5
0 / 0

[JBoss JIRA] Created: (JBREM-604) allow socket server invoker to accept third party requests

by Tom Elrod (JIRA)

allow socket server invoker to accept third party requests ---------------------------------------------------------- Key: JBREM-604 URL: http://jira.jboss.com/jira/browse/JBREM-604 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) The http server invoker (i.e. CoyoteInvoker) allows thirdparty clients to make requests and process those requests and return raw response from handler. Really no reason that the socket server invoker could not do this as well so that someone could write their own socket client and send raw data to the socket server invoker. -- 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

18 years

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-606) patch to 1.4.4.GA to include fix for socket server thread leak

by Tom Elrod (JIRA)

patch to 1.4.4.GA to include fix for socket server thread leak -------------------------------------------------------------- Key: JBREM-606 URL: http://jira.jboss.com/jira/browse/JBREM-606 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 1.4.4.GA Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 1.4.5.GA Need to back port fix for JBREM-409. -- 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

18 years

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-594) invoker not torn down upon connector startup error

by Tom Elrod (JIRA)

invoker not torn down upon connector startup error -------------------------------------------------- Key: JBREM-594 URL: http://jira.jboss.com/jira/browse/JBREM-594 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) If get a jvm bind error when starting connector, if stop connector and then re-create a new connector and try to start it, will get an exception saying invoker for connector has already been created and are basically stuck. -- 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

18 years

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-586) socket client invoker connection pooling not bounded

by Tom Elrod (JIRA)

socket client invoker connection pooling not bounded ---------------------------------------------------- Key: JBREM-586 URL: http://jira.jboss.com/jira/browse/JBREM-586 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) Due to code change for JBREM-576, the socket client invoker's bounded connection pooling was broken and the pool became unbounded (due to reducing the scope of the pool being sychronized within MicroSocketClientInvoker.getConnection(). The fix for JBREM-576 needs to remain (so do not get dealock on disconnect of one client invoker while another is still in use). However, will also need to synchronize the increase/decrease of number of pooled connections in use. -- 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

18 years

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-597) Allow access to underlying stream in marshaller with socket transport

by Tim Fox (JIRA)

Allow access to underlying stream in marshaller with socket transport --------------------------------------------------------------------- Key: JBREM-597 URL: http://jira.jboss.com/jira/browse/JBREM-597 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tim Fox Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Currently the ClientSocketWrapper::createOuputStream always returns an ObjectOutputStream wrapping the underlying socket ouput stream. This ends up getting passed into the marshaller. With messaging we'd like to use the underlying socket output stream directly in the marshaller - i.e. we don't want to have to write through an object output stream. This is because the object output stream adds some overhead in terms of the amount of stuff written to the underlying stream.. A similar reasoning applies to InputStream too. Any chance of changing the socket transport to pass in the underlying socket stream, not an object output/input stream? -- 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

18 years

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006