September 2010 - embjopr-issues - Jboss List Archives

[JBoss JIRA] Created: (EMBJOPR-99) Root node Metrics Trait Values table has inappropriate layout

by Ondrej Žižka (JIRA)

Root node Metrics Trait Values table has inappropriate layout ------------------------------------------------------------- Key: EMBJOPR-99 URL: https://jira.jboss.org/jira/browse/EMBJOPR-99 Project: Embedded Jopr Issue Type: Bug Reporter: Ondrej Žižka The table has 2 rows with 3 rows, making it too wide: Trait Values ---------------------- Hostname: jawa12.englab.brq.redhat.com | OS Name: Linux | OS Version: 2.6.18-92.1.18.el5xen Architecture: amd64 | Distribution Name: Red Hat Enterprise Linux Server | Distribution Version: release 5.3 (Tikanga) Why not simply put it in a single column... -- 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

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-312) Repeated EAR Restart operation: javax.el.PropertyNotFoundException: Property 'statusMessages' not found on type org.jboss.seam.Namespace

by Ondrej Žižka (JIRA)

Repeated EAR Restart operation: javax.el.PropertyNotFoundException: Property 'statusMessages' not found on type org.jboss.seam.Namespace ---------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-312 URL: https://jira.jboss.org/browse/EMBJOPR-312 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.4.0 Environment: EAP 5.1.0.CR1 Reporter: Ondrej Žižka Priority: Minor STR: 1) Using the console, deploy an ear (e.g. the attached one) 2) Click it, go to controls tab 3) Invoke the Restart operation until you get the error: javax.el.PropertyNotFoundException: Property 'statusMessages' not found on type org.jboss.seam.Namespace See attached log. This is a bit rare use case as you need to click really fast. But the root cause might cause problems somewhere else, esp. for customers with slower machines. -- 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

12 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-315) Script: shutdown.sh -S does not work

by Ondrej Žižka (JIRA)

Script: shutdown.sh -S does not work ------------------------------------ Key: EMBJOPR-315 URL: https://jira.jboss.org/browse/EMBJOPR-315 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.4.0 Environment: Linux, AS 6 M4 Reporter: Ondrej Žižka Running the shutdown.sh script with args "-S" does not do it's job, only shows this output: "A JMX client to shutdown (exit or halt) a remote JBoss server." >From the terminal, the command works. -- 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

12 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (EMBJOPR-339) Deploying an EAR in exploded form fails with NPE

by Ivo Studensky (JIRA)

Deploying an EAR in exploded form fails with NPE ------------------------------------------------ Key: EMBJOPR-339 URL: https://jira.jboss.org/browse/EMBJOPR-339 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.3.4 Environment: EAP 5.1.0 CR-3.5 + CXF Reporter: Ivo Studensky Priority: Critical -- 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

13 years, 1 month

5
11
0 / 0

[JBoss JIRA] Created: (EMBJOPR-63) Login page content shifted towards the top in IE7

by Charles Crouch (JIRA)

Login page content shifted towards the top in IE7 ------------------------------------------------- Key: EMBJOPR-63 URL: https://jira.jboss.org/jira/browse/EMBJOPR-63 Project: Embedded Jopr Issue Type: Bug Components: Look 'n' Feel (html/css) Affects Versions: 1.1 Reporter: Charles Crouch See attached screenshot -- 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

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (EMBJOPR-320) Embedded Application resources should support same operations as non-embedded Application resources

by Larry O'Leary (JIRA)

Embedded Application resources should support same operations as non-embedded Application resources --------------------------------------------------------------------------------------------------- Key: EMBJOPR-320 URL: https://jira.jboss.org/browse/EMBJOPR-320 Project: Embedded Jopr Issue Type: Feature Request Components: Plugin Affects Versions: 1.3.2 Environment: JBoss EAP 5.0.1 running default configuration profile Admin Console provided from Embedded JOPR 1.3.2 Deployed EJB3 JAR to $JBOSS_HOME/server/default/deploy Deployed EAR containing an EJB3 JAR to $JBOSS_HOME/server/default/deploy Reporter: Larry O'Leary Embedded JOPR AS plug-in should expose operations for embedded application resources (EJB, WAR, etc). Feature request has been captured in upstream as https://bugzilla.redhat.com/show_bug.cgi?id=622588 and should be incorporated into Embedded JOPR or fixed in Embedded JOPR and ported upstream. -- 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

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (EMBJOPR-337) DS stats: Division by zero in org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getAverageBlockTime()

by Ondrej Zizka (JIRA)

DS stats: Division by zero in org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getAverageBlockTime() ------------------------------------------------------------------------------------------------------------------------ Key: EMBJOPR-337 URL: https://jira.jboss.org/browse/EMBJOPR-337 Project: Embedded Jopr Issue Type: Bug Environment: EAP 5.1.0.CR3.5 Reporter: Ondrej Zizka TODO: Copy to Bugzilla. java.lang.reflect.UndeclaredThrowableException: Failed to invoke method 'listStatistics' on component 'jboss.jca:name=wer,service=ManagedConnectionPool' with parameters []. at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:201) at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:103) 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:597) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:99) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:930) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:2034) at org.jboss.remoting.Client.invoke(Client.java:877) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$0.invoke(AOPProxy$0.java) at org.jboss.profileservice.management.client.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:63) at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:216) 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:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: javax.management.RuntimeMBeanException at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:165) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 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.ServiceControllerContext.invoke(ServiceControllerContext.java:190) at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus$1.dispatch(LifecycleAwareKernelBus.java:61) at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus$1.dispatch(LifecycleAwareKernelBus.java:58) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:71) at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus.invoke(LifecycleAwareKernelBus.java:57) at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:186) at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:103) 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:597) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:99) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:930) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:2034) at org.jboss.remoting.Client.invoke(Client.java:877) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$0.invoke(AOPProxy$0.java) at org.jboss.profileservice.management.client.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:63) at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:216) 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:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) ... 18 more Caused by: java.lang.ArithmeticException: / by zero at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getAverageBlockTime(InternalManagedConnectionPool.java:591) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.listStatistics(JBossManagedConnectionPool.java:1086) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool.listStatistics(JBossManagedConnectionPool.java:158) 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: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.server.Invocation.invoke(Invocation.java:88) 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.ServiceControllerContext.invoke(ServiceControllerContext.java:190) at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus$1.dispatch(LifecycleAwareKernelBus.java:61) at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus$1.dispatch(LifecycleAwareKernelBus.java:58) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:71) at org.jboss.kernel.plugins.registry.basic.LifecycleAwareKernelBus.invoke(LifecycleAwareKernelBus.java:57) at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:186) at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:103) 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:597) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:99) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:930) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:2034) at org.jboss.remoting.Client.invoke(Client.java:877) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) ... 18 more -- 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

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EMBJOPR-335) Datasources: JNDI name allowed to change, but does not work afterwards.

by Ondrej Zizka (JIRA)

Datasources: JNDI name allowed to change, but does not work afterwards. ----------------------------------------------------------------------- Key: EMBJOPR-335 URL: https://jira.jboss.org/browse/EMBJOPR-335 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.3.4 Environment: EAP 510 CR3.5 Reporter: Ondrej Zizka -- 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

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EMBJOPR-336) JBoss cache: Malfunctioning after destroying

by Ondrej Zizka (JIRA)

JBoss cache: Malfunctioning after destroying -------------------------------------------- Key: EMBJOPR-336 URL: https://jira.jboss.org/browse/EMBJOPR-336 Project: Embedded Jopr Issue Type: Bug Reporter: Ondrej Zizka -- 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

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (EMBJOPR-334) Better description of connection factory metrics

by Ondrej Zizka (JIRA)

Better description of connection factory metrics ------------------------------------------------ Key: EMBJOPR-334 URL: https://jira.jboss.org/browse/EMBJOPR-334 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.3.4 Reporter: Ondrej Zizka Priority: Minor Connection factory's Metrics tab shows "Min size" and "Max size". It's not exactly clear what do these values mean - a maximum during whole life of the factory? Pls add some better description. -- 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

13 years, 5 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues September 2010