[JBoss JIRA] Commented: (JBAOP-256) java.lang.RuntimeException: defrost(): org.jboss.jms.client.delegate.ClientBrowserDelegate$... was pruned
by Raghu K (JIRA)
[ http://jira.jboss.com/jira/browse/JBAOP-256?page=comments#action_12407316 ]
Raghu K commented on JBAOP-256:
-------------------------------
I think I discovered the cause of the problem. It was due to jar files containing
aopc instrumented classes that were showing up in the aopc task classpath.
Removing these jars from classpath fixed problem.
> java.lang.RuntimeException: defrost(): org.jboss.jms.client.delegate.ClientBrowserDelegate$... was pruned
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBAOP-256
> URL: http://jira.jboss.com/jira/browse/JBAOP-256
> Project: JBoss AOP
> Issue Type: Bug
> Affects Versions: 1.5.0.GA
> Reporter: Ovidiu Feodorov
> Assigned To: Flavia Rainone
> Attachments: antlog.txt, optac-aop.xml.xml
>
>
> Messaging build fails at the AOPC phase if we dont' do a full clean after modifying advised clases.
> An example of exception that is thrown by the AOPC in such cases follows:
> compile-classes:
> [javac] Compiling 1 source file to C:\work\src\cvs\jboss-head\jms\output\classes
> [aopc] java.lang.RuntimeException: defrost(): org.jboss.jms.client.delegate.ClientBrowserDelegate$close_N4742752445160157748 was pruned.
> [aopc] at javassist.CtClassType.checkPruned(CtClassType.java:1093)
> [aopc] at javassist.CtClassType.defrost(CtClassType.java:272)
> [aopc] at org.jboss.aop.instrument.OptimizedInvocations.defrostClassIfExists(OptimizedInvocations.java:66)
> [aopc] at org.jboss.aop.instrument.OptimizedInvocations.makeInvocationClass(OptimizedInvocations.java:96)
> [aopc] at org.jboss.aop.instrument.OptimizedMethodInvocations.createOptimizedInvocationClass(OptimizedMethodInvocations.java:78)
> [aopc] at org.jboss.aop.instrument.OptimizedMethodExecutionTransformer.transformMethod(OptimizedMethodExecutionTransformer.java:59)
> [aopc] at org.jboss.aop.instrument.MethodExecutionTransformer.instrument(MethodExecutionTransformer.java:137)
> [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:654)
> [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:835)
> [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:747)
> [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:345)
> [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:234)
> [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:90)
> [aopc] [error] failed to transform: org.jboss.jms.client.delegate.ClientBrowserDelegate.. Do verbose mode if you want full stack trace.
> [aopc] java.lang.RuntimeException: failed to transform: org.jboss.jms.client.delegate.ClientBrowserDelegate
> [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:728)
> [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:835)
> [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:747)
> [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:345)
> [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:234)
> [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:90)
> [aopc] Caused by: java.lang.RuntimeException: defrost(): org.jboss.jms.client.delegate.ClientBrowserDelegate$close_N4742752445160157748 was pruned.
> [aopc] at javassist.CtClassType.checkPruned(CtClassType.java:1093)
> [aopc] at javassist.CtClassType.defrost(CtClassType.java:272)
> [aopc] at org.jboss.aop.instrument.OptimizedInvocations.defrostClassIfExists(OptimizedInvocations.java:66)
> [aopc] at org.jboss.aop.instrument.OptimizedInvocations.makeInvocationClass(OptimizedInvocations.java:96)
> [aopc] at org.jboss.aop.instrument.OptimizedMethodInvocations.createOptimizedInvocationClass(OptimizedMethodInvocations.java:78)
> [aopc] at org.jboss.aop.instrument.OptimizedMethodExecutionTransformer.transformMethod(OptimizedMethodExecutionTransformer.java:59)
> [aopc] at org.jboss.aop.instrument.MethodExecutionTransformer.instrument(MethodExecutionTransformer.java:137)
> [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:654)
> [aopc] ... 5 more
> [aopc] Exception in thread "main"
> BUILD FAILED
> C:\work\src\cvs\jboss-head\jms\build.xml:339: Java returned: 1
--
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
18 years, 1 month
[JBoss JIRA] Created: (JBAS-5376) Deploying war inside an ear leaks ear's classloader
by Brian Stansberry (JIRA)
Deploying war inside an ear leaks ear's classloader
---------------------------------------------------
Key: JBAS-5376
URL: http://jira.jboss.com/jira/browse/JBAS-5376
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ClassLoading, Deployment services, Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Brian Stansberry
Assigned To: Scott M Stark
If a war is packaged inside an ear, the war's classloader is leaked on undeploy.
>From a JBoss Profiler heap analysis of a ClassloaderLeakUnitTestCase failure:
!--BaseClassLoader@7ba4f9{vfsfile:/C:/dev/jboss/jboss-head/testsuite/output/lib/classloader-leak-simple.ear}
!--!--FieldReference private java.lang.ClassLoader org.jboss.classloader.plugins.loader.ClassLoaderToLoaderAdapter.classLoader=BaseClassLoader@7ba4f9{vfsfile:/C:/dev/jboss/jboss-head/testsuite/output/lib/classloader-leak-simple.ear}
!--!--!--FieldReference private org.jboss.classloader.spi.Loader org.jboss.classloader.spi.ClassLoaderDomain.parent=ClassLoaderDomain@10ed39f{vfsfile:/C:/dev/jboss/jboss-head/testsuite/output/lib/classloader-leak-simple.ear/classloader-leak-simple-ejb.war}
!--!--!--!--FieldReference java.lang.Object java.util.HashMap$Entry.value=vfsfile:/C:/dev/jboss/jboss-head/testsuite/output/lib/classloader-leak-simple.ear/classloader-leak-simple-ejb.war=ClassLoaderDomain@10ed39f{vfsfile:/C:/dev/jboss/jboss-head/testsuite/output/lib/classloader-leak-simple.ear/classloader-leak-simple-ejb.war}
!--!--!--!--!--arrayRef [Ljava.util.HashMap$Entry;[6] id=@18063131
!--!--!--!--!--!--FieldReference transient java.util.HashMap$Entry[] java.util.HashMap.table={..............}, =ClassLoaderDomain@6c5482{}}
!--!--!--!--!--!--!--FieldReference private java.util.Map org.jboss.classloader.spi.ClassLoaderSystem.registeredDomains=DefaultClassLoaderSystem@8b1a4
I'll create a forum thread and discuss the details of how this occurs there.
--
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
18 years, 1 month
[JBoss JIRA] Created: (JBCACHE-1319) NPE with CacheMode.LOCAL and buddy replication enabled
by Brian Stansberry (JIRA)
NPE with CacheMode.LOCAL and buddy replication enabled
------------------------------------------------------
Key: JBCACHE-1319
URL: http://jira.jboss.com/jira/browse/JBCACHE-1319
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.1.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Priority: Minor
Proving the theory no good deed goes unpunished, the fix for JBCACHE-1311 results in an NPE if a cache is configured for local mode but has BR enabled. Minor issue, as this isn't a meaningful config; just cropped up in an AS unit test one of whose permutations by chance used such a config:
NPE is from ResponseValdityFilter, which passes a null members list to new ArrayList(Collection):
java.lang.NullPointerException
at java.util.ArrayList.<init>(ArrayList.java:133)
at org.jboss.cache.interceptors.DataGravitatorInterceptor$ResponseValidityFilter.<init>(DataGravitatorInterceptor.java:482)
at org.jboss.cache.interceptors.DataGravitatorInterceptor.gravitateData(DataGravitatorInterceptor.java:338)
at org.jboss.cache.interceptors.DataGravitatorInterceptor.remoteBackupGet(DataGravitatorInterceptor.java:286)
at org.jboss.cache.interceptors.DataGravitatorInterceptor.handleGetMethod(DataGravitatorInterceptor.java:184)
at org.jboss.cache.interceptors.DataGravitatorInterceptor.handleGetKeyValueMethod(DataGravitatorInterceptor.java:100)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:58)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.CacheLoaderInterceptor.handleGetKeyValueMethod(CacheLoaderInterceptor.java:146)
at org.jboss.cache.interceptors.ActivationInterceptor.handleGetKeyValueMethod(ActivationInterceptor.java:118)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.PessimisticLockInterceptor.handleGetKeyValueMethod(PessimisticLockInterceptor.java:347)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)
at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:81)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:58)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:456)
at org.jboss.cache.interceptors.TxInterceptor.handleGetKeyValueMethod(TxInterceptor.java:250)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.CacheMgmtInterceptor.handleGetKeyValueMethod(CacheMgmtInterceptor.java:81)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:73)
at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:123)
at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:64)
at org.jboss.cache.invocation.CacheInvocationDelegate.get(CacheInvocationDelegate.java:387)
at org.jboss.web.tomcat.service.session.JBossCacheWrapper.get(JBossCacheWrapper.java:80)
at org.jboss.web.tomcat.service.session.JBossCacheService.loadSession(JBossCacheService.java:312)
at org.jboss.web.tomcat.service.session.JBossCacheManager.loadSession(JBossCacheManager.java:1189)
at org.jboss.web.tomcat.service.session.JBossCacheManager.findSession(JBossCacheManager.java:933)
at org.jboss.test.cluster.defaultcfg.simpleweb.test.SessionCountUnitTestCase.createAndUseSession(SessionCountUnitTestCase.java:951)
at org.jboss.test.cluster.defaultcfg.simpleweb.test.SessionCountUnitTestCase.standaloneWarRedeployTest(SessionCountUnitTestCase.java:695)
at org.jboss.test.cluster.defaultcfg.simpleweb.test.SessionCountUnitTestCase.testStandaloneRestart(SessionCountUnitTestCase.java:673)
One fix is to check for null in the ResponseValidityFilter constructor. Probably better is to detect the CacheMode.LOCAL and don't initialize the whole BR subsystem.
--
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
18 years, 1 month
[JBoss JIRA] Created: (JBRULES-1547) missing pom file
by Gerta (JIRA)
missing pom file
----------------
Key: JBRULES-1547
URL: http://jira.jboss.com/jira/browse/JBRULES-1547
Project: JBoss Drools
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Affects Versions: 4.0.4
Reporter: Gerta
Assigned To: Mark Proctor
Priority: Minor
I tried to buld the source with Maven, but got this mistake:
C:\>mvn -Declipse -Ddocumentation clean install -DlocalEclipseDrop=C:\DOCS\JBossBusinessRules\local-eclipse-drop-mirror -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one.
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Sun Apr 06 22:18:33 CEST 2008
[INFO] Final Memory: 1M/2M
[INFO] ------------------------------------------------------------------------
--
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
18 years, 1 month
[JBoss JIRA] Created: (JBCOMMON-49) Update serialVersionUIDs
by Scott M Stark (JIRA)
Update serialVersionUIDs
------------------------
Key: JBCOMMON-49
URL: http://jira.jboss.com/jira/browse/JBCOMMON-49
Project: JBoss Common
Issue Type: Task
Security Level: Public (Everyone can see)
Components: common-core
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: 2.2.5.GA
Change set http://fisheye.jboss.com/changelog/JBossCommon/?cs=2787 included setting a number of implicit serialVersionUIDs to 1. These should match the 4.2.2 version. Running the attached serial.sh script from wthin the 4.2.2.GA client directory produces:
valkyrie:client starksm$ sh serial.sh
org.jboss.net.sockets.RMIMultiSocketClient: static final long serialVersionUID = -945837789475428529L;
org.jboss.util.LongCounter: static final long serialVersionUID = 1615297462859270139L;
org.jboss.util.LongCounter$1: static final long serialVersionUID = 8903330696503363758L;
org.jboss.util.LongCounter$2: static final long serialVersionUID = -8902748795144754375L;
org.jboss.util.LongCounter$3: static final long serialVersionUID = 2584758778978644599L;
org.jboss.util.LongCounter.Wrapper: static final long serialVersionUID = 6720507617603163762L;
org.jboss.util.Null: static final long serialVersionUID = -403173436435490144L;
org.jboss.util.UnexpectedThrowable: static final long serialVersionUID = 4318032849691437298L;
org.jboss.util.NoSuchMethodException: static final long serialVersionUID = -3044955578250977290L;
org.jboss.util.NestedError: static final long serialVersionUID = -4135571897343827853L;
org.jboss.util.NullArgumentException: static final long serialVersionUID = -2308503249278841584L;
org.jboss.util.UnreachableStatementException: static final long serialVersionUID = -6741968131968754812L;
org.jboss.util.NestedSQLException: static final long serialVersionUID = -8348882503434035185L;
org.jboss.util.deadlock.ApplicationDeadlockException: static final long serialVersionUID = -908428091244600395L;
org.jboss.util.NestedException: static final long serialVersionUID = 7003381223684751953L;
org.jboss.util.property.PropertyException: static final long serialVersionUID = 452085442436956822L;
org.jboss.util.property.PropertyEvent: static final long serialVersionUID = -5007209897739884086L;
org.jboss.util.property.PropertyContainer: static final long serialVersionUID = -3347198703863412326L;
org.jboss.util.property.PropertyError: static final long serialVersionUID = -4956548740655706282L;
org.jboss.util.platform.PID: static final long serialVersionUID = -6837013326314943907L;
org.jboss.util.NestedRuntimeException: static final long serialVersionUID = 9017248167673450852L;
org.jboss.util.collection.CollectionException: static final long serialVersionUID = 1470947618739421094L;
Class org.jboss.util.collection.LazyList not found.
Class org.jboss.util.collection.LazyMap not found.
org.jboss.util.collection.SerializableEnumeration: static final long serialVersionUID = 8678951571196067510L;
org.jboss.util.collection.ListSet: static final long serialVersionUID = 7333619218072079496L;
org.jboss.util.collection.EmptyCollectionException: static final long serialVersionUID = -4562591066479152759L;
Class org.jboss.util.collection.LazySet not found.
org.jboss.util.collection.FullCollectionException: static final long serialVersionUID = -1795773071357559465L;
org.jboss.util.collection.CompoundKey: static final long serialVersionUID = -1181463173922935047L;
org.jboss.util.StopWatch: static final long serialVersionUID = 4628094303187435707L;
org.jboss.util.StopWatch.Wrapper: static final long serialVersionUID = 6859401939735540773L;
Class org.jboss.util.StopWatch.Wrapper$1 not found.
org.jboss.util.state.IllegalTransitionException: static final long serialVersionUID = -3392564168782896452L;
org.jboss.util.NotImplementedException: static final long serialVersionUID = -3915801189311749818L;
org.jboss.util.EmptyStringException: static final long serialVersionUID = -7958716001355854762L;
org.jboss.util.id.VMID: static final long serialVersionUID = -4339675822939194520L;
org.jboss.util.HashCode: static final long serialVersionUID = 2391396931740264021L;
org.jboss.util.Counter: static final long serialVersionUID = 7736259185393081556L;
org.jboss.util.Counter$1: static final long serialVersionUID = -6024309396861726945L;
org.jboss.util.Counter$2: static final long serialVersionUID = 2161377898611431781L;
org.jboss.util.Counter$3: static final long serialVersionUID = -4683457706354663230L;
org.jboss.util.Counter.Wrapper: static final long serialVersionUID = -1803971437884946242L;
Class org.jboss.util.xml.catalog.CatalogException not found.
org.jboss.util.threadpool.ThreadPoolStoppedException: static final long serialVersionUID = 8732248855455909385L;
org.jboss.util.threadpool.TaskStoppedException: static final long serialVersionUID = -5166095239829218680L;
org.jboss.util.threadpool.StartTimeoutException: static final long serialVersionUID = 2287779538710535096L;
org.jboss.util.threadpool.ThreadPoolFullException: static final long serialVersionUID = -1044683480627340299L;
--
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
18 years, 1 month
[JBoss JIRA] Created: (JBAS-4815) UnifiedInvokerProxyHA - Client instance check and assignment should be atomic
by Galder Zamarreno (JIRA)
UnifiedInvokerProxyHA - Client instance check and assignment should be atomic
-----------------------------------------------------------------------------
Key: JBAS-4815
URL: http://jira.jboss.com/jira/browse/JBAS-4815
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Remoting
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
I have realised that UnifiedInvokerProxy/UnifiedInvokerProxyHA maintain a instance reference to
the InvokerLocator/Client instances to a specific invocation is using. That is, when a new target is
chosen, the unified proxy updates its Client and corresponding InvokerLocator instances (if they've
changed), and uses the Cient instance variable to make the call. As far as I can see there's no
synchronisation in the usage/assignment of Client or InvokerLocator. Proxies are meant to be thread
safe which means that multiple client app threads could be using the same proxy without any problems.
I can see all this going wrong the moment someone uses client proxies this way in a clustered
environment with round robin load balance policy. We've got no guarantee that round robin will work
correctly in these situations.
Several solutions have been discussed in
--
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
18 years, 1 month