December 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6697) provide API in DeploymentManager for specifying which dir the file should be deployed to (e.g. to deploy to farm dir, rather than deploy dir)

by Ian Springer (JIRA)

provide API in DeploymentManager for specifying which dir the file should be deployed to (e.g. to deploy to farm dir, rather than deploy dir) --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-6697 URL: https://jira.jboss.org/jira/browse/JBAS-6697 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Ian Springer Assignee: Emanuel Muckenhuber -- 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, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-6680) Extract Profile Service into its own project

by Jesper Pedersen (JIRA)

Extract Profile Service into its own project -------------------------------------------- Key: JBAS-6680 URL: https://jira.jboss.org/jira/browse/JBAS-6680 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Jesper Pedersen Assignee: Scott M Stark Fix For: JBossAS-6.0.0.Alpha1 Extract the profiler service out of the application server repository into its own project. That way other projects can depend on it. -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-6070) Need an overview of the profile service in the 5.0 docs

by Scott M Stark (JIRA)

Need an overview of the profile service in the 5.0 docs ------------------------------------------------------- Key: JBAS-6070 URL: https://jira.jboss.org/jira/browse/JBAS-6070 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Docs/Administration and Configuration Guide, Docs/Clustering Guide, Docs/Installation and Getting Started Guide Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA There is no mention of the profile service as an abstraction over the 4.x and earlier file system structure in the current guides. It needs to be emphasized that the file system based server profiles will be changing and that edits via the profile service management view will obsolete the original file system deployment content. -- 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, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-5990) ProfileService Repository

by Scott M Stark (JIRA)

ProfileService Repository ------------------------- Key: JBAS-5990 URL: https://jira.jboss.org/jira/browse/JBAS-5990 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ProfileService Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.1.0.CR1 We need to make the profile service repository a proper external spi that can be used during bootstrap, offline operation, ... -- 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, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1797) JBm queue conflict in a cluster environment.

by Marek Baluch (JIRA)

JBm queue conflict in a cluster environment. -------------------------------------------- Key: JBMESSAGING-1797 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1797 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.6.GA Reporter: Marek Baluch Priority: Critical First server starts no problem, but during the second server startup I see the following exception in log: 2010-04-02 10:05:09,668 ERROR [org.jboss.messaging.util.ExceptionUtil] (main) Queue[null, name=B] startService java.lang.IllegalStateException: Channel id map for node 2 already contains binding for queue 5 at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBindingInMemory(MessagingPostOffice.java:2543) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalAddBinding(MessagingPostOffice.java:1980) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBinding(MessagingPostOffice.java:470) at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:126) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322) at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189) at $Proxy38.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1440) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1158) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1179) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1099) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:782) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:775) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java: at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:619) All jBPM queues have their "Clustered" attribute set to "true" and ServerPeerID's are different. Each instance in the cluster uses it's own database schema. Dependencies on "PostOffice" service are defined for each queue. -- 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, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-7046) Support CDI injection into managed Servlet objects

by Pete Muir (JIRA)

Support CDI injection into managed Servlet objects -------------------------------------------------- Key: JBAS-7046 URL: https://jira.jboss.org/jira/browse/JBAS-7046 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Pete Muir Fix For: JBossAS-5.2.0.Beta1 -- 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, 7 months

6
17
0 / 0

[JBoss JIRA] Created: (JBRULES-2820) Add support to drools channels in drools-camel

by Edson Tirelli (JIRA)

Add support to drools channels in drools-camel ---------------------------------------------- Key: JBRULES-2820 URL: https://jira.jboss.org/browse/JBRULES-2820 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assignee: Edson Tirelli Add support to drools channels in drools-camel, so that routes can be created straight from channel definitions. Example: rule X when $st : StockTick( symbol == "RHT" ) then channels["RHT_ticks"].send( $st ); end And in camel, one would simply configure: from( "drools://node/ksession1?channel=RHT_ticks" ).to( "somewhere ); -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWEB-143) ThreadName in AccessLogValve

by Vijayanandraj Amaladoss (JIRA)

ThreadName in AccessLogValve ----------------------------- Key: JBWEB-143 URL: https://jira.jboss.org/jira/browse/JBWEB-143 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossWeb-2.0.0.GA Environment: Jboss 4.2 GA EAP / Any operating system Reporter: Vijayanandraj Amaladoss Assignee: Remy Maucherat Writing the thread name in the access log using "%I" pattern is not supported in Jboss web 2.0 GA. This is implemented in Jboss web 2.1.2 GA. Please refer to thread http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236960' -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBXB-252) config option to warn on parser errors instead of throwing errors

by Alexey Loubyansky (JIRA)

config option to warn on parser errors instead of throwing errors ----------------------------------------------------------------- Key: JBXB-252 URL: https://jira.jboss.org/browse/JBXB-252 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA It might be useful to log a warning instead of terminating parsing with an error if a document doesn't satisfy some schema constraints. The original request is JBAS-8268 -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBXB-256) make warnOnParserErrors getters JavaBean compliant

by Alexey Loubyansky (JIRA)

make warnOnParserErrors getters JavaBean compliant -------------------------------------------------- Key: JBXB-256 URL: https://jira.jboss.org/browse/JBXB-256 Project: JBoss XML Binding (JBossXB) Issue Type: Task Affects Versions: JBossXB-2.0.2.Beta8 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA In Unmarshaller and UnmarshallerFactory the boolean getters look like public boolean getWarnOnParserErrors() while to be JavaBean compliant they should be public boolean isWarnOnParserErrors() -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
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 December 2010