July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1210) Messaging subsystem binds JMS destinations to java:

by jaikiran pai (JIRA)

Messaging subsystem binds JMS destinations to java: --------------------------------------------------- Key: AS7-1210 URL: https://issues.jboss.org/browse/AS7-1210 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.0.0.CR1 Reporter: jaikiran pai As per the discussion in this mail thread http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/002890.html: {quote} 1) Unqualified relative names like "DefaultDS" or "jdbc/DefaultDS" should be qualified relative to "java:comp/env", "java:module/env", or "java:jboss/env", depending on the context. {quote} So in case of JMS destinations configured in the standalone.xml/domain.xml, JNDI entries like these: {code:xml} <jms-destinations> <jms-queue name="testQueue"> <entry name="queue/test"/> </jms-queue> <jms-topic name="testTopic"> <entry name="topic/test"/> </jms-topic> </jms-destinations> {code} should bind under java:jboss/ namespace. Instead, currently the org.jboss.as.messaging.jms.AS7BindingRegistry binds it to java: namespace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (AS7-1419) AbstractClassFactory runs into NullPointerException

by jaikiran pai (JIRA)

AbstractClassFactory runs into NullPointerException --------------------------------------------------- Key: AS7-1419 URL: https://issues.jboss.org/browse/AS7-1419 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.0.0.Final Reporter: jaikiran pai Assignee: David Lloyd {code} Caused by: java.lang.NullPointerException at org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:150) at org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:118) at org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$2.configure(StatelessComponentDescription.java:121) at org.jboss.as.ee.component.ComponentDescription$DefaultFirstConfigurator.configure(ComponentDescription.java:778) at org.jboss.as.ee.component.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:65) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more {code} One scenario where this can happen is if the business interface of a bean is from the JDK. Referenced forum thread has more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1208) poor error message with type in logging

by Bill Burke (JIRA)

poor error message with type in logging --------------------------------------- Key: AS7-1208 URL: https://issues.jboss.org/browse/AS7-1208 Project: Application Server 7 Issue Type: Quality Risk Reporter: Bill Burke Priority: Minor I had a typo in logging config for standalone.xml "TRACEy" instead of "TRACE" I got the obscure message of: 09:26:08,720 WARN [org.jboss.as.controller] Operation ("add") failed - address: ([ ("subsystem" => "logging"), ("periodic-rotating-file-handler" => "FILE") ]) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-9423) Recieving ClassNotFoundException with sqljdbc4.jar using JBoss 6

by Michael Gafron (JIRA)

Recieving ClassNotFoundException with sqljdbc4.jar using JBoss 6 ---------------------------------------------------------------- Key: JBAS-9423 URL: https://issues.jboss.org/browse/JBAS-9423 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Environment: Laptop with Windows 7 Ultimate, x64 Intel Core i7 - 2.3ghz, 16 GB ram, 2048 video card, manufacturer = Lenovo. JBoss 6.0, Eclipse Helios 4.2.3 SP2. Reporter: Michael Gafron Priority: Critical Deploying an EAR file to JBoss 6. If I use eclipse the project starts successfully. If I deploy outside of eclipse (i.e. place .ear in the deploy directory) I receive the following message: ERROR: Deployment "vfs:///C:/work/jboss-6.0.0.Final_LocalCopy/jboss-6.0.0.Final/server/default/deploy/NapersoftCCM_JBOSS60_EAR.ear" is in error due to the following reason(s): java.lang.ClassNotFoundException: sqljdbc4.jar.com.microsoft.sqlserver.jdbc.XAReturnValue The sqljdbc4.jar file is located in the ..\jboss-6.0.0.Final\server\default\lib directory. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1320) Parsing issue in Logging Subsystem - level is required by parser, but not schema

by John Bailey (JIRA)

Parsing issue in Logging Subsystem - level is required by parser, but not schema -------------------------------------------------------------------------------- Key: AS7-1320 URL: https://issues.jboss.org/browse/AS7-1320 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Reporter: John Bailey Assignee: David Lloyd Fix For: 7.0.1.Final There seems to be an issue with the handler element parsing that expects the level and encoding to be defined, but they are both listed as minOccurs="0" in the schema. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-2264) Cannot specify default loadBalancePolicy for Clustered EJB3s

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/EJBTHREE-2264?page=com.atlassian.jira.plu... ] Brad Maxwell updated EJBTHREE-2264: ----------------------------------- Component Fix Version(s): proxy-clustered 1.0.5 (was: proxy-clustered 1.0.4) > Cannot specify default loadBalancePolicy for Clustered EJB3s > ------------------------------------------------------------ > > Key: EJBTHREE-2264 > URL: https://issues.jboss.org/browse/EJBTHREE-2264 > Project: EJB 3.0 > Issue Type: Bug > Components: proxy-clustered > Affects Versions: bom-eap5-1.0.2 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: bom-eap5-1.0.3 > > > Tried using ejb3-interceptors-aop.xml, however it seems you cannot modify @Clustered annotations, since the EJBs already have @Clustered on them. > This file is where the defaults are currently, This file can be modified to allow you to specify the default loadBalancePolicy to be specified and the default sticky load balance policy in the $JBOSS_HOME/server/$PROFILE/deployers/ejb3.deployer/META-INF/ejb3-deployers-jboss-beans.xml > jboss-ejb3-proxy-clustered-1.0.3/src/main/java/org/jboss/ejb3/proxy/clustered/registry/ProxyClusteringRegistry.java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Moved: (EJBTHREE-2264) Cannot specify default loadBalancePolicy for Clustered EJB3s

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/EJBTHREE-2264?page=com.atlassian.jira.plu... ] Brad Maxwell moved JBPAPP-6912 to EJBTHREE-2264: ------------------------------------------------ Project: EJB 3.0 (was: JBoss Enterprise Application Platform) Key: EJBTHREE-2264 (was: JBPAPP-6912) Affects Version/s: bom-eap5-1.0.2 (was: EAP_EWP 5.1.0) Component Fix Version(s): proxy-clustered 1.0.4 Component/s: proxy-clustered (was: Clustering) Security: (was: Public) Fix Version/s: bom-eap5-1.0.3 (was: EAP_EWP 5.1.2) Docs QE Status: (was: NEW) > Cannot specify default loadBalancePolicy for Clustered EJB3s > ------------------------------------------------------------ > > Key: EJBTHREE-2264 > URL: https://issues.jboss.org/browse/EJBTHREE-2264 > Project: EJB 3.0 > Issue Type: Bug > Components: proxy-clustered > Affects Versions: bom-eap5-1.0.2 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: bom-eap5-1.0.3 > > > Tried using ejb3-interceptors-aop.xml, however it seems you cannot modify @Clustered annotations, since the EJBs already have @Clustered on them. > This file is where the defaults are currently, This file can be modified to allow you to specify the default loadBalancePolicy to be specified and the default sticky load balance policy in the $JBOSS_HOME/server/$PROFILE/deployers/ejb3.deployer/META-INF/ejb3-deployers-jboss-beans.xml > jboss-ejb3-proxy-clustered-1.0.3/src/main/java/org/jboss/ejb3/proxy/clustered/registry/ProxyClusteringRegistry.java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-3152) Control of KnowledgeAgent instances

by Burkhard Vogel (JIRA)

Control of KnowledgeAgent instances ----------------------------------- Key: JBRULES-3152 URL: https://issues.jboss.org/browse/JBRULES-3152 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Burkhard Vogel Assignee: Mark Proctor There should be a way limit the number of KA on a server - as I restart test-clients and redeploy my client apps they tend to accumulate. Shouldn't the KA name be unique and any reference to a KA with the same name recover the already created KA? Or shouldn't all KA created by a client app (web or standalone) die when the creating app terminates? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2591) Documentation contains duplicate section (one in use, one dead code)

by Geoffrey De Smet (JIRA)

Documentation contains duplicate section (one in use, one dead code) -------------------------------------------------------------------- Key: JBRULES-2591 URL: https://jira.jboss.org/browse/JBRULES-2591 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-docs-expert Affects Versions: 5.1.0.CR1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.1.0.FINAL The duplicated dead code versions are not published. Find out which are duplicate dead code versions and delete them. For example: Section-What_is_a_Rule_Engine.xml exists twice -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2908) Build: Our parent pom must extend jboss parent pom and do not replicate anything in there

by Geoffrey De Smet (JIRA)

Build: Our parent pom must extend jboss parent pom and do not replicate anything in there ----------------------------------------------------------------------------------------- Key: JBRULES-2908 URL: https://issues.jboss.org/browse/JBRULES-2908 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor <parent> <groupId>org.jboss</groupId> <artifactId>jboss-parent</artifactId> <version>5</version> </parent> More info in http://community.jboss.org/wiki/MavenDeployingaSnapshot -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011