[Design of JBoss internal QA (Test Suite)] - Re: Testsuite runs failing due to server failed startups/tim
by rachmatowicz@jboss.com
1. The 'all' server was experiencing OOMEs of the PermSpace variety, as opposed to the heap space variety. Heap space is used to store object instances and other garbage-collectable data items, whereas PermSpace is used to store class definitions and other 'permanent' data structures, which are not subject to garbage collection (as far as I am aware). These were visible in the log as:
18:23:08,027 ERROR [STDERR] Exception in thread "JBoss System Threads(1)-108"
18:23:08,027 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@8aba19
java.lang.OutOfMemoryError: PermGen space
2. The fact that servers controlled with server:start and server:stop do not shutdown correctly seems to be due to memory problems: I ran the testsuite with the JVM memory settings
-Xms256m -Xmx256m -XX:MaxPermSize=128m -XX:PermSize=128m
and the server shutdown problems (as well as the OOMEs) disappeared.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030024#4030024
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030024
19 years
[Design of EJB 3.0] - Re: ManyToMany enhancement?
by joe.marques@jboss.com
anonymous wrote : how was Object_B merge operation
I don't really understand the question...but I'll attempt to answer what I think your asking anyway. ;)
My best guess tells me your question targets my latter post:
SELECT someA FROM A someA, IN (someA.Bs) someB WHERE someB.stuff=<value>
...which pertains to how Hibernate would do the merge of the additional qualifying data (stuff) into some object (someB) for the traversal (someB.stuff).
Well, as it stands today, Hibernate3 returns proxy objects. So I was thinking that it wouldn't be a stretch of the imagination to use that concept here in this case.
One might be able to generate proxies that are the extension of the domain object (e.g., class B), but which also include attributes that represent the additional qualifying information (Stuff). So the proxy might have an effective definition that looked like:
class B_proxy {
| List<A> As; // because proxy extends class B
| String stuff; // assuming stuff was a string qualifier
| ...
| }
If this "extended" proxy were returned by the query, then I think it would be possible to get the "auto-magical access to the additional qualifiers".
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029998#4029998
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029998
19 years