slf4j
by Steve Ebersole
I am considering moving Hibernate to use slf4j instead of commons-logging. I
had been considering moving to straight log4j usage anyway to get MDC/NDC
capability, but slf4j just added this capability. So it now has all the
capabilities I need.
Just curious whether anyone has seen it used within JBoss AS and what the
experiences were.
19 years
trunk test suite
by Aleksandar Kostadinov
Hi,
When running the test suite it fails as server minimal doesn't shutdown
fast enough. Below there is from the server.log:
...
vfsfile:/qa/services/hudson/hudson_workspace/workspace/JBoss_AS_Testsuite_HEAD-jdk15/src/build/output/jboss-5.0.0.Beta3/server/minimal/deploy/shutdown.sar
2007-07-20 04:36:05,992 ERROR [STDERR] Exception in thread "ExitOnShutdown"
2007-07-20 04:36:05,993 ERROR [STDERR] java.lang.NoClassDefFoundError:
java/lang/System
2007-07-20 04:36:05,994 ERROR [STDERR] at
org.jboss.test.jmx.shutdown.ExitOnShutdown$1.run(ExitOnShutdown.java:52)
2007-07-20 04:36:05,994 ERROR [STDERR] at
java.lang.Thread.run(Thread.java:595)
2007-07-20 04:38:57,671 INFO
[org.jboss.system.server.profileservice.ServerImpl] JBoss SHUTDOWN
...
You can see NoClassDefFoundError java/lang/System and 3 minutes delay.
Odd is that it doesn't happen by the cruisecontrol build on build01. As
environments are identical could that be a timing issue?
Full server log you can see on
http://dev45.qa.atl.jboss.com:8585/hudson/job/JBoss_AS_Testsuite_HEAD-jdk...
All other logs you can see
http://dev45.qa.atl.jboss.com:8585/hudson/job/JBoss_AS_Testsuite_HEAD-jdk...
Any idea?
Thanks,
Aleksandar
19 years
Re: [jboss-dev] JEMS installer for JBossAS 4.2.1.GA
by Thomas Heute
Amit Bhayani wrote:
> Since JEMS Installer is all about different components, I believe it
> would be great if leads of individual component drive the future
> requirements.
> I tried mailing jBPM, Portal, JBoss Messaging, Seam team number of times
> on what they want but didn't get much response.
You should send to jboss-portal(a)redhat.com for us. I don't remember
seeing any email about this, maybe Julien got that.
> JEMS Installer 1.2.1CR2 which included JBoss AS 4.2.0.GA, JBoss
> Messaging 1.2.0.SP1 and Portal 2.6CR3 (Lot of issues were faced here to
> integrate portal 2.6.CR3 with JBoss AS 4.2.0.GA) is still in QA and now
> I don't think it makes any sense to release as all these components are
> already changed.
Still i haven't heard about the issues, 2.6.CR3 was still made for JBoss
AS 4.0.5. Good news 2.6.1 is made for 4.2.1.GA (And still works on 4.0.5.GA)
> So going forward I would request individual leads to open up JIRA
> request on what they want in next release of JEMS Installer, and
> installer team will take care of it.
I know this is difficult but we need some timeframe. For Portal we are
discussing about having time-boxed releases (one every x months, x has
still to be defined) it should be easier for the installer to plan
accordingly.
So basically if you plan to ship the JEMS installer in the next month,
go with JBoss Portal 2.6.1.GA. If this is in 7-8 months that would be
JBoss Portal 2.6.2, otherwise it's useless. (seen as deprecated stuff)
JEMS installer should be released often on short cycles. If it's
something released every month, we wouldn't feel like missing THE boat
when it is about to release a former version (with known issues) of our
products.
So what about something like this:
On the 1st of odd month: check what products are in GA (or SPs).
Send to each project an email with that list.
Give us a week to raise the red flag if there are known integration
issues (most of the time we won't even know, but the released JEMS
installer will help finding those)
If there is no red flag release *quickly*. Otherwise postpone by a month.
Thomas.
19 years
Re: [jboss-dev] JEMS installer for JBossAS 4.2.1.GA
by Tim Fox
In order to know what version of product X goes in what installer
release we need some kind of installer roadmap with dates.
Amit Bhayani wrote:
> Since JEMS Installer is all about different components, I believe it
> would be great if leads of individual component drive the future
> requirements.
> I tried mailing jBPM, Portal, JBoss Messaging, Seam team number of
> times on what they want but didn't get much response.
>
> JEMS Installer 1.2.1CR2 which included JBoss AS 4.2.0.GA, JBoss
> Messaging 1.2.0.SP1 and Portal 2.6CR3 (Lot of issues were faced here
> to integrate portal 2.6.CR3 with JBoss AS 4.2.0.GA) is still in QA and
> now I don't think it makes any sense to release as all these
> components are already changed.
>
> So going forward I would request individual leads to open up JIRA
> request on what they want in next release of JEMS Installer, and
> installer team will take care of it.
>
> Also integration testing is one issue where we don't have concrete
> answer, but remember this is just Community Installer for early
> adoption of new releases of components so I guess emphasis should be
> on releasing the Installer early in cycle rather than 100% accurate.
>
> Amit.
>
> Tim Fox wrote:
>> I would prefer the installer team to hang on too, and include JBM
>> 1.4.0, not 1.3.0 which is already superceded.
>>
>> Can we be involved in the process in the future, regarding timescales
>> and release dates? Then we could advise better about the best version
>> to include
>>
>> I can't see any release dates on JBINSTALL JIRA. When is the release
>> date?
>>
>> Regarding integration tests, we have plenty, but as you know we have
>> been prevented in adding them to AS because you guys don't want JBM
>> there.
>>
>> Dimitris Andreadis wrote:
>>> If you want the latest portal included with the latest installer,
>>> why don't you say so *before* we get to the last stages of releasing
>>> the damned thing?
>>>
>>> Like going to the jems installer JIRA and see what's included in the
>>> next installer release?
>>> http://jira.jboss.com/jira/browse/JBINSTALL
>>>
>>> Anyway, Rajesh's initial question was related to the how we now the
>>> combination works if there is no integration testing in CruiseControl.
>>>
>>> Same for JBoss Messaging.
>>>
>>> It's a valid point that needs to be fixed, however, I was thinking,
>>> those are community releases (not to say installer configs that are
>>> commonly perceived as previews) were we could take our chances and
>>> let the community test the combinations...
>>>
>>> Thomas Heute wrote:
>>>> True, please hold on for the JEMS installer. I'm about to tag JBoss
>>>> Portal 2.6.1 and we will get provide the bundle with JBoss AS4.2.1.GA.
>>>>
>>>> It would be awesome if the JEMS installer could provide the same
>>>> thing :)
>>>>
>>>>
>>>> Bolesław Dawidowicz wrote:
>>>>> I think that JBoss Portal 2.6.1 is going to ship AS 4.2.1.GA, and
>>>>> should come out like next week.
>>>>>
>>>>> Rajesh Rajasekaran wrote:
>>>>>> The JEMS installer for JBossAS 4.2.1.GA (JEMS Installer
>>>>>> 1.2.1.CR3) packages JBoss Portal 2.6.GA for the portal configuration
>>>>>>
>>>>>> and includes JBoss Messaging 1.3.0.GA.
>>>>>>
>>>>>>
>>>>>>
>>>>>> What should be the testing criteria for these components?
>>>>>>
>>>>>>
>>>>>>
>>>>>> JBoss Portal 2.6.GA ships with JBossAS 4.0.5.GA and there is no
>>>>>> continuous integration testing of portal 2.6.x with jboss-4.2.x.
>>>>>>
>>>>>>
>>>>>>
>>>>>> JBoss Messaging 1.3.0.GA was never included in JBoss AS
>>>>>> Branch_4_2. Is there some sort of integration testing that can be
>>>>>> used
>>>>>>
>>>>>> for testing jboss messaging with JBoss AS 4.2.1.GA?
>>>>>>
>>>>>>
>>>>>>
>>>>>> The installer release process
>>>>>> (http://wiki.jboss.org/wiki/Wiki.jsp?page=JEMSInstallerReleaseGuide)
>>>>>> just verifies the functionalities of the
>>>>>>
>>>>>> Installer assuming all the components that go into it work together.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I just brought this up to verify the above components work before
>>>>>> releasing the installer.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Rajesh
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-development mailing list
>>>>>> jboss-development(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>
>>>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>
19 years
Re: [jboss-dev] JEMS installer for JBossAS 4.2.1.GA
by Amit Bhayani
Resending as there was problem initially
Amit Bhayani wrote:
> Since JEMS Installer is all about different components, I believe it
> would be great if leads of individual component drive the future
> requirements.
> I tried mailing jBPM, Portal, JBoss Messaging, Seam team number of
> times on what they want but didn't get much response.
>
> JEMS Installer 1.2.1CR2 which included JBoss AS 4.2.0.GA, JBoss
> Messaging 1.2.0.SP1 and Portal 2.6CR3 (Lot of issues were faced here
> to integrate portal 2.6.CR3 with JBoss AS 4.2.0.GA) is still in QA and
> now I don't think it makes any sense to release as all these
> components are already changed.
>
> So going forward I would request individual leads to open up JIRA
> request on what they want in next release of JEMS Installer, and
> installer team will take care of it.
>
> Also integration testing is one issue where we don't have concrete
> answer, but remember this is just Community Installer for early
> adoption of new releases of components so I guess emphasis should be
> on releasing the Installer early in cycle rather than 100% accurate.
>
> Amit.
>
> Tim Fox wrote:
>> I would prefer the installer team to hang on too, and include JBM
>> 1.4.0, not 1.3.0 which is already superceded.
>>
>> Can we be involved in the process in the future, regarding timescales
>> and release dates? Then we could advise better about the best version
>> to include
>>
>> I can't see any release dates on JBINSTALL JIRA. When is the release
>> date?
>>
>> Regarding integration tests, we have plenty, but as you know we have
>> been prevented in adding them to AS because you guys don't want JBM
>> there.
>>
>> Dimitris Andreadis wrote:
>>> If you want the latest portal included with the latest installer,
>>> why don't you say so *before* we get to the last stages of releasing
>>> the damned thing?
>>>
>>> Like going to the jems installer JIRA and see what's included in the
>>> next installer release?
>>> http://jira.jboss.com/jira/browse/JBINSTALL
>>>
>>> Anyway, Rajesh's initial question was related to the how we now the
>>> combination works if there is no integration testing in CruiseControl.
>>>
>>> Same for JBoss Messaging.
>>>
>>> It's a valid point that needs to be fixed, however, I was thinking,
>>> those are community releases (not to say installer configs that are
>>> commonly perceived as previews) were we could take our chances and
>>> let the community test the combinations...
>>>
>>> Thomas Heute wrote:
>>>> True, please hold on for the JEMS installer. I'm about to tag JBoss
>>>> Portal 2.6.1 and we will get provide the bundle with JBoss AS4.2.1.GA.
>>>>
>>>> It would be awesome if the JEMS installer could provide the same
>>>> thing :)
>>>>
>>>>
>>>> Bolesław Dawidowicz wrote:
>>>>> I think that JBoss Portal 2.6.1 is going to ship AS 4.2.1.GA, and
>>>>> should come out like next week.
>>>>>
>>>>> Rajesh Rajasekaran wrote:
>>>>>> The JEMS installer for JBossAS 4.2.1.GA (JEMS Installer
>>>>>> 1.2.1.CR3) packages JBoss Portal 2.6.GA for the portal configuration
>>>>>>
>>>>>> and includes JBoss Messaging 1.3.0.GA.
>>>>>>
>>>>>>
>>>>>>
>>>>>> What should be the testing criteria for these components?
>>>>>>
>>>>>>
>>>>>>
>>>>>> JBoss Portal 2.6.GA ships with JBossAS 4.0.5.GA and there is no
>>>>>> continuous integration testing of portal 2.6.x with jboss-4.2.x.
>>>>>>
>>>>>>
>>>>>>
>>>>>> JBoss Messaging 1.3.0.GA was never included in JBoss AS
>>>>>> Branch_4_2. Is there some sort of integration testing that can be
>>>>>> used
>>>>>>
>>>>>> for testing jboss messaging with JBoss AS 4.2.1.GA?
>>>>>>
>>>>>>
>>>>>>
>>>>>> The installer release process
>>>>>> (http://wiki.jboss.org/wiki/Wiki.jsp?page=JEMSInstallerReleaseGuide)
>>>>>> just verifies the functionalities of the
>>>>>>
>>>>>> Installer assuming all the components that go into it work together.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I just brought this up to verify the above components work before
>>>>>> releasing the installer.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Rajesh
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-development mailing list
>>>>>> jboss-development(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>
>>>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>
>
19 years
Brock and Diesler: build breakers
by Bill Burke
Hmmmm, how long has it been since Adrian's deployer commit and we still
can't build from trunk? Come on guys. If you're gonna make huge
changes, the build has to work. No exceptions or excuses.
This is ridiculous.
--
Bill Burke
JBoss, a division of Red Hat
http://burkecentral.blogspot.com
19 years
commons-core 2.0.5 release?
by Jason T. Greene
Hi Dimitris,
Is it possible to do a 2.0.5 release of commons-core that includes a fix
for JBCOMMON-25 sometime soon? We need a GA version by mid-july for
JBossCache + POJO Cache. I have already merged the changes into the 2_0
branch.
Thanks,
--
Jason T. Greene
Lead, POJO Cache
JBoss, a division of Red Hat
19 years
Re: [jboss-dev] JEMS installer for JBossAS 4.2.1.GA
by Thomas Heute
True, please hold on for the JEMS installer. I'm about to tag JBoss
Portal 2.6.1 and we will get provide the bundle with JBoss AS4.2.1.GA.
It would be awesome if the JEMS installer could provide the same thing :)
Bolesław Dawidowicz wrote:
> I think that JBoss Portal 2.6.1 is going to ship AS 4.2.1.GA, and should
> come out like next week.
>
> Rajesh Rajasekaran wrote:
>> The JEMS installer for JBossAS 4.2.1.GA (JEMS Installer 1.2.1.CR3)
>> packages JBoss Portal 2.6.GA for the portal configuration
>>
>> and includes JBoss Messaging 1.3.0.GA.
>>
>>
>>
>> What should be the testing criteria for these components?
>>
>>
>>
>> JBoss Portal 2.6.GA ships with JBossAS 4.0.5.GA and there is no
>> continuous integration testing of portal 2.6.x with jboss-4.2.x.
>>
>>
>>
>> JBoss Messaging 1.3.0.GA was never included in JBoss AS Branch_4_2. Is
>> there some sort of integration testing that can be used
>>
>> for testing jboss messaging with JBoss AS 4.2.1.GA?
>>
>>
>>
>> The installer release process
>> (http://wiki.jboss.org/wiki/Wiki.jsp?page=JEMSInstallerReleaseGuide)
>> just verifies the functionalities of the
>>
>> Installer assuming all the components that go into it work together.
>>
>>
>>
>> I just brought this up to verify the above components work before
>> releasing the installer.
>>
>>
>>
>>
>>
>> Thanks
>>
>> Rajesh
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
19 years
EJB3 client launcher
by Heiko Braun
What happended to the EJB3 ClientLauncher?
It's not included [1] in the build anymore and there's an open issue
scheduled [2]. It used to be working and included in the EJB3 client
jars.
[1]
----------------------------------------------
<target name="compile">
[...]
<exclude name="org/jboss/ejb3/client/**"/>
[2]
----------------------------------------------
http://jira.jboss.com/jira/browse/EJBTHREE-718
/Heiko
19 years
