January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-401) add ability to lock a node to prevent concurrent editing

by Michael Neale (JIRA)

add ability to lock a node to prevent concurrent editing -------------------------------------------------------- Key: JBRULES-401 URL: http://jira.jboss.com/jira/browse/JBRULES-401 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben -- 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

17 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3544) org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable

by Jaroslaw Kijanowski (JIRA)

org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable ------------------------------------------------------------------------------------------------------------ Key: JBAS-3544 URL: http://jira.jboss.com/jira/browse/JBAS-3544 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Environment: win xp Reporter: Jaroslaw Kijanowski Fix For: JBossAS-5.0.0.Beta org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails because the services jbossweb-tomcat55.sar and jboss-aop.deployer can't be registered, becasue in JB5.0 they changed their names to jbossweb-tomcat6.sar and jboss-aop-jdk50.deployer. FIX: change testsuite/src/main/org/jboss/test/management/test/DeploymentDescriptorUnitTestCase.java . . . public void testGetSarDescriptor() throws Exception { // String moduleName = "jbossweb-tomcat55.sar"; String moduleName = "jbossweb-tomcat6.sar"; . . . public void testGetDeployerDescriptor() throws Exception { // String moduleName = "jboss-aop.deployer"; String moduleName = "jboss-aop-jdk50.deployer"; -- 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

17 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1057) Create/update DTD/schemas for descriptors.

by Chris Laprun (JIRA)

Create/update DTD/schemas for descriptors. ------------------------------------------ Key: JBPORTAL-1057 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1057 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Roy Russo Priority: Minor Fix For: 2.4.1 Final -- 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

17 years, 7 months

7
11
0 / 0

[JBoss JIRA] Created: (JBAS-3918) jbossweb virtual-host processing not working

by Scott M Stark (JIRA)

jbossweb virtual-host processing not working -------------------------------------------- Key: JBAS-3918 URL: http://jira.jboss.com/jira/browse/JBAS-3918 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Scott M Stark Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.Beta2 Add a Host entry to the deployers/jbossweb.deployer/server.xml as described in the 4.0.x section of: http://wiki.jboss.org/wiki/Wiki.jsp?page=VirtualHosts for example: <Host name="succubus-vhost" autoDeploy="false" deployOnStartup="false" deployXML="false"> <Valve className="org.apache.catalina.valves.AccessLogValve" prefix="succubus-vhost" suffix=".log" pattern="common" directory="${jboss.server.home.dir}/log"/> </Host> add a virtual-host entry to the jmx-console.war/WEB-INF/jboss-web.xml: <jboss-web> <virtual-host>succubus-vhost</virtual-host> </jboss-web> and try to access the jmx-console using succubus-vhost: [starksm@succubus Security]$ wget http://succubus-vhost:8080/jmx-console/index.jsp --08:21:41-- http://succubus-vhost:8080/jmx-console/index.jsp => `index.jsp' Resolving succubus-vhost... 192.168.10.10 Connecting to succubus-vhost|192.168.10.10|:8080... connected. HTTP request sent, awaiting response... 400 No Host matches server name succubus-vhost 08:21:41 ERROR 400: No Host matches server name succubus-vhost. -- 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

17 years, 8 months

7
10
0 / 0

[JBoss JIRA] Created: (JBAS-3654) The deploy dependency fails between WAR of one EAR and EJB of the other EAR.

by Sakthi Samabsivam (JIRA)

The deploy dependency fails between WAR of one EAR and EJB of the other EAR. ---------------------------------------------------------------------------- Key: JBAS-3654 URL: http://jira.jboss.com/jira/browse/JBAS-3654 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.5.CR1, JBossAS-4.0.4.GA, JBossAS-4.0.4RC1, JBossAS-4.0.3 SP1, JBossAS-4.0.3 Final, JBossAS-4.0.3RC2, JBossAS-4.0.3RC1 Reporter: Sakthi Samabsivam Assigned To: Dimitris Andreadis When I try to setup a deployment order between two EARS using depends tag in the Jboss-web.xml of one EAR's WAR with other EAR's EJB component, it fails. for example. I have two ears example1. ear and example2.ear. I want my example1.ear's war file to be deployed after the example2.ear's EJB component is deployed.. So I am wrting this depends tag entry in my example1.ear's WAR compoent jboss-web.xml <depends>jboss.j2ee:url='FiboApp.ear',service=EARDeployment</depends> This depends is working till jboss 4.0.1 It fails in 4.0.3 SP1 , 4.0.4 GA 15:52:24,359 WARN [ServiceController] Problem starting service jboss.web.deploy ment:war=crimeportal.war,id=-1360680885 org.jboss.deployment.DeploymentException: Error during deploy; - nested throwabl e: (javax.security.jacc.PolicyContextException: Operation not allowed) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:366) at org.jboss.web.WebModule.startModule(WebModule.java:68) at org.jboss.web.WebModule.startService(WebModule.java:46) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS upport.java:274) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:230) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:245) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl ler.java:943) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:428) at org.jboss.system.ServiceController.start(ServiceController.java:446) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:245) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy21.start(Unknown Source) at org.jboss.deployment.EARDeployer.start(EARDeployer.java:297) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753) at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept or.java:118) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM BeanOperationInterceptor.java:127) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:245) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen tScanner.java:319) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS canner.java:507) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. doScan(AbstractDeploymentScanner.java:192) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A bstractDeploymentScanner.java:265) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS upport.java:274) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:230) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:245) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl ler.java:943) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:428) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:245) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept or.java:118) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM BeanOperationInterceptor.java:127) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:245) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330) at org.jboss.Main.boot(Main.java:187) at org.jboss.Main$1.run(Main.java:438) at java.lang.Thread.run(Thread.java:595) Caused by: javax.security.jacc.PolicyContextException: Operation not allowed at org.jboss.security.jacc.JBossPolicyConfiguration.validateState(JBossP olicyConfiguration.java:201) at org.jboss.security.jacc.JBossPolicyConfiguration.linkConfiguration(JB ossPolicyConfiguration.java:160) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:347) ... 94 more Caused by: org.jboss.util.state.IllegalTransitionException: No transition for ac tion: linkConfiguration from state:inService at org.jboss.util.state.StateMachine.nextState(StateMachine.java:111) at org.jboss.security.jacc.JBossPolicyConfiguration.validateState(JBossP olicyConfiguration.java:196) ... 96 more 15:52:24,359 INFO [EARDeployer] Started J2EE application: file:/C:/jboss/traini ng/JBossForAdvancedJ2EE/labs/jboss-4.x/server/default/deploy/FiboApp.ear 15:52:24,359 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.web.deployment:war=crimeportal.war,id=-1360680885 State: FAILED Reason: org.jboss.deployment.DeploymentException: Error during deploy; - neste d throwable: (javax.security.jacc.PolicyContextException: Operation not allowed) I Depend On: jboss.j2ee:url='FiboApp.ear',service=EARDeployment --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.web.deployment:war=crimeportal.war,id=-1360680885 State: FAILED Reason: org.jboss.deployment.DeploymentException: Error during deploy; - neste d throwable: (javax.security.jacc.PolicyContextException: Operation not allowed) I Depend On: jboss.j2ee:url='FiboApp.ear',service=EARDeployment -- 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

17 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3591) For SESSION and ATTRIBUTE don't marshal values if UseRegionBasedMarshalling is on

by Brian Stansberry (JIRA)

For SESSION and ATTRIBUTE don't marshal values if UseRegionBasedMarshalling is on --------------------------------------------------------------------------------- Key: JBAS-3591 URL: http://jira.jboss.com/jira/browse/JBAS-3591 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Storing session or attributes in the cache as byte[] or MarshalledValue is unnecessary if region based marshalling is used. Doing it greatly increases the memory footprint of distributed sessions. Need to benchmark the performance impact of this (could be positive or negative), although the memory savings would outweigh all but a major performance loss. Can't do this in Branch_4_0 is it breaks binary compatibility. -- 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

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3914) Thread dumps from ServerInfo MBean do not contain line breaks.

by Darran Lofthouse (JIRA)

Thread dumps from ServerInfo MBean do not contain line breaks. -------------------------------------------------------------- Key: JBAS-3914 URL: http://jira.jboss.com/jira/browse/JBAS-3914 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.5.GA Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.2.0.CR1 Thread dumps from ServerInfo MBean do not contain line breaks, as the output HTML and displayed in a browser this is generally not a problem as the browser formats the output using the HTML tags not based on the presence of line breaks. If users copy the data from the web browser to a text editor as there are no line breaks in the original output the data is pasted to the text editor without breaks which causes everything to be on one line. The ouput thread dumps should have line breaks added to get round this. -- 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

17 years, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys

by Elias Ross (JIRA)

Be able to set the internal ordering of child nodes and data keys ----------------------------------------------------------------- Key: JBCACHE-841 URL: http://jira.jboss.com/jira/browse/JBCACHE-841 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani I believe that this issue is required to resolve JBCACHE-166 satisfactorily. But it would also be a useful (and easily added) feature for JBossCache 2.0. The attached .java file explains two additional methods to add. The internal implementation would likely need to rely on the JDK1.6 java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change to other code that rely on iteration to work on concurrently modified sets. As JDK 1.6 is new, this might require use of http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support from the jbossretro to change these JDK1.6 classes to use the backport for 1.5. -- 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

17 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-941) org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces

by Elias Ross (JIRA)

org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces ---------------------------------------------------------------------------------------------------- Key: JBCACHE-941 URL: http://jira.jboss.com/jira/browse/JBCACHE-941 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani The java.util.Collections utility class supplies useful methods for dealing with legacy interfaces and wrapping collection classes for concurrency, type safety, read-only, etc. In a simiilar vein, I wrote a "Caches" class that returns java.util.Map instances for a Node, which allow data to be modified through the standard Map interface. This I expect to be extremely useful for allowing uses to integrate their existing application with JBoss Cache, and will eliminate some of the confusion of using a new API and they can use the API they know best. Users also often demand an API which is "generic" so that their code is not tied to a particular vendor. There are basically two methods in Caches, one looks like this: Cache cache = DefaultCacheFactory.getInstance().createCache(); Map m = Caches.asMap(cache); m.put("foo", "bar"); The API and examples explain themselves. "Caches" could also include other useful methods for printing or reporting. Note that this functionality could be considered duplicated from PojoCache...) -- 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

17 years, 9 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-789) DelegatingCacheLoader that can use a load balanced proxy

by Brian Stansberry (JIRA)

DelegatingCacheLoader that can use a load balanced proxy -------------------------------------------------------- Key: JBCACHE-789 URL: http://jira.jboss.com/jira/browse/JBCACHE-789 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.2.0 Using cache mode LOCAL and a DelegatingCacheLoader (aka a far-cache) has the potential to be a very performant cluster topology. But, the far cache is a single point of failure. Idea here is to develop an HA proxy to a cluster of far-caches; proxy pins to one far-cache, but can fail over to another if the primary target fails. -- 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

17 years, 9 months

3
9
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 2007