November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2166) portal admin testing

by Prabhat Jha (JIRA)

portal admin testing -------------------- Key: JBPORTAL-2166 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2166 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Prabhat Jha Assignee: Viliam Rockai -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1459) Equivalent of servlet transport for JBM/Netty

by Tim Fox (JIRA)

Equivalent of servlet transport for JBM/Netty --------------------------------------------- Key: JBMESSAGING-1459 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1459 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0 Beta We need some kind of equivalent of the remoting servlet transport for Netty/JBM to allow JBM 2.0 to be used over standard web server port (8080) in AS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-544) Use NBIO for connection model

by Tim Fox (JIRA)

Use NBIO for connection model ----------------------------- Key: JBMESSAGING-544 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 For throughput and scalability we need to use a non blocking IO model to provide connections between jms clients and server. Unfortunately the JBoss remoting model does not currently allows this. We can either drive JBoss Remoting to support this model (may take some time) Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA. This would also solve the problem of providing a functional and performant multiplex transport. Essentially we need a bidirectional channel between jms client and server. On either end bytes can be read or witten in a non blocking fashion. On top of that we can introduce simple framing in order to provide multiplex functionality. -- 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, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-604) Duplicate message detection

by Tim Fox (JIRA)

Duplicate message detection --------------------------- Key: JBMESSAGING-604 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-604 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Whereas JMS requires once and only once *delivery* of messages, there are no such guarantees when sending messages to a queue/durable sub. This can result in duplicate messages existing in a queue or durable sub. For some clients this is unacceptable, so we should implement a feature which alerts to the presence of duplicates. This can be done by keeping a persistent cache of message (or transaction) id on the server. Entries should time out after a period of time. This will not remove duplicates 100% of the time since we cannot cache the previous values of id for ever, but only for a window. See forum thread 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

17 years, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1341) Client side failover

by Tim Fox (JIRA)

Client side failover -------------------- Key: JBMESSAGING-1341 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1341 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta Need to re-enable client side failover. We will implement automatic failover onto backup node. This will involve resending messages that backup node says it has not received. This means we will need to keep track on the client side of messages sent but for which no confirmation has arrived. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2197) convert portal reference guide to product format

by Prabhat Jha (JIRA)

convert portal reference guide to product format ------------------------------------------------ Key: JBPORTAL-2197 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2197 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Reference Guide Reporter: Prabhat Jha Assignee: Samson Kittoli current contents are at: http://anonsvn.jboss.org/repos/portal/docs/branches/JBoss_Portal_Branch_2.... Please put the converted contents at http://anonsvn.jboss.org/repos/portal/docs/enterprise/trunk/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (JBAS-6114) http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd is missing

by Juergen Zimmermann (JIRA)

http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd is missing --------------------------------------------------------- Key: JBAS-6114 URL: https://jira.jboss.org/jira/browse/JBAS-6114 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR2 Reporter: Juergen Zimmermann %JBOSS_HOME%\docs\schema\jboss-ds_5_0.dtd refers to http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd. But this url doesn't exist -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1401) Create Tests for @Remote pass-by-value within local JVM

by Andrew Lee Rubinger (JIRA)

Create Tests for @Remote pass-by-value within local JVM ------------------------------------------------------- Key: EJBTHREE-1401 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1401 Project: EJB 3.0 Issue Type: Task Components: proxy Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR2 Ensure EJB3 Core Specification 3.2.1 is intact: "The arguments and results of the methods of the remote business interface are passed by value." -- 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, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBRULES-1811) syntax errors caused by use of special characters in decision table cells

by Frank Langelage (JIRA)

syntax errors caused by use of special characters in decision table cells ------------------------------------------------------------------------- Key: JBRULES-1811 URL: https://jira.jboss.org/jira/browse/JBRULES-1811 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 4.0.7 Environment: JBoss-4.24GA with Drools 4.0.7 on Solaris Sparc 10, Sun JDK 1.6.0_07 Reporter: Frank Langelage Assignee: Mark Proctor A customer entered item codes with special characters into an decision table. This caused syntax errors on the generated code. The item codes contained dimension in inches and they used a double quote for the unit (e.g. '... 24"....'). As this double quotes terminate a string, the generated code out of the decision table is invalid. If a double quote sign is in the cell content this double quote must be masked by inserting a backslash character automatically. So we would get "....24\"...." as the string literal in generated code. >From our opinion it's not acceptable to force the user who fills in the data cells into the spreadsheet to learn java and masquerade problematic characters by inserting the backslash in front of them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1440) JTA-prepared message delivered to other consumer.

by szhigunov (JIRA)

JTA-prepared message delivered to other consumer. -------------------------------------------------- Key: JBMESSAGING-1440 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1440 Project: JBoss Messaging Issue Type: Bug Environment: JBoss 4.2.2 + JBM 1.4.0.SP3. Windows XP. Reporter: szhigunov Assignee: Tim Fox The problem is that when fully prepared tx1 fails in the commit phase, JBM delivers the message second time in tx2, while tx1 is still in progress. Eventually recovery commits tx1, so the message gets delivered and committed twice. The attached test (myxatest.zip) is a clean JBoss 4.2.2 + JBM 1.4.0 SP3 with my test MBean: jboss-4.2.2.GA\server\messaging\lib\myxatest.jar (code and source) + jboss-4.2.2.GA\server\messaging\deploy\myxatest-service.xml. Steps to reproduce the problem: 1. Start the server. 2. Go to JMX console + myxatest + service=Test. Invoke send. 3. Go to JMX console + jboss.messaging.destination + name=A.service=Queue. Verify MessageCount=1. 4. Go to JMX console + myxatest + service=Test. Invoke receive. That will start XA transaction; enlist DummyXAResource; get JMS connection from JCA and receive message. DummyXAResource sleeps 60 sec inside the commit call. 5. Verify that DummyXAResource prints "DummyXAResource commit start sleeping for 60 sec" message. 6. Go to JMX console + jboss.jca + name=JmsXA,service=ManagedConnectionPool and invoke stop(). Check that DummyXAResource finished commit and printed "DummyXAResource commit end" message. JBM commit fails. 7. Now we have fully prepared JBM transaction in progress. You can see one record in JBM_TX. 8. Go to JMX console + jboss.jca + name=JmsXA,service=ManagedConnectionPool and invoke start(). 9. Go to JMX console + myxatest + service=Test. Invoke receive again. Same message delivered again. And this is wrong. Wait for a minute and let transaction finish successfully. 10. Got to JBM_TX and verify that transaction is still there (nobody recovered it!). 11. Stop server, enable JBM recovery, start server. In couple minutes the original transaction is found and committed (second time). JBM_TX is empty. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

4
19
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 November 2008