July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2844) Encoding problem with Flow definition files which contain german characters

by Alex Alvarez (JIRA)

Encoding problem with Flow definition files which contain german characters --------------------------------------------------------------------------- Key: JBRULES-2844 URL: https://issues.jboss.org/browse/JBRULES-2844 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow), drools-eclipse (flow) Affects Versions: 5.1.0.FINAL Reporter: Alex Alvarez Assignee: Mark Proctor The eclipse workflow plugin generates xml files with invalid encoding when german characters are used. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JASSIST-96) Publish javassist to Maven central

by Pete Muir (JIRA)

Publish javassist to Maven central ---------------------------------- Key: JASSIST-96 URL: https://jira.jboss.org/jira/browse/JASSIST-96 Project: Javassist Issue Type: Task Reporter: Pete Muir It would be nice if Javassist were published to Maven central regularly -- 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

14 years, 2 months

4
15
0 / 0

[JBoss JIRA] Created: (JBAS-4526) JBossMQ UIL2 Read/Write Tasks should not be doing initialization

by Adrian Brock (JIRA)

JBossMQ UIL2 Read/Write Tasks should not be doing initialization ---------------------------------------------------------------- Key: JBAS-4526 URL: http://jira.jboss.com/jira/browse/JBAS-4526 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.1.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1 The JBossMQ UIL2 Read/Write tasks both do their stream initialization when each thread starts. This code needs changing such that the streams are allocated before started the threads. Only if all resources can be succesfully allocated should we start the threads. -- 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

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1732) Pooling strategy and configuration information needed at runtime

by Galder Zamarreno (JIRA)

Pooling strategy and configuration information needed at runtime ---------------------------------------------------------------- Key: EJBTHREE-1732 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1732 Project: EJB 3.0 Issue Type: Bug Components: ejb3 Affects Versions: AS 4.2.3.GA Reporter: Galder Zamarreno There needs to be a way at runtime to see what pooling strategy (including configuration options) an EJB3 bean is using. Currently, the only way to see this is by enabling TRACE on org.jboss.ejb3 and making an invocation to that EJB3 bean. -- 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

14 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JGRP-1313) RELAY: bridge multiple sites

by Bela Ban (JIRA)

RELAY: bridge multiple sites ---------------------------- Key: JGRP-1313 URL: https://issues.jboss.org/browse/JGRP-1313 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 The current RELAY (2.12.1) bridges only 2 local clusters (sites). Think about ways to bridge multiple sites, e.g. in a star topology (all sites bridge to a central site, but not to each other), or daisy chaining (a site A bridges to site B, which bridges to site C etc) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1412) ServerEnvironment accepts invalid or non-existent directory configurations

by Thomas Diesler (JIRA)

ServerEnvironment accepts invalid or non-existent directory configurations -------------------------------------------------------------------------- Key: AS7-1412 URL: https://issues.jboss.org/browse/AS7-1412 Project: Application Server 7 Issue Type: Bug Reporter: Thomas Diesler Assignee: Brian Stansberry I tried changing the testsuite/pom.xml to allow tests to override certain AS7 modules, by adding a "testsuite" modules entry to the module.path. It looks like OSGI gets confused by multiple entries in the module path. module.path = /home/smarlow/work/as7/testsuite/compat/target/jbossas:/home/smarlow/work/as7/testsuite/compat/../../build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT/modules server.log http://pastie.org/2278519 that shows what looks like an OSGI error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
11
0 / 0

[JBoss JIRA] Created: (AS7-1217) Deployment fails when deployment-scanner is pointed to UNC path

by James Livingston (JIRA)

Deployment fails when deployment-scanner is pointed to UNC path --------------------------------------------------------------- Key: AS7-1217 URL: https://issues.jboss.org/browse/AS7-1217 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.CR1 Reporter: James Livingston On JBoss 5, you could add an additional deployment directory located via a UNC path (\\computername\share on Windows). On AS 7.0.0.CR1 it detects that a deployment has been added, but fails deployment because a backslash character gets lost between the host and share parts of the path. To reproduce: 1) share a directory on a Windows machine, for example "share" on the machine "host" 2) In standalone.xml, add a deployment-scanner with the path "\\host\share\" (or "\\\\host\\share", escaping the backshashes doesn't make a difference) 3) Put a WAR file in that directory 4) start JBoss It will fail with the error: ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."sample.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."sample.war".STRU CTURE: Failed to process phase STRUCTURE of deployment "sample.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.6.0_24] at java.lang.Thread.run(Unknown Source) [:1.6.0_24] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to mount deployment content at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:82) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more Caused by: java.io.FileNotFoundException: \\hostshare\sample.war (The network path was not found) at java.io.FileInputStream.open(Native Method) [:1.6.0_24] at java.io.FileInputStream.<init>(Unknown Source) [:1.6.0_24] at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:55) at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:238) at org.jboss.vfs.VFS.mountZipExpanded(VFS.java:567) at org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:73) at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:78) ... 6 more 05:47:04,303 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "sample.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"sample.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"sample.war\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"sample.war\""}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2197) Two WARs containing no-local-view EJBs with same name fails to deploy

by Nicklas Karlsson (JIRA)

Two WARs containing no-local-view EJBs with same name fails to deploy --------------------------------------------------------------------- Key: EJBTHREE-2197 URL: https://jira.jboss.org/browse/EJBTHREE-2197 Project: EJB 3.0 Issue Type: Bug Reporter: Nicklas Karlsson Both try to bind to the same JNDI name causing the second WAR to fail deployment: 13:49:05,276 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=vfs:///C:/Java/AS/jboss-6.0.0-SNAPSHOT/server/default/deploy/LTK.war$Kirjautumistoiminnot state=Create: javax.naming.NameAlreadyBoundException: no-interface at org.jnp.server.NamingServer.bind(NamingServer.java:209) [:5.0.5.Final] at org.jnp.server.NamingServer.bind(NamingServer.java:167) [:5.0.5.Final] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:652) [:5.0.5.Final] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:613) [:5.0.5.Final] at org.jboss.util.naming.Util.bind(Util.java:105) [jboss-common-core.jar:2.2.17.GA] at org.jboss.util.naming.Util.bind(Util.java:91) [jboss-common-core.jar:2.2.17.GA] at org.jboss.ejb3.nointerface.impl.jndi.SessionAwareNoInterfaceViewJNDIBinder.bindNoInterfaceView(SessionAwareNoInterfaceViewJNDIBinder.java:118) [:] at org.jboss.ejb3.nointerface.impl.jndi.NoInterfaceViewJNDIBinderFacade.onStart(NoInterfaceViewJNDIBinderFacade.java:127) [:] at sun.reflect.GeneratedMethodAccessor336.invoke(Unknown Source) [:1.6.0_20] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_20] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_20] 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] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:894) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:641) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:182) [:2.2.0.Alpha8] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:58) [:2.2.0.Alpha8] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.Alpha8] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1571) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.Alpha8] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha8] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0-SNAPSHOT] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.1.0.Alpha1] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59) [:0.1.0.Alpha1] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.1.0.Alpha1] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94) [:0.1.0.Alpha1] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.1.0.Alpha1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_20] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_20] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20] at java.lang.Thread.run(Thread.java:619) [:1.6.0_20] -- 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

14 years, 2 months

3
15
0 / 0

[JBoss JIRA] Created: (AS7-1415) Allow Arquillian tests to monitor server and deployment status explicitely

by Karel Piwko (JIRA)

Allow Arquillian tests to monitor server and deployment status explicitely -------------------------------------------------------------------------- Key: AS7-1415 URL: https://issues.jboss.org/browse/AS7-1415 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Affects Versions: 7.0.0.Final Reporter: Karel Piwko Assignee: Andrew Rubinger Deployment can be checked via management API using ArquillianServiceObserver at least. The AS monitoring should use management API as well. These objects will be fully accessible in the testsuite. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-9089) Synchronization of servers back to the domain following failed operations

by Brian Stansberry (JIRA)

Synchronization of servers back to the domain following failed operations ------------------------------------------------------------------------- Key: JBAS-9089 URL: https://issues.jboss.org/browse/JBAS-9089 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 Determine strategies for bringing a server back into compliance with the domain following failed operations. Simplest is to restart the server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
12
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 July 2011