January 2009 - jboss-dev-forums - Jboss List Archives

[Design of Embedded JBoss] - Re: Need vfs work for the embedded startup

by scott.stark＠jboss.org

I have tried with and without the options in the junit test setup and they don't seem to make much difference. I'll update some of the version dependencies and retry before digging into what is going on. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205775#4205775 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205775

15 years, 3 months

1
0
0 / 0

[Design of Embedded JBoss] - Re: Need vfs work for the embedded startup

by ALRubinger

For starters the VFS dependencies should surely be upgraded, and we should also look at the caching options to see if they're appropriate: http://anonsvn.jboss.org/repos/jbossas/projects/embedded/trunk/build/pom.xml <argLine>-ea -Xmx1024M -Djboss.vfs.cache=org.jboss.virtual.plugins.cache.TimedVFSCache -Djboss.vfs.forceCopy=true</argLine> S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205774#4205774 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205774

15 years, 3 months

1
0
0 / 0

[Design of Embedded JBoss] - Re: Need vfs work for the embedded startup

by alesj

I think ALR already enabled some flags for VFS which help you run this a bit faster: - forceCopy - some 'real' vfs cache It should be in some test or maven property. If this is already true for your test as well, then I have no idea what you can do. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205772#4205772 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205772

15 years, 3 months

1
0
0 / 0

[Design of Embedded JBoss] - Need vfs work for the embedded startup

by scott.stark＠jboss.org

In looking at extending the JBossEmbeddedAS work Andrew started to allow for better integration with a profile service, the memory usage and speed of trying to use a jbossas structure from within a large monolithic jar is poor. The jboss-embedded-assembly-0.1.0-SNAPSHOT-embedded.jar which combines most of the jbossas dependencies is ~40Mb. This little test which is the start of identifying the embedded server locations is taking way too much memory and time: | public void testBootstrapLib() | throws Exception | { | long start = System.currentTimeMillis(); | URL jarUrl = JBossEmbeddedAS.class.getProtectionDomain().getCodeSource().getLocation(); | System.out.println("JBossEmbeddedAS CodeSource: "+jarUrl); | long now = System.currentTimeMillis(); | System.out.println("Elapsed to determine CodeSource: "+(now = start)); | // Construct VFS representation | VirtualFile jarVirtualFile = VFS.getRoot(jarUrl); | VirtualFile jbossHome = jarVirtualFile.getChild("embedded"); | if(jbossHome == null) | throw new IllegalStateException("Failed to locate child 'embedded' in: "+jarUrl); | URL homeURL = jbossHome.toURL(); | | System.out.println("JBOSS_HOME: "+jbossHome); | now = System.currentTimeMillis(); | System.out.println("Elapsed to locate child 'embedded' : "+(now - start)); | | URL libraryURL = new URL(homeURL, ServerConfig.LIBRARY_URL_SUFFIX); | now = System.currentTimeMillis(); | VirtualFile libraryDir = VFS.getRoot(libraryURL); | System.out.println("LIBRARY_URL: "+libraryDir); | List<VirtualFile> jars = libraryDir.getChildren(); | if(jars != null) | { | for(VirtualFile jar : jars) | { | URL url = jar.toURL(); | System.out.println(jar); | } | } | now = System.currentTimeMillis(); | System.out.println("Elapsed to locate/list boot lib: "+(now - start)); | } | The output shows its taking 5+ secs just to get to the point of loading listing the contents of the JBOSS_HOME/lib directory, and this also requires increasing the test memory to 128m: | JBossEmbeddedAS CodeSource: file:/Users/svn/repository.jboss.org/maven2/org/jboss/embedded/jboss-embe... | Elapsed to determine CodeSource: 1 | JBOSS_HOME: ZipEntryHandler@12724795[path=embedded context=file:/Users/svn/repository.jboss.org/maven2/org/jboss/embedded/jb... real=file:/Users/svn/repository.jboss.org/maven2/org/jboss/embedded/jboss...] | Elapsed to locate child 'embedded' : 759 | LIBRARY_URL: ZipEntryHandler@14031599[path= context=vfszip:/Users/svn/repository.jboss.org/maven2/org/jboss/embedded/... real=vfszip:/Users/svn/repository.jboss.org/maven2/org/jboss/embedded/jbo...] | ZipEntryHandler@3232789[path=empty context=vfszip:/Users/svn/repository.jboss.org/maven2/org/jboss/embedded/... real=vfszip:/Users/svn/repository.jboss.org/maven2/org/jboss/embedded/jbo...] | Elapsed to locate/list boot lib: 5675 | We need to be under a sec and 64Mb to fully boot the embedded server. I'm looking at what is happening. It looks like vfs 2.0.0.CR5 is being pulled in by the current snapshot dependencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205770#4205770 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205770

15 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Accessing org.hibernate.Session from EntityManager

by jaikiran

For accessing org.hibernate.Session from a EntityManager, the JBossAS4.x docs for EJB3, recommend: anonymous wrote : You can get access to the current underlying Hibernate Session by typecasting your reference to EntityManager. | | @PersistenceContext EntityManager entityManager; | | public void someMethod(); | | { | | org.jboss.ejb3.entity.HibernateSession hs = (HibernateSession)entityManager; | | org.hibernate.Session session = hs.getHibernateSession(); | | } | | However, in AS5, the cast throws an CCE: | [java] Exception in thread "main" javax.ejb.EJBException: java.lang.ClassCastException: org.jboss.jpa.tx.TransactionScopedEntityManager | [java] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:77) | [java] at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) | [java] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) | [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | [java] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) | [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | [java] at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) | [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | [java] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) | [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | [java] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) | [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | [java] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | [java] at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) | [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | [java] at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) | [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | [java] at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:487) | [java] at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53) | [java] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) | [java] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | [java] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) | [java] at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742) | [java] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695) | [java] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:522) | [java] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230) | [java] Caused by: java.lang.ClassCastException: org.jboss.jpa.tx.TransactionScopedEntityManager | [java] at org.jboss.tutorial.hibernate.bean.AnotherCustomerBean.getCustomer(AnotherCustomerBean.java:68) | for this line: org.jboss.ejb3.entity.HibernateSession hs = (HibernateSession)entityManager; >From the javadocs of javax.persistence.EntityManager, i see that there is a getDelegate method available which can be used instead. So i have changed the reference doc and also added a new tutorial with this piece of code, which is working; public Customer getCustomer(long id) | { | org.hibernate.Session session = (Session) em.getDelegate(); | return (Customer) session.get(Customer.class, id); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205769#4205769 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205769

15 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: jboss_5_0.xsd: jboss version attribute

by alex.loubyansky＠jboss.com

getEjbVersion() returns the EJB spec version - right. But there is no xsd component in jboss schema for it. The value is set to the EJB version from the ejb-jar.xml and/or JBoss50Creator (at the initialization). Version attribute reflects not the AS version but the schema version of the deployment descriptor. Although, I don't see where it is actually used. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205767#4205767 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205767

15 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Transitions problem.

by ms_shitole

Hi Ronald Design of Process definitions, jpdl language problems are not part of this forum? In this forum, all are working on jbpm, workflow system. So some people may face the same problem, they will answer this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205756#4205756 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205756

15 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: LDAP assignment handler

by alex.guizar＠jboss.com

It was just deleted from the old CVS repository along with everything else, to prevent further commits there. Back then, it was in a branch and never reached the trunk, not because of incompatibility or quality issues, just because other priorities surfaced and I moved on. Now is as good time as any other to bring it back and finally merge it into the trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205731#4205731 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205731

15 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Transitions problem.

by kukeltje

wrong forum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205700#4205700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205700

15 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: LDAP assignment handler

by kukeltje

it was never in the code... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205699#4205699 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205699

15 years, 3 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 January 2009