February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3828) spelling mistake in xml tag

by Goran Oberg (JIRA)

spelling mistake in xml tag --------------------------- Key: JBAS-3828 URL: http://jira.jboss.com/jira/browse/JBAS-3828 Project: JBoss Application Server Issue Type: Bug Affects Versions: JBossAS-4.0.4.GA Environment: All Reporter: Goran Oberg Priority: Trivial Just a spelling mistake... Should be <url-delimiter> instead of <url-delimeter> in <ha-local-tx-datasource> -- 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, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-953) wiki not visible

by Sacha Labourey (JIRA)

wiki not visible ---------------- Key: JBPORTAL-953 URL: http://jira.jboss.com/jira/browse/JBPORTAL-953 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: Sacha Labourey deploying wiki.war from portletswap in JBP deploy's folder doesn't make it visible in the list of creatable portlet (admin interface) -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-806) JBM is assuming it can look up system properties on the client side

by Tim Fox (JIRA)

JBM is assuming it can look up system properties on the client side ------------------------------------------------------------------- Key: JBMESSAGING-806 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-806 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP3, 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta2, 1.0.1.SP4 JBM (JMSRemotingConnection) does several System.getProperties() to get the override bind address and port. However in a security restricted environment e.g. jnlp or applet this may not work. This causes an exception to be thrown and the connection is not created. Need to catch the exception and set to null. -- 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, 6 months

5
15
0 / 0

[JBoss JIRA] Created: (HIBERNATE-43) SQL native Request who respond only the first letter

by Alexandre PETRILLO (JIRA)

SQL native Request who respond only the first letter ---------------------------------------------------- Key: HIBERNATE-43 URL: http://jira.jboss.com/jira/browse/HIBERNATE-43 Project: Hibernate Issue Type: Bug Environment: Jboss 4.0.4 G.A. patch 1 Reporter: Alexandre PETRILLO Assigned To: Steve Ebersole I need to do some sql native query (to a data base Oracle 9i) from an EJB session Bean. I use Jboss in version 4.0.4 G.A. patch 1 My simple code : public List doNativeQueryMultiple(String sqlQuery) { List list = manager.createNativeQuery(sqlQuery).getResultList(); return list; } This is some exemple for understand the probleme. SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : O,N SELECT 'TOTO' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : TOTO,NON SELECT 'TOT' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : T,N SELECT 'OUI' val FROM dual union SELECT 'abc' FROM dual Order BY 1 asc Response is : O,a SELECT 'OUI' val FROM dual union SELECT 'abcd' FROM dual Order BY 1 asc Response is : OUI,abcd SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOT' FROM dual Order BY 1 asc Response is : O,N,T SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOTO' FROM dual Order BY 1 asc Response is : OUI,NON,TOTO When the response of the request is correct, the return class type is java.lang.String And when is incorrect , the return class type is java.lang.Charactere, and the response contain the first letter. The bug is when the size of all of the selected string have the same length. The test done by Jboss for determine the class return type maybe is wrong. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-887) Testsuite's HttpUtils assumes Tomcat is listening on localhost

by Brian Stansberry (JIRA)

Testsuite's HttpUtils assumes Tomcat is listening on localhost -------------------------------------------------------------- Key: EJBTHREE-887 URL: http://jira.jboss.com/jira/browse/EJBTHREE-887 Project: EJB 3.0 Issue Type: Task Reporter: Brian Stansberry Priority: Minor org.jboss.ejb3.test.servlet.unit.HttpUtils creates URLs that point to localhost. Tests using these URLs will fail if the testsuite is run with the server bound to an IP. The class needs to integrate with the test environment to find the proper IP address. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-609) add org.drools.Otherwise as automatically imported class

by Michael Neale (JIRA)

add org.drools.Otherwise as automatically imported class -------------------------------------------------------- Key: JBRULES-609 URL: http://jira.jboss.com/jira/browse/JBRULES-609 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.5 Reporter: Michael Neale Assigned To: Edson Tirelli Fix For: 3.1-m1 this is for the Otherwise() fact for capturing rules not firing. -- 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, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBJMX-103) snmp mib for jsr 77

by Luca Stancapiano (JIRA)

snmp mib for jsr 77 ------------------- Key: JBJMX-103 URL: http://jira.jboss.com/jira/browse/JBJMX-103 Project: JBoss JMX Issue Type: Patch Affects Versions: JBossAS-4.0.1 Environment: not important Reporter: Luca Stancapiano Fix For: JBossAS-5.0 Alpha Attachments: j2ee.mib hi......I send you a j2ee.mib for jsr 77 to testing a future implementation of snmp for jsr 77 -- 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, 6 months

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

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