November 2008 - jboss-dev-forums - Jboss List Archives

[Design of Security on JBoss] - Re: PrivilegedBlock location

by anil.saldhana＠jboss.com

"scott.stark(a)jboss.org" wrote : Oh, but createMessage() here is a joinpoint generated by the aop layer which should have had the privileged block. It would have to be moved to the JBossSession class. At this very moment, my hands got tired adding privileged blocks to the JBossSession class because it uses an aspect (delegate). The privileged block needs to go in JBossSession. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190714#4190714 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190714

17 years, 4 months

1
0
0 / 0

[Design of Security on JBoss] - Re: PrivilegedBlock location

by scott.stark＠jboss.org

Oh, but createMessage() here is a joinpoint generated by the aop layer which should have had the privileged block. It would have to be moved to the JBossSession class. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190713#4190713 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190713

17 years, 4 months

1
0
0 / 0

[Design of Security on JBoss] - Re: PrivilegedBlock location

by anil.saldhana＠jboss.com

"scott.stark(a)jboss.org" wrote : The code calling the aop layer should have the getClassLoader permission since its expected that loading/generating aspects will need access to it, and user code should not be able to do this without specific permissions. | | In this case the ClientSessionDelegate should have a privileged block. | Ok. There goes my night of sleep. I had this nagging doubt. If it would be aop, then the messaging release could go ahead. They use aop everywhere. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190712#4190712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190712

17 years, 4 months

1
0
0 / 0

[Design of Security on JBoss] - Re: PrivilegedBlock location

by scott.stark＠jboss.org

The code calling the aop layer should have the getClassLoader permission since its expected that loading/generating aspects will need access to it, and user code should not be able to do this without specific permissions. In this case the ClientSessionDelegate should have a privileged block. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190711#4190711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190711

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: 1.4.1.GA ready

by gaohoward

I'll hold on the proces. I just need to verify our examples locally. Anything needs me, pls let me know. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190710#4190710 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190710

17 years, 4 months

1
0
0 / 0

[Design of Security on JBoss] - PrivilegedBlock location

by anil.saldhana＠jboss.com

Scott, given the following stack trace, where do you think the privileged block should be placed that appropriate permission ("getClassLoader") should be placed? I feel that it needs to go in the aop project but I also have the suspicion that users of aop need to arrive with the "getClassLoader" permission. Thanks for the second opinion. | 23:22:07,502 ERROR [STDERR] access: access denied (java.lang.RuntimePermission getClassLoader) | 23:22:07,502 ERROR [STDERR] java.lang.Exception: Stack trace | 23:22:07,503 ERROR [STDERR] at java.lang.Thread.dumpStack(Thread.java:1158) | 23:22:07,503 ERROR [STDERR] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:253) | 23:22:07,503 ERROR [STDERR] at java.security.AccessController.checkPermission(AccessController.java:427) | 23:22:07,503 ERROR [STDERR] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) | 23:22:07,503 ERROR [STDERR] at java.lang.Class.getClassLoader(Class.java:588) | 23:22:07,503 ERROR [STDERR] at org.jboss.aop.advice.GenericAspectFactory.getClazz(GenericAspectFactory.java:123) | 23:22:07,503 ERROR [STDERR] at org.jboss.aop.advice.GenericAspectFactory.createPerInstance(GenericAspectFactory.java:175) | 23:22:07,503 ERROR [STDERR] at org.jboss.aop.InstanceAdvisorDelegate.initializeAspects(InstanceAdvisorDelegate.java:109) | 23:22:07,503 ERROR [STDERR] at org.jboss.aop.InstanceAdvisorDelegate.initialize(InstanceAdvisorDelegate.java:71) | 23:22:07,503 ERROR [STDERR] at org.jboss.aop.ClassInstanceAdvisor.setAdvisorAndInitialise(ClassInstanceAdvisor.java:84) | 23:22:07,503 ERROR [STDERR] at org.jboss.aop.ClassInstanceAdvisor.<init>(ClassInstanceAdvisor.java:68) | 23:22:07,503 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate._getInstanceAdvisor(ClientSessionDelegate.java) | 23:22:07,503 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate.createMessage(ClientSessionDelegate.java) | 23:22:07,503 ERROR [STDERR] at org.jboss.jms.client.JBossSession.createMessage(JBossSession.java:124) | 23:22:07,503 ERROR [STDERR] at org.jboss.test.security.ejb.RunAsWithRolesMDB.sendReply(RunAsWithRolesMDB.java:130) | 23:22:07,503 ERROR [STDERR] at org.jboss.test.security.ejb.RunAsWithRolesMDB.onMessage(RunAsWithRolesMDB.java:105) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190709#4190709 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190709

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - 1.4.1.GA examples

by gaohoward

So far I didn't see any jbm examples included in AS5 build. That means the AS5 user need to download JBM release separately to run examples. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190706#4190706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190706

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: 1.4.1.GA ready

by anil.saldhana＠jboss.com

Clebert told me that he would do the release tomorrow and now I see Howard is doing it. The reason is that I have been working for a full hour on your codebase and the following list is growing: | ========================================= | anil@localhost:~/messaging/Branch_1_4$ svn stat | M src/main/org/jboss/jms/wireformat/SessionCreateConsumerDelegateRequest.java | M src/main/org/jboss/jms/wireformat/ConnectionCreateSessionDelegateRequest.java | M src/main/org/jboss/jms/server/endpoint/ServerConnectionFactoryEndpoint.java | M src/main/org/jboss/jms/server/endpoint/SecurityActions.java | M src/main/org/jboss/jms/client/JBossConnection.java | M src/main/org/jboss/jms/client/container/SessionAspect.java | M src/main/org/jboss/jms/client/container/ConsumerAspect.java | ============================================ | Since JBoss Messaging is a heavy user of aspects, under a security manager, a permission check for "getClassLoader" is getting triggered which needs to be dealt in the messaging code base. We could have dealt it in AOP, but that is not correct. Let Clebert do the release tomorrow. Once I fix your codebase, please send me a pillow to sleep during the day. ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190704#4190704 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190704

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - profileservice-testTopic-service.xml deployment failures

by scott.stark＠jboss.org

The profileservice-testTopic-service.xml: | <?xml version="1.0" encoding="UTF-8" standalone="yes"?> | <server> | <mbean xmbean-dd="xmdesc/Topic-xmbean.xml" | name="jboss.messaging.destination:service=Topic,name=testTopic" | code="org.jboss.jms.server.destination.TopicService"> | <annotation>@org.jboss.system.deployers.managed.ManagementObjectClass(code=org.jboss.jms.server.destination.TopicServiceMO)</annotation> | <attribute name="JNDIName">testTopic</attribute> | <attribute name="MessageCounterHistoryDayLimit">1</attribute> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | </server> | is failing to deploy with: | 20:40:31,382 ERROR [AbstractKernelController] Error installing to Configured: name=jboss.messaging.destination:name=testTopic,service=Topic state=Instantiated mode=Manual requiredState=Configured | org.jboss.deployment.DeploymentException: Exception setting attribute MessageCounterHistoryDayLimit on mbean jboss.messaging.destination:service=Topic,name=testTopic | at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:155) | at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:99) | at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58) | at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:42) | at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) | at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) | at org.jboss.system.ServiceController.doChange(ServiceController.java:672) | at org.jboss.system.ServiceController.install(ServiceController.java:258) | at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:95) | at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) | at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:293) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:194) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:404) | at org.jboss.Main.boot(Main.java:209) | at org.jboss.Main$1.run(Main.java:547) | at java.lang.Thread.run(Thread.java:613) | Caused by: java.lang.NullPointerException | at org.jboss.jms.server.destination.ManagedTopic.getMessageCounters(ManagedTopic.java:159) | at org.jboss.jms.server.destination.ManagedTopic.setMessageCounterHistoryDayLimit(ManagedTopic.java:191) | at org.jboss.jms.server.destination.DestinationServiceSupport.setMessageCounterHistoryDayLimit(DestinationServiceSupport.java:410) | 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.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:136) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) | at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) | at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617) | at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:151) | ... 40 more | where the NPE is due to the ManagedTopic.setMessageCounterHistoryDayLimit calling ManagedTopic.getMessageCounters which relies on the serverPeer to have been injected. This is broken for configuration. This test appears to just have been added today. Was it working for you Emanuel? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190702#4190702 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190702

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: 1.4.1.GA ready

by clebert.suconic＠jboss.com

I thought the build at jboss5 is renaming jboss-messaging-client as /client/jboss-messaging.jar. If that's the real server, then that's wrong, but that's done at jb5 build. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190701#4190701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190701

17 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2008