March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJMX-106) "Getting started with JBoss 3.2 [PDF]" link points to invalid location

by Micah Modell (JIRA)

"Getting started with JBoss 3.2 [PDF]" link points to invalid location ---------------------------------------------------------------------- Key: JBJMX-106 URL: http://jira.jboss.com/jira/browse/JBJMX-106 Project: JBoss JMX Issue Type: Bug Affects Versions: JBossAS-4.0.0 Environment: JBoss AS 4.0.1 sp1 on Windows Reporter: Micah Modell The topmost link on the JMX console page that reads "Getting started with JBoss 3.2 [PDF]" points to http://www.jboss.org/modules/html/docs/jbossj2ee.pdf which is no longer accessible and renders a 404 Error to the user. -- 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: (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: (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

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

17 years, 2 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-4028) nosuchmethoderror

by tony anecito (JIRA)

nosuchmethoderror ----------------- Key: JBAS-4028 URL: http://jira.jboss.com/jira/browse/JBAS-4028 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows 2000 Professional JDK 1.6.0 Reporter: tony anecito 21:10:46,843 ERROR [[/invoker]] Exception sending context initialized event to l istener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigure Listener java.lang.NoSuchMethodError: javax.servlet.ServletContext.getContextPath()Ljava/ lang/String; at com.sun.faces.config.WebConfiguration.getServletContextName(WebConfig uration.java:191) -- 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: (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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3945) RunAs Causes Unexpected Principal Propagation Switch

by Stefan Schulze (JIRA)

RunAs Causes Unexpected Principal Propagation Switch ---------------------------------------------------- Key: JBAS-3945 URL: http://jira.jboss.com/jira/browse/JBAS-3945 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA Environment: JBoss 4.0.5.GA JSE 1.5.0_09 Reporter: Stefan Schulze Assigned To: Scott M Stark Attachments: runAsError.zip My application is using JAAS authentication on web and ejb side. An authenticated user calls a stateless session bean from the web application which uses 'runAs' to change security role and calls a second stateless session bean. The second bean recuperates an 'anonymous' principal but it should be the authenticated user. This does not happen on our production server (JBoss 3.2.7) but on JBoss 4.05.GA. Test case: I try to attach my test case (where can I attach it ???) which boils down the problem. To run it, please - unzip the file (runAsError.zip) - you can import the content as a project in Eclipse if you prefer - change the 'jboss.dist' property in the 'ant.properties' file to your jBoss 4.0.5.GA installation - run the 'install' target of 'build.xml' which creates a new jboss container called 'runAsError' - start the 'runAsError' container (run -c runAsError) - run the 'test' target of 'build.xml' What happens: Standalone client calls Session1.hello() with caller principal 'max' . Session1 calls Session2.hello2() using runAs 'internal'. Session2 should get caller principal 'max' but gets 'anonymous'. See Exception that is thrown in SessionBean2.hello2(). It seems to be a different bug than http://jira.jboss.com/jira/browse/JBAS-1852 since I run the JBAS-1852 test and it seemed to work (I had some troubles with the DatabaseServerLoginModule that were probably related to my incompetence ;-). -- 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

5
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-752) Create safe mode where session concurrent access is checked

by Tim Fox (JIRA)

Create safe mode where session concurrent access is checked ----------------------------------------------------------- Key: JBMESSAGING-752 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-752 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 As per JMS spec, a JMS session is supposed to be only accessed from one thread at a time. This is so the implementor does not have to synchronize access which might degrade performance. However, users are often unaware of this and use the session concurrent by multiple threads, resulting in subtle or hard to identify bugs. We should create a "safeMode", where if enabled, concurrent access is checked. safeMode should be turned on for development and off for production, so no performance penalty is incurred in production. -- 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
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 March 2007