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

[Design of POJO Server] - Re: VFS Permissions - JBMICROCONT-149

by anil.saldhana＠jboss.com

With the current setup, the protection domain that is failing is: | ProtectionDomain (vfszip:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.GA/lib/jboss-aop-asintegration-core.jar <no signer certificates>) | null | <no principals> | java.security.Permissions@12910b0b ( | (java.net.SocketPermission * connect,resolve) | (java.lang.RuntimePermission getClassLoader) | (java.lang.RuntimePermission accessClassInPackage.*) | (java.lang.RuntimePermission org.jboss.security.SecurityAssociation.getSubject) | (java.lang.RuntimePermission queuePrintJob) | (java.lang.RuntimePermission getProtectionDomain) | (java.util.PropertyPermission * read) | (javax.management.MBeanServerPermission findMBeanServer) | (javax.management.MBeanPermission org.jboss.mx.modelmbean.XMBean#*[JMImplementation:type=MBeanRegistry] *) | (javax.management.MBeanPermission org.jboss.security.plugins.JaasSecurityManagerService#*[jboss.security:service=JaasSecurityManager] invoke) | (javax.management.MBeanPermission org.jboss.security.plugins.AuthorizationManagerService#*[jboss.security:service=AuthorizationManager] invoke) | (javax.management.MBeanPermission org.jboss.security.auth.login.XMLLoginConfig#*[jboss.security:service=XMLLoginConfig] invoke) | (javax.security.auth.AuthPermission createLoginContext.*) | (javax.security.auth.AuthPermission getLoginConfiguration) | (java.io.FilePermission file:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.GA/bin/../server/default/tmp/- read) | (java.io.FilePermission file:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.GA/server/default/tmp/- read) | (java.security.SecurityPermission getPolicy) | ) | | I tried the protocol handler approach to apply the vfszip handler. No luck. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187596#4187596 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187596

17 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - java.util.logging Bridge Component

by david.lloyd＠jboss.com

I dusted off and fixed up two small yet related projects I've had lying around forever. The first is a substitute java.util.logging LogManager that fixes about 10 zillion bugs, and is all-around much better-behaved (not to mention far simpler) than the default JDK implementation. The second is a deployable java.util.logging Handler JAR that forwards j.u.l LogRecords to log4j. The upshot of this thing is, two tiny JARs and you're able to see all j.u.l messages mapped in properly with the regular server log, without having to rearchitecht the whole logging system. While I was hoping to uncover the secrets of the universe, unfortunately on a stock 5.0.0.CR2 startup, the only extra stuff printed was a couple RMI messages. Oh well. The logmanager source is here (the resultant classes must be on the boot classpath, and the -Djava.util.logging.manager system property must point at the org.jboss.logmanager.LogManager class): http://anonsvn.jboss.org/repos/sandbox/david.lloyd/jboss-logmanager/trunk The logbridge deployable is here (make a JAR and stick it in deployers/ to get early logs, or deploy/ if you don't care about that stuff): http://anonsvn.jboss.org/repos/sandbox/david.lloyd/jboss-logbridge/trunk/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187587#4187587 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187587

17 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: VFS Permissions - JBMICROCONT-149

by anil.saldhana＠jboss.com

The customized CodeSource is not going to work. The default policy file implementation usage of URL (to get the URLConnection's permission) is a problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187584#4187584 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187584

17 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5689, bootstrap deployments not seen by profileserv

by scott.stark＠jboss.org

This is affecting getting hold of runtime beans like the ServerInfo bean that is loaded by the conf/jmx.xml bootstrap piece. So I'm looking at extending the Bootstrap interface to make the start signature: | start(Server server, Map<String, KernelDeployment> serverDeployments) | and then pass this onto the MainDeployer.addDeployment(Deployment) without having these reprocessed. It looks this would require a change in the MainDeployerImpl.addContext(DeploymentContext context, boolean addToDeploy) to look for a DeploymentState.DEPLOYED and simply add it to the deploy list, bypassing the deployers. Does this sound like the best approach? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187582#4187582 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187582

17 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: creating integration layer

by clebert.suconic＠jboss.com

Being brain storm... In my experience, when you break JARs you need to ensure the dependencies are aways one way. For example, if there is something on jbm_core referencing jbm_jms by accident like an unused import, it needs to be verified / fixed. Or else you will aways require to have all the jars no matter what you use. I can only think about testing it using compilation targets. ... end brain storm View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187580#4187580 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187580

17 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Changes on the JBM stack on JBoss5 (Repost)

by clebert.suconic＠jboss.com

"bstansberry(a)jboss.com" wrote : | They do show this test server2 was started about 50 times before this failure occurred. So, it seems quite intermittent and likely hard to track down. A key thing is understanding what exactly changed that triggered this, or if we don't really know, understanding we don't really know so we can avoid chasing the wrong thing. So, This is because each test on the clustered-testsuite will start/stop all the servers. So I believe we could make a test that only start/stops the servers until this issue appears. We could actually do that by putting a single test to run in a loop. under /tests/bin you will find a way of doing this. If you contact me offline i will tell you how to use that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187579#4187579 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187579

17 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Changes on the JBM stack on JBoss5

by clebert.suconic＠jboss.com

"bstansberry(a)jboss.com" wrote : | They do show this test server2 was started about 50 times before this failure occurred. So, it seems quite intermittent and likely hard to track down. A key thing is understanding what exactly changed that triggered this, or if we don't really know, understanding we don't really know so we can avoid chasing the wrong thing. So, This is because each test on the clustered-testsuite will start/stop all the servers. So I believe we could make a test that only start/stops the servers until this issue appears. We could actually do that by putting a single to run in a loop. under /tests/bin you will find a way of doing this. If you contact me offline i will tell you how to use that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187579#4187579 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187579

17 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Changes on the JBM stack on JBoss5

by clebert.suconic＠jboss.com

"Brian" wrote : | 1) Did this failure start appearing regularly after a certain point? Or did it just happen once? | | 2) If it's regular, was the change to the stack config the *only* change before it started happening? | | 3) When did you start testing with JGroups 2.6.5? How much testing did you do with JGroups 2.6.5 before this issue appeared? | The testsuite started failing right after this change, which was the only change: [url]http://viewvc.jboss.org/cgi-bin/viewvc.cgi/messaging/branches/Branch_... [/url] I was using 2.6.5. before that change already and I got all successful runs. It happens most of the times now. It could happen on any test on the clustering-testsuite. To run the clustering testsuite on JBM you need to: svn co http://anonsvn.jboss.org/repos/messaging/branches/Branch_1_4 jbm-1.4 cd jbm-1.4 edit build.properties (make sure it says AS5) cd tests (you may want to edit build.properties on tests also and put a local IP there. It should run fine with localhost thought, but I have used a local IP just in case) ant clustered-tests View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187573#4187573 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187573

17 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Changes on the JBM stack on JBoss5

by bstansberry＠jboss.com

I have the logs. They don't show anything helpful, at least not right around the time of the failure, which is in the server2 log at 17:04:09,119. They do show this test server2 was started about 50 times before this failure occurred. So, it seems quite intermittent and likely hard to track down. A key thing is understanding what exactly changed that triggered this, or if we don't really know, understanding we don't really know so we can avoid chasing the wrong thing. So, 1) Did this failure start appearing regularly after a certain point? Or did it just happen once? 2) If it's regular, was the change to the stack config the *only* change before it started happening? 3) When did you start testing with JGroups 2.6.5? How much testing did you do with JGroups 2.6.5 before this issue appeared? anonymous wrote : I will not hold the JBM 1 release because of this, but I will open a JIRA on JBAS for this issue. +1. The only thing happening when this failed was an ordinary start of a server. Your tests failed because the server didn't start properly. The AS testsuite starts servers all the time; it's perfectly reasonably to track this issue there. However, if you think the problem will consistently appear over the course of a testsuite run, I make ask for some help in running your testsuite occasionally, to see if changing settings makes the issue go away. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187566#4187566 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187566

17 years, 5 months

1
0
0 / 0

[Design of JBoss Identity] - Re: SAML Assertions (JBossESB)

by jkurtz.wa＠gmail.com

anil Have you thought about using smooks to do the conversion of the SAML Assertion into Java and back to XML? If you want, I can create the component, just point me to some SAML assertions and I will make the software and test cases. I have the SAML Assertion schema and can generate the test cases for this component if you want. I would follow the way that XACML does its conformance testing. This might find its way into the SAML Spec, at least the tests. John View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187564#4187564 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187564

17 years, 5 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