Package name
by Tomaž Cerar
Hi,
What should be package name for new stuff being added to WildFly?
org.wildfly.<subsystem-name>
or
org.wildfly.as.<subsystem-name>
or something else?
I would go for org.wildfly.<subsystem-name>
this mostly applies to new subsystems and as we agreed we won't rename
packages for existing code until it break compatibility.
--
tomaz
10 years, 9 months
Memory leaks
by Tomaž Cerar
Hi,
during weekend we have been investigating some rather big memory leaks we
have in current WildFly code.
What our research has found out is that we had problems in
- JPA integration
- Validation integration
- undertow / undertow integration
- msc
- resteasy
- hibernate
For now we have fixed most of the issues in integration code which can be
found at
https://github.com/ctomc/wildfly/commits/mem-leak
undertow
https://github.com/undertow-io/undertow/commits/master
msc
https://github.com/jbossas/jboss-msc/commit/1bcdbd0d874a5d5e22ef2a00fa1eb...
RestEasy
https://github.com/resteasy/Resteasy/pull/344
I am not sure for RestEasy fixes and should code be properly fixed by
people that know code bit better.
All this components need new release to be cut before they can be included
into WildFly.
I am not sure if this will hold WildFly Alpha 3 release or not, IMHO it
should.
Also beyond this leaks we also found that we leak somewhere deep in
hibernate integration and properties(or better copy of them) that are
passed as part of JPA initialization remain referenced by hibernate service
loader after application has already been undeployed.
This is problematic as part of this properties are instances of BeanManager
and ValidatorFactory and similar if they would be just primitive values it
would be lesser of issue.
I was unable to find proper place to fix this. So I would like to ask
people that are more familiar with that area to take a look.
This is GC root from Yourkit profile session:
Paths from "GC Roots" to "Object SerializableValidatorFactory #323736"
+-------------------------------------------------------------------------------------------------------+-----------------+----------------+
|
Name | Retained Size |
Shallow Size |
+-------------------------------------------------------------------------------------------------------+-----------------+----------------+
|
+---org.jboss.as.jpa.validator.SerializableValidatorFactory
| 16 | 16 |
|
|
| | |
| +---value of
java.util.HashMap$Entry
| 64 | 24 |
|
|
| | |
| +---[83] of
java.util.HashMap$Entry[256]
| 4.088 | 1.040 |
|
|
| | |
| +---table of
java.util.HashMap
| 4.152 | 48 |
|
|
| | |
| +---configurationValues of
org.hibernate.boot.registry.internal.StandardServiceRegistryImpl |
15.688 | 24 |
|
|
| | |
| +---serviceRegistry of
org.jboss.as.jpa.hibernate4.JBossAppServerJtaPlatform
| 15.776 | 40 |
|
|
| | |
| +---delegate of
org.jboss.as.jpa.hibernate4.DefaultJtaPlatform
| 16.128 | 352 |
|
|
| | |
| +---[7] of
java.lang.Object[2560]
| 258.520 | 10.256 |
|
|
| | |
| +---elementData of
java.util.Vector |
258.544 | 24 |
|
|
| | |
| +---classes of
org.jboss.modules.ModuleClassLoader
| 518.696 | 80 |
|
|
| | |
| +---referent of
java.util.WeakHashMap$Entry
| 248 | 40 |
|
|
| | |
| +---next of
java.util.WeakHashMap$Entry
| 976 | 40 |
|
|
| | |
| +---[29] of
java.util.WeakHashMap$Entry[32] |
9.720 | 144 |
|
|
| | |
| +---table of
java.util.WeakHashMap |
9.808 | 56 |
|
|
| | |
| +---loaderToCache of java.lang.reflect.Proxy
[Class] | 14.864 | 344 |
+-------------------------------------------------------------------------------------------------------+-----------------+----------------+
I was testing with
http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/kitchensink-html...
to reproduce it all you need to do is deploy app, undeploy it and
profile app server. There should be no BeanManager & ValidatorFactory
instances laying around.
I would also like to encgurage everyone else to profile their part of code
just to make sure we haven't missed anything.
--
tomaz
10 years, 9 months
8.0.0.Alpha3 Released!
by Jason Greene
Hello Everyone,
I am happy to announce the availability of Alpha3, which is available for download in the usual location:
wildfly.org/download
Some key updates in this release are:
• EJB invocations now use HTTP upgrade over port 8080
• This is a major step towards the port reduction initiative we have for WildFly 8
• WildFly can now be ran as a Windows service
• Mod_cluster functionality restored
• Bean Validation 1.1 now supported with JAX-RS and CDI
• Undertow subsystem and integration improvements
• Bytecode enhanced entities now supported in JPA
• User creation script also supports groups
• Initial support for a syslog logging appender
For complete details on what is in Alpha3, see the release notes here:
https://community.jboss.org/wiki/800Alpha3ReleaseNotes
If anyone notices an area I missed, or wishes to add additional notes, feel free to update the wiki entry.
Thanks!
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
10 years, 9 months
When to tag 8.0.0.Alpha3?
by Cheng Fang
Is there an estimate when 8.0.0.Alpha3 will be tagged? I understand
there are issues (like memory leak issues) being worked on, but wanted
to check if my feature (batch integration) can make it, or if Alpha3 is
waiting on it.
Thanks,
Cheng
10 years, 9 months
JAXB APIs and Wildfly
by Shelly McGowan
With JAXB APIs now part of Java SE 7 and Java SE 7 being the minimum requirement for Wildfly, are there plans to remove the explicit
dependency of org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec and com.sun.xml.bind:jaxb-impl?
Would it be more appropriate to include these packages are part of the javax.api module?
Shelly McGowan
JBoss, by Red Hat
10 years, 9 months
ejb-client invocation broken (upstream yesterday/today)
by Wolf-Dieter Fink
I try to run my quickstart (ejb-multi-server) with WildFly.
Configuration and deployment work.
But the (remote) EJB invocation failed. Neither standalone nor client
inside the server works.
If I use an older WildFly pulled at the 07/11 (don't know the exact
commit) everything works fine.
I retest with the ejb-remote QS, here the same issue.
To avoid any maven issue I've used plain java command and include the
correct jboss-client.jar
I've attached the logfiles from a working and non-working attempt.
The only difference I see is that the ejb-client library is new (moved
from 1.x => 2.x.Beta), remoting is unkown and XNIO 3.1.0.CR3.
- Wolf
10 years, 9 months
LSB init script for Debian based distros
by Jorge Solórzano
Hi dev and users of WildFly,
I wish to provide a LSB init script for Debian based distros, and would be
nice to get some feedback about it.
WildFly currently provides init scripts in the bin folder, but this are
designed for RedHat/Fedora and don't integrate correctly with
Debian/Ubuntu....
I could provide a LSB-compliant init script with all the features required
for a complete startup script with some features that are not available in
the current init script such as reload.
I could do some testing in various distros versions if required.
If you are interested send a comment.
Jorge Solórzano
10 years, 9 months
