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

[Design the new POJO MicroContainer] - Re: Alternative vfs jar implementation

by alesj

"mstruk" wrote : I commited noCopy support to jar-alter-work branch. I also added two additional system property switches: | | -Djboss.vfs.forceVfsJar=true | to fallback to vfsjar | | and | | -Djboss.vfs.forceNoReaper=true | | to turn off asynchronous release of file locks | Nice. ;-) "mstruk" wrote : | Known issues: | | 1) When deployment archive is removed from deploy directory an exception occurs, and the application is not undeployed - even though the file has been removed. | | 00:29:28,205 WARN [HDScanner] Scan failed | | org.jboss.deployers.spi.DeploymentException: Exception determining structure: AbstractVFSDeployment(autogen-bloated.ear) | | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | | at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:85) | | at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:845) | | at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:303) | | at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:260) | | at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:270) | | at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) | | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) | | at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) | | at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) | | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) | | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) | | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) | | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) | | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) | | at java.lang.Thread.run(Thread.java:619) | | Caused by: java.lang.RuntimeException: Error determining structure: autogen-bloated.ear | | at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:274) | | at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.java:72) | | at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersImpl.java:196) | | at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImpl.java:220) | | at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:77) | | ... 14 more | | Caused by: java.lang.RuntimeException: /autogen-bloated.jar module listed in application.xml does not exist within .ear autogen-bloated.ear | | at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:253) | | ... 18 more | | | | I'm not sure this is VFS's problem. | Better question is why is this ear being treated as new deployment. Since you can see that it's being added as deployment. 1) Why is it added / who still sees it? 2) What's the real cause module jar cannot be found? "mstruk" wrote : | 2) As applications are redeployed, memory consumption keeps increasing. It needs to be investigated. | That would be great. "mstruk" wrote : | Tomorrow I'm merging the code into trunk :) | Like Dimitris said, little commits as possible - making revert simple. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154536#4154536 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154536

16 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBossSessionBeanMetadataCreator a la EjbJar30Creator

by ALRubinger

Thanks, Alexey; would you ping me when that's done? I'll refactor some of my tests to use it. :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154530#4154530 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154530

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by thomas.diesler＠jboss.com

I am not aware of any change. Where are you seeing this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154520#4154520 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154520

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: AIO error

by clebert.suconic＠jboss.com

I forgot to say that for the release... making MaxAIO=5000 on jbm-configuration is good enough for Alpha what fixed this error message already. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154508#4154508 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154508

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: AIO error

by clebert.suconic＠jboss.com

As the close and open are both asynchronous, at high rates we could have 5 or 6 files opened what would maximize the max AIO on the OS. I want to add a retry block on open, but since that will require some minor changes on the native layer I will leave it for Beta. My concern is this excpetion is thrown by a constructor and I'm concerned If we keep retrying to open the file, hitting the constructor and ignoring the memory created. I don't know what are the consequences and I don't have enough time to test this before alpha. A simple and easy change.. but requires testing. (It is almost done on my workspace BTW.. but I won't commit it now) The native layer is stable for a while already and I would like to keep as is for Alpha now. I have added these two tasks to revisit this on Beta: http://jira.jboss.org/jira/browse/JBMESSAGING-1350 - Revisit Error codes and messages on exceptions thrown by the native layer http://jira.jboss.org/jira/browse/JBMESSAGING-1349 - Retry blocks on asynchronous open Maybe I will make one tiny change on the native layer before the release that wouldn't cause any issues though... just to change that error message. (Can't initialize aio). It is an optional task. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154507#4154507 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154507

16 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - JBoss Security

by sivananthamrg

Hi, Iam working on JBoss security features.I can able to see that below features are supported by JBoss 4.2 Auditing Authentication Authorization Single Sign-On Identity and Trust SSL Firewalls I just want to know whether JBoss 4.2 will support SAML based security. Thanks in Advance, Deepak View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154503#4154503 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154503

16 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: A problem about soapAction and wsdl in JBossESB

by djlxiong

I have sent it to you, thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154497#4154497 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154497

16 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Maven Version Resolution Differences 2.0.8 / 2.0.9

by ALRubinger

I've filed: http://jira.codehaus.org/browse/MNG-3606 S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154496#4154496 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154496

16 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Alternative vfs jar implementation

by mstruk

I commited noCopy support to jar-alter-work branch. I also added two additional system property switches: -Djboss.vfs.forceVfsJar=true to fallback to vfsjar and -Djboss.vfs.forceNoReaper=true to turn off asynchronous release of file locks Known issues: 1) When deployment archive is removed from deploy directory an exception occurs, and the application is not undeployed - even though the file has been removed. 00:29:28,205 WARN [HDScanner] Scan failed | org.jboss.deployers.spi.DeploymentException: Exception determining structure: AbstractVFSDeployment(autogen-bloated.ear) | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:85) | at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:845) | at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:303) | at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:260) | at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:270) | at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) | at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) | at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) | at java.lang.Thread.run(Thread.java:619) | Caused by: java.lang.RuntimeException: Error determining structure: autogen-bloated.ear | at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:274) | at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.java:72) | at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersImpl.java:196) | at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImpl.java:220) | at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:77) | ... 14 more | Caused by: java.lang.RuntimeException: /autogen-bloated.jar module listed in application.xml does not exist within .ear autogen-bloated.ear | at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:253) | ... 18 more | I'm not sure this is VFS's problem. 2) As applications are redeployed, memory consumption keeps increasing. It needs to be investigated. Tomorrow I'm merging the code into trunk :) Cheers, - marko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154495#4154495 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154495

16 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Controlling deployments via a barrier bean

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | If you look in broad brush terms, the profile service is made up of two components | | 1) A client side api that lets you define what a profile is | 2) A server side that implements that profile at runtime | | For the current default profile (hot deployment) that means three pojos that know how | to scan three sets of directories/urls (bootstrap/deployers/deploy) | which are the three sub-profiles that make up the profile. | The client side api for the default hot deployment profile is of course to just modify the directory structure and the file contents. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154475#4154475 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154475

16 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2008