December 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1831) Implement decent shutdown of ConnectionConsumer

by Yong Hao Gao (JIRA)

Implement decent shutdown of ConnectionConsumer ----------------------------------------------- Key: JBMESSAGING-1831 URL: https://jira.jboss.org/browse/JBMESSAGING-1831 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP11 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Priority: Critical Fix For: 1.4.0.SP3.CP12, 1.4.8.GA The JBossConnectionConsumer should track all deliveries and only close its sessions when all deliveries are complete. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
8
0 / 0

[JBoss JIRA] Created: (JGRP-1253) TCPPING: ergononics sets return_entire_cache to false, needs to be overridden

by Bela Ban (JIRA)

TCPPING: ergononics sets return_entire_cache to false, needs to be overridden ----------------------------------------------------------------------------- Key: JGRP-1253 URL: https://jira.jboss.org/browse/JGRP-1253 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.11.1, 2.12 In TCPPING.init(), we set return_entire_cache=true. However, ergonomics can change that to false, in the superclass. SOLUTION: even with ergonomics=true, the decision of TCPPING to set return_entire_cache to true needs to be respected. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8688) I'm using jboss-eap-5.0 server getting the exception when connecting to mssql-ds.xml(mssqldb) org.jboss.resource.adapter.jdbc.WrapperDataSource cannot be cast to javax.sql.DataSource but its working fine in jboss4.2.3GA i didn't getting what happen

by siva Rama krishna Bonepalli (JIRA)

I'm using jboss-eap-5.0 server getting the exception when connecting to mssql-ds.xml(mssqldb) org.jboss.resource.adapter.jdbc.WrapperDataSource cannot be cast to javax.sql.DataSource but its working fine in jboss4.2.3GA i didn't getting what happen --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-8688 URL: https://jira.jboss.org/browse/JBAS-8688 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.GA Environment: windows xp,Eclipse IDE,jboss-eap-5.0,jboss-4.2.3 GA,JDK1.6,1GB RAM,MSSQL 2005,java,jsp,servlets Reporter: siva Rama krishna Bonepalli Fix For: JBossAS-5.0.0.GA Hi all, I'm using jboss-eap-5.0 application server trying to get connection with database using jndi and mssql-ds.xml(in default/deploy) i'm getting exception org.jboss.resource.adapter.jdbc.WrapperDataSource cannot be cast to javax.sql.DataSource in jboss-eap-5.0 but it's fine everything in jboss4.2.3GA,tomcat6.0. could you please give me solution asap.its urgent. i'used jndi like that InitialContext ctx = new InitialContext(); DataSource sd = (DataSource)ctx.lookup(strJNDI); con = sd.getConnection(); -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBAS-8668) All OSGi bundle install code paths must go through deployer chain

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/browse/JBAS-8668?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler commented on JBAS-8668: -------------------------------------- Merge from master waiting on JBAS-8690 > All OSGi bundle install code paths must go through deployer chain > ----------------------------------------------------------------- > > Key: JBAS-8668 > URL: https://jira.jboss.org/browse/JBAS-8668 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: OSGi integration > Reporter: Thomas Diesler > Assignee: Jason Greene > Fix For: 7.0.0.Alpha2 > > > There are multiple code paths paths that install a bundle > Aries JMX install --> BundleContext.install() > DeploymentChain --> DeployerService.deploy(Deployment) > Bundle Hotdeploy --> DeployerService.deploy(Deployment) > OSGi Console --> DeployerService.deploy(Deployment) > BundleContext.install() -> BundleManager.install(Deployment) > DeployerService.deploy(Deployment) --> BundleManager.install(Deployment) > In AS7 all bundle install paths must go through the DeploymentChain -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8689) JNDI namespace doesn't contain beans with inherited business interfaces anymore since 6.0.0.CR1

by Tobias Grundmann (JIRA)

JNDI namespace doesn't contain beans with inherited business interfaces anymore since 6.0.0.CR1 ----------------------------------------------------------------------------------------------- Key: JBAS-8689 URL: https://jira.jboss.org/browse/JBAS-8689 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3, Java EE APIs Affects Versions: 6.0.0.CR1 Environment: java version "1.6.0_18" Reporter: Tobias Grundmann Assignee: Carlo de Wolf Since 6.0.0.CR1 the lookup of EJBs via jndi doesnt' work anymore if the bean itself doesn't "implement" a business interface but inherits it. I''ve tried this with @Local annotated interfaces and both the old JBoss syntax ("appName/beanName/local") and the newly supported (as of 6.0.0.CR1) portable ones ("java:global/appName/moduleName/beanName!InterfaceFQN"). "Implements" here means actually specifying an implements statement at the class definition: @Local interface IBeanA {} @Stateful class BeanA implements IBeanA {} //lookup of BeanA works @Stateful class BeanB extends BeanA {} //lookup of BeanB doesn't work -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7862) Servlet can't reach JNDI standard resources

by Carlo de Wolf (JIRA)

Servlet can't reach JNDI standard resources ------------------------------------------- Key: JBAS-7862 URL: https://jira.jboss.org/jira/browse/JBAS-7862 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Carlo de Wolf Assignee: Remy Maucherat Servlet 3.0 15.2.3 java:global[/<app-name>]/<module-name>!ROOT java:app/<module-name>!ROOT JavaEE 6 EE.5.15 java:app/AppName java:module/ModuleName -- 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

13 years, 4 months

5
15
0 / 0

[JBoss JIRA] Created: (JBAS-7908) Re-enable the NamingServletTestCase once the naming components are integrated into jboss-web

by John Bailey (JIRA)

Re-enable the NamingServletTestCase once the naming components are integrated into jboss-web -------------------------------------------------------------------------------------------- Key: JBAS-7908 URL: https://jira.jboss.org/jira/browse/JBAS-7908 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-6.0.0.M3 Reporter: John Bailey Assignee: John Bailey Fix For: JBossAS-6.0.0.M4 The NamingServletTestCase fails because it is testing functionality that does not currently exist in jboss-web. The test are commented out now, and should be re-enabled when jboss-web correctly uses the naming components. -- 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

13 years, 4 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2010