October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJMX-98) Monitoring Only Sends Single Notification Message

by Brian Husted (JIRA)

Monitoring Only Sends Single Notification Message ------------------------------------------------- Key: JBJMX-98 URL: http://jira.jboss.com/jira/browse/JBJMX-98 Project: JBoss JMX Issue Type: Bug Affects Versions: JBossAS-4.0.0 Environment: Windows 2000, Sun JDK 1.5, Single CPU 1GB RAM Reporter: Brian Husted I have configured a threshold monitoring mbean to monitor the QueueDepth on a JMS queue. When the QueueDepth is greater than 500, I have registered to receive a notification on the ConsoleAlterListener. The problem is that only one notification is sent when the QueueDepth exceeds 500. The depth will go back down below 500 and minutes later it will again exceed 500 but a notificaiton is NOT sent. I did notice that if I click the clear-all-alerts button on the web-console then the notification will be sent again but only if you clear it each time it appears. Below is my config for the threshold monitor. I have tested this with the ConsoleAlertMonitor and a custom MBeanListener and I experience the same problem with either configuration. [Code] <?xml version="1.0" encoding="UTF-8"?> <server> <mbean code="org.jboss.monitor.ThresholdMonitor" name="jboss.monitor:service=SlaveQueue_Monitor"> <attribute name="MonitorName">SlaveQueue Monitor</attribute> <depends optional-attribute-name="ObservedObject">jboss.mq.destination:service=Queue,name=B</depends> <attribute name="ObservedAttribute">QueueDepth</attribute> <depends-list optional-attribute-name="AlertListeners"> <depends-list-element>jboss.alerts:service=ConsoleAlertListener</depends-list-element> </depends-list> <attribute name="Threshold">500</attribute> <attribute name="Period">2000</attribute> <attribute name="CompareTo">-1</attribute> <attribute name="Enabled">true</attribute> </mbean> </server> [/Code] -- 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

16 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-478) Create indexes to improve performance

by Tim Fox (JIRA)

Create indexes to improve performance ------------------------------------- Key: JBMESSAGING-478 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-478 Project: JBoss Messaging Issue Type: Sub-task Affects Versions: 1.0.1.CR3 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Create indexes in memory so that we don't have to iterate through all the messages in memory to find the ones that match. Also make sure it all works when messages are paged to storage. -- 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

16 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3774) Synch up with the ide team on use of the VDF

by Scott M Stark (JIRA)

Synch up with the ide team on use of the VDF -------------------------------------------- Key: JBAS-3774 URL: http://jira.jboss.com/jira/browse/JBAS-3774 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta Part of fleshing out the VDF should be the jbosside integration usecase. -- 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

16 years, 10 months

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

16 years, 10 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

16 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-133) Multiplexer documentation

by Brian Stansberry (JIRA)

Multiplexer documentation ------------------------- Key: JBCLUSTER-133 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-133 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q4Y6 -- 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

16 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-134) Buddy replication documentation for http sessions

by Brian Stansberry (JIRA)

Buddy replication documentation for http sessions ------------------------------------------------- Key: JBCLUSTER-134 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-134 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q4Y6 -- 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

16 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3647) Backport SingleRetryInterceptor to 3.2

by Scott M Stark (JIRA)

Backport SingleRetryInterceptor to 3.2 -------------------------------------- Key: JBAS-3647 URL: http://jira.jboss.com/jira/browse/JBAS-3647 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, EJB2 Affects Versions: JBossAS-3.2.8.SP1 Reporter: Scott M Stark Assigned To: Brian Stansberry A 3.2.8.SP1 client attempting to connect to a 4.0.4 clustered bean fails with the following error due to the SingleRetryInterceptor not being available in 3.2.8.SP1: 2006-09-12 16:44:30,178 [Thread-0::] - javax.naming.CommunicationException. Root exception is java.lang.ClassNotFoundException: org.jboss.proxy.ejb.SingleRetryInterceptor (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:318) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:132) at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:143) at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918) We should backport this. -- 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

16 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-744) EJB3 JACC Layer Container Task

by Anil Saldhana (JIRA)

EJB3 JACC Layer Container Task ------------------------------ Key: EJBTHREE-744 URL: http://jira.jboss.com/jira/browse/EJBTHREE-744 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD Container Task for validation of the ejb3 jacc layer for correct permissions creation and checking, as per JACC 1.1 specification. In the future, the EJB3 security layer needs alignment with the security spi. -- 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

16 years, 11 months

5
16
0 / 0

[JBoss JIRA] Created: (JBAS-3570) SSLUnitTestCase testsuite failures when using the IBM JVM

by Matt Wringe (JIRA)

SSLUnitTestCase testsuite failures when using the IBM JVM --------------------------------------------------------- Key: JBAS-3570 URL: http://jira.jboss.com/jira/browse/JBAS-3570 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: IBM 1.4.2 JDK RHEL 4, Linux Kernel 2.6.9 Arch: i386 Reporter: Matt Wringe The org.jboss.test.web.test.ssl.SSLUnitTestCase tests fail when the IBM JDK is used. testHttpRedirect Error: Connection refused testHttpRedirectSecurityDomain Error: Connection refused testHttps Error: Connection refused testHttpsSecurityDomain Error: Connection refused Stack Trace: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:336) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:201) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:188) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.connect(Socket.java:428) at java.net.Socket.<init>(Socket.java:335) at java.net.Socket.<init>(Socket.java:150) at com.ibm.jsse.bv.<init>(Unknown Source) at com.ibm.jsse.JSSESocketFactory.createSocket(Unknown Source) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:93) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:652) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:628) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497) at org.jboss.test.web.test.ssl.SSLUnitTestCase.doHttps(SSLUnitTestCase.java:117) at org.jboss.test.web.test.ssl.SSLUnitTestCase.testHttpsSecurityDomain(SSLUnitTestCase.java:85) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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

16 years, 11 months

4
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006