12:01 a.m.
ReadOnlyAccessFilter relies on naming service impl details
----------------------------------------------------------
Key: JBAS-7457
URL: https://jira.jboss.org/jira/browse/JBAS-7457
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Naming
Reporter: Scott M Stark
Assignee: Scott M Stark
The ReadOnlyAccessFilter is looking for a MethodMap from its invokerName mbean. This is
related to old detached invoker proxy code that should just be replaced with injection of
a proxy. Longer term this filter should be obsolete as acl security is added to the naming
service itself.
--
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:39 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7457) ReadOnlyAccessFilter relies on naming service impl details
[
https://jira.jboss.org/jira/browse/JBAS-7457?page=com.atlassian.jira.plug...
]
Scott M Stark commented on JBAS-7457:
-------------------------------------
Actually, we are still deploying the old mbean with the MethodMap attribute as described
in the conf/xmdesc/NamingService-xmbean.xml:
&defaultAttributes;
<attribute access="read-only" getMethod="getMethodMap">
<name>MethodMap</name>
<type>java.util.Map</type>
</attribute>
but its not visible for some reason:
22:35:23,406 ERROR [ReadOnlyAccessFilter] Failed to init ReadOnlyAccessFilter:
javax.management.AttributeNotFoundException: not found: MethodMap
at org.jboss.mx.server.AbstractMBeanInvoker.getAttribute(AbstractMBeanInvoker.java:335)
at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:565)
at
org.jboss.invocation.http.servlet.ReadOnlyAccessFilter.init(ReadOnlyAccessFilter.java:72)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:462)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3800)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4464)
at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:307)
ReadOnlyAccessFilter relies on naming service impl details
----------------------------------------------------------
Key: JBAS-7457
URL: https://jira.jboss.org/jira/browse/JBAS-7457
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Naming
Reporter: Scott M Stark
Assignee: Scott M Stark
The ReadOnlyAccessFilter is looking for a MethodMap from its invokerName mbean. This is
related to old detached invoker proxy code that should just be replaced with injection of
a proxy. Longer term this filter should be obsolete as acl security is added to the naming
service itself.
--
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
1:11 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7457) ReadOnlyAccessFilter relies on naming service impl details
[
https://jira.jboss.org/jira/browse/JBAS-7457?page=com.atlassian.jira.plug...
]
Scott M Stark commented on JBAS-7457:
-------------------------------------
Ok, the issue is that the NamingService is now deployed as an MCBean:
<!-- An obsolete bean only needed if using legacy detached invoker access,
or the createAlias/removeAlias operations
-->
<bean name="NamingService"
class="org.jboss.naming.NamingService">
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=NamingService",
exposedInterface=org.jboss.naming.NamingServiceMBean,
registerDirectly=true)</annotation>
<!-- An example of using the unifed invoker as the transport.
<depends optional-attribute-name="InvokerProxyFactory"
proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming</depends>
-->
<property name="namingInfo"><inject
bean="RemoteNamingBean"/></property>
</bean>
and this is not reproducing the same attributes as are exposed by default or via the
xmbean descriptor. What I see is:
{JNPServerSocketFactory=InvocationContext[ name=JNPServerSocketFactory, type=null,
attributeType=java.lang.String, isReadable=true, isWritable=true, returnType=null,
signature=null ], BootstrapURL=InvocationContext[ name=BootstrapURL, type=null,
attributeType=java.lang.String, isReadable=true, isWritable=false, returnType=null,
signature=null ], ClientSocketFactory=InvocationContext[ name=ClientSocketFactory,
type=null, attributeType=java.lang.String, isReadable=true, isWritable=true,
returnType=null, signature=null ], ClientSocketFactoryBean=InvocationContext[
name=ClientSocketFactoryBean, type=null,
attributeType=java.rmi.server.RMIClientSocketFactory, isReadable=true, isWritable=true,
returnType=null, signature=null ], InstallGlobalService=InvocationContext[
name=InstallGlobalService, type=null, attributeType=boolean, isReadable=true,
isWritable=true, returnType=null, signature=null ], NamingProxy=InvocationContext[
name=NamingProxy, type=null, attributeType=java.lang.Object, isReadable=true,
isWritable=true, returnType=null, signature=null ], RmiBindAddress=InvocationContext[
name=RmiBindAddress, type=null, attributeType=java.lang.String, isReadable=true,
isWritable=true, returnType=null, signature=null ], Port=InvocationContext[ name=Port,
type=null, attributeType=int, isReadable=true, isWritable=true, returnType=null,
signature=null ], NamingInfo=InvocationContext[ name=NamingInfo, type=null,
attributeType=org.jnp.server.NamingBean, isReadable=true, isWritable=true,
returnType=null, signature=null ], Backlog=InvocationContext[ name=Backlog, type=null,
attributeType=int, isReadable=true, isWritable=true, returnType=null, signature=null ],
JNPServerSocketFactoryBean=InvocationContext[ name=JNPServerSocketFactoryBean, type=null,
attributeType=javax.net.ServerSocketFactory, isReadable=true, isWritable=true,
returnType=null, signature=null ], ServerSocketFactory=InvocationContext[
name=ServerSocketFactory, type=null, attributeType=java.lang.String, isReadable=true,
isWritable=true, returnType=null, signature=null ], NamingInstance=InvocationContext[
name=NamingInstance, type=null, attributeType=org.jnp.interfaces.Naming, isReadable=true,
isWritable=false, returnType=null, signature=null ], BindAddress=InvocationContext[
name=BindAddress, type=null, attributeType=java.lang.String, isReadable=true,
isWritable=true, returnType=null, signature=null ],
ServerSocketFactoryBean=InvocationContext[ name=ServerSocketFactoryBean, type=null,
attributeType=java.rmi.server.RMIServerSocketFactory, isReadable=true, isWritable=true,
returnType=null, signature=null ], RmiPort=InvocationContext[ name=RmiPort, type=null,
attributeType=int, isReadable=true, isWritable=true, returnType=null, signature=null ],
UseGlobalService=InvocationContext[ name=UseGlobalService, type=null,
attributeType=boolean, isReadable=true, isWritable=true, returnType=null, signature=null
], CallByValue=InvocationContext[ name=CallByValue, type=null, attributeType=boolean,
isReadable=true, isWritable=true, returnType=null, signature=null ],
LookupListenerException=InvocationContext[ name=LookupListenerException, type=null,
attributeType=java.lang.Exception, isReadable=true, isWritable=false, returnType=null,
signature=null ]}
ReadOnlyAccessFilter relies on naming service impl details
----------------------------------------------------------
Key: JBAS-7457
URL: https://jira.jboss.org/jira/browse/JBAS-7457
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Naming
Reporter: Scott M Stark
Assignee: Scott M Stark
The ReadOnlyAccessFilter is looking for a MethodMap from its invokerName mbean. This is
related to old detached invoker proxy code that should just be replaced with injection of
a proxy. Longer term this filter should be obsolete as acl security is added to the naming
service itself.
--
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:57 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-7457) ReadOnlyAccessFilter relies on naming service impl details
[
https://jira.jboss.org/jira/browse/JBAS-7457?page=com.atlassian.jira.plug...
]
Scott M Stark resolved JBAS-7457.
---------------------------------
Fix Version/s: JBossAS-6.0.0.M2
Resolution: Done
It was a change in the name of the mbean that provided the legacy interface. The mbean is
now called jboss:service=NamingBeanImpl
ReadOnlyAccessFilter relies on naming service impl details
----------------------------------------------------------
Key: JBAS-7457
URL: https://jira.jboss.org/jira/browse/JBAS-7457
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Naming
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: JBossAS-6.0.0.M2
The ReadOnlyAccessFilter is looking for a MethodMap from its invokerName mbean. This is
related to old detached invoker proxy code that should just be replaced with injection of
a proxy. Longer term this filter should be obsolete as acl security is added to the naming
service itself.
--
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
5517
days inactive
5518
days old
3 comments
1 participants
participants (1)
-
Scott M Stark (JIRA)