March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBFORUMS-163) Performance tests based on jboss.com nukes forums access logs

by Ryszard Kozmik (JIRA)

Performance tests based on jboss.com nukes forums access logs ------------------------------------------------------------- Key: JBFORUMS-163 URL: http://jira.jboss.com/jira/browse/JBFORUMS-163 Project: JBoss Forums Issue Type: Task Components: Forum Test Suite Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Blocker Fix For: 1.1.0 Alpha We need to make sure that JBoss Forums are enough performant before trying to deploy moving all load from jboss.com nukes forums to them. IT should be able to provide nukes forums access logs and basing on them we should be able to create much more realistic load tests. junitperf toolkit with JProfiler might be a good choice for this task. -- 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

19 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-350) Retroweaving does not translate java.util.Timer constructors new in Java5

by Manik Surtani (JIRA)

Retroweaving does not translate java.util.Timer constructors new in Java5 ------------------------------------------------------------------------- Key: JBBUILD-350 URL: http://jira.jboss.com/jira/browse/JBBUILD-350 Project: JBoss Build System Issue Type: Bug Components: JBossRetro Environment: JBoss Retro 1.0.4.GA affected (This version is not in the select box for affected versions!) Reporter: Manik Surtani Assigned To: Paul Gier Java 5 added 2 new constructors to java.util.Timer which aren't retrotranslated at the moment, and causes runtime failures. http://java.sun.com/j2se/1.4.2/docs/api/java/util/Timer.html http://java.sun.com/j2se/1.5.0/docs/api/java/util/Timer.html -- 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

19 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-511) JDBC and Transaction close/cleanup operations should be bullet-proofed JDBCChannelMapper and elsewhere.

by Joel Lindheimer (JIRA)

JDBC and Transaction close/cleanup operations should be bullet-proofed JDBCChannelMapper and elsewhere. ------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-511 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-511 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: Windows Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov I am concerned with object close and wrap.end() methods in JDBCChannelMapper possibly being bypassed if an exception is thrown in the rs.close(), ps.close() blocks (code below is an example of what is currently in the JDBCChannelMapper). JDBCChannelMapper : public DurableSubscription getDurableSubscription(String clientID, String subscriptionName, MessageStore ms, PersistenceManager pm, MemoryManager mm) throws Exception { // Look in memory first DurableSubscription sub = getDurableSubscription(clientID, subscriptionName); if (sub != null) { return sub; } //Now look in the db Connection conn = null; PreparedStatement ps = null; ResultSet rs = null; TransactionWrapper wrap = new TransactionWrapper(); try { conn = ds.getConnection(); ps = conn.prepareStatement(selectDurableSub); (do stuff here... ) return sub; } finally { if (rs != null) { // JL what if it blose up here? rs.close(); } if (ps != null) { // JL or here? ps.close(); } if (conn != null) { // or here? conn.close(); } wrap.end(); } } -- 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

19 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBAOP-351) Intercept Integer and Long bit manipulation methods

by Elias Ross (JIRA)

Intercept Integer and Long bit manipulation methods --------------------------------------------------- Key: JBAOP-351 URL: http://jira.jboss.com/jira/browse/JBAOP-351 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Elias Ross Add support for Integer.bitCount(), etc. appearing in JDK 1.5 -- 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

19 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBBUILD-342) Add support for reading and generating jar files

by Paul Gier (JIRA)

Add support for reading and generating jar files ------------------------------------------------ Key: JBBUILD-342 URL: http://jira.jboss.com/jira/browse/JBBUILD-342 Project: JBoss Build System Issue Type: Feature Request Components: JBossRetro Reporter: Paul Gier Assigned To: Paul Gier Fix For: JBossRetro-1.0.6.GA Add support for translating class files from an input jar to an output jar. This would eliminate the need to generate a classes-retro folder. This would also allow the jar generation to be removed from the retro maven plugin. -- 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

19 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-916) CLONE -JDBCPersistenceManager and JDBCSupport do not close Statements

by jivkoto (JIRA)

CLONE -JDBCPersistenceManager and JDBCSupport do not close Statements --------------------------------------------------------------------- Key: JBMESSAGING-916 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-916 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.GA, 1.2.0.Alpha2 Environment: JBoss 4.0.4 GA, Windows XP + SP2, MS SQL SERVER 2000 Reporter: jivkoto Assigned To: Juha Lindfors Priority: Minor Fix For: 1.0.2.CR1 After starting jboss-messaging configured to use MS SQLServer2000 there a lots of mumbles that there are lots of statements that are left open. 10:38:32,265 WARN [WrappedConnection] Closing a statement you left open, please do your own housekeeping java.lang.Throwable: STACKTRACE The places where the statements are left open are: org.jboss.jms.server.plugin.JDBCChannelMapper#createSchema org.jboss.messaging.core.plugin.JDBCPersistenceManager#createSchema Even if my report is for jboss-messaging 1.0.1.GA I checked the related places in jboss-messaging-1.2.0.Alpha2. And there is code such as conn.createStatement().executeUpdate(statement) too. The places I found it are: org.jboss.jms.server.plugin.JDBCJMSUserManager#insertUserRoleData org.jboss.messaging.core.plugin.JDBCSupport#createSchema Please close the statements. I hope that what I am reporting is useful for you. -- 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

19 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-609) Decide the way to go forward (with or without Remoting)

by Ovidiu Feodorov (JIRA)

Decide the way to go forward (with or without Remoting) ------------------------------------------------------- Key: JBMESSAGING-609 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-609 Project: JBoss Messaging Issue Type: Task Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Alpha2 Conclude the http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971228 discussion thread and make a decision on how to go further: 1. Modify Remoting to include Messaging-specific requirements (asynchronicity, AMQP, etc) 2. Implement our own remoting solution. -- 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

19 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-848) Shutting down messaging with JBoss 4.0.3SP1 standalone fails

by Ovidiu Feodorov (JIRA)

Shutting down messaging with JBoss 4.0.3SP1 standalone fails ------------------------------------------------------------ Key: JBMESSAGING-848 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-848 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical -- 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

19 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-913) ProcessBean.startInstance does not set ProcessInstance.key, causing second process start for any user to fail

by Kevin Klinemeier (JIRA)

ProcessBean.startInstance does not set ProcessInstance.key, causing second process start for any user to fail ------------------------------------------------------------------------------------------------------------- Key: JBPM-913 URL: http://jira.jboss.com/jira/browse/JBPM-913 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2 Reporter: Kevin Klinemeier Assigned To: Tom Baeyens The web console isn't setting the ProcessInstance.key value. This value has a unique constraint across key_ and processdefinition_ To reproduce, either: run against a non-hypersonic database and attempt to create two process instances for any one process definition. or run against hypersonic, writing data to a file. Inspect Process_Instances to see constraint violated by null, which apparently isn't caught by hypersonic. It's not clear to me how to correctly populate this field. -- 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

19 years, 1 month

5
10
0 / 0

[JBoss JIRA] Created: (JBCACHE-832) Develop CacheSPI impl for use in JBoss JMX microkernel

by Brian Stansberry (JIRA)

Develop CacheSPI impl for use in JBoss JMX microkernel ------------------------------------------------------ Key: JBCACHE-832 URL: http://jira.jboss.com/jira/browse/JBCACHE-832 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.GA If we want JBC 2.0 to work in AS 4.2, we'll need a way to construct a CacheSPI via the 4.x microkernel/SARDeployer. Initial thoughts: 1) Create class "CacheSPIWrapper" that implements CacheSPI, plus exposes all the configuration-related mbean attributes from JBC 1.4. This is the class that's used for the "class" attribute of the mbean in the -service.xml file. 2) Class when instantiated also instantiates a Configuration object. When SARDeployer invokes the setters on the legacy mbean attributes, the values are passed through to the Configuration object. 3) In createService(), the Configuration object is passed to DefaultCacheFactory, which returns an instance of the standard CacheSPI impl. CacheSPIWrapper holds a ref to this object for use as a delegate. 4) CacheSPIWrapper implements CacheSPI by delegation to the standard object. If we decide we don't want to support use of JBC 2.0 in 4.2, this task can be closed. -- 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

19 years, 1 month

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