January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8490) Validate any domain/host/standalone config files we ship

by Brian Stansberry (JIRA)

Validate any domain/host/standalone config files we ship -------------------------------------------------------- Key: JBAS-8490 URL: https://jira.jboss.org/browse/JBAS-8490 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 As part of the testsuite smoke tests, validate any config files we ship. There is already a smoke test that does something like this, but it is validating example files. It should validate the real files. -- 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

15 years

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8408) java.lang.NoClassDefFoundError: com/rsa/cryptoj/c/di using JBoss 6.0.0.M3

by Sasha Matison (JIRA)

java.lang.NoClassDefFoundError: com/rsa/cryptoj/c/di using JBoss 6.0.0.M3 ------------------------------------------------------------------------- Key: JBAS-8408 URL: https://jira.jboss.org/browse/JBAS-8408 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: 6.0.0.M3 Environment: JBoss 6.0.0.M3, Windows 2003 R2 SP2. Reporter: Sasha Matison Assignee: Scott M Stark Priority: Critical Our application uses RSA crypto-j version 4.1. When executing a transaction we get the following error: java.lang.NoClassDefFoundError: com/rsa/cryptoj/c/di Although the class is present in the jar file (see attached screenshot). A sample .war that reproduces the problem is attached. -- 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

15 years

5
12
0 / 0

[JBoss JIRA] Created: (JBRULES-2660) withdrawing BRMS patches

by y y (JIRA)

withdrawing BRMS patches ------------------------ Key: JBRULES-2660 URL: https://jira.jboss.org/browse/JBRULES-2660 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 5.1.0.FINAL Reporter: y y Assignee: Mark Proctor Hi, For several reasons, I decided to withdraw those contributions introduced from my spare time. Please ensure that the following codes from me are removed from the upstream code repository, any further versions, and any RedHat proprietary code repository. https://jira.jboss.org/browse/BRMS-145 https://jira.jboss.org/browse/BRMS-226 https://jira.jboss.org/browse/BRMS-230 https://jira.jboss.org/browse/JBRULES-2008 https://jira.jboss.org/browse/JBRULES-2010 https://jira.jboss.org/browse/JBRULES-2280 https://jira.jboss.org/browse/JBRULES-2231 More specifically, please remove all of them: /drools-guvnor/src/main/java/org/drools/guvnor/client/messages/Constants_ja_JP.properties /drools-compiler/src/test/java/org/drools/compiler/MultibyteDSLTest.java /drools-compiler/src/test/resources/org/drools/compiler/multibyte-utf8.dsl /drools-compiler/src/test/resources/org/drools/compiler/multibyte-utf8.dslr https://jira.jboss.org/secure/attachment/12325927/javadialecti18n.patch -- 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

15 years

2
11
0 / 0

[JBoss JIRA] Created: (JGRP-1007) Flush: change signature of JChannel#startFlush to include checked exception

by Vladimir Blagojevic (JIRA)

Flush: change signature of JChannel#startFlush to include checked exception --------------------------------------------------------------------------- Key: JGRP-1007 URL: https://jira.jboss.org/jira/browse/JGRP-1007 Project: JGroups Issue Type: Task Affects Versions: 2.6, 2.8 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 3.0 We have to change signature of startFlush method to include checked exceptions in its signature. We have previously relied on boolean return value of startFlush to get information about success of startFlush method invocation. This approach has been proven to be insufficient, particularly in the light of dealing with [JGRP-985]. We need to discriminate various reasons why startFlush failed, i.e due flush collision, missing response from flush member and so on. Therefore, starting with release 3.0 startFlush method will be void and will throw checked exceptions. -- 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

15 years

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8776) "Failed to resolve Java binding" for jboss-web.xml version 6.0

by Frank Langelage (JIRA)

"Failed to resolve Java binding" for jboss-web.xml version 6.0 -------------------------------------------------------------- Key: JBAS-8776 URL: https://issues.jboss.org/browse/JBAS-8776 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.Final Reporter: Frank Langelage Assignee: Ales Justin I changed my jboss-web.xml file like to use the current xsd: <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_6_0.xsd" version="6.0"> <security-domain>java:/jaas/mbisso</security-domain> </jboss-web> This leads to the following Exception / Stacktrace: 15:05:21,665 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=vfs:///mbi/tools/jboss/6.01/server/mbi/deploy/web-mbi2e-lafr-sb2000-ipc.war state=PreParse mode=Manual requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfs:///mbi/tools/jboss/6.01/server/mbi/deploy/web-mbi2e-lafr-sb2000-ipc.war at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:383) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343) [:2.2.0.GA] at org.jboss.deployment.JBossWebAppParsingDeployer.createMetaData(JBossWebAppParsingDeployer.java:99) [:6.0.1-SNAPSHOT] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:315) [:2.2.0.GA] at org.jboss.deployment.JBossWebAppParsingDeployer.createMetaData(JBossWebAppParsingDeployer.java:80) [:6.0.1-SNAPSHOT] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:255) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.1-SNAPSHOT] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_23] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_23] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_23] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_23] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_23] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: java.lang.Exception: Failed to resolve Java binding for /mbi/tools/jboss/6.01/server/mbi/deploy/web-mbi2e-lafr-sb2000-ipc.war/WEB-INF/jboss-web.xml (check the SchemaBinding resolver configuration) at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:259) [jbossxb.jar:2.0.3.GA] at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:231) [jbossxb.jar:2.0.3.GA] at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137) [:2.2.0.GA] at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121) [:2.2.0.GA] at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:352) [:2.2.0.GA] at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:334) [:2.2.0.GA] at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:251) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:369) [:2.2.0.GA] ... 43 more Then I used Altova XmSpy to validate my jboss-web.xml file online. It says that jboss-web_6_0.xsd is invalid, because it includes jboss-common_6_0.xsd which cannot be found. BTW: The documentation within the boss-web_6_0.xsd document says: "The deployment descriptor must be named "META-INF/jboss-web.xml" in the WAR file." In assume this still should be placed under WEB-INF for a war file. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

6
12
0 / 0

[JBoss JIRA] Created: (JBAS-7950) HornetQ keeps re-delivering the message infinitely on a failure to deliver to MDB

by jaikiran pai (JIRA)

HornetQ keeps re-delivering the message infinitely on a failure to deliver to MDB ---------------------------------------------------------------------------------- Key: JBAS-7950 URL: https://jira.jboss.org/jira/browse/JBAS-7950 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (HornetQ) Environment: AS trunk (hornetq 2.1.0 Beta2) Reporter: jaikiran pai Assignee: Clebert Suconic As discussed in the referenced forum thread, when HornetQ first fails to deliver a message to a MDB, it continues to redeliver the message infinitely. Also note that the JMS Message.getJMSRedelivered() is also broken - it keeps returning false even on a redelivered message. -- 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

15 years

8
36
0 / 0

[JBoss JIRA] Created: (JBAS-8817) Service POJO deployment throws NullPointerException

by Devinder Singh (JIRA)

Service POJO deployment throws NullPointerException --------------------------------------------------- Key: JBAS-8817 URL: https://issues.jboss.org/browse/JBAS-8817 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers, Weld/CDI Affects Versions: 6.0.0.CR1 Environment: RedHat Linux 5.5 Reporter: Devinder Singh Assignee: Ales Justin I have a very simple test service POJO that I'm trying to deploy to JBoss AS 6 on Linux. But it's failing with below exception: Java code for the test can be obtained from the forum link: http://community.jboss.org/message/581413 14:42:21,599 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:ear=foliage.ear,jar=foliageEJB.jar,name=CoolSystemInitService,service=EJB3 state=Configured: java.lang.NullPointerException at org.jboss.weld.integration.instantiator.Jsr299BeanInstantiator.locateWeldManager(Jsr299BeanInstantiator.java:102) [:6.0.0.20101110-CR1] at org.jboss.weld.integration.instantiator.Jsr299BeanInstantiator.getWeldManager(Jsr299BeanInstantiator.java:93) [:6.0.0.20101110-CR1] at org.jboss.weld.integration.instantiator.Jsr299BeanInstantiator.create(Jsr299BeanInstantiator.java:72) [:6.0.0.20101110-CR1] at org.jboss.ejb3.EJBContainer.construct(EJBContainer.java:997) [:1.6.3] at org.jboss.ejb3.service.ServiceContainer.create(ServiceContainer.java:205) [:1.6.3] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_21] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_21] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_21] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_21] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.Alpha9] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-8193) Clustering configuration object model

by Brian Stansberry (JIRA)

Clustering configuration object model ------------------------------------- Key: JBAS-8193 URL: https://jira.jboss.org/browse/JBAS-8193 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 Object model that represents the clustering subsystem configuration schema. -- 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

15 years

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8207) mod_cluster subsystem configuration schema

by Brian Stansberry (JIRA)

mod_cluster subsystem configuration schema ------------------------------------------ Key: JBAS-8207 URL: https://jira.jboss.org/browse/JBAS-8207 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Domain Management, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Jean-Frederic Clere Fix For: 7.0.0.M1 Domain model configuration schema for mod_cluster subsystem. -- 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

15 years

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8181) Clustering configuration schema

by Brian Stansberry (JIRA)

Clustering configuration schema ------------------------------- Key: JBAS-8181 URL: https://jira.jboss.org/browse/JBAS-8181 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 Domain model configuration for clustering. Clustering integration won't happen until M2, but the configuration schema should be largely worked out by M1. -- 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

15 years

3
5
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 January 2011