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

[Design of JBoss Wiki] - Re: how to unregister this forum

by PeterJ

Click on the Watched Forums and Watched Topics links at the top of the page. Then uncheck those topics and forums you no longer want sent to your email. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145880#4145880 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145880

16 years, 5 months

1
0
0 / 0

[Design of Security on JBoss] - Security EJB2 and dependencies

by adrian＠jboss.org

If you run the pooled tests in JBoss5 | ./build.sh test -Dtest=pooled -Dnojars=t | you will see it fails with | 16:20:26,857 ERROR [UsersRolesLoginModule] Failed to load users/passwords/role files | java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found | at org.jboss.security.auth.spi.Util.loadProperties(Util.java:366) | at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:186) | at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:200) | at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:127) | 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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:756) | at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) | at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) | at java.security.AccessController.doPrivileged(Native Method) | at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) | at javax.security.auth.login.LoginContext.login(LoginContext.java:579) | at org.jboss.security.plugins.auth.JaasSecurityManagerBase.defaultLogin(JaasSecurityManagerBase.java:563) | at org.jboss.security.plugins.auth.JaasSecurityManagerBase.authenticate(JaasSecurityManagerBase.java:497) | at org.jboss.security.plugins.auth.JaasSecurityManagerBase.isValid(JaasSecurityManagerBase.java:365) | at org.jboss.security.javaee.EJBAuthenticationHelper.isValid(EJBAuthenticationHelper.java:76) | at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityContext(SecurityInterceptor.java:301) | at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:238) | at org.jboss.ejb.plugins.SSLSessionInterceptor.invokeHome(SSLSessionInterceptor.java:53) | at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132) | at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107) | at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:640) | at org.jboss.ejb.Container.invoke(Container.java:1031) | at sun.reflect.GeneratedMethodAccessor156.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | 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.invocation.pooled.server.PooledInvoker$MBeanServerAction.invoke(PooledInvoker.java:896) | at org.jboss.invocation.pooled.server.PooledInvoker.invoke(PooledInvoker.java:383) | at org.jboss.invocation.pooled.server.ServerThread.processInvocation(ServerThread.java:233) | at org.jboss.invocation.pooled.server.ServerThread.dorun(ServerThread.java:275) | at org.jboss.invocation.pooled.server.ServerThread.run(ServerThread.java:156) | This is because it has been configured to use the ssl-pooled domain which is hot deployed with the ejbs, but it is actually using the "other" domain. I'd guess this is because org.jboss.ejb.plugins.SecurityInterceptor is not respecting the jmx dependency rules. i.e. it is trying to retrieve the SecurityDomain in setContainer() instead of start() setContainer() is invoked from EJB.create() | public void setContainer(Container container) | { | ... | | // HERE This is invoked from EJB.create() which is too early since | the SecurityDomain is not deployed until start() | | if(securityManager != null) | { | appSecurityDomain = securityManager.getSecurityDomain(); | appSecurityDomain = SecurityUtil.unprefixSecurityDomain(appSecurityDomain); | } | } | } | >From the debug logging | | This is where it tries to retrieve the security domain: | | 2008-04-22 16:20:25,185 DEBUG [org.jboss.ejb.StatelessSessionContainer] (RMI TCP Connection(6)-127.0.0.1) Creating jboss.j2ee:jndiName=StatelessSessionWithPooledSSL,se | rvice=EJB | | This is where the security domain is actually deployed | | 2008-04-22 16:20:25,198 DEBUG [org.jboss.security.plugins.JaasSecurityDomain] (RMI TCP Connection(6)-127.0.0.1) Starting jboss.security:service=JaasSecurityDomain,doma | in=pooled-ssl | 2008-04-22 16:20:25,201 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] (RMI TCP Connection(6)-127.0.0.1) Added pooled-ssl, org.jboss.security.plugins.Ja | asSecurityDomain@18441c1 to map | 2008-04-22 16:20:25,213 DEBUG [org.jboss.security.plugins.auth.JaasSecurityManagerBase.pooled-ssl] (RMI TCP Connection(6)-127.0.0.1) CachePolicy set to: org.jboss.util | .TimedCachePolicy@1f90a95 | 2008-04-22 16:20:25,213 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] (RMI TCP Connection(6)-127.0.0.1) setCachePolicy, c=org.jboss.util.TimedCachePoli | cy@1f90a95 | 2008-04-22 16:20:25,213 DEBUG [org.jboss.security.plugins.JaasSecurityDomain] (RMI TCP Connection(6)-127.0.0.1) Started jboss.security:service=JaasSecurityDomain,domai | n=pooled-ssl | | This is where it should be retrieved | | 2008-04-22 16:20:25,269 DEBUG [org.jboss.ejb.StatelessSessionContainer] (RMI TCP Connection(6)-127.0.0.1) Started jboss.j2ee:jndiName=StatelessSessionWithPooledSSL,ser | vice=EJB | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145879#4145879 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145879

16 years, 5 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Used of JGroups shared transport in AS 5

by galder.zamarreno＠jboss.com

"bstansberry(a)jboss.com" wrote : The AS fix is still hacky though, as the method signatures of the two createMultiplexerChannel methods include other params besides the stack name that are now totally ignored. Hmmm, I suppose you can always indicate this in the AS's ChannelFactory javadoc? As long as it's noted somewhere, doesn't look that bad. It's certainly safer than returning different type of objects depending on whether its shared transport or multiplexer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145874#4145874 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145874

16 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Pulling security out as a separate module

by ALRubinger

"anil.saldhana(a)jboss.com" wrote : It was added to core/jboss-ejb3-client.xml. I am not creating a separate jar with 2-3 classes, even if it means an imperfect world. That's fine, but in the future we cannot assume that the classes marked for inclusion are checked out alongside core. ie: <fileSet> | <directory>../security/target/classes</directory> I'll take that task this time around, FYI. :) http://jira.jboss.com/jira/browse/EJBTHREE-1308 S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145862#4145862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145862

16 years, 5 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Solution of JBREM-954 and ramifications into UnifiedInvo

by galder.zamarreno＠jboss.com

Bugged, I messed up the link at the top again. Here's the proper link: http://jira.jboss.com/jira/browse/JBREM-954 "david.lloyd(a)jboss.com" wrote : I think Remoting should do it. Though I don't know offhand how big a change this is in the Remoting 2.x codebase. But there is a general need to differentiate between a client-side interruption and server-side interruption. This is a not unique requirement of the unified invoker, as far as I can see. And it certainly shouldn't break existing code, since it's already broken, right? It has a very nasty side effect on the HA version: As an IE is wrapped in a CannotConnectException, that destination is not longer available in the proxy. So a client side interruption results on the client not being able to connect to the server it was trying to connect to until the proxy is regenerated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145860#4145860 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145860

16 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Pulling security out as a separate module

by anil.saldhana＠jboss.com

http://wiki.jboss.org/wiki/DevEJB3RunningUnitTests Does this wiki page still hold true for running the ejb3 unit tests? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145855#4145855 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145855

16 years, 5 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-5233 - Logging synchronous cluster wide RPC calls a

by galder.zamarreno＠jboss.com

"bstansberry(a)jboss.com" wrote : Yes, please just put boring long format URLs in your posts, the short version above doesn't work. ;) Good shout! I thought they're working fine. Not enough testing on my side... :| There you go: http://jira.jboss.com/jira/browse/JBAS-5233 "bstansberry(a)jboss.com" wrote : Seriously, though, I don't like logging all that at DEBUG. Perhaps the "Ignoring non-received response message" at debug, and include more info about the call in the msg so you have context. | | But run tests-clustering-non-http before putting that in and see what it does to the logs first. Ok, that sounds fair enough. It's "Ignoring non-received response message" the one I'm really interested in anyway. Ok with running the tests too, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145854#4145854 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145854

16 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Refreshing entries in JARs

by alesj

Regarding this JIRA issue: - http://jira.jboss.com/jira/browse/JBVFS-7 I created this test: | public void testEntryModified() throws Exception | { | File tmp = File.createTempFile("testJarEntry", ".jar"); | Manifest mf = new Manifest(); | mf.getMainAttributes().putValue("Created-By", getClass().getName() + "." + "testEntryModified"); | FileOutputStream fos = new FileOutputStream(tmp); | JarOutputStream jos = new JarOutputStream(fos, mf); | try | { | jos.setComment("testJarURLs"); | jos.setLevel(0); | } | finally | { | jos.close(); | } | VFS vfs = VFS.getVFS(tmp.toURI()); | VirtualFile metainf = vfs.findChild("META-INF"); | List<VirtualFile> children = metainf.getChildren(); | assertEquals(1, children.size()); | | fos = new FileOutputStream(tmp); | jos = new JarOutputStream(fos, mf); | try | { | ZipEntry entry = new ZipEntry("META-INF/some.txt"); | entry.setComment("some_comment"); | entry.setExtra("qwerty".getBytes()); | entry.setSize(1); | jos.putNextEntry(entry); | jos.closeEntry(); | | entry = new ZipEntry("META-INF/other.txt"); | entry.setComment("other_comment"); | entry.setExtra("foobar".getBytes()); | entry.setSize(1); | jos.putNextEntry(entry); | jos.closeEntry(); | } | finally | { | jos.close(); | } | | // vfs = VFS.getVFS(tmp.toURI()); | // metainf = vfs.findChild("META-INF"); | System.out.println("metainf = " + metainf.hasBeenModified()); | children = metainf.getChildren(); | assertEquals(3, children.size()); | } | Which looks legit, since when I uncomment two lines at the bottom, the new vfs handle picks up all three entries. But in our case, where we don't want to create new handle, but use the existing one, where the handle should see that the content has changed and return 3 entries. Of course that is not the case. :-( And I don't see how you really do this in generic fashion w/o modifying all VFS, e.g. lets say some 4level nested jar is updated. Even in this case, where we have just simple jar, updating contents of META-INF handler is far from trivial. The handler that maps to META-INF is SynthenticDirEntryHandler, which only gets populated when we iterate over entries of parent jar. Meaning we would have to go back and recreate every entry. And I don't know how much information that's needed for reconstruction we're holding. I'll have a look what can be done if I add some 'reconstruct' method to VirtualFileHandler. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145853#4145853 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145853

16 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Pulling security out as a separate module

by jesper.pedersen

I have committed an update version, since inner interfaces and inner classes wasn't included. Can you go through it and see which are actually needed ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145851#4145851 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145851

16 years, 5 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-5233 - Logging synchronous cluster wide RPC calls a

by bstansberry＠jboss.com

Seriously, though, I don't like logging all that at DEBUG. Perhaps the "Ignoring non-received response message" at debug, and include more info about the call in the msg so you have context. But run tests-clustering-non-http before putting that in and see what it does to the logs first. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145845#4145845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145845

16 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2008