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

15 years, 11 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

15 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4917) remote call to LoaderRepository.getPackageClassLoaders throws a NotSerializableException

by Fran￧ois Karman (JIRA)

remote call to LoaderRepository.getPackageClassLoaders throws a NotSerializableException ---------------------------------------------------------------------------------------- Key: JBAS-4917 URL: http://jira.jboss.com/jira/browse/JBAS-4917 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Environment: I have tested this problems on Windows Platform only. Reporter: Fran￧ois Karman Assigned To: Dimitris Andreadis A call to the getPackageClassLoaders operation of the MBean : JMImplementation:name=Default,service=LoaderRepository throws an exception. The simpliest way to view the bug : twiddle invoke "JMImplementation:name=Default,service=LoaderRepository" getPackageClassLoaders javax.ejb.EntityBean Start of the trace : java.io.NotSerializableException: org.jboss.mx.loading.ClassLoaderUtils$RepositoryClassLoaderComparator at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at java.util.TreeSet.writeObject(TreeSet.java:458) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) The comparator used by the result TreeSet is not serializable and could not be send to the remote client. (twiddle or a J2EE Client application) http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/jmx/src/main/org... -- 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

15 years, 11 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

15 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1349) Revisit Error codes on native layer

by Clebert Suconic (JIRA)

Revisit Error codes on native layer ----------------------------------- Key: JBMESSAGING-1349 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1349 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 2.0.0 Beta -- 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

15 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (GPD-29) referencing an unknown class gives exception at deployment

by Koen Aers (JIRA)

referencing an unknown class gives exception at deployment ---------------------------------------------------------- Key: GPD-29 URL: http://jira.jboss.com/jira/browse/GPD-29 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers preferrably, this should be a warning in the problems view. in case the class is not found to be included in the .par, it just shouldn't be included. maybe a warning would be good; -- 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

15 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (GPD-63) Inner classes are not deployed.

by Matej Knopp (JIRA)

Inner classes are not deployed. ------------------------------- Key: GPD-63 URL: http://jira.jboss.com/jira/browse/GPD-63 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.0.13 Reporter: Matej Knopp Assigned To: Koen Aers When process is being deployed, the inner classes are ignored. So when I have class Foo with inner class Bar, the Foo.class file gets deployed, but the Foo$Bar.class is not. -- 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

15 years, 11 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1308) Remove unnecessary System.currentTimeMillis() from ClientConsumerImpl

by Tim Fox (JIRA)

Remove unnecessary System.currentTimeMillis() from ClientConsumerImpl --------------------------------------------------------------------- Key: JBMESSAGING-1308 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1308 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta There is currently an unnecessary System.currentTimeMillis() call in clientconsumerImpl when retrieveing a message. This can be removed. -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1331) Check for race between commit/rollback and delivery

by Tim Fox (JIRA)

Check for race between commit/rollback and delivery --------------------------------------------------- Key: JBMESSAGING-1331 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1331 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta It is legal for session commit/rollback to be called while a session delivery (predeliver/postdeliver) is occurring - must make sure no race occurs. -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2178) NPE when requesting dashboard as unauthenticated user

by Martin Putz (JIRA)

NPE when requesting dashboard as unauthenticated user ----------------------------------------------------- Key: JBPORTAL-2178 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2178 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.6 Final Reporter: Martin Putz Assignee: Thomas Heute Fix For: 2.6.7 Final As a user who is not logged when I type into my browser the url <host:port>/portal/dashboard or <host:port>/portal/dashboard/<something> I get a HTTP 500 and a stacktrace with a NullPointerException and in the server log the message 2008-09-25 17:36:17,048 ERROR [org.jboss.portal.server.servlet.PortalServlet] Unexpected exception java.lang.NullPointerException at org.jboss.portal.core.model.portal.command.view.ViewContextCommand.execute(ViewContextCommand.java:62) at org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) at org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:123) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:134) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78) ..... -- 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

15 years, 11 months

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