June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1462) Documentation should include a section on how to remove/destroy created objects via the Admin GUI

by Chris Laprun (JIRA)

Documentation should include a section on how to remove/destroy created objects via the Admin GUI ------------------------------------------------------------------------------------------------- Key: JBPORTAL-1462 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1462 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.CR2 Reporter: Chris Laprun Assigned To: Julien Viet Fix For: 2.6 Final -- 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

18 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1521) Missing documentation on properties?

by Chris Laprun (JIRA)

Missing documentation on properties? ------------------------------------ Key: JBPORTAL-1521 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1521 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6 Final Reporter: Chris Laprun Assigned To: Julien Viet Fix For: 2.6.1 Final -- 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

18 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JASSIST-34) Throw a more descriptive exception when a class file does not start with 0xCAFEBABE

by Josh Devins (JIRA)

Throw a more descriptive exception when a class file does not start with 0xCAFEBABE ----------------------------------------------------------------------------------- Key: JASSIST-34 URL: http://jira.jboss.com/jira/browse/JASSIST-34 Project: Javassist Issue Type: Bug Environment: Jboss 4.0.5 GA with EJB3 deployer and IBM DB2 JDBC driver v3.3.54 Reporter: Josh Devins Assigned To: Shigeru Chiba Attachments: server.snipped.log I have deployed an application that is using the IBM DB2 JDBC driver jar version 3.3.54. With the EJB3 deployer installed (since we have EJB3s), some class file in the DB2 jar apparently does not start with 0XCAFEBABE, or "the magic hex code". The EJB3 deployer is using Javassist to examine all of the class files in the jar, but when it hits one of these wonky IBM class files, Javaasisst is throwing an IOException with message "non class file". This is rather useless as the EJB3 deployer then rethrows this IOException as a RuntimeException. I get no info about what class failed, what jar file it was in, etc. Perhaps this is an EJB3 deployer issue, but I believe that Javassist should at least throw a more descriptive exception, and not even an IOException. Or better yet, the EJB3 deployer should not just die and rethrow the RuntimeException, just skip the file! Stepping through the JBoss and Javassist code with my debugger was the only way to figure this out. You can look at the attached stack trace from the server log for the exact files and line numbers. -- 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

18 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4254) Client read timeout setting wanted for HTTP Invoker

by Anders Welen (JIRA)

Client read timeout setting wanted for HTTP Invoker ---------------------------------------------------- Key: JBAS-4254 URL: http://jira.jboss.com/jira/browse/JBAS-4254 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.3 SP1 Reporter: Anders Welen Priority: Minor There is no read timeout setting to prevent client threads from hanging while using the HTTP Invoker. A quick fix (if you are using SUN JVM) is to use the parameter "-Dsun.net.client.defaultReadTimeout=60000". The problem with this solution is that it affects all connection, not just the HTTPInvoker. A solution that works (if Java 5 is used) is to add a call to the method "setReadTimeout(xxx)" on the "conn" variable in the method "invoke()" in "org.jboss.invocation.http.interfaces.Util". (The same problem exists with the standard JRMP Invoker aswell. It's just the Pooled Invoker that has a read timeout) -- 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

18 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4455) LoadBalancePolicy that tries to pin all requests associated with a tx to one server

by Brian Stansberry (JIRA)

LoadBalancePolicy that tries to pin all requests associated with a tx to one server ----------------------------------------------------------------------------------- Key: JBAS-4455 URL: http://jira.jboss.com/jira/browse/JBAS-4455 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Galder Zamarreno Priority: Minor The HA proxies don't allow failover once a tx has reached a server. This can lead to this kind of situation: EJB A deployed on nodes 1 and 2. EJB B deployed on nodes 1 and 2. 1) Start tx, invoke on A.1. 2) Lookup B. 3) Invoke on B. LB policy picks B.2 4) Node 2 is dead for some reason so call fails. 5) Can't fail over because tx context won't allow a failover after a call has reached a server. But, B.1 is fine and is running on the only node the tx has invoked on. :( Approach to improving this. This is based on JRMPInovkerProxyHA methods, but the idea is generic: In invocationHasReachedAServer, instead of storing null as the value, you store the target (key is the tx). In invoke, if there's a tx, you add that target (if there is one) to the invocation as transient metadata The LB policy gets passed the invocation as an arg when it chooses a target (this is already in the API) LB policy checks for the metadata. If there, and that target is in its target list, return that target -- 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

18 years, 6 months

3
12
0 / 0

[JBoss JIRA] Created: (JBRULES-944) Support in Rule Workbench for custom colors

by Andrew (JIRA)

Support in Rule Workbench for custom colors ------------------------------------------- Key: JBRULES-944 URL: http://jira.jboss.com/jira/browse/JBRULES-944 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Environment: Eclipse SDK 3.2.1 Reporter: Andrew Assigned To: Mark Proctor As far as I can find, the Rule Workbench plug-in for eclipse doesn't support custom colors. I use a black background and since the Rule Workbench uses black text, the editor is completely useless to me. Support for changing the colors in the DRL editor would be greatly appreciated. -- 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

18 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBFORUMS-232) Add Italian and German support

by Ryszard Kozmik (JIRA)

Add Italian and German support ------------------------------ Key: JBFORUMS-232 URL: http://jira.jboss.com/jira/browse/JBFORUMS-232 Project: JBoss Forums Issue Type: Task Components: Forum View Layer, Portlet Productization Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC ResourceBundles for those languages have to be added and made simplified like the main one. -- 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

18 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-324) Build.xml in testsuite directory doesn't support multiple JVM argument

by Sunny Chan (JIRA)

Build.xml in testsuite directory doesn't support multiple JVM argument ---------------------------------------------------------------------- Key: JBBUILD-324 URL: http://jira.jboss.com/jira/browse/JBBUILD-324 Project: JBoss Build System Issue Type: Feature Request Components: Targets and Tasks Affects Versions: Repository Build head, Repsository Build Branch_4_0 Environment: Any Reporter: Sunny Chan Priority: Minor We are using the JBoss unit test as part of our JVM verification testsuite. We wanted to be able to invoke tests with multiple JVM options, but it didn't work. If you set parameters via build.sh -Djunit.vm.options with multiple paramters (e.g. -Djunit.vm.options="-d64 -verbose:gc"), it will fail with unrecongized option error. The problem is that in testsuite/build.xml, the junit.vm.options is passed onto junit ant task via <jvmarg value> tag rather then <jvmarg line> tag. The jvmarg line allows multiple JVM options exist in one line. Once I replace all instance of <jvmarg value="${junit.jvm.options}"/> with <jvmarg line="${junit.jvm.options}"/> then the problem goes away. I can provide a patch for this if you want - but I don't know the rules on patches (whether I need to be cleared for contribution) so let me know if you want that. -- 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

18 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-4301) Evaluate replacing FileCacheLoader with JdbmCacheLoader

by Brian Stansberry (JIRA)

Evaluate replacing FileCacheLoader with JdbmCacheLoader ------------------------------------------------------- Key: JBAS-4301 URL: http://jira.jboss.com/jira/browse/JBAS-4301 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Need to establish a relationship with the JDBM guys to see how suitable and supportable it is. -- 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

18 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-378) Research options for testing dependency version ranges

by Paul Gier (JIRA)

Research options for testing dependency version ranges ------------------------------------------------------ Key: JBBUILD-378 URL: http://jira.jboss.com/jira/browse/JBBUILD-378 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: MavenBuild 2007 It would be helpful to be able to automatically run a maven build with each of the valid combinations of dependency versions. For example, if a dependency includes a version range of 1.1, 1.2, and 1.3. We would want to build and test the project using each of these versions to make sure that they all work correctly. Sherriff on the maven forum has worked on something like this for continuum. When we move our automated builds to hudson, maybe we could create something similar to 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

18 years, 6 months

2
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 June 2007