June 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-987) Release 2.4.0.GA

by Ron Sigal (JIRA)

Release 2.4.0.GA ---------------- Key: JBREM-987 URL: http://jira.jboss.com/jira/browse/JBREM-987 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.GA (Pinto) -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4911) MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver

by Luc Texier (JIRA)

MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver -------------------------------------------------------------------------------- Key: JBAS-4911 URL: http://jira.jboss.com/jira/browse/JBAS-4911 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Luc Texier Assigned To: Weston Price After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource <datasources> <local-tx-datasource> <jndi-name>DefaultDS</jndi-name> <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class> <user-name>sa</user-name> <password>jboss</password> <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name> <metadata> <type-mapping>MS SQLSERVER2000</type-mapping> </metadata> </local-tx-datasource> </datasources> during start-up, the following exception is throwed 2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo 2007-10-25 11:26:36,328 WARN [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection. 2007-10-25 11:26:36,328 WARN [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection@9a42ef com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source) at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231) at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341) at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396) -- 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, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JBASPECT-19) Release current-invocation 1.0.0.CR1

by Andrew Lee Rubinger (JIRA)

Release current-invocation 1.0.0.CR1 ------------------------------------ Key: JBASPECT-19 URL: http://jira.jboss.com/jira/browse/JBASPECT-19 Project: JBoss Aspects Issue Type: Task Components: current-invocation Affects Versions: 1.0.0.CR1 Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Critical Required of EJB3 for updated dependency on org.jboss.remoting groupId instead of jboss-remoting:jboss-remoting -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5277) Upgrade jboss remoting to v2.4.0 (from 2.2.2)

by Dimitris Andreadis (JIRA)

Upgrade jboss remoting to v2.4.0 (from 2.2.2) --------------------------------------------- Key: JBAS-5277 URL: http://jira.jboss.com/jira/browse/JBAS-5277 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Remoting Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.CR1 Trying: - <componentref name="jboss/remoting" version="2.2.2.SP4-brew"/> + <componentref name="jboss/remoting" version="2.4.0.Beta2"/> -- 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, 11 months

2
16
0 / 0

[JBoss JIRA] Updated: (JBAS-2870) Separate the HA aspect from the invoker proxy

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2870?page=all ] Brian Stansberry updated JBAS-2870: ----------------------------------- Fix Version/s: (was: JBossAS-5.0.0.CR1) JBossAS-5.0.0.CR2 Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)]) > Separate the HA aspect from the invoker proxy > --------------------------------------------- > > Key: JBAS-2870 > URL: http://jira.jboss.com/jira/browse/JBAS-2870 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.CR2 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Comment from Scott Stark (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926369#3926369) > HA proxy invokers like JRMPInvokerProxyHA should not exist. The only difference between an ha proxy and regular proxy would be an interceptor that selected from the available targets and set the invocation proxy such that the common Invoker proxy was told the transport proxy to use. Even an unclustered proxy could have a recover/ha sematic like blocking until the server is availble with this configuration. HA is an aspect that should not be embedded in the transport specific proxy. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4388) Place all management web applications, web invokers, etc under a common context root

by Jeff Schnitzer (JIRA)

Place all management web applications, web invokers, etc under a common context root ------------------------------------------------------------------------------------ Key: JBAS-4388 URL: http://jira.jboss.com/jira/browse/JBAS-4388 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Console Reporter: Jeff Schnitzer Assigned To: Darran Lofthouse In any enterprise environment, administrative interfaces are blocked from the public even if they require a password; administrative interfaces can only be accessed through the internal network or a SSL-secured VPN. This means the load balancer (or whatever) must block out all the possible management/invocation web apps: /jmx-console /web-console /invoker /jbossmq-httpil These paths sometimes change between JBoss versions without any significant announcement, plus services are occasionally added. This could easily result in unsecured or poorly secured (basic auth) services exposed to the public. Please put all JBoss-provided webapps under a base context that can easily be blocked to the public: /jboss/jmx-console /jboss/web-console /jboss/invoker /jboss/jbossmq-httpil -- 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, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (SECURITY-231) IDTrust : Handle Audit Configuration

by Anil Saldhana (JIRA)

IDTrust : Handle Audit Configuration ------------------------------------ Key: SECURITY-231 URL: http://jira.jboss.com/jira/browse/SECURITY-231 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: stand-alone Affects Versions: 2.0.2.CR2 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.CR3 -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-586) Switch dependency on org.jboss:javassist to javassist:javassist

by Andrew Lee Rubinger (JIRA)

Switch dependency on org.jboss:javassist to javassist:javassist --------------------------------------------------------------- Key: JBAOP-586 URL: http://jira.jboss.com/jira/browse/JBAOP-586 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR10 Reporter: Andrew Lee Rubinger Assigned To: Kabir Khan org.jboss:javassist is a deprecated groupId/artifact currently prohibited by the EJB3 Enforcer. Please change this to javassist:javassist current release. ;) -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-1358) Cache Loader preloading does not happen!

by Manik Surtani (JIRA)

Cache Loader preloading does not happen! ---------------------------------------- Key: JBCACHE-1358 URL: http://jira.jboss.com/jira/browse/JBCACHE-1358 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 2.1.1.GA Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Critical Fix For: 2.1.X Regression on preloading. Cache loader tests appear not to test preloading anymore either. -- 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, 11 months

1
6
0 / 0

[JBoss JIRA] Created: (JBSER-107) Better error reporting when non serializable classes have default empty constructor missing

by Galder Zamarreno (JIRA)

Better error reporting when non serializable classes have default empty constructor missing ------------------------------------------------------------------------------------------- Key: JBSER-107 URL: http://jira.jboss.com/jira/browse/JBSER-107 Project: JBoss Serialization Issue Type: Bug Affects Versions: 1.0.3 GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Seems like JBoss Serialization would throw something like this: Caused by: java.lang.NoClassDefFoundError: org/jaxen/VariableContext at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2365) at java.lang.Class.getDeclaredMethod(Class.java:1907) at org.jboss.serial.classmetamodel.ClassMetaData.lookupMethodOnHierarchy(ClassMetaData.java:101) When a non serializable object that JBoss Serialization tries to serialize does not contain an default empty constructor. Better error reporting is required. -- 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, 11 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2008