March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7051) ManagedObjects are exposed for JBossMQ topics and queues - the MOs have the same component type as the MOs exposed for JBossMessaging destinations

by Ian Springer (JIRA)

ManagedObjects are exposed for JBossMQ topics and queues - the MOs have the same component type as the MOs exposed for JBossMessaging destinations -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-7051 URL: https://jira.jboss.org/jira/browse/JBAS-7051 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.1.0.GA Reporter: Ian Springer Assignee: Scott M Stark Fix For: JBossAS-5.2.0.Beta1 This is an issue, because some of the managed properties are not of the same type. For example "serverPeer" is exposed as a composite rather than a simple, as it is for JBM destinations (see the stack trace below). I think the we need to do one of the following: 1) Expose JBossMQ destinations as MOs with different component types than JBossMessaging destinations. This way clients can distinguish between the two and the managed properties don't have to be exactly the same. 2) Continue to use the same component types for JBossMQ and JBossMessaging destinations, but fix the disparities between the managed properties. If we do this, we also need to expose a managed property that indicates which container the destination corresponds to, e.g.: container=JBossMQ|JBossMessaging which will allow the Jopr plugin to distinguish between the two and expose them as different types of Resources. Here's the CCE that is caused by the 'serverPeer' prop not being of the expected type (simple string) on JBossMQ destination MOs: 15:19:43,782 ERROR [PluginContainerResourceManager] Error retrieving configuration for resource: Resource[id=-37, type=Q ueue, key=jboss.mq.destination:name=defaultedtutorial,service=Queue, name=jboss.mq.destination:name=defaultedtutorial,se rvice=Queue, parent=JBoss EAP 5 (default)] org.rhq.core.clientapi.agent.PluginContainerException: Cannot load Resource configuration for [-37] at org.rhq.core.pc.configuration.ConfigurationManager.loadResourceConfiguration(ConfigurationManager.java:174) at org.jboss.on.embedded.manager.pc.PluginContainerResourceManager.getResourceConfiguration(PluginContainerResou rceManager.java:235) at org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean.resourceConfiguration(ResourceCon figurationUIBean.java:144) 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.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean_$$_javassist_12.resourceConfigura tion(ResourceConfigurationUIBean_$$_javassist_12.java) 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.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:274) at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59) at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:174) at org.jboss.seam.navigation.Pages.callAction(Pages.java:711) at org.jboss.seam.navigation.Pages.preRender(Pages.java:349) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:562) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:473) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:146) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.jav a:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java :70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.RuntimeException: [Warning] java.lang.RuntimeException:Failed to convert managed property ManagedPr operty{serverPeer,serverPeer,metaType=ImmutableCompositeMetaType{javax.management.ObjectName items=[name=domain type=jav a.lang.String], [name=keyPropertyList type=java.util.Properties]}} to RHQ property of type SimpleProperty[serverPeer] (T ype: STRING). -> java.lang.ClassCastException:org.rhq.core.domain.configuration.definition.PropertyDefinitionSimple cann ot be cast to org.rhq.core.domain.configuration.definition.PropertyDefinitionMap ... 84 more -- 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, 8 months

6
13
0 / 0

[JBoss JIRA] Created: (JBAS-6486) Upport JBPAPP986: Ejb3AuthenticationInterceptor should propagate the GeneralSecurityException

by Carlo de Wolf (JIRA)

Upport JBPAPP986: Ejb3AuthenticationInterceptor should propagate the GeneralSecurityException --------------------------------------------------------------------------------------------- Key: JBAS-6486 URL: https://jira.jboss.org/jira/browse/JBAS-6486 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Reporter: Carlo de Wolf Assignee: Anil Saldhana Priority: Critical Fix For: JBossAS-5.1.0.CR1 -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6446) Blob.length or other methods fail on Blob when used from standalone java getting datasource from jboss.

by Jay Howell (JIRA)

Blob.length or other methods fail on Blob when used from standalone java getting datasource from jboss. ------------------------------------------------------------------------------------------------------- Key: JBAS-6446 URL: https://jira.jboss.org/jira/browse/JBAS-6446 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA, JBossAS-4.2.3.GA, JBossAS-5.0.1.GA Reporter: Jay Howell Fix For: JBossAS-4.2.4.GA, JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1 When we add the method hashes, we don't add any for blobs in the org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService. /** * Calculate the method hashes */ protected void calculateMethodHases() throws Exception { Method[] methods = DataSource.class.getMethods(); for(int m = 0; m < methods.length; m ++) { Method method = methods[m]; Long hash = new Long(MarshalledInvocation.calculateHash(method)); marshalledInvocationMapping.put(hash, method); } // Get the Long to Method mappings Map m = MarshalledInvocation.methodToHashesMap(Connection.class); displayHashes(m); marshalledInvocationMapping.putAll(m); m = MarshalledInvocation.methodToHashesMap(Statement.class); displayHashes(m); marshalledInvocationMapping.putAll(m); m = MarshalledInvocation.methodToHashesMap(CallableStatement.class); displayHashes(m); marshalledInvocationMapping.putAll(m); m = MarshalledInvocation.methodToHashesMap(PreparedStatement.class); displayHashes(m); marshalledInvocationMapping.putAll(m); m = MarshalledInvocation.methodToHashesMap(ResultSet.class); displayHashes(m); marshalledInvocationMapping.putAll(m); m = MarshalledInvocation.methodToHashesMap(DatabaseMetaData.class); displayHashes(m); marshalledInvocationMapping.putAll(m); } I'm still currently getting information and will add a test case for this when I'm done. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6291) Programmatic Web Authentication: validate security domain issues

by Anil Saldhana (JIRA)

Programmatic Web Authentication: validate security domain issues ---------------------------------------------------------------- Key: JBAS-6291 URL: https://jira.jboss.org/jira/browse/JBAS-6291 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.GA Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-5.0.1.CR1 Related to the "java:/jaas" prefix. http://www.jboss.org/community/docs/DOC-12656 -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6268) Null pointer exception for misconfigured web.xml

by Daniel Taylor (JIRA)

Null pointer exception for misconfigured web.xml ------------------------------------------------ Key: JBAS-6268 URL: https://jira.jboss.org/jira/browse/JBAS-6268 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR2 Environment: Linux Reporter: Daniel Taylor Priority: Minor A misconfigured web.xml throws a null pointer exception: <welcome-file-list> <welcome-file>secure/main.html</welcome-file>  </welcome-file-list> throws exception: 10:20:00,977 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.jboss.security.plugins.javaee.WebAuthorizationHelper.hasUserDataPermission(WebAuthorizationHelper.java:175) at org.jboss.web.tomcat.security.JBossWebRealm.hasUserDataPermission(JBossWebRealm.java:636) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:461) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:91) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:92) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:325) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) while not crucial to the development of jboss, I speak from experience when I say that it can take a long time to find the configuration error based upon the exception thrown... -- 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, 8 months

6
13
0 / 0

[JBoss JIRA] Created: (JBAS-6884) ConcurrentModificationExceptions and inconsistent number of results from getComponentsByType() occur when reload() is used rather than load()

by Ian Springer (JIRA)

ConcurrentModificationExceptions and inconsistent number of results from getComponentsByType() occur when reload() is used rather than load() --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-6884 URL: https://jira.jboss.org/jira/browse/JBAS-6884 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.1.0.CR1 Reporter: Ian Springer Assignee: Scott M Stark Fix For: JBossAS-5.1.0.GA When I accidentally switched the as5 plugin code to use reload() rather than load() whenever it reloaded the management view, I started seeing very messed up behavior when calling methods on the ManagementView. 1) When iterating Sets of components returned by ManagementView methods, I saw ConcurrentModificationExceptions. 2) When calling ManagementView.getComponentsByType(someType), I would get 5 results, then calling it a second later, 0 results, then another second later 3 results. It seems there are some serious concurrency issues within ManagementView that really come to light when reload() is called. On a related note, why do we even need reload()? It seems redundant, since load() does a reload of the view anyway if the view isn't already up-to-date. Can we deprecate 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

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-7306) Create a findbugs filter.xml file

by Jesper Pedersen (JIRA)

Create a findbugs filter.xml file --------------------------------- Key: JBAS-7306 URL: https://jira.jboss.org/jira/browse/JBAS-7306 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jesper Pedersen Assignee: Shelly McGowan Fix For: JBossAS-6.0.0.Alpha1 Hook up a findbugs filter.xml file to the run such that excludes can be added. -- 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, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-6416) exit method dissapeared from the jboss.system:type=Server MBean

by Dimitris Andreadis (JIRA)

exit method dissapeared from the jboss.system:type=Server MBean --------------------------------------------------------------- Key: JBAS-6416 URL: https://jira.jboss.org/jira/browse/JBAS-6416 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-5.0.0.GA Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: JBossAS-5.1.0.Beta1 The exit method are gone from the jboss.system:type=Server mbean, and so restarting remotely the server with a 'shutdonw -e 10' is impossible. -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-6297) Add optional notion to mbean service depends

by Scott M Stark (JIRA)

Add optional notion to mbean service depends -------------------------------------------- Key: JBAS-6297 URL: https://jira.jboss.org/jira/browse/JBAS-6297 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers, System service Affects Versions: JBossAS-5.0.0.GA Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.1.CR1 We should be able to leverage the mc optional dependency notion in mbean services depends. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6723) JAXBElementDeployer needs cleanup

by Anil Saldhana (JIRA)

JAXBElementDeployer needs cleanup --------------------------------- Key: JBAS-6723 URL: https://jira.jboss.org/jira/browse/JBAS-6723 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-5.1.0.GA, JBossAS-6.0.0.Alpha1 Based on the discussion in the design thread, Ales has done changes in the JAXBDeployer which may make JAXBElementDeployer redundant. When Ales releases his code into the AS, this JIRA issue will take a look. -- 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, 8 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010