September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7215) Update the XA datasource examples for Mysql, PostgreSQL, DB2, Sybase, Oracle and MSSQL

by Ivo Studensky (JIRA)

Update the XA datasource examples for Mysql, PostgreSQL, DB2, Sybase, Oracle and MSSQL -------------------------------------------------------------------------------------- Key: JBAS-7215 URL: https://jira.jboss.org/jira/browse/JBAS-7215 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Reporter: Ivo Studensky Assignee: Ivo Studensky Priority: Minor Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1 Update, or add a new if there is not any, the XA datasource examples for databases MySQL, PostgreSQL, DB2, Sybase, Oracle and MSSQL. The updates will come from the JBPAPP_5_0 branch, see JBPAPP-2575 . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7214) Port the TS crash recovery tests from JBPAPP_5_0 to Branch_5_x

by Ivo Studensky (JIRA)

Port the TS crash recovery tests from JBPAPP_5_0 to Branch_5_x -------------------------------------------------------------- Key: JBAS-7214 URL: https://jira.jboss.org/jira/browse/JBAS-7214 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: JBossAS-5.2.0.Beta1 Porting the JBossTS crash recovery tests from the JBPAPP_5_0 branch (EAP5) to the Branch_5_x. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWEB-101) Thread handle leak using Jboss Web native connectors on Windows

by Mike Poindexter (JIRA)

Thread handle leak using Jboss Web native connectors on Windows --------------------------------------------------------------- Key: JBWEB-101 URL: http://jira.jboss.com/jira/browse/JBWEB-101 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.1 GA Reporter: Mike Poindexter Assigned To: Mladen Turk When running JBossWeb using the native connectors under Windows XP/Win2k3 I'm seeing a Thread Handles leak. I've traced this with the !htrace feature of CDB (like at http://blogs.technet.com/brad_rutkowski/archive/2007/11/13/got-a-handle-l...). It appears as though this is the behavior reported at https://issues.apache.org/bugzilla/show_bug.cgi?id=42728. The native stack trace from the leaked handles looks like: Handle = 0x00000c64 - OPEN Thread ID = 0x00001014, Process ID = 0x00003e44 0x2c2d624c: libapr_1!apr_os_thread_current+0x0000003c 0x2c339202: LIBEAY32!ERR_remove_state+0x00000062 0x7c9011a7: ntdll!LdrInitializeThunk+0x00000029 0x7c919213: ntdll!LdrShutdownThread+0x000000ed 0x7c80c096: kernel32!ExitThread+0x0000003e 0x7c87545b: kernel32!GetConsoleCharType+0x000002a8 0x7c80b683: kernel32!GetModuleFileNameA+0x000001b4 >From what I can tell, the end result is that one thread handle leaks per JVM thread that terminates. Over the course of a long running server application, this becomes a major leak. -- 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

16 years, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (JBREM-1149) Do not include samples in the JAR

by Ondrej Medek (JIRA)

Do not include samples in the JAR --------------------------------- Key: JBREM-1149 URL: https://jira.jboss.org/jira/browse/JBREM-1149 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss AS 5.1.0GA Reporter: Ondrej Medek Priority: Minor We have a Java swing application using session beans. We have to distribute jboss-remoting.jar (1,14MB) to our clients. I have found that when I delete samples from the jboss-remoting.jar, it has only 0,86MB. It saves some download time for our clients behind a thin line. Please, remove the samples and all not-necessary code from the jboss-remoting.jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2455) DTD for Theme Descriptors

by Fernando Ribeiro (JIRA)

DTD for Theme Descriptors ------------------------- Key: JBPORTAL-2455 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2455 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.7.2 Final Reporter: Fernando Ribeiro Like other descriptors, theme descriptors should have a DTD included in the product. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1151) Correct dependency discussion in Chapter 4 of Remoting Guide

by Ron Sigal (JIRA)

Correct dependency discussion in Chapter 4 of Remoting Guide ------------------------------------------------------------ Key: JBREM-1151 URL: https://jira.jboss.org/jira/browse/JBREM-1151 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.3, 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder), 2.2.3.SP1 The discussion is misleading and possibly incorrect. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1152) If MicroSocketClientInvoker gets a SocketException in getConnection(), it should retry

by Ron Sigal (JIRA)

If MicroSocketClientInvoker gets a SocketException in getConnection(), it should retry -------------------------------------------------------------------------------------- Key: JBREM-1152 URL: https://jira.jboss.org/jira/browse/JBREM-1152 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3, 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder), 2.2.3.SP1 If a SocketException is thrown in the main loop in org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(), the invocation will be retried (if "numberOfCallRetries" is set to a value > 1). The same should apply if a SocketConnection is thrown in the preliminary attempt to create a socket. This issue is particularly relevant to the bisocket transport, where the attempt by a callback client to create a socket involves a write on the control connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

1
6
0 / 0

[JBoss JIRA] Closed: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ] Jason T. Greene closed JBAS-7032. --------------------------------- Resolution: Done EAR isolation is now on by default, so this should be resolved. > Getting invalid deployment on what appears to be valid, a webbeans ear file. > ---------------------------------------------------------------------------- > > Key: JBAS-7032 > URL: https://jira.jboss.org/jira/browse/JBAS-7032 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Environment: JBoss AS 5.1 > JDK 1.6 u 13 > OpenSuSe 11.1 / SLES 10.2 > Reporter: John Ament > Assignee: Shelly McGowan > Fix For: JBossAS-5.2.0.Beta1 > > Attachments: jboss-app.xml, PrintResourcePathContextListener.class, PrintResourcePathContextListener.java, WhatUpDawg.ear, WhatUpDawg.ear > > > The best description I can give is from the forum. > Basically, I have an EAR that appears to be completely valid, it's 2 war's and 1 ejb module. It's built using web beans. I get the described stack trace when either deploying via the UI or just dropping the EAR file in deploy. However, I get different results. When I drop the ear in and restart, it loads perfectly (my app) but embedded jopr fails. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7143) Upgrade AS 5.2 to JSF 2.0.0-Beta2

by Stan Silvert (JIRA)

Upgrade AS 5.2 to JSF 2.0.0-Beta2 --------------------------------- Key: JBAS-7143 URL: https://jira.jboss.org/jira/browse/JBAS-7143 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JSF Affects Versions: JBossAS-5.1.0.GA Reporter: Stan Silvert Assignee: Stan Silvert Fix For: JBossAS-5.2.0.Beta1 Upgrade AS 5.2 to JSF 2.0.0-Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-7217) Upgrade JSF to 2.0.0-RC

by Stan Silvert (JIRA)

Upgrade JSF to 2.0.0-RC ----------------------- Key: JBAS-7217 URL: https://jira.jboss.org/jira/browse/JBAS-7217 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1 Reporter: Stan Silvert Assignee: Stan Silvert Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

3
6
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 September 2009