November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJMX-100) Class loader doesn't contain classes from MBean jar file when the MBean is redeployed.

by Doug Palmer (JIRA)

Class loader doesn't contain classes from MBean jar file when the MBean is redeployed. -------------------------------------------------------------------------------------- Key: JBJMX-100 URL: http://jira.jboss.com/jira/browse/JBJMX-100 Project: JBoss JMX Issue Type: Bug Affects Versions: JBossAS-4.0.0 Environment: Mac OSX and Windows XP Reporter: Doug Palmer This is a simplified version of a Deployer MBean that I have been writing. The MBean uses some jaxb generated classes. When the MBean is first deployed it's create method functions perfectly. However, if the MBean is redeployed then calling create fails because the class loader can't find the package "decs2.process_definition". To replicate the problem execute the ant target named "deploy-all"; then run JBoss; then execute the ant target named "deploy". If the package "decs2.process_definition" is is placed in a seperate jar file and that jar file is placed in the server/lib directory then the MBean redeploys successfully. -- 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, 2 months

2
3
0 / 0

[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

17 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3859) Initialization of XMBean attributes doesn't occur

by Chris (JIRA)

Initialization of XMBean attributes doesn't occur ------------------------------------------------- Key: JBAS-3859 URL: http://jira.jboss.com/jira/browse/JBAS-3859 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.3 SP1 Environment: Windows XP, Mac OSX 10.4.8, Java 1.5.0_04, 1.6.0 Reporter: Chris Assigned To: Scott M Stark The Wiki for initializing XMBean values upon deployment (see http://wiki.jboss.org/wiki/Wiki.jsp?page=HowCanIInitializeXMBeanAttributes) suggests 2 ways to set the initial value. One is to use a <descriptor>, the other is to use a plain <value> tag. This has been confirmed to be the way it should work by Dimitris (see forum thread). I have tried both ways on JBoss 4.0.3, 4.0.5, and JBoss 5.0.0 (JEE5_TCK) - using JDK1.5 and JDK 1.6, on XP and also on Mac .... and it does not set the initial value. Instead the value is always the default value "I've got the devil inside me" which comes from the String definition within the class file itself. (Incidentally, as an aside, if you change the value in the JMX Console and restart JBoss, then the value is correctly recovered from the persistence store). To reproduce, open the file $JBOSS_HOME\docs\examples\jmx\persistent-service.sar\META-INF\jboss-service.xml and edit the file as per the Wiki's suggestion. e.g. for attribute SomeString add a <value> tag as follows: <attribute access="read-write" getMethod="getSomeString" setMethod="setSomeString"> <name>SomeString</name> <type>java.lang.String</type> <value>This is my initial value</value>  </attribute> Copy this to the $JBOSS_HOME\server\default\deploy\ directory and start JBoss. Then view the XMBean using the JMX console: http://localhost:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=jb... You will see that the value for SomeString is "I've got the devil inside me" from the class definition whereas I would expect it to be "This is my initial value" as taken from the XML file. (Incidentally, setting an MBean initial attribute does work, the persistence service example has such a value for SomeElement: "<some-message>Welcome to the Athens 2004, Olympic Games!</some-message>" But setting the XMBean initial attribute does not work) (Also, if the attribute is changed to read-only then there is no error upon deployment to show that the setting of the value has even been attempted.) -- 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, 2 months

3
3
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

17 years, 3 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

17 years, 3 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

17 years, 3 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, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (HIBERNATE-50) Embedded Objects get set to null if all its members are null

by milan w?lke (JIRA)

Embedded Objects get set to null if all its members are null ------------------------------------------------------------ Key: HIBERNATE-50 URL: http://jira.jboss.com/jira/browse/HIBERNATE-50 Project: Hibernate Issue Type: Bug Environment: WinXP SP2, JBoss 4.0.4 GA as well as JBoss 4.0.5 GA, installation profile ejb3 Reporter: milan w?lke Assigned To: Steve Ebersole When having an embedded object only containing members of non-simple-types (e.g. String) and fetching it with the entity manager the following happens: If all columns, the embedded objects values are based on, are null the embedded object itself is set to null even if a non-arg-constructor set it to a non-null value before. A valid workaround is to include a member of a simple-type (e.g. int) in the embedded object. Doing this not all the values can be set to null, which results in not setting the embedded object itself to null, too. -- 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, 4 months

13
16
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

17 years, 4 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

17 years, 4 months

2
5
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 2006