October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-603) Performance graphs

by Ovidiu Feodorov (JIRA)

Performance graphs ------------------ Key: JBMESSAGING-603 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-603 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.GA -- 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, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JGRP-337) Make STOP_FLUSH phase in FLUSH asynchronous

by Bela Ban (JIRA)

Make STOP_FLUSH phase in FLUSH asynchronous ------------------------------------------- Key: JGRP-337 URL: http://jira.jboss.com/jira/browse/JGRP-337 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Revert back from synchronous. Only possible if we make the STOP_FLUSH message *out-of-band* ! -- 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, 7 months

3
5
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, 7 months

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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-592) Write JBossMQ to Messaging Migration Guide

by Ovidiu Feodorov (JIRA)

Write JBossMQ to Messaging Migration Guide ------------------------------------------ Key: JBMESSAGING-592 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-592 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha2 This is the stub: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingJBossMQMigrationGuide -- 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, 7 months

5
11
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, 8 months

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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-607) Add idle timeout setting for invoker threads

by Galder Zamarreno (JIRA)

Add idle timeout setting for invoker threads -------------------------------------------- Key: JBREM-607 URL: http://jira.jboss.com/jira/browse/JBREM-607 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Tom Elrod An idle timeout minutes setting so that any unused threads are removed. It needs to have the possibility of disabling 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBREM-614) Client.invoke() should check isConnected().

by Ron Sigal (JIRA)

Client.invoke() should check isConnected(). ------------------------------------------- Key: JBREM-614 URL: http://jira.jboss.com/jira/browse/JBREM-614 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) This changed due to a leasing bug that Clebert found within messaging. The problem was that the isConnected() calls on it's invoker to see if it is connected (assuming the invoker is not null). So is possible that another Client is using the same client invoker and that invoker is already connected. This would cause the new Client to not set up leasing (which it would need to do). I guess the isConnected() call could be added back in, but would need to change the Client.isConnected() to use an member variable keeping track of state (connect or not connected) instead of calling on the invoker to see if it's connect. Ron Sigal wrote: > Hi Tom, > > I noticed something about Client.connect() and CallbackPoller.start(). In particular, CallbackPoller.start() calls Client.connect(), as it should. If leasing is configured, the Client will be registered with the LeasePinger. When the application calls Client.connect(), the Client will be re-registered with the LeasePinger. It doesn't cause an error, but it's a bit redundant. Looks like Client.connect() should start with > > if (isConnected()) > return; > > ?? > > -Ron -- 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, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBREM-622) InvokerLocator already exists for listener

by Galen Dunkleberger (JIRA)

InvokerLocator already exists for listener ------------------------------------------ Key: JBREM-622 URL: http://jira.jboss.com/jira/browse/JBREM-622 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 4.0.5.GA JBoss Messaging 1.0.1.GA Linux BEA Jrockit R26.0.0-jdk1.5.0_04_x86_64 Reporter: Galen Dunkleberger Assigned To: Tom Elrod When trying to send many small messsages very quickly through JBoss messaging I was getting the following error javax.jms.IllegalStateException: InvokerLocator already exists for listener id 1436420135. Remove t his listener before adding again. at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:91) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6 840474864420126404.invokeNext()Ljava.lang.Object;(ClientConnectionFactoryDelegate$createConnectionDe legate_N6840474864420126404.java:???) at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6 840474864420126404.invokeNext()Ljava.lang.Object;(ClientConnectionFactoryDelegate$createConnectionDe legate_N6840474864420126404.java:???) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(Lj ava.lang.String;Ljava.lang.String;)Lorg.jboss.jms.delegate.ConnectionDelegate;(ClientConnectionFacto ryDelegate.java:???) at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFacto ry.java:202) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory. java:108) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory. java:103) -- 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, 8 months

4
8
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 October 2006