AS 4.2.3.GA freeze
by Dimitris Andreadis
We are going to release AS 4.2.3.GA this week so unless you are working on some last minute
task or testsuite fix, please refrain from making changes to Branch_4_2 (or let me know).
Check out the JIRA in case in case you have some tasks left:
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hid...
I'm thinking of releasing 2 binaries, one build with jdk5 and one build with jdk6, the
latter one will have support for jdbc4 apis. This is mostly needed so JBoss can be released
with Fedora that only includes OpenJDK.
If you have any issues/concerns with this release let me know.
Cheers
/Dimitris
16 years, 5 months
Additional smoke tests
by Adrian Brock
I've added a few additional smoke tests.
They show some new test failures.
These tests look appropriate to me
as "standup tests".
* The "deployers" tests that checks all
the different kind of deployments are processed correctly
* DDValidatorUnitTestCase that validates all
deployment descriptors used by the testsuite
can be parsed with xml validation enabled
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
16 years, 5 months
Oldest bug
by Adrian Brock
The JMXConnectorUnitTestCase is the oldest bug in the JBoss5 testsuite.
I don't think it has ever worked since Tom never finished his
JSR160 implementation and it makes bad assumptions about how
the JDK version (which we now use) does things.
As I explain on the JIRA issue,
http://jira.jboss.com/jira/browse/JBAS-5691
I think we should just remove the one remaining test
since it is testing the JDK implementation not anything
within JBoss.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
16 years, 5 months
JBoss community domain name changes (Affects *.labs.jboss.com, *.forge.jboss.com, *.jboss.org services.)
by Tom Benninger
All,
For the last year we have been using jboss.org domains, rather than the
older labs.jboss.com and forge.jboss.com domains, as the primary site
for JBoss community services. (https://svn.jboss.org instead of
https://svn.labs.jboss.com, for example.)
On the Sunday the 13th we will be converting the web services on older
labs and forge domains to be redirects to jboss.org. This is the first
step in our plans to unify and simplify access to JBoss community
services. Later steps will include the migration of non web services and
the eventual decommissioning of the forge and labs domains.
All services will be maintained, just at *.jboss.org, where they should
already be accessible.
There are some caveats to this:
* Most SVN clients do not support redirection. If you are one of the
handful of users still using svn.labs.jboss.com or other old svn URLS,
you will need to update your clients after the change.
* The domain cms.labs.jboss.com will remain available for short period.
* Non-web services, which do not support redirection will not be
affected at this time.
These changes represent phase one of our effort to clean up domains and
simplify and unify our community service management. As noted above,
further changes will be made in the future.
Thanks,
Tom Benninger
tbenning(a)redhat.com
tom.benninger(a)jboss.com
16 years, 5 months
AS5 startup time
by David M. Lloyd
Transcript from a Random Guy regarding the startup time of 5.0.0.CR1 (his
ear takes nearly 10 times longer to deploy in 5.0.0.CR1 compared to 4.2):
<robmv> has anyone noticed JBoss 5 is extremely slow deploying a big EAR?
<robmv> JBoss 4.2 start with our big EAR in 1.5 minutes. JBoss 5 7 minutes
and counting
<robmv> does not appear to be memory related ([GC
196991K->178224K(312472K), 0.0060150 secs])
<robmv> but because it is looking annotations (I think)
<robmv> 2008-07-04 17:56:27,400 DEBUG
[org.jboss.deployment.AnnotatedClassFilter] (main) Incomplete class:
org.apache.xmlbeans.impl.xpath.saxon.XBeansIndependentContext, NCDFE:
java.lang.NoClassDefFoundError: net/sf/saxon/trans/IndependentContext
<robmv> that is the last line written on the debug log
(org.apache.xmlbeans.impl.xpath.saxon.XBeansIndependentContext is on my
EAR/lin directory)
<robmv> EAR/lib*
<robmv> final time 11m:6s ohhhhhhh
<dmlloyd> is that 5.0.0.CR1?
<robmv> yes
<robmv> memory usage after startup finished: [GC 227524K->204726K(364624K),
0.0403380 secs]
- DML
16 years, 5 months
JBPM Fork parallel (simeltaneous) issue
by Ashish Parikh
Below is the process definition i was trying fork.. The node and node1 are
running sequencially instead of parallel. I am putting wait in
MyActionHandler. It does not execute node1 till node is finished.
Realized that this is the default behavior for jbpm fork.. One way to run
the nodes in parallel is to add async=true property on node.. But it throws
JBPMServiceException: service 'message' unavailable. Any to configure
async=true would be appreciated.
We are using jbpm-jpdl 3.2.2 version.
<process-definition name='TestProcess'>
<start-state>
<transition name='fork' to='fork'>
</transition>
</start-state>
<fork name='fork'>
<transition to='node'></transition>
<transition to='node1'></transition>
</fork>
<node name='node'>
<action class='MyActionHandler' config-type='field'>
<inputs>inputs from node node;</inputs>
</action>
<transition to='join'></transition>
</node>
<node name='node1'>
<action class='MyActionHandler' config-type='field'>
<inputs>inputs from node1</inputs>
</action>
<transition to='join'></transition>
</node>
<join name='join'>
<transition to='node2' />
</join>
<node name='node2'>
<action class='MyActionHandler' config-type='field'>
<inputs>inputs from node2;</inputs>
</action>
<transition to='end'></transition>
</node>
<end-state name='end' />
</process-definition>
--
View this message in context: http://www.nabble.com/JBPM-Fork-parallel-%28simeltaneous%29-issue-tp18325...
Sent from the JBoss - Dev mailing list archive at Nabble.com.
16 years, 5 months
JBoss AS 4.2.3.GA
by Dimitris Andreadis
Now that AS5 CR1 is out, I think we can afford to spend some cycles in the background to
produce AS 4.2.3.GA. There are 100+ bug fixes committed to Branch_4_2 since AS 4.2.2.GA went
out 8 months ago, so I think it is important to get those out to the community.
----------------------
The first thing is to complete any component updates. If there is an update that you want to
see included, and you can justify the reason (i.e. is fully compatible and solves some
important bug), now is the time to do so:
http://jira.jboss.com/jira/browse/JBAS-4874
-----------------------
Second step is to review the AS 4.2.3.GA JIRA and make sure any important tasks (i.e. bugs)
that still need to be fixed are marked as Critical/Blockers. Some unscheduled tasks could
also be rescheduled for 4.2.3.GA. Before doing that you must be prepared to spend time on
those, or find someone that can. Our primary goal is to get out those bugs already solved,
not spend more time on new fixes.
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hid...
I will push forward or unschedule tasks marked as Major or less.
------------------------
The third step is to make 4.2.x build & run with jdk6. This is needed to get JBossAS
distributed with Fedora, that now bundles OpenJDK 6, so we need to make sure JBossAS
compiles and runs under sun jdk6/openjdk6:
http://jira.jboss.com/jira/browse/JBAS-4501
http://jira.jboss.com/jira/browse/JBAS-5712
This incorporates 2 new testsuite runs:
JBoss-AS-4.2.x-TestSuite-openjdk16-openjdk16
JBoss-AS-4.2.x-TestSuite-sun15-sun16
Independent of Fedora, there is the question of how we ship JBoss for jdk6. If we compile
with jdk5 and run with jdk6 then JDBC 4.0 support will not be compiled into the JCA classes.
I see 3 options:
a) we say we don't support JDBC 4.0, we ship only jdk5 compiled binaries, that can run under
jdk5/jdk6.
b) We make a dual jdk6 build for jboss-common-jdbc-wrapper.jar (and possibly other libs),
include those in docs/examples/jdk6 together with a script that is able to replace those
libraries as a post installation step, for those that want JDBC 4.0 support.
c) we create a separate jbossas-jdk6-x.y.z.GA distro
We are facing the same issue with AS5, so your input is very much appreciated.
----------------------------
The final (fourth) step is to make sure all testsuites/tck are in order:
http://jira.jboss.com/jira/browse/JBAS-5722
- compatibility matrix
- sun15
- jrockit15
- sun15sun16
- openjdk16openjdk16
- tck14
- ejb3
- ws
-----------------------------
We could try to release sometime after July 14th, but I don't want to put down a hard date
before we evaluate the current status of the testsuites.
Again for those working on AS5 CR2, AS 4.2.3.GA is not our #1 priority. We have put it on
the backburner for some time now, so let's get over with it without much fuss.
Any issues/concerns let me know.
Thank you
/Dimitris
16 years, 5 months
