May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4407) Fix the compatibility testsuite

by Dimitris Andreadis (JIRA)

Fix the compatibility testsuite ------------------------------- Key: JBAS-4407 URL: http://jira.jboss.com/jira/browse/JBAS-4407 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Priority: Blocker Fix For: JBossAS-4.2.0.GA The compatibility testsuite is failing because of the jboss remoting upgrade. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4416) Introduce compatibility tests for interoperating with older jboss versions using the legacy rmi invokers

by Dimitris Andreadis (JIRA)

Introduce compatibility tests for interoperating with older jboss versions using the legacy rmi invokers -------------------------------------------------------------------------------------------------------- Key: JBAS-4416 URL: http://jira.jboss.com/jira/browse/JBAS-4416 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Build System Affects Versions: JBossAS-4.2.0.GA Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.1.CR1 Complete the work reported in the parent issue, i.e. introduce tests for verifying the interoperability of jboss 4.2.x with all the older versions over the legacy rmi invokers. -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBFORUMS-217) Change SummaryView

by Ryszard Kozmik (JIRA)

Change SummaryView ------------------ Key: JBFORUMS-217 URL: http://jira.jboss.com/jira/browse/JBFORUMS-217 Project: JBoss Forums Issue Type: Sub-task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC SummaryView has to be rewritten to new design. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4444) The invoker-proxy-binding in the base container configuration is ignored on sub-configurations.

by Dimitris Andreadis (JIRA)

The invoker-proxy-binding in the base container configuration is ignored on sub-configurations. ----------------------------------------------------------------------------------------------- Key: JBAS-4444 URL: http://jira.jboss.com/jira/browse/JBAS-4444 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.2.0.GA, JBossAS-4.0.5.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.1.CR1 When overriding a container configuration, without specifying an explicit invoker-proxy-binding-name e.g. <container-configurations> <container-configuration extends="Standard CMP 2.x EntityBean"> <container-name>CMP 2.x and Cache</container-name> <commit-option>A</commit-option> </container-configuration> </container-configurations> Then, instead of deriving it from the base configuration invoker-proxy-binding-name (since we are extending it), it falls back to whatever is the hardcoded default, e.g. for entity beans in 4.2.x it is: public class EntityMetaData extends BeanMetaData { ... public static final String DEFAULT_ENTITY_INVOKER_PROXY_BINDING = "entity-unified-invoker"; -- 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, 2 months

1
1
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, 2 months

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

3
7
0 / 0

[JBoss JIRA] Created: (JBRULES-874) Allow direct property access to pattern bound variables

by Edson Tirelli (JIRA)

Allow direct property access to pattern bound variables ------------------------------------------------------- Key: JBRULES-874 URL: http://jira.jboss.com/jira/browse/JBRULES-874 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assigned To: Edson Tirelli Allow the usage of direct property access for pattern bound variables. Example: rule "test auto bindings 1" when $p : Person(); $c : Cheese( type == $p.likes, price == $c.price ) then results.add( $p ); 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, 2 months

1
1
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, 2 months

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

3
6
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-402) Update the EJB3 example so it work with the latest EJB3 release.

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-402?page=all ] Tim Fox closed JBMESSAGING-402. ------------------------------- Resolution: Won't Fix We test only against the version of EJB3 shipped with AS 4.2.0, and it works fine. > Update the EJB3 example so it work with the latest EJB3 release. > ---------------------------------------------------------------- > > Key: JBMESSAGING-402 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-402 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR2 > Reporter: Ovidiu Feodorov > Fix For: 1.4.1.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Currently, it works with EJB 3.0 RC5 - PFD , but seems to break for EJB 3.0 RC7 - FD -- 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, 2 months

1
0
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 May 2007