[JBoss-dev] JIRA back online (was RE: JIRA Downtime/Upgrade at 8 PM EDT Today)

[Ryan Campbell]

Title: JIRA back online (was RE: JIRA Downtime/Upgrade at 8 PM EDT Today)






This is complete; the JIRA server is online.

Please report any issues to [EMAIL PROTECTED] .

_
From: Ryan Campbell
Sent: Tuesday, June 27, 2006 8:15 AM
To: The Core; jboss-development@lists.sourceforge.net
Cc: QA; IT Ops
Subject: JIRA Downtime/Upgrade at 8 PM EDT Today

We are upgrading the JIRA instance to a faster box, and the latest version of JIRA.  The main purpose of this upgrade is reduced downtime and improved performance.

JIRA will go down at 8 PM EDT.  It will remain offline until the migration is complete.  I expect it to be back online early in the morning, EDT, and will send out a notice once the new server is live.

See below for the new features you can expect from this upgrade:

http://confluence.atlassian.com/display/JIRA/JIRA+3.3+Release+Notes 

http://confluence.atlassian.com/display/JIRA/JIRA+3.4+and+3.4.1+Release+Notes 

http://confluence.atlassian.com/display/JIRA/JIRA+3.5+Release+Notes 

http://confluence.atlassian.com/display/JIRA/JIRA+3.6+Release+Notes

In addition to this, we will be deploying the Fisheye plugin for more reliable integration with CVS and SVN.

As a note, this deployment will only include the “Release Notes Report” custom plugin.  The additional Global Reports (developer involvement, issues closed, developers per project, etc) will be deployed at a later, to be determined time.

Thanks,

Ryan Campbell

QA Manager

JBoss, a division of Red Hat


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] What is this repository.jboss.com/jboss/artifactscontent?

[Ryan Campbell]

These are jars required by portal. Where should they go instead?

I also see repository.jboss.com/jbossas/core-libs which is probably the
convention which should have been used here, no?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Tuesday, June 27, 2006 6:16 PM
To: JBoss.org development list
Subject: [JBoss-dev] What is this
repository.jboss.com/jboss/artifactscontent?

What is this subset of jbossas content for?

[EMAIL PROTECTED] jboss]$ ls artifacts/4.0.4.GA/lib/
CVS/   jboss-saaj.jar
jboss-aspect-library.jar   jboss-system.jar
jboss-common-client.jarjboss-transaction.jar
jboss-common-jdbc-wrapper.jar  jboss.jar
jboss-common.jar   jbossha.jar
jboss-hibernate.jarjbosssx.jar
jboss-j2ee.jar jmx-invoker-adaptor-client.jar
jboss-jaxrpc.jar   jnp-client.jar
jboss-jca.jar  jnpserver.jar
jboss-jmx.jar  namespace.jar
jboss-local-jdbc.jar
 

Scott Stark
VP Architecture & Technology
JBoss, a division of Red Hat
 
 

Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] JIRA Downtime/Upgrade at 8 PM EDT Today

[Ryan Campbell]

Title: JIRA Downtime/Upgrade at 8 PM EDT Today






We are upgrading the JIRA instance to a faster box, and the latest version of JIRA.  The main purpose of this upgrade is reduced downtime and improved performance.

JIRA will go down at 8 PM EDT.  It will remain offline until the migration is complete.  I expect it to be back online early in the morning, EDT, and will send out a notice once the new server is live.

See below for the new features you can expect from this upgrade:

http://confluence.atlassian.com/display/JIRA/JIRA+3.3+Release+Notes 

http://confluence.atlassian.com/display/JIRA/JIRA+3.4+and+3.4.1+Release+Notes 

http://confluence.atlassian.com/display/JIRA/JIRA+3.5+Release+Notes 

http://confluence.atlassian.com/display/JIRA/JIRA+3.6+Release+Notes

In addition to this, we will be deploying the Fisheye plugin for more reliable integration with CVS and SVN.

As a note, this deployment will only include the “Release Notes Report” custom plugin.  The additional Global Reports (developer involvement, issues closed, developers per project, etc) will be deployed at a later, to be determined time.

Thanks,

Ryan Campbell

QA Manager

JBoss, a division of Red Hat


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Tomcat 6 integrated

[Ryan Campbell]

So, head should only be compilable with a 1.5 jdk.

However, some modules will still enforce source & target at 1.4, so that
we can back merge fixes to the jboss4 tree.

Correct?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Anil Saldhana
Sent: Thursday, June 22, 2006 11:10 AM
To: Scott M Stark
Cc: JBoss.org development list; The Core; Bill Burke
Subject: Re: [JBoss-dev] Tomcat 6 integrated

Ruel is looking into this.  The issue is that the Tomcat jars need JDK5 
for compilation and the way the current HEAD build is setup, we may have

some issues.

Scott M Stark wrote:
> The tomcat module needs jdk5, not all of head. jboss5 will require a
> jdk5 runtime. 
>
>   
>> -Original Message-
>> From: Anil Saldhana 
>> Sent: Thursday, June 22, 2006 8:06 AM
>> To: JBoss.org development list
>> Cc: Bill Burke; The Core
>> Subject: Re: [JBoss-dev] Tomcat 6 integrated
>>
>> Hi Scott,
>> with regard to the current TC6 integration that Bill 
>> undertook in HEAD:
>>http://jira.jboss.com/jira/browse/JBAS-3330
>>
>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85382
>>
>> This has placed a need for JDK5 in HEAD as TC6 needs it.
>>
>> You will need to make a decision to make HEAD requiring JDK5.
>>
>> Regards,
>> Anil
>> 
>
>   


Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Thirdparty licenses

[Ryan Campbell]

So, we want it to fail fatally, instead of just eating the error like it
does now.

-Original Message-
From: Adrian Brock 
Sent: Monday, June 19, 2006 11:35 AM
To: jboss-development
Cc: QA
Subject: Thirdparty licenses

There are problems with the license types
of some of the newer additions to thirdparty.

e.g.
sun-jaxb refers to CDDL-1.0 (it should be cddl?)
quartz refers to ASL 2.0 (it should be Apache-2.0?)

Here are the licenses that actually exist:
http://repository.jboss.com/licenses/

I think the thirdparty processing should verify
the existance of the license.

We obviously can't trust individual developers to verify
this, otherwise this current problem wouldn't exist. :-)

Instead it just gives errors, e.g.

[get-ASL 2.0] Getting: http://repository.jboss.com/licenses/ASL 2.0.txt
[get-ASL 2.0] To: /home/ejort/jboss-4.0/build/../thirdparty/licenses/ASL
2.0.txt
[get-ASL 2.0] Error opening connection java.io.IOException
[get-ASL 2.0] Error opening connection java.io.IOException
[get-ASL 2.0] Error opening connection java.io.IOException
[get-ASL 2.0] Can't get http://repository.jboss.com/licenses/ASL 2.0.txt
to /home/ejort/jboss-4.0/build/../thirdparty/licenses/ASL 2.0.txt

-- 

Adrian Brock
Chief Scientist
JBoss Inc.




___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] JBossAS v4.0.4.SP1

[Ryan Campbell]

We can create a separate 4.0.4_SP testsuite run for this, scheduled for
every few hours as before.

It just involves adding a few lines to an xml file, should be done
today.

-Original Message-
From: Dimitris Andreadis 
Sent: Friday, June 02, 2006 10:50 AM
To: Dimitris Andreadis; 'jboss-development@lists.sourceforge.net'; QA
Cc: Scott M Stark; Bill Burke; Alex Pinkin; Ryan Campbell; Ivelin
Ivanov; Ruel Loehr
Subject: RE: JBossAS v4.0.4.SP1

I'm not sure what's the best way to handle this, make CC 4.0. builds,
point to Branch_4_0_4_SP instead (for a week until we release this), or
introduce new CC build/testsuite/compatibility builds for 4.0.4.SP1?

Ryan? 

> -Original Message-
> From: Dimitris Andreadis 
> Sent: 02 June, 2006 18:11
> To: jboss-development@lists.sourceforge.net; QA
> Cc: Scott M Stark; Bill Burke; Alex Pinkin; Ryan Campbell; 
> Ivelin Ivanov; Ruel Loehr
> Subject: JBossAS v4.0.4.SP1
> 
> We are going to have an SP1 for 4.0.4 just before JBW, to fix 
> minor glitches and upgrade EJB3 to CR8.
> 
> Branch JBoss_4_0_4_SP was created for this purpose, to check 
> this out use:
> 
> cvs co -r JBoss_4_0_4_SP jboss-4.0.x
> 
> The JIRA for this SP1 is here:
> http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=tr
> ue&pid=10030&fixfor=12310828
> 
> I've made this entry for QA to handle the release
> http://jira.jboss.com/jira/browse/JBQA-381
> 
> We'll also upgrade jboss-serialization to 1.0.1.
> 
> Any other important/annoying things you want to fix in 4.0.4, 
> this is your chance. But do keep it simple because there is 
> virtually no time for experiments at this point.
> 
> Thanks
> /Dimitris
> 


___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Error deploying latest Seam on JBoss-4.0.4.GA

[Ryan Campbell]

Ok, I think you mean not up to date with jboss-4.0?

Just be aware 4.0.4.GA comes is about to be released tonight (just
waiting for sourceforge).  I'm worried about hundreds of seam converts
following your directions and seeing the stack trace below...  JavaOne
and all that...

-Original Message-
From: Gavin King 
Sent: Sunday, May 14, 2006 9:12 PM
To: Ryan Campbell; Dev - JBossSeam
Cc: 'jboss-development@lists.sourceforge.net'
Subject: Re: Error deploying latest Seam on JBoss-4.0.4.GA

Seam is not yet up to date with the latest unreleased changes in jboss
head.


--
Sent from my BlackBerry Wireless Handheld


-Original Message-----
From: Ryan Campbell
To: Gavin King; Dev - JBossSeam
CC: 'jboss-development@lists.sourceforge.net'

Sent: Sun May 14 21:06:38 2006
Subject: Error deploying latest Seam on JBoss-4.0.4.GA

I checked out Seam from head, and I'm trying to deploy the booking
example on JBoss-4.0.4.  I've followed the instructions in the
readme.txt (installed the ejb3 profile, deployed the seam booking).

When I start the instance, I receive the error below.

Is the Seam 1.0 release being tested on Jboss-4.0.4.GA?  Or did I do
something wrong?

21:51:40,523 INFO  [EARDeployer] Init J2EE application:
file:/home/rcampbell/jboss-4.0.4.GA/seam/server/default/deploy/jboss-sea
m-booking.ear
21:51:41,778 WARN  [ServiceController] Problem creating service
jboss.j2ee:service=EJB3,module=jboss-seam-booking.jar
java.lang.NoClassDefFoundError: javax/ejb/InvocationContext
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)
at java.lang.Class.getDeclaredMethods(Class.java:1763)
at
org.jboss.ejb3.interceptor.InterceptorInfoRepository$AnnotationInitialis
er.getInfo(InterceptorInfoRepository.java:656)
at
org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialiseFromAnnot
ations(InterceptorInfoRepository.java:454)
at
org.jboss.ejb3.interceptor.InterceptorInfoRepository.getOrInitialiseFrom
Annotations(InterceptorInfoRepository.java:436)
at
org.jboss.ejb3.interceptor.InterceptorInfoRepository.getOrInitialiseFrom
Annotations(InterceptorInfoRepository.java:422)
at
org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialiseDefaultIn
terceptors(InterceptorInfoRepository.java:411)
at
org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialise(Intercep
torInfoRepository.java:100)
at
org.jboss.ejb3.Ejb3HandlerFactory$DDFactory.(Ejb3HandlerFactory.ja
va:44)
at
org.jboss.ejb3.Ejb3HandlerFactory.getInstance(Ejb3HandlerFactory.java:79
)
at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:507)
at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:463)
at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:125)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSup
port.java:260)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
Support.java:243)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
...


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Error deploying latest Seam on JBoss-4.0.4.GA

[Ryan Campbell]

Title: Error deploying latest Seam on JBoss-4.0.4.GA






I checked out Seam from head, and I’m trying to deploy the booking example on JBoss-4.0.4.  I’ve followed the instructions in the readme.txt (installed the ejb3 profile, deployed the seam booking).

When I start the instance, I receive the error below.

Is the Seam 1.0 release being tested on Jboss-4.0.4.GA?  Or did I do something wrong?

21:51:40,523 INFO  [EARDeployer] Init J2EE application: file:/home/rcampbell/jboss-4.0.4.GA/seam/server/default/deploy/jboss-seam-booking.ear

21:51:41,778 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=jboss-seam-booking.jar

java.lang.NoClassDefFoundError: javax/ejb/InvocationContext

    at java.lang.Class.getDeclaredMethods0(Native Method)

    at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)

    at java.lang.Class.getDeclaredMethods(Class.java:1763)

    at org.jboss.ejb3.interceptor.InterceptorInfoRepository$AnnotationInitialiser.getInfo(InterceptorInfoRepository.java:656)

    at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialiseFromAnnotations(InterceptorInfoRepository.java:454)

    at org.jboss.ejb3.interceptor.InterceptorInfoRepository.getOrInitialiseFromAnnotations(InterceptorInfoRepository.java:436)

    at org.jboss.ejb3.interceptor.InterceptorInfoRepository.getOrInitialiseFromAnnotations(InterceptorInfoRepository.java:422)

    at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialiseDefaultInterceptors(InterceptorInfoRepository.java:411)

    at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialise(InterceptorInfoRepository.java:100)

    at org.jboss.ejb3.Ejb3HandlerFactory$DDFactory.(Ejb3HandlerFactory.java:44)

    at org.jboss.ejb3.Ejb3HandlerFactory.getInstance(Ejb3HandlerFactory.java:79)

    at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:507)

    at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:463)

    at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:125)

    at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)

    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)

    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)

…

[JBoss-dev] RE: FW: jboss-4.0.4 portal-2.2 issue

[Ryan Campbell]

Yes, ehcache is included in Portal, just a previous version.

We are testing with ehcache 1.2, per Emmanuel's comment.

If it works, we can document the workaround for now, and possibly
release Portal 2.2.1.SP1 shortly after 4.0.4?

-Original Message-
From: Adrian Brock 
Sent: Friday, May 12, 2006 1:42 PM
To: Ryan Campbell
Cc: Steve Ebersole; Julien Viet; Roy Russo;
jboss-development@lists.sourceforge.net; QA
Subject: Re: FW: jboss-4.0.4 portal-2.2 issue

Actually (2) is not an option because it looks like 
Portal/Hibernate in 2.2 is expecting a different/incompatible
version of EhCache?

On Fri, 2006-05-12 at 20:34 +0200, Adrian Brock wrote:
> Why isn't portal using JBoss's hibernate-int session factory?
> 
> The solutions are:
> 1) JBoss Portal's session factory is configured to use JBoss Cache 
> not EhCache
> 2) JBossAS's installer should include EhCache as an optional
> part of the install
> 3) JBoss Portal includes EhCache itself (since it is not a part of the
> JBossAS install)
> 
> On a related issue, why does Portal have its own transaction
> demarcation? :-)
> 
>
org.jboss.portal.common.transaction.Transactions.notSupported(Transactio
ns.java:245)
> 
> Looks like too much "not invented here" in the Portal code
> that JBossAS can do nothing about.
> 
> > 
> > 
> On Fri, 2006-05-12 at 13:05 -0500, Ryan Campbell wrote:
> > Portal 2.2.1 fails to deploy on 4.0.4.  Is this a bug in Hibernate?

> > 
> >
> >
__
> > From:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of
> > Rali Genova
> > Sent: Friday, May 12, 2006 12:00 PM
> > To: Ryan Campbell
> > Subject: jboss-4.0.4 portal-2.2 issue
> > 
> > 
> >  
> > 
> > Attached is the server log, but here is the relevant exception. I
was
> > using the Hypersonic DB and then MySQL, repeats with both. The AS is
> > built from source, I am working on verifying this with the installer
> > that Scott created as well.
> > 
> > 2006-05-12 11:22:16,353 DEBUG
[org.hibernate.impl.SessionFactoryImpl]
> > instantiating session factory with properties:...(I took those off)
> > 2006-05-12 11:22:16,363 WARN  [org.jboss.system.ServiceController]
> > Problem starting service portal:service=Hibernate
> > java.lang.IllegalAccessError: tried to access method
> > net.sf.ehcache.CacheManager.()V from class
> > org.hibernate.cache.EhCacheProvider
> > at
> > org.hibernate.cache.EhCacheProvider.start(EhCacheProvider.java:124)
> > at
> >
org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:180
)
> > at
> >
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1
213)
> > at org.jboss.portal.core.hibernate.SessionFactoryBinder
> > $3.run(SessionFactoryBinder.java:509)
> > at
> >
org.jboss.portal.common.transaction.Transactions.apply(Transactions.java
:199)
> > at
> >
org.jboss.portal.common.transaction.Transactions.notSupported(Transactio
ns.java:245)
> > at
> >
org.jboss.portal.core.hibernate.SessionFactoryBinder.createSessionFactor
y(SessionFactoryBinder.java:505)
> > at
> >
org.jboss.portal.core.hibernate.SessionFactoryBinder.startService(Sessio
nFactoryBinder.java:291)
> > at
> >
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp
ort.java:289)
> > at
> >
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
> > at
> >
org.jboss.portal.common.system.AbstractJBossService.start(AbstractJBossS
ervice.java:86)
> > at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
> > at
> >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> >
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
java:155)
> > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> > at
> >
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.
java:133)
> > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> > at
> >
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea
nOperationInterceptor.java:142)
> > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> > at
> >
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
a:264)
> > at
> > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> > at org.jboss.system.ServiceController
&

[JBoss-dev] FW: jboss-4.0.4 portal-2.2 issue

[Ryan Campbell]

Portal 2.2.1 fails to deploy on 4.0.4. 
Is this a bug in Hibernate?  









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rali Genova
Sent: Friday, May 12, 2006 12:00
PM
To: Ryan Campbell
Subject: jboss-4.0.4 portal-2.2
issue



 

Attached is the server log, but here is the relevant exception. I was
using the Hypersonic DB and then MySQL, repeats with both. The AS is built from
source, I am working on verifying this with the installer that Scott created as
well.

2006-05-12 11:22:16,353 DEBUG [org.hibernate.impl.SessionFactoryImpl]
instantiating session factory with properties:...(I took those off)
2006-05-12 11:22:16,363 WARN  [org.jboss.system.ServiceController] Problem
starting service portal:service=Hibernate
java.lang.IllegalAccessError: tried to access method
net.sf.ehcache.CacheManager.()V from class
org.hibernate.cache.EhCacheProvider
    at
org.hibernate.cache.EhCacheProvider.start(EhCacheProvider.java:124)
    at
org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:180)
    at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1213)
    at
org.jboss.portal.core.hibernate.SessionFactoryBinder$3.run(SessionFactoryBinder.java:509)
    at
org.jboss.portal.common.transaction.Transactions.apply(Transactions.java:199)
    at
org.jboss.portal.common.transaction.Transactions.notSupported(Transactions.java:245)
    at
org.jboss.portal.core.hibernate.SessionFactoryBinder.createSessionFactory(SessionFactoryBinder.java:505)
    at
org.jboss.portal.core.hibernate.SessionFactoryBinder.startService(SessionFactoryBinder.java:291)
    at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
    at
org.jboss.portal.common.system.AbstractJBossService.start(AbstractJBossService.java:86)
    at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown
Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
    at $Proxy0.start(Unknown Source)


-- 
Bug? That's not a bug, that's a feature. 

[JBoss-dev] RE: FW: 4.0.4.CR2 distribution (.zip only?)

[Ryan Campbell]

It looks like we just need to add a zipfileset for the *.sh files and
use the filemode attribute with the exec bit set.  This should work with
"most unixes"; we'll test on solaris, linux & hp.

http://ant.apache.org/manual/CoreTypes/zipfileset.html

Otherwise, we'll use native zip.

For the record, we do build on unix.

I guess this hasn't been an issue up until now because most folks used
tar.gz on unix, as did I.

-Original Message-
From: Dimitris Andreadis 
Sent: Friday, May 05, 2006 7:30 AM
To: Mladen Turk
Cc: Scott M Stark; QA; jboss-development@lists.sourceforge.net
Subject: RE: FW: 4.0.4.CR2 distribution (.zip only?)


I tested it too, so if we zip with /usr/bin/zip the produced zip file
maintains the file permissions, as long as you unzip with
/usr/bin/unzip.

If you use the 'jar' utility, the permission are lost when zipping, and
also ignored when unzipping (if they were put there by /usr/bin/zip).

So a solution would be to 

A) Make sure the jboss bin .sh file have the correct permissions, or
'chmod ugo+rx $JBOSS_HOME/bin/*.sh' (since those are set in the bin-tgz
target, etc.)

B) zip with the external utility, e.g.: /usr/bin/zip -9qr
jboss-4.0.4.GA.zip jboss-4.0.4.GA/

C) Document that the user needs to either use the zip utility on unix,
or jar -xvf and chmod yourself.

Can someone from QA comment?


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jbossws-testsuite Build Failed

[Ryan Campbell]

Compile failures in jbossws: [javac] /services/cruisecontrol/checkout/jbossws-testsuite/src/main/java/org/jboss/ws/metadata/EndpointMetaData.java:36: package org.jboss.webservice.metadata.serviceref does not exist    [javac] import org.jboss.webservice.metadata.serviceref.HandlerMetaData;    [javac] ^    [javac] /services/cruisecontrol/checkout/jbossws-testsuite/src/main/java/org/jboss/ws/metadata/ServiceMetaData.java:39: package org.jboss.webservice.metadata.jaxrpcmapping does not exist    [javac] import org.jboss.webservice.metadata.jaxrpcmapping.JavaWsdlMapping;    [javac]    ^    [javac] /services/cruisecontrol/checkout/jbossws-testsuite/src/main/java/org/jboss/ws/metadata/ServiceMetaData.java:40: package org.jboss.webservice.metadata.jaxrpcmapping does not exist    [javac] import org.jboss.webservice.metadata.jaxrpcmapping.JavaWsdlMappingFactory;    [javac]    ^    [javac] /services/cruisecontrol/checkout/jbossws-testsuite/src/main/java/org/jboss/ws/metadata/EndpointMetaData.java:81: cannot find symbol    [javac] symbol  : class HandlerMetaData    [javac] location: class org.jboss.ws.metadata.EndpointMetaData    [javac]    private List handlers = new ArrayList();    [javac] ^    [javac] /services/cruisecontrol/checkout/jbossws-testsuite/src/main/java/org/jboss/ws/metadata/EndpointMetaData.java:337: cannot find symbol    [javac] symbol  : class HandlerMetaData    [javac] location: class org.jboss.ws.metadata.EndpointMetaData    [javac]    public void addHandler(HandlerMetaData handler)

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 03, 2006 3:36
AM
To: jboss-development@lists.sourceforge.net;
QA
Subject: jbossws-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossws-testsuite?log=log20060503043454




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jbossws-testsuite.xml:41:
  Exit code: 1 See compilejbossws.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 05/03/2006 04:34:54
  
 
 
  
  Time
  to build: 1 minute 31 seconds
  
 




 




 
  
  
  
   

 Unit Tests:
(0)  Total Errors and Failures: (0) 

   
   



 
  
   
  
 





 


 


 

   
   

 


 


 


 

   
   

 


 


 

   
  
  
   
  
  
   

 Modifications
since last build:  (first 50 of 0) 

   
  
  
   
  
  
   

 

   
  
  
  
  
 




 

[JBoss-dev] RE: jboss-head-jdk-matrix Build Failed

[Ryan Campbell]

No, it doesn't.  

We plan to reduce the lag on the repository updates, which should reduce
our exposure to this problem.

-Original Message-
From: Adrian Brock 
Sent: Tuesday, May 02, 2006 4:45 PM
To: QA
Cc: Adrian Brock; Bill Burke; Brian Stansberry; Clebert Suconic;
Dimitris Andreadis; [EMAIL PROTECTED];
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; Ovidiu
Feodorov; Rajesh Rajasekaran; Thomas Diesler; Weston Price
Subject: Re: jboss-head-jdk-matrix Build Failed

It looks like the "popcorn" check done by cruisecontrol
doesn't take into account waiting for the repository update to take
place?

synchronize.jboss/microcontainer:
  [get] Getting:
http://repository.jboss.com/jboss/microcontainer/snapshot/component-info
.xml
  [get] To:
/services/cruisecontrol/checkout/jboss-head/thirdparty/jboss/microcontai
ner/component-info.xml
  [get] local file date : Tue May 02 13:30:19 EDT 2006
  [get] Not modified - so not downloaded


On Tue, 2006-05-02 at 17:00 -0400, [EMAIL PROTECTED] wrote:
> View results here ->
>
http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log
=log20060502164357
> 
>  BUILD FAILED
>   Ant Error
> Message:
/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The
following error occurred while executing this line:
/services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit
code: 1 See compile.log in Build Artifacts for details.
>   Date of build: 05/02/2006 16:43:57
>  Time to build: 15 minutes 38 seconds
>   Last changed: 05/02/2006 16:18:48
>   Last log entry: Temporary fix for optional compilation with JDK1.4
> 
> 

>Unit Tests: (0)  Total Errors and Failures: (0) 
>
>
> 
>  Modifications
>   since last
> build:  (first
>  50 of 139) 
>  1.4
>modified
>dimitris
>
testsuite/src/main/org/jboss/test/jmx/test/BaseURLDeploymentScannerTestC
ase.java
> JBAS-3119, add
> URLDeploymentScanner suspendDeployment(URL)/resumeDeployment(URL) test
>  1.3
>modified
>dimitris
>
testsuite/src/main/org/jboss/test/jmx/test/SimpleURLDeploymentScannerUni
tTestCase.java
> JBAS-3119, add
> URLDeploymentScanner suspendDeployment(URL)/resumeDeployment(URL) test
>  1.9
>modified
>dimitris
>  testsuite/src/main/org/jboss/test/deployment/DeploymentTestCase.java
>  make
> org.jboss.test.JBossTestServices.getDeployURL() return URL instead of
String
>  1.4
>modified
>dimitris
>
testsuite/src/main/org/jboss/test/deployers/AbstractDeploymentTest.java
>  make
> org.jboss.test.JBossTestServices.getDeployURL() return URL instead of
String
>  1.11
>modified
>dimitris
>
testsuite/src/main/org/jboss/test/classloader/test/ScopingUnitTestCase.j
ava
>  make
> org.jboss.test.JBossTestServices.getDeployURL() return URL instead of
String
>  1.15
>modified
>dimitris
>   testsuite/src/main/org/jboss/test/JBossTestClusteredServices.java
>  make
> org.jboss.test.JBossTestServices.getDeployURL() return URL instead of
String
>  1.5
>modified
>dimitris
>test/src/main/org/jboss/test/JBossTestCase.java
>  make
> org.jboss.test.JBossTestServices.getDeployURL() return URL instead of
String
>  1.7
>modified
>dimitris
>  test/src/main/org/jboss/test/JBossTestServices.java
>  make
> org.jboss.test.JBossTestServices.getDeployURL() return URL instead of
String
>  1.3
>modified
>dimitris
>test/src/main/org/jboss/test/JBossTestSetup.java
>  make
> org.jboss.test.JBossTestServices.getDeployURL() return URL instead of
String
>  1.36
>modified
> 

[JBoss-dev] RE: Change to HEAD Build. Microcontainer now binary dependency.WASRE: jboss-head-jdk-matrix Build Failed

[Ryan Campbell]

You just rename them using the -d option when checking them out.  So the
actual cvs modules use the "jboss-" prefix while the local directories
do not.

-Original Message-
From: Rajesh Rajasekaran 
Sent: Tuesday, May 02, 2006 4:42 PM
To: Adrian Brock; Ryan Campbell
Cc: Scott M Stark; QA; jboss-development@lists.sourceforge.net
Subject: RE: Change to HEAD Build. Microcontainer now binary
dependency.WASRE: jboss-head-jdk-matrix Build Failed

Are the container and kernel modules "jboss-container" &
"jboss-microkernel" as explained in the checkout instructions in the
wiki, or are they just "container" & "microkernel" 



-Original Message-
From: Adrian Brock 
Sent: Tuesday, May 02, 2006 4:37 PM
To: Ryan Campbell
Cc: Adrian Brock; Scott M Stark; QA;
jboss-development@lists.sourceforge.net
Subject: RE: Change to HEAD Build. Microcontainer now binary
dependency.WASRE: jboss-head-jdk-matrix Build Failed

You will just need to checkout the container/dependency/kernel projects
manually (they are no longer a part of the jboss-head alias).
Using whatever tag was added for that release. 

Other than that, it will be the same.

It shouldn't affect AOP. Only AOP2.0 (which hasn't been released yet)
has a dependency on container.

On Tue, 2006-05-02 at 16:20 -0500, Ryan Campbell wrote:
> Will removing these modules from jboss-head prevent previous releases
of
> ejb3, aop & microcontainer from being built?
> 
> I guess the answer is no, but the checkout instructions have changed?
> 
> -Original Message-
> From: Adrian Brock 
> Sent: Tuesday, May 02, 2006 2:21 PM
> To: Scott M Stark
> Cc: Adrian Brock; Ryan Campbell; QA;
> jboss-development@lists.sourceforge.net
> Subject: Change to HEAD Build. Microcontainer now binary dependency.
> WASRE: jboss-head-jdk-matrix Build Failed
> 
> This has been done, except the cruisecontrol changes.
> I've left some other issues open for a more complete standalone build:
> http://jira.jboss.com/jira/browse/JBMICROCONT-87
> 
> The updated build instructions are here:
> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMicrocontainer
> if you already have a previous head checked out, the only change
> is that these projects won't automatically be a part of the main
build.
> 
> The version of the microcontainer used is a snapshot from
> earlier this afternoon. Which will be updated to 2.0.0M1
> when that is finalised.
> 
> On Tue, 2006-05-02 at 16:26 +0200, Adrian Brock wrote:
> > On Tue, 2006-05-02 at 09:07 -0500, Scott M Stark wrote:
> > > > It would potentially be possible to require the MC projects 
> > > > to be developed against head while still being thirdparty 
> > > > binaries in the main jboss-head build.
> > > > i.e. You would checkout the projects separately into the head
> tree.
> > > Meaning just dropping them from the jboss-head module alias and
> manually
> > > checking
> > > them out into it? If that is the case this should just be done
> > > independent of the svn move just to decouple the mc code from
jboss5
> as
> > > currently the only user of these is ejb3 as far as I can see. We
> just
> > > need the mc artifacts pushed out to the repository.
> > > 
> > 
> > Ok, I'll do this. If you want to use JDK5 features, we
> > should also look at make jboss retro binaries.
> > 
> > I'll make JBoss-Head build on the JBossMC-1.0.2.GA
> > binaries. Besides the bean deployer in varia, only EJB3
> > is using it until JBossMC-2.0.0M1 is finished.
> > 
> > Then I'll update the WIKI page on how to develop
> > the microcontainer until we have a proper standalone build.
> > 
> > Cruisecontrol will also need updating once this is done.
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Change to HEAD Build. Microcontainer now binary dependency. WASRE: jboss-head-jdk-matrix Build Failed

[Ryan Campbell]

Will removing these modules from jboss-head prevent previous releases of
ejb3, aop & microcontainer from being built?

I guess the answer is no, but the checkout instructions have changed?

-Original Message-
From: Adrian Brock 
Sent: Tuesday, May 02, 2006 2:21 PM
To: Scott M Stark
Cc: Adrian Brock; Ryan Campbell; QA;
jboss-development@lists.sourceforge.net
Subject: Change to HEAD Build. Microcontainer now binary dependency.
WASRE: jboss-head-jdk-matrix Build Failed

This has been done, except the cruisecontrol changes.
I've left some other issues open for a more complete standalone build:
http://jira.jboss.com/jira/browse/JBMICROCONT-87

The updated build instructions are here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMicrocontainer
if you already have a previous head checked out, the only change
is that these projects won't automatically be a part of the main build.

The version of the microcontainer used is a snapshot from
earlier this afternoon. Which will be updated to 2.0.0M1
when that is finalised.

On Tue, 2006-05-02 at 16:26 +0200, Adrian Brock wrote:
> On Tue, 2006-05-02 at 09:07 -0500, Scott M Stark wrote:
> > > It would potentially be possible to require the MC projects 
> > > to be developed against head while still being thirdparty 
> > > binaries in the main jboss-head build.
> > > i.e. You would checkout the projects separately into the head
tree.
> > Meaning just dropping them from the jboss-head module alias and
manually
> > checking
> > them out into it? If that is the case this should just be done
> > independent of the svn move just to decouple the mc code from jboss5
as
> > currently the only user of these is ejb3 as far as I can see. We
just
> > need the mc artifacts pushed out to the repository.
> > 
> 
> Ok, I'll do this. If you want to use JDK5 features, we
> should also look at make jboss retro binaries.
> 
> I'll make JBoss-Head build on the JBossMC-1.0.2.GA
> binaries. Besides the bean deployer in varia, only EJB3
> is using it until JBossMC-2.0.0M1 is finished.
> 
> Then I'll update the WIKI page on how to develop
> the microcontainer until we have a proper standalone build.
> 
> Cruisecontrol will also need updating once this is done.
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-head-jdk-matrix Build Failed

[Ryan Campbell]

This is the use case which Maven enables especially well, no?

ie, update code in container, build it, and then test the impact in AOP.
The jars from container are integrated into the AOP build using Maven's
local repository.  There is no "update the repository step" since it is
part of the default build cycle.

-Original Message-
From: Scott M Stark 
Sent: Tuesday, May 02, 2006 11:54 AM
To: Adrian Brock
Cc: Ryan Campbell; QA; jboss-development@lists.sourceforge.net
Subject: RE: jboss-head-jdk-matrix Build Failed

We have to bootstrap the repository with a snapshot version. This can be
a local jbossbuild repository override to avoid having to synch through
cvs and then out to the webserver.

It's the same problem we will face when developing multiple maven
projects with inter-dependencies. Maven just has a natural mechanism for
bootstrapping its repository by following the dependency and building
the projects as needed by adding a parent project.

> -Original Message-
> From: Adrian Brock 
> Sent: Tuesday, May 02, 2006 9:31 AM
> To: Scott M Stark
> Cc: Adrian Brock; Ryan Campbell; QA; 
> jboss-development@lists.sourceforge.net
> Subject: RE: jboss-head-jdk-matrix Build Failed
> 
> The first problem I've come across is that AOP is using the 
> "container"
> project for the metadata repository interfaces.
> 
> There is no binary release of this yet, since it is still 
> being developed.
> 
> So how doable is this while we are still working on the 
> AOP/MC integration with still unstable apis?


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] jboss-4.0 testsuite build fails

[Ryan Campbell]

I think this error has something to do with the update of
commons-logging yesterday?

http://fisheye.jboss.com/changelog/JBoss/build/jboss?cs=Branch_4_0:stark
sm:20060422185517


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Kabir Khan
Sent: Sunday, April 23, 2006 4:27 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] jboss-4.0 testsuite build fails

Any idea what this exception means?

$ build.sh 
Searching for build.xml ...
Buildfile: C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\build.xml
Overriding previous definition of reference to xdoclet.task.classpath

check.inhibit.downloads:

check.proxy:

set.proxy:

createthirdparty:

init:
[mkdir] Created dir:
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\output\gen-src\org\jboss\te
st\c
ts\interfaces
 [copy] Copying 1 file to
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\output\gen-src\org\jboss\te
st\c
ts\interfaces
[mkdir] Created dir:
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\output\gen-src\org\jboss\te
st\c
lassloader\scoping\singleton
 [copy] Copying 1 file to
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\output\gen-src\org\jboss\te
st\c
lassloader\scoping\singleton

compile-resources:
[mkdir] Created dir:
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\output\resources
 [copy] Copying 869 files to
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\output\resources

init-code-generation:
[mkdir] Created dir:
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\output\reports

compile-bean-sources:
[mkdir] Created dir:
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\output\resources\ejb-conf\r
eado
nly\META-INF

BUILD FAILED
C:\cygwin\home\Kabir\cvs\jboss-4.0\testsuite\imports\code-generation.xml
:26:
org.apache.commons.logging.LogConfigurationException:
java.lang.reflect.UndeclaredThrowableException (Caused by
java.lang.reflect.UndeclaredThrowableException)



---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] JBossCache 1.3.0.GA released

[Ryan Campbell]

Is this (and the tutorial issue) not a
good reason for 1.3.1.CR1?  

 

And then 1 week later, once we have a bug
free release, we just rename (and retag it) as 1.3.1.GA.

 









From: Ben Wang 
Sent: Tuesday, April 04, 2006 8:42
PM
To: jboss-development@lists.sourceforge.net
Cc: QA
Subject: RE: [JBoss-dev]
JBossCache 1.3.0.GA released



 

I know this not good timing. :-) But
during my work on migrating ejb3 sfsb passivation using JBossCache (http://jira.jboss.com/jira/browse/EJBTHREE-500),
I have discovered two bugs. And I will need these two fixed so I can check in
my code in head. So first option is to create a patch and use that. Second
option is use the snapshot in JBossCache and couting on that 1.4 release will
be out soon.

 

I am leaning towards the second option
such that if there is any future bug fixes or enahncement then I can create
another shapshot right away. What do people think? And how do I do that
properly?

 

Thanks,

 

-Ben 

 







From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rajesh
 Rajasekaran
Sent: Tuesday, April 04, 2006 6:04
AM
To: jboss-development@lists.sourceforge.net
Cc: QA
Subject: [JBoss-dev] JBossCache
1.3.0.GA released

JBossCache 1.3.0.GA  “Wasabi” has been
released and is available for download at 

http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920

 

JBossCache 1.3.0.GA  has also been updated in the
repository.

 

 

Thanks

Rajesh

JBoss QA

RE: [JBoss-dev] Unassigned for 4.0.4

[Ryan Campbell]

Adrian, it doesn't look like this filter is public.

Errors

* Could not getRequest search with this id.



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Monday, April 03, 2006 2:26 PM
To: jboss-development
Subject: [JBoss-dev] Unassigned for 4.0.4

There are still 19 tasks unassigned for 4.0.4
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestI
d=12310482

We should get these assigned or deferred,
so there isn't a mad rush come release time. :-)
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Upgrade jbossxb to a non-snapshot release

[Ryan Campbell]

It is from head and it is tagged as JBossXB_1_0_0_CR3

-Original Message-
From: Alexey Loubyansky 
Sent: Monday, April 03, 2006 9:40 AM
To: Ryan Campbell
Cc: Scott M Stark; Dimitris Andreadis;
jboss-development@lists.sourceforge.net; QA; Alexey Loubyansky
Subject: Re: Upgrade jbossxb to a non-snapshot release

What snapshot was used for CR3? The one from the repository or the one 
from HEAD?
The one from the repository would be a bad choice because I don't now 
what should go into release notes. Having a release w/o release notes is

no different from using a snapshot.

Ryan Campbell wrote:
> Ok, I'll do the 1.0.0.CR3 release later today and document the process
I
> use in the wiki. 
> 
> -Original Message-
> From: Scott M Stark 
> Sent: Wednesday, March 29, 2006 7:57 PM
> To: Dimitris Andreadis; 'jboss-development@lists.sourceforge.net'; QA
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: Upgrade jbossxb to a non-snapshot release
> 
> If Alexey does not reply by tomorrow I would take the current
jboss-head
> code and make a jbossxb-1.0.0.CR3 release. I don't know how this is
> being built since this has not been broken out yet. For the 4.0.4.GA
the
> common module needs to be broken up into a separate projects with
those
> jars released to the repository and integrated into the jbossas build.
> 
>> -Original Message-
>> From: Dimitris Andreadis 
>> Sent: Wednesday, March 29, 2006 12:01 PM
>> To: jboss-development@lists.sourceforge.net; QA
>> Cc: '[EMAIL PROTECTED]'
>> Subject: Upgrade jbossxb to a non-snapshot release
>>
>>  
>> Related to http://jira.jboss.com/jira/browse/JBAS-3011
>>
>> Alexey, should we just copy the current "snapshot" into a 
>> jbossxb-1.0.0.CR3, or wait another day?
>>
>> Thanks
> 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: JBoss-4.0.4.CR2 today - 4.0.x freeze

[Ryan Campbell]

I had this problem yesterday.  I resolved it by deleting my 
thirdparty/jboss/jbossws directory.  I'm not sure why this isn't being updated 
correctly.

-Original Message-
From: Dimitris Andreadis 
Sent: Friday, March 31, 2006 8:13 AM
To: 'jboss-development@lists.sourceforge.net'; QA
Subject: JBoss-4.0.4.CR2 today - 4.0.x freeze


So we are good to "Go" from Scott about the jboss-4.0.4.CR2 release today!

The 2 remaining WS testsuite issues will be solved sortly after using 
jbossws-1.0.0.CR7, but we won't hold the JBAS release for that.

Please refrain from making changes to Branch_4_0, until we tag the release.

I see there are a couple of issues after the last build.xml updates.

One problem is there is an attempt to build the ejb3/ejb3x modules with jdk1.4 
which shoudn't happen.

Another problem is somehow I'm getting a versioning missmatch from 
apache-logging v1.0.4jboss, but I can't see where is this coming from:

BUILD FAILED
X:\cvs\jboss-public\jboss-4.0\build\build.xml:859: The following error occurred
while executing this line:
X:\cvs\jboss-public\jboss-4.0\build\build-thirdparty.xml:123: A versioning probl
em exists:
Component: apache-logging is at version: 1.0.4jboss
 but it is also required to be compatible with: [EMAIL PROTECTED], ver
sion=1.0.4.1jboss}]
 by: jboss/jbossws

--
xxx
Dimitris Andreadis
Core Developer
JBoss Europe SàRL
xxx


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Upgrade jbossxb to a non-snapshot release

[Ryan Campbell]

I'm seeing several jbossxb testsuite failures.  The report is below.
This is from the tests-xml-unit target. 


JBoss daily test results

SUMMARY

Number of tests run:   221



Successful tests:  208

Errors:4

Failures:  9




DETAILS OF ERRORS



Suite:   org.jboss.test.xml.AnnotatedPojoServerUnitTestCase
Test:testGenericBeanFactory
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: 
-



Suite:   org.jboss.test.xml.AnnotatedPojoServerUnitTestCase
Test:testDemandSupply
Type:error
Exception:   java.lang.ClassCastException
Message: java.lang.String
-



Suite:   org.jboss.test.xml.AnnotatedPojoServerUnitTestCase
Test:testDemandSupplyWhenRequired
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected: but was:
-



Suite:   org.jboss.test.xml.AnnotatedPojoServerUnitTestCase
Test:testSimpleCollection
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:<2> but was:<0>
-



Suite:   org.jboss.test.xml.JbxbPojoServerUnitTestCase
Test:testGenericBeanFactory
Type:error
Exception:   org.jboss.xb.binding.JBossXBException
Message: Failed to parse source:
file:///home/rcampbell/jboss-head/testsuite/output/resources/xml/pojoser
ver/[EMAIL PROTECTED],96
-



Suite:   org.jboss.test.xml.MiscUnitTestCase
Test:testSandboxXml
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:<[choiceCollection1=[[a=choice1_a, b=null],
[a=null, b=choice1_b]], choice2=[[c=choice2_c, d=choice2_d, e=null],
[c=null, d=choice2_d, e=choice2_e]], choice3=[[listOfIntegers=[1, 2, 3],
listOfStrigns=null], [listOfIntegers=null, listOfStrigns=[1, 2, 3>
but was:<[choiceCollection1=[choice1_a, choice1_b],
choice2=[[c=choice2_c, d=choice2_d, e=null], [c=null, d=choice2_d,
e=choice2_e]], choice3=[[listOfIntegers=[1, 2, 3], listOfStrigns=null],
[listOfIntegers=null, listOfStrigns=[1, 2, 3>
-



Suite:   org.jboss.test.xml.SchemaIncludeUnitTestCase
Test:testSimpleInclude
Type:error
Exception:   org.jboss.xb.binding.JBossXBRuntimeException
Message: -1:-1 25:57 sch-props-correct.2: A schema cannot contain
two global components with the same name; this schema contains two
occurrences of 'urn:jboss:bean-deployer:2.0,deployment'.
-



Suite:   org.jboss.test.xml.SchemaIncludeUnitTestCase
Test:testComplexInclude
Type:error
Exception:   org.jboss.xb.binding.JBossXBRuntimeException
Message: -1:-1 25:57 sch-props-correct.2: A schema cannot contain
two global components with the same name; this schema contains two
occurrences of 'urn:jboss:bean-deployer:2.0,deployment'.
-



Suite:   org.jboss.test.xml.SoapEncUnitTestCase
Test:testMarshallingXerces
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Element varDateTime has text '0096-05-31T23:00:00.000Z'.
Expected 
String1   3512359
-2147483648   -9223372036854775808
-32768   3512359.1456
1.4E-45   4.9E-324
false   -128   String2
0096-05-31T23:00:00.000Z
String3
false
1.4E-45
4.9E-324
3512359.
-2147483648
-32768   -128
gAB/
80007f
gAB/  but was

String1   3512359
-2147483648   -9223372036854775808
-32768   3512359.1456
1.4E-45   4.9E-324
false   -128   String2
0096-06-01T05:00:00.000Z
String3
false
1.4E-45
4.9E-324
3512359.
-2147483648
-32768   -128
gAB/
80007f
gAB/ 
-



Suite:   org.jboss.test.xml.SoapEncUnitTestCase
Test:testMarshallingSunday
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Element varDateTime has text '0096-05-31T23:00:00.000Z'.
Expected 
String1   3512359
-2147483648   -9223372036854775808
-32768   3512359.1456
1.4E-45   4.9E-324
false   -128   String2
0096-05-31T23:00:00.000Z
String3
false
1.4E-45
4.9E-324
3512359.
-2147483648
-32768   -128
gAB/
80007f
gAB/  but was

-2147483648   gAB/
gAB/
-128   false
3512359.1456   String1
-128   1.4E-45
1.4E-45
String3
-32768
4.9E-324
3512359   -32768
String2   -9223372036854775808
-2147483648
3512359.
4.9E-324
0096-06-01T05:00:00.000Z
80007f   false

-



Suite:   org.jboss.test.xml.SoapEncUnitTestCase
Test:testUnmarshalling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:<[varString=String1 varInteger=3512359
varInt=-2147483648 varLong=-9223372036854775808 varShort=-32768
varDecimal=3512359.1456 varFloat=1.4E-45 varDouble=4.9E-324
varBoolean=false varByte=-128 va

[JBoss-dev] RE: Upgrade jbossxb to a non-snapshot release

[Ryan Campbell]

Ok, I'll do the 1.0.0.CR3 release later today and document the process I
use in the wiki. 

-Original Message-
From: Scott M Stark 
Sent: Wednesday, March 29, 2006 7:57 PM
To: Dimitris Andreadis; 'jboss-development@lists.sourceforge.net'; QA
Cc: '[EMAIL PROTECTED]'
Subject: RE: Upgrade jbossxb to a non-snapshot release

If Alexey does not reply by tomorrow I would take the current jboss-head
code and make a jbossxb-1.0.0.CR3 release. I don't know how this is
being built since this has not been broken out yet. For the 4.0.4.GA the
common module needs to be broken up into a separate projects with those
jars released to the repository and integrated into the jbossas build.

> -Original Message-
> From: Dimitris Andreadis 
> Sent: Wednesday, March 29, 2006 12:01 PM
> To: jboss-development@lists.sourceforge.net; QA
> Cc: '[EMAIL PROTECTED]'
> Subject: Upgrade jbossxb to a non-snapshot release
> 
>  
> Related to http://jira.jboss.com/jira/browse/JBAS-3011
> 
> Alexey, should we just copy the current "snapshot" into a 
> jbossxb-1.0.0.CR3, or wait another day?
> 
> Thanks


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] aop/jbossretro org.jboss.lang.Enum conflict

[Ryan Campbell]

This is done.  Thomas can make build the jbossws14 release now.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Wednesday, March 29, 2006 4:28 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] aop/jbossretro org.jboss.lang.Enum conflict

The class has been renamed to org.jboss.lang.EnumImpl, and I moved the
JBossRetro_1_0_0_CR1 tag on the updated files so can you rebuild the
current 1.0.0.CR1 jars.

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Ryan Campbell
> Sent: Wednesday, March 29, 2006 2:13 PM
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] aop/jbossretro org.jboss.lang.Enum conflict
> 
> >> A new jbossws14 binary will need to be created
> 
> Hopefully one that fixes 
> http://jira.jboss.com/jira/browse/JBWS-683 so that the 
> remaining 4.0.4 webservice testsuite failures are resolved.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] aop/jbossretro org.jboss.lang.Enum conflict

[Ryan Campbell]

>> A new jbossws14 binary will need to be created

Hopefully one that fixes http://jira.jboss.com/jira/browse/JBWS-683 so
that the remaining 4.0.4 webservice testsuite failures are resolved.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Wednesday, March 29, 2006 3:58 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] aop/jbossretro org.jboss.lang.Enum conflict

Ok. A new jbossws14 binary will need to be created from the updated
jbossretro jars.

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Adrian Brock
> Sent: Wednesday, March 29, 2006 1:43 PM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev] aop/jbossretro org.jboss.lang.Enum conflict
> 
> Ideally we want a way for aop and jbosretro to use the same 
> implementations. The same thing applies to the 
> ScopedClassPool vs AOPClassPool/JBossClassPool and the annotations.
> 
> For now, I'd suggest just renaming the JBossRetro class until 
> somebody has time to look at it.
> 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Completed With Testsuite Errors

[Ryan Campbell]

The all server starts with an error in
HAJNDI:

 2006-03-29 09:05:40,711 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=HAJNDI2006-03-29 09:05:40,711 DEBUG [org.jboss.ha.jndi.HANamingService] Creating jboss:service=HAJNDI2006-03-29 09:05:40,711 DEBUG [org.jboss.ha.jndi.HANamingService] Initializing HAJNDI server on partition: DefaultPartition2006-03-29 09:05:40,734 DEBUG [org.jboss.ha.jndi.HANamingService] initialize HAJNDI2006-03-29 09:05:40,734 DEBUG [org.jboss.ha.jndi.HAJNDI] subscribeToStateTransferEvents2006-03-29 09:05:40,735 DEBUG [org.jboss.ha.jndi.HANamingService] Initialization failed jboss:service=HAJNDIjava.lang.NullPointerException    at org.jboss.ha.jndi.HAJNDI.init(HAJNDI.java:76)    at org.jboss.ha.jndi.DetachedHANamingService.createService(DetachedHANamingService.java:312)    at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)    at java.lang.reflect.Method.invoke(Method.java:324)    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)    at $Proxy0.create(Unknown Source)    at org.jboss.system.ServiceController.create(ServiceController.java:330)    at org.jboss.system.ServiceController.create(ServiceController.java:273)

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 29, 2006
9:31 AM
To: Adrian Brock; Alexey
Loubyansky; Anil Saldhana; Bela Ban;
Bill Burke; Brian Stansberry; Clebert Suconic;
Dimitris Andreadis; Emmanuel Bernard; jboss-development@lists.sourceforge.net;
[EMAIL PROTECTED]; Kabir Khan; QA; Ryan Campbell; Ruel
 Loehr; Scott M Stark;
Thomas Diesler; Tom Elrod
Subject: jboss-4.0-testsuite Build
Completed With Testsuite Errors
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060329084534




 
  
  TESTS
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build
  Successful - Tests completed with errors or failures.
  
 
 
  
  Date
  of build: 03/29/2006 08:45:34
  
 
 
  
  Time
  to build: 102 minutes 46 seconds
  
 
 
  
  Last
  changed: 03/29/2006 04:51:47
  
 
 
  
  Last
  log entry: replace
  isDebugEnabled() with isTraceEnabled()
  
 




 

[JBoss-dev] RE: ejb3-4.0-testsuite Build Failed

[Ryan Campbell]

The ejb3 testsuite servers fail to start. 
I guess they need to be updated to deal with the new location of javassist?

 

Caused by: java.lang.NoClassDefFoundError: javassist/NotFoundException    at org.jboss.aop.deployment.AspectManagerService.setSuppressTransformationErrors(AspectManagerService.java:374)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)    at java.lang.reflect.Method.invoke(Method.java:585)    at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:136)

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 29, 2006
12:24 AM
To: Adrian Brock; Bill Decoste;
Bill Burke; Dimitris Andreadis; Emmanuel Bernard; Gavin King;
jboss-development@lists.sourceforge.net; Kabir Khan; QA; Ruel
 Loehr; Scott M Stark;
Thomas Diesler
Subject: ejb3-4.0-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060329010736




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83:
  Exit code: 1 See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 03/29/2006 01:07:36
  
 
 
  
  Time
  to build: 15 minutes 15 seconds
  
 
 
  
  Last
  changed: 12/31/2005 16:46:08
  
 
 
  
  Last
  log entry: call isOpen() when
  obtaining session so that HEM registers with EM with TXset
  cglib_use_reflection flag to false
  
 




 

RE: [JBoss-dev] Do a clean build before committing changes to build-thirdparty.xml

[Ryan Campbell]

I'm going to test jbossws-1.0.0.CR6 with remoting-1.4.1_final in
jboss-head with jdk5.  If it passes, I'd like to update the
component-info for jbossws-1.0.0.CR6 to reflect this compatibility.

If this can get resolved today vs. tomorrow, perhaps we have some hope
of releasing this week?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom
Elrod
Sent: Tuesday, March 28, 2006 1:23 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] Do a clean build before committing changes to
build-thirdparty.xml

Ok.  I have rolled back to 1.4.0.  The web services team can put back to

1.4.1 when they are ready.

Scott M Stark wrote:
> Start doing a clean build before committing any changes to
> build-thirdparty.xml to avoid this consistent problem:
> 
> [synchronizeinfo] Checking currentComponentRef:
> ComponentRef{id=jboss/remoting,n
>
ame=jboss/remoting,filename=component-info.xml,location=null,version=1.4
> .0_final
> ,[EMAIL PROTECTED],
> version=1.4.0_final}],component=null,im
> [EMAIL PROTECTED]/jbossws
> atts={licensetype=lgpl} outpu
> t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\jbossws
version=1.0.0.CR6
> isLocal
> =false [EMAIL PROTECTED]
> output=C:\cvs\JBoss4.0\jboss-4.
> 0.x\thirdparty\jboss\jbossws\lib\jbossws.sar type=null},
> [EMAIL PROTECTED]
> sws-client.jar
> output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\jbossws\lib\j
> bossws-client.jar type=null}] module=null
> location=null},fileResolved=true}
> [synchronizeinfo] against newComponent:
> [EMAIL PROTECTED]/remoting atts=
> {projecthome=http://www.jboss.org/products/remoting, licensetype=lgpl}
> output=C:
> \cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\remoting
version=1.4.1_final
> isLocal=
> false [EMAIL PROTECTED]
> output=C:\cvs\JBoss4.0\j
> boss-4.0.x\thirdparty\jboss\remoting\lib\jboss-remoting.jar
type=null}]
> module=n
> ull location=null}
> setVersion, version=1.4.1_final
>  
> BUILD FAILED
> C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:937: The following error
> occurred wh
> ile executing this line:
> C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:125: A
versioning
> problem
>  exists:
> Component: jboss/remoting is at version: 1.4.1_final
>  but it is also required to be compatible with:
> [EMAIL PROTECTED], version=1.4.0_final}]
>  by: jboss/jbossws
> 
> 
> Scott Stark
> VP Architecture & Technology
> JBoss Inc.
>  
>  


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

[Ryan Campbell]

It looks like aop 1.3.4 is not compatible with javassist 3.2.0.CR1, but this is how I interpreted Kabir’s assent to the upgrade on Friday. _jars-cache:    [mkdir] Created dir: /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INF [copy] Copying 9 files to /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INFOverriding previous definition of reference to aop.task.classpath [aopc] java.lang.NoSuchMethodError: javassist.CtClass.stopPruning(Z)V [aopc]    at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.createOptimizedInvocationClass(FieldAccessTransformer.java:857) [aopc]    at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.buildFieldWrappers(FieldAccessTransformer.java:533) [aopc]    at org.jboss.aop.instrument.FieldAccessTransformer.buildFieldWrappers(FieldAccessTransformer.java:73) [aopc]    at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:657) [aopc]    at org.jboss.aop.AspectManager.translate(AspectManager.java:792) [aopc]    at org.jboss.aop.AspectManager.transform(AspectManager.java:704) [aopc]    at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:325) [aopc]    at org.jboss.aop.standalone.Compiler.compile(Compiler.java:217) [aopc]    at org.jboss.aop.standalone.Compiler.main(Compiler.java:73)

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Monday, March 27, 2006 5:43
PM
To: Adrian Brock; Alexey
Loubyansky; Anil Saldhana; Bill
Burke; Brian Stansberry; Emmanuel Bernard;
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; Kabir Khan; QA;
Ryan Campbell; Ruel Loehr; Scott M Stark; Thomas
 Diesler
Subject: jboss-4.0-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060327182315




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit code: 1
  See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 03/27/2006 18:23:15
  
 
 
  
  Time
  to build: 17 minutes 43 seconds
  
 
 
  
  Last
  changed: 03/27/2006 18:15:55
  
 
 
  
  Last
  log entry: JBAS-3014 upgrade
  javassist to 3.2.0.CR1
  
 




 

[JBoss-dev] RE: thirdparty broken and build is throwning an NPE

[Ryan Campbell]

It looks like Branch_4_0 wasn't updated with JBossBuild_1_1_DR2 which
included your fix:

[EMAIL PROTECTED] work]$ md5sum jboss-head/tools/lib/jbossbuild.jar
fba87e22de426cc76eef7563f5c75cce  jboss-head/tools/lib/jbossbuild.jar
[EMAIL PROTECTED] work]$ md5sum jboss-4.0/tools/lib/jbossbuild.jar
69bf8d05a6459321f5bf79e6cd5d8c20  jboss-4.0/tools/lib/jbossbuild.jar

If I take the version from head and move it to 4.0, I see the versioning
problem *without* the NPE.

I'll update the version in 4.0 to reflect the version in head.

-Original Message-
From: Scott M Stark 
Sent: Monday, March 27, 2006 3:41 PM
To: Ryan Campbell; QA; 'jboss-development'
Subject: RE: thirdparty broken and build is throwning an NPE

The problem seems to be that the Version class has not been updated with
the change I gave to Ruel a while back. When I apply this and rebuild
the jbossbuild.jar, the problem is seen to be an invalid 3.1RC2 version
specification coming from jboss/aop:

[synchronizeinfo] against newComponent: [EMAIL PROTECTED]
atts={pro
jecthome=http://sourceforge.net/projects/jboss,
licensetype=mozilla-1.0.1.txt} o
utput=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\javassist version=3.2.0.CR1
isLocal
=false [EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss
-4.0.x\thirdparty\javassist\lib\javassist.jar type=null}] module=null
location=n
ull}
setVersion, version=3.2.0.CR1

BUILD FAILED
C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:937: The following error
occurred wh
ile executing this line:
C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:125: A versioning
problem
 exists:
Component: javassist is at version: 3.2.0.CR1
 but it is also required to be compatible with:
[EMAIL PROTECTED], version=3.1RC2}]
 by: jboss/aop 

> -Original Message-
> From: Ryan Campbell 
> Sent: Monday, March 27, 2006 12:57 PM
> To: Scott M Stark; QA; 'jboss-development'
> Subject: RE: thirdparty broken and build is throwning an NPE
> 
> Well, I'm working on upgrading javassist.  That its throwing 
> an NPE instead of a more informative error is a separate problem.
> 
> -Original Message-
> From: Ryan Campbell
> Sent: Monday, March 27, 2006 2:54 PM
> To: Scott M Stark; QA; 'jboss-development'
> Subject: RE: thirdparty broken and build is throwning an NPE
> 
> Yes, I'm working on this.
> 
> -Original Message-
> From: Scott M Stark
> Sent: Monday, March 27, 2006 2:51 PM
> To: QA; 'jboss-development'
> Subject: thirdparty broken and build is throwning an NPE
> 
> 
> [synchronizeinfo] [10]: javassist
> [synchronizeinfo] Checking currentComponentRef: 
> ComponentRef{id=javassist,name=j
> avassist,filename=component-info.xml,location=null,version=3.1
> RC2,compatibles=[C
> [EMAIL PROTECTED], 
> version=3.1RC2}],component=null,importingComponent=Com
> [EMAIL PROTECTED]/aop 
> atts={projecthome=http://www.jboss.org/products/aop,
>  licensetype=lgpl} 
> output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop versi
> on=1.3.4 isLocal=false 
> [EMAIL PROTECTED] output=C:\cvs
> \JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop.jar 
> type=null}, Artifac
> [EMAIL PROTECTED] 
> output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\j
> boss\aop\lib\jboss-aop-jdk50.jar type=null}, 
> [EMAIL PROTECTED]
> umentor.jar 
> output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\pluggabl
> e-instrumentor.jar type=null}, 
> [EMAIL PROTECTED]
> jar 
> output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jd
> k14-pluggable-
> instrumentor.jar type=null}, 
> [EMAIL PROTECTED] outpu
> t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-a
> op-jdk50-client.ja
> r type=null}, 
> [EMAIL PROTECTED] output=C:\c
> vs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jrockit-plugg
> able-instrumentor.
> jar type=null}] module=null location=null},fileResolved=true}
> [synchronizeinfo] against newComponent: 
> [EMAIL PROTECTED] atts={pro
> jecthome=http://sourceforge.net/projects/jboss, 
> licensetype=mozilla-1.0.1.txt} o
> utput=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\javassist 
> version=3.2.0.CR1 isLocal
> =false [EMAIL PROTECTED] 
> output=C:\cvs\JBoss4.0\jboss
> -4.0.x\thirdparty\javassist\lib\javassist.jar type=null}] 
> module=null location=n
> ull}
> setVersion, version=3.2.0.CR1
> 
> BUILD FAILED
> C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:937: The 
> following error occurred wh
> ile executing this line:
> C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:125: 
> java.lang.NullPointe
> rException
>  
> Total time: 13 seconds
> 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live

[JBoss-dev] RE: thirdparty broken and build is throwning an NPE

[Ryan Campbell]

I'm going to rollback until I can figure out this NPE.

-Original Message-
From: Ryan Campbell 
Sent: Monday, March 27, 2006 2:57 PM
To: Scott M Stark; QA; 'jboss-development'
Subject: RE: thirdparty broken and build is throwning an NPE

Well, I'm working on upgrading javassist.  That its throwing an NPE
instead of a more informative error is a separate problem.

-Original Message-
From: Ryan Campbell 
Sent: Monday, March 27, 2006 2:54 PM
To: Scott M Stark; QA; 'jboss-development'
Subject: RE: thirdparty broken and build is throwning an NPE

Yes, I'm working on this.

-Original Message-
From: Scott M Stark 
Sent: Monday, March 27, 2006 2:51 PM
To: QA; 'jboss-development'
Subject: thirdparty broken and build is throwning an NPE


[synchronizeinfo] [10]: javassist
[synchronizeinfo] Checking currentComponentRef:
ComponentRef{id=javassist,name=j
avassist,filename=component-info.xml,location=null,version=3.1RC2,compat
ibles=[C
[EMAIL PROTECTED],
version=3.1RC2}],component=null,importingComponent=Com
[EMAIL PROTECTED]/aop
atts={projecthome=http://www.jboss.org/products/aop,
 licensetype=lgpl}
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop versi
on=1.3.4 isLocal=false [EMAIL PROTECTED]
output=C:\cvs
\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop.jar type=null},
Artifac
[EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\j
boss\aop\lib\jboss-aop-jdk50.jar type=null},
[EMAIL PROTECTED]
umentor.jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\pluggabl
e-instrumentor.jar type=null},
[EMAIL PROTECTED]
jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jdk14-plugga
ble-
instrumentor.jar type=null},
[EMAIL PROTECTED] outpu
t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop-jdk50-c
lient.ja
r type=null}, [EMAIL PROTECTED]
output=C:\c
vs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jrockit-pluggable-instr
umentor.
jar type=null}] module=null location=null},fileResolved=true}
[synchronizeinfo] against newComponent: [EMAIL PROTECTED]
atts={pro
jecthome=http://sourceforge.net/projects/jboss,
licensetype=mozilla-1.0.1.txt} o
utput=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\javassist version=3.2.0.CR1
isLocal
=false [EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss
-4.0.x\thirdparty\javassist\lib\javassist.jar type=null}] module=null
location=n
ull}
setVersion, version=3.2.0.CR1

BUILD FAILED
C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:937: The following error
occurred wh
ile executing this line:
C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:125:
java.lang.NullPointe
rException
 
Total time: 13 seconds


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: thirdparty broken and build is throwning an NPE

[Ryan Campbell]

Well, I'm working on upgrading javassist.  That its throwing an NPE
instead of a more informative error is a separate problem.

-Original Message-
From: Ryan Campbell 
Sent: Monday, March 27, 2006 2:54 PM
To: Scott M Stark; QA; 'jboss-development'
Subject: RE: thirdparty broken and build is throwning an NPE

Yes, I'm working on this.

-Original Message-
From: Scott M Stark 
Sent: Monday, March 27, 2006 2:51 PM
To: QA; 'jboss-development'
Subject: thirdparty broken and build is throwning an NPE


[synchronizeinfo] [10]: javassist
[synchronizeinfo] Checking currentComponentRef:
ComponentRef{id=javassist,name=j
avassist,filename=component-info.xml,location=null,version=3.1RC2,compat
ibles=[C
[EMAIL PROTECTED],
version=3.1RC2}],component=null,importingComponent=Com
[EMAIL PROTECTED]/aop
atts={projecthome=http://www.jboss.org/products/aop,
 licensetype=lgpl}
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop versi
on=1.3.4 isLocal=false [EMAIL PROTECTED]
output=C:\cvs
\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop.jar type=null},
Artifac
[EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\j
boss\aop\lib\jboss-aop-jdk50.jar type=null},
[EMAIL PROTECTED]
umentor.jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\pluggabl
e-instrumentor.jar type=null},
[EMAIL PROTECTED]
jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jdk14-plugga
ble-
instrumentor.jar type=null},
[EMAIL PROTECTED] outpu
t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop-jdk50-c
lient.ja
r type=null}, [EMAIL PROTECTED]
output=C:\c
vs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jrockit-pluggable-instr
umentor.
jar type=null}] module=null location=null},fileResolved=true}
[synchronizeinfo] against newComponent: [EMAIL PROTECTED]
atts={pro
jecthome=http://sourceforge.net/projects/jboss,
licensetype=mozilla-1.0.1.txt} o
utput=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\javassist version=3.2.0.CR1
isLocal
=false [EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss
-4.0.x\thirdparty\javassist\lib\javassist.jar type=null}] module=null
location=n
ull}
setVersion, version=3.2.0.CR1

BUILD FAILED
C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:937: The following error
occurred wh
ile executing this line:
C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:125:
java.lang.NullPointe
rException
 
Total time: 13 seconds


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: thirdparty broken and build is throwning an NPE

[Ryan Campbell]

Yes, I'm working on this.

-Original Message-
From: Scott M Stark 
Sent: Monday, March 27, 2006 2:51 PM
To: QA; 'jboss-development'
Subject: thirdparty broken and build is throwning an NPE


[synchronizeinfo] [10]: javassist
[synchronizeinfo] Checking currentComponentRef:
ComponentRef{id=javassist,name=j
avassist,filename=component-info.xml,location=null,version=3.1RC2,compat
ibles=[C
[EMAIL PROTECTED],
version=3.1RC2}],component=null,importingComponent=Com
[EMAIL PROTECTED]/aop
atts={projecthome=http://www.jboss.org/products/aop,
 licensetype=lgpl}
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop versi
on=1.3.4 isLocal=false [EMAIL PROTECTED]
output=C:\cvs
\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop.jar type=null},
Artifac
[EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\j
boss\aop\lib\jboss-aop-jdk50.jar type=null},
[EMAIL PROTECTED]
umentor.jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\pluggabl
e-instrumentor.jar type=null},
[EMAIL PROTECTED]
jar
output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jdk14-plugga
ble-
instrumentor.jar type=null},
[EMAIL PROTECTED] outpu
t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jboss-aop-jdk50-c
lient.ja
r type=null}, [EMAIL PROTECTED]
output=C:\c
vs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\aop\lib\jrockit-pluggable-instr
umentor.
jar type=null}] module=null location=null},fileResolved=true}
[synchronizeinfo] against newComponent: [EMAIL PROTECTED]
atts={pro
jecthome=http://sourceforge.net/projects/jboss,
licensetype=mozilla-1.0.1.txt} o
utput=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\javassist version=3.2.0.CR1
isLocal
=false [EMAIL PROTECTED]
output=C:\cvs\JBoss4.0\jboss
-4.0.x\thirdparty\javassist\lib\javassist.jar type=null}] module=null
location=n
ull}
setVersion, version=3.2.0.CR1

BUILD FAILED
C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:937: The following error
occurred wh
ile executing this line:
C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:125:
java.lang.NullPointe
rException
 
Total time: 13 seconds


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

[Ryan Campbell]

This was fixed by the upgrade to
1.0.0.CR5. Triggering test run.

 









From: Ryan Campbell 
Sent: Friday, March 24, 2006 3:33
PM
To: 'Thomas
 Diesler'
Cc: 'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Failed



 

It looks like javax.jws.WebService is
missing from jbossws14.jar.  This was working yesterday, so I think this
update to the repository didn’t include it for some reason?

 

http://fisheye.jboss.com/changelog/JBoss/repository.jboss.com?cs=MAIN:tdiesler:20060324094641


 

stack trace:

 

15:16:54,946 ERROR [MainDeployer] Could
not create deployment:
file:/home/rcampbell/work/jboss-4.0/build/output/jboss-4.0.4.CR2/server/all/deploy/httpha-invoker.sar/invoker.war/

org.jboss.ws.WSException:
java.lang.ClassNotFoundException: No ClassLoaders found for:
javax.jws.WebService

   
at
org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:159)

   
at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)

   
at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:65)

   
at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)

   
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, March 24, 2006 1:38
PM
To: Adrian Brock; Anil Saldhana; Bill Burke; Brian Stansberry;
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; QA; Ryan
Campbell; Ruel Loehr; Scott M Stark; Thomas
 Diesler
Subject: jboss-4.0-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060324140634




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:148:
  Exit code: 1 See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 03/24/2006 14:06:34
  
 
 
  
  Time
  to build: 29 minutes 7 seconds
  
 
 
  
  Last
  changed: 03/24/2006 13:34:24
  
 
 
  
  Last
  log entry: Add wsdl4j.jar,
  xmlsec.jar to jbossall-client.jar
  
 




 

[JBoss-dev] RE: Adding javassist to server/default/lib

[Ryan Campbell]

This brings up a question of the javassist
version.  AOP only declares compatibility with 3.1RC2.  Can this be
upgraded to 3.2.0.CR1?

 









From: Ryan Campbell 
Sent: Friday, March 24, 2006 1:51
PM
To: Scott
 M Stark; Bill Burke; 'Thomas
 Diesler'
Cc: '[EMAIL PROTECTED]';
'jboss-development@lists.sourceforge.net'
Subject: Adding javassist to
server/default/lib 



 

Since javaassist is needed by multiple
components (aop, webservice, hibernate), it needs to be in
server/default/lib.  I’ll be adding it there, and removing it from
jbossws14.sar where Thomas put it earlier today.

 

So I think this means we need to remove it
from aop.deployer as well.

 









From: Scott M Stark 
Sent: Thursday, March 23, 2006
7:31 PM
To: Scott
 M Stark; Ryan Campbell; '[EMAIL PROTECTED]';
'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Completed With Testsuite Errors



 

This is failing under 1.4.2 because
javassist is not getting pulled into the jacc config:

 

2006-03-23 15:59:02,535 ERROR
[org.jboss.deployment.MainDeployer] Could not create deployment:
file:/services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/lib/cmp2-audit.jar
java.lang.NoClassDefFoundError: javassist/NotFoundException
   at
org.jboss.ws.server.WebServiceDeployerEJB21.isWebserviceDeployment(WebServiceDeployerEJB21.java:76)
   at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)

 

javassist should be integrated via the
server lib dir rather than the aop deployer due to the jbossretro, hibernate,
etc dependencies not related to aop. I'm not seeing the jbossretro-rt.jar
anywhere in the current 4.0 build, and my workspace is up to date. Has this
been integrated into the dist structure yet?



 

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

[Ryan Campbell]

It looks like javax.jws.WebService is
missing from jbossws14.jar.  This was working yesterday, so I think this update
to the repository didn’t include it for some reason?

 

http://fisheye.jboss.com/changelog/JBoss/repository.jboss.com?cs=MAIN:tdiesler:20060324094641


 

stack trace:

 

15:16:54,946 ERROR [MainDeployer] Could
not create deployment:
file:/home/rcampbell/work/jboss-4.0/build/output/jboss-4.0.4.CR2/server/all/deploy/httpha-invoker.sar/invoker.war/

org.jboss.ws.WSException:
java.lang.ClassNotFoundException: No ClassLoaders found for:
javax.jws.WebService

   
at
org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:159)

   
at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)

   
at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:65)

   
at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)

   
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, March 24, 2006 1:38
PM
To: Adrian Brock; Anil Saldhana; Bill Burke; Brian Stansberry;
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; QA; Ryan
Campbell; Ruel Loehr; Scott M Stark; Thomas Diesler
Subject: jboss-4.0-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060324140634




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit code: 1
  See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 03/24/2006 14:06:34
  
 
 
  
  Time
  to build: 29 minutes 7 seconds
  
 
 
  
  Last
  changed: 03/24/2006 13:34:24
  
 
 
  
  Last
  log entry: Add wsdl4j.jar,
  xmlsec.jar to jbossall-client.jar
  
 




 

[JBoss-dev] Adding javassist to server/default/lib

[Ryan Campbell]

Since javaassist is needed by multiple
components (aop, webservice, hibernate), it needs to be in server/default/lib. 
I’ll be adding it there, and removing it from jbossws14.sar where Thomas
put it earlier today.

 

So I think this means we need to remove it
from aop.deployer as well.

 









From: Scott M Stark 
Sent: Thursday, March 23, 2006
7:31 PM
To: Scott
 M Stark; Ryan Campbell; '[EMAIL PROTECTED]';
'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Completed With Testsuite Errors



 

This is failing under 1.4.2 because
javassist is not getting pulled into the jacc config:

 

2006-03-23 15:59:02,535 ERROR
[org.jboss.deployment.MainDeployer] Could not create deployment: file:/services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/lib/cmp2-audit.jar
java.lang.NoClassDefFoundError: javassist/NotFoundException
   at
org.jboss.ws.server.WebServiceDeployerEJB21.isWebserviceDeployment(WebServiceDeployerEJB21.java:76)
   at
org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)

 

javassist should be integrated via the
server lib dir rather than the aop deployer due to the jbossretro, hibernate,
etc dependencies not related to aop. I'm not seeing the jbossretro-rt.jar
anywhere in the current 4.0 build, and my workspace is up to date. Has this
been integrated into the dist structure yet?



 

[JBoss-dev] RE: jboss-4.0-testsuite Build Completed With Testsuite Errors

[Ryan Campbell]

I just triggered a testsuite run.

 









From: Scott M Stark 
Sent: Friday, March 24, 2006 11:00
AM
To: Ryan Campbell; '[EMAIL PROTECTED]'; 'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Completed With Testsuite Errors



 

Its only integrated when building with
j2se1.4.x which is why I was not seeing it. Can you trigger another testsuite
run as I have not seen one since I have updated the jacc configs.



 







From: Ryan
Campbell 
Sent: Thursday, March 23, 2006
5:44 PM
To: Scott
 M Stark; '[EMAIL PROTECTED]';
'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Completed With Testsuite Errors

>>I'm not seeing the
jbossretro-rt.jar anywhere in the current 4.0 build, and my workspace is up to
date. Has this been integrated into the dist structure yet?

 

 

http://fisheye.jboss.com/changelog/JBoss/build/jboss?cs=Branch_4_0:rcampbell:20060323050136




 

I see it in the cruisecontrol checkout:

 

/services/cruisecontrol/work/checkout/jboss-4.0-testsuite/build/output/jboss-4.0.4.CR2/server/all/lib

[EMAIL PROTECTED] lib]$ ls jbossretro-rt.jar

jbossretro-rt.jar

 

[JBoss-dev] RE: jboss-4.0-testsuite Build Completed With Testsuite Errors

[Ryan Campbell]

>>I'm not seeing the
jbossretro-rt.jar anywhere in the current 4.0 build, and my workspace is up to
date. Has this been integrated into the dist structure yet?

 

 

http://fisheye.jboss.com/changelog/JBoss/build/jboss?cs=Branch_4_0:rcampbell:20060323050136




 

I see it in the cruisecontrol checkout:

 

/services/cruisecontrol/work/checkout/jboss-4.0-testsuite/build/output/jboss-4.0.4.CR2/server/all/lib

[EMAIL PROTECTED] lib]$ ls jbossretro-rt.jar

jbossretro-rt.jar

 







From: Scott M Stark 
Sent: Thursday, March 23, 2006
7:31 PM
To: Scott M Stark; Ryan Campbell;
'[EMAIL PROTECTED]'; 'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Completed With Testsuite Errors



 

This is failing under 1.4.2 because
javassist is not getting pulled into the jacc config:

 

2006-03-23 15:59:02,535 ERROR
[org.jboss.deployment.MainDeployer] Could not create deployment: file:/services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/lib/cmp2-audit.jar
java.lang.NoClassDefFoundError: javassist/NotFoundException
   at
org.jboss.ws.server.WebServiceDeployerEJB21.isWebserviceDeployment(WebServiceDeployerEJB21.java:76)
   at
org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)

 

javassist should be integrated via the
server lib dir rather than the aop deployer due to the jbossretro, hibernate,
etc dependencies not related to aop. I'm not seeing the jbossretro-rt.jar
anywhere in the current 4.0 build, and my workspace is up to date. Has this
been integrated into the dist structure yet?



 







From: Scott M
Stark 
Sent: Thursday, March 23, 2006
4:50 PM
To: Ryan Campbell; '[EMAIL PROTECTED]';
'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Completed With Testsuite Errors

That is an irrelevant debug level log
message indicating that the does not have a setter for injecting the xmbean
object name. It has no affect on the jacc service. I'm looking at the failures.



 







From: Ryan
Campbell 
Sent: Thursday, March 23, 2006
3:03 PM
To: [EMAIL PROTECTED]; 'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Completed With Testsuite Errors

All these JACC tests are failing, and the
jacc-security-mgr logs show this:

 

java.lang.NoSuchMethodException: org.jboss.security.jacc.SecurityService.setObjectName(javax.management.ObjectName)    at java.lang.Class.getMethod(Class.java:986)    at org.jboss.mx.server.AbstractMBeanInvoker.inject(AbstractMBeanInvoker.java:944)    at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:658)    at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:697)    at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:211)    at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)    at java.lang.reflect.Method.invoke(Method.java:324)    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)    at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1422)    at java.security.AccessController.doPrivileged(Native Method)    at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1417)    at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1350)    at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:345)    at org.jboss.system.ServiceCreator.install(ServiceCreator.java:181)

 

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 23, 2006
3:12 PM
To: Adrian Brock; Anil Saldhana; Bill Burke; Brian Stansberry; jboss-development@lists.sourceforge.net;
[EMAIL PROTECTED]; QA; Ryan Campbell; Ruel Loehr;
Scott M Stark; Thomas Diesler
Subject: jboss-4.0-testsuite Build
Completed With Testsuite Errors
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060323142936




 
  
  TESTS
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235:
  The following error occurred while executing this line:
  /services/cruisecontrol/work

[JBoss-dev] RE: 4.0.4.CR2 remaining tasks recap

[Ryan Campbell]

I've updated crusiecontrol to run the 4.0 testsuite every 4 hours.

-Original Message-
From: Dimitris Andreadis 
Sent: Saturday, March 18, 2006 12:15 PM
To: 'jboss-development@lists.sourceforge.net'; QA
Cc: Scott M Stark; Ivelin Ivanov; Thomas Diesler; Ryan Campbell
Subject: 4.0.4.CR2 remaining tasks recap


http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hi
de&sorter/order=DESC&sorter/field=priority&resolutionIds=-1&pid=10030&fi
xfor=12310573

The major things left are (a) use jbossretro for jbossws (b) the
installer (c) resolve existing testcases and any other failing tests
that may pop up, especially in jbossws.

The (d) misc items could also be deferred for GA.

It would also help if we can run the 4.0 testsuite more often until we
get the release out.

(a) JBossRetro-ize JBossWS (Ryan, Ruel)
JBAS-2791
JBAS-2510 depends on
JBBUILD-188 depends on
JBBUILD-194
JBBUILD-299
JBBUILD-300
JBBUILD-301
JBBUILD-302

(b) Installer (Scott)
JBAS-2646
JBAS-2701
JBAS-2334

(c) Testcase resolution (Anil, Ruel)
JBAS-2947
JBAS-2744

(d) Misc
JBAS-2944 (Ben)
JBAS-2865 (Scott)
JBAS-2311 (Scott)



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4

[Ryan Campbell]

I didn't realize they were versioned together, but this makes sense. 

So the question is, is webservices ready for a 1.0.0.CR4?  

I have tested webservices snapshot code with jboss-4.0/testsuite (weaved
with jbossretro and retrotranslator) and got the following error:

Suite:   org.jboss.test.webservice.samples.ServerSideJMSTestCase
Test:testSOAPMessageToEndpointQueue
Type:error
Exception:   javax.naming.NameNotFoundException
Message: MessageDrivenEndpointQueue not bound

-Original Message-
From: Jason T. Greene 
Sent: Saturday, March 18, 2006 12:07 AM
To: jboss-development@lists.sourceforge.net; Thomas Diesler
Cc: QA; Adrian Brock
Subject: RE: [JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4

Codewise, they are identical. The intention is to maintain one codebase
across both versions of the JDK. So there is no need for another tag.

-Jason

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:jboss-
> [EMAIL PROTECTED] On Behalf Of Ryan Campbell
> Sent: Friday, March 17, 2006 11:19 AM
> To: Thomas Diesler
> Cc: QA; Adrian Brock; jboss-development
> Subject: [JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4
> 
> Thomas,
> 
> I noticed that you have tags for JBOSSWS_1_0_* but not specifically
for
> JBossWS14.  So do the versions for jbossws14 in the repository
> correspond to the JBOSSWS_1_0_* tags?
> 
> http://repository.jboss.com/jboss/jbossws14/
> 
> I was planning on creating a JBossWS14_1_0_0_CR3, but I see you have a
> JBOSSWS_1_0_RC3.
> 
> What is the relationship between jbossws releases to jbossws14
releases?
> 



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4

[Ryan Campbell]

Ok, so I will perform the Javassist 3.2.0.CR1 release and will include
the change comments from Adrian's commits in the Readme.html unless he
sends me something different.

http://wiki.jboss.org/wiki/Wiki.jsp?page=JavassistReleaseGuide 

-Original Message-
From: Shigeru Chiba [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 17, 2006 7:47 PM
To: Adrian Brock
Cc: Ryan Campbell; QA; jboss-development
Subject: Re: JBossRetro, JBossWS and JDK1.4

Hi,

Since these days are really hectic and I have to fly to Germany  
tomorrow etc, I haven't checked Adrian's code carefully yet.  Sorry.   
But as far as I took a quick look, the code seems OK.  Unless I find  
a serious problem in Adrian's code, releasing the current snapshot of  
Javassist is fine with me.

Regards,

Chiba

On 03/18/2006, at 1:58, Adrian Brock wrote:

> We need to speak to Chiba.
> I don't know whether he has even seen my latest fixes yet? ;-)
>
> On Fri, 2006-03-17 at 10:39 -0600, Ryan Campbell wrote:
>> For the Javassist release, how can this be handled?
>>
>> I think we need a Javassist_3_2_1_CR1.  QA will handle the release
>> unless told otherwise.  I assume it will need to be published to SF.
>>
>> http://jira.jboss.com/jira/browse/JBQA-324
>>
>>



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: repository.jboss.com checkout problem

[Ryan Campbell]

I guess its because they are so big?

http://repository.jboss.com/eclipse/sdk/3.1.1/
[   ] eclipse-SDK-3.1.1-li..> 06-Dec-2005 14:02   99M  
[   ] eclipse-SDK-3.1.1-li..> 06-Dec-2005 14:01   99M  
[   ] eclipse-SDK-3.1.1-wi..> 05-Oct-2005 15:47  103M  

-Original Message-
From: Adrian Brock 
Sent: Friday, March 17, 2006 11:46 AM
To: jboss-development
Cc: QA
Subject: repository.jboss.com checkout problem

Anybody else having problems checking out from cvs?

It is getting stuck here:
cvs update: Updating eclipse/sdk/3.1.1
U eclipse/sdk/3.1.1/eclipse-SDK-3.1.1-linux-gtk.tar.gz

I tried cancelling it and restarting, but it still gets stuck?
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4

[Ryan Campbell]

Thomas,

I noticed that you have tags for JBOSSWS_1_0_* but not specifically for
JBossWS14.  So do the versions for jbossws14 in the repository
correspond to the JBOSSWS_1_0_* tags?

http://repository.jboss.com/jboss/jbossws14/

I was planning on creating a JBossWS14_1_0_0_CR3, but I see you have a
JBOSSWS_1_0_RC3.

What is the relationship between jbossws releases to jbossws14 releases?

-Original Message-
From: Adrian Brock 
Sent: Friday, March 17, 2006 7:00 AM
To: jboss-development
Cc: QA
Subject: JBossRetro, JBossWS and JDK1.4

Let's move this discussion here so we make sure everybody 
is "on the same page".

I want to get this done before 4.0.4CR2
so the community has a chance to test it,
rather than dumping it on them in a final release.

http://jira.jboss.com/jira/browse/JBBUILD-188

We need to come up with a roadmap to define who is doing what.

The tasks that need are:

1) Tag concurrent in our cvs repository
The only change since I imported it (tag=BUC_2_1)
is to add an ant script to build and run tests.
I'd suggest something like JBoss_BUC_2_1

2) Get a Javassist release with the 
lastest annotation fixes.
This is only necessary when purge=true
but purge=true is very desirable for memory reasons.

3) Update buildmagic to provide the retro and retrocheck
tasks to all projects (if they desire it)

4) Use it in JBossWS in jboss-head

5) Backport to JBoss4 the 
* JBossRetro runtime classes
* JBossWS binaries 
* javassist
* backport-concurrent-util

6) Test it in JBoss4 with JDK1.4
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4

[Ryan Campbell]

For the Javassist release, how can this be handled?

I think we need a Javassist_3_2_1_CR1.  QA will handle the release
unless told otherwise.  I assume it will need to be published to SF.  

http://jira.jboss.com/jira/browse/JBQA-324


-Original Message-
From: Adrian Brock 
Sent: Friday, March 17, 2006 7:00 AM
To: jboss-development
Cc: QA
Subject: JBossRetro, JBossWS and JDK1.4

Let's move this discussion here so we make sure everybody 
is "on the same page".

I want to get this done before 4.0.4CR2
so the community has a chance to test it,
rather than dumping it on them in a final release.

http://jira.jboss.com/jira/browse/JBBUILD-188

We need to come up with a roadmap to define who is doing what.

The tasks that need are:

1) Tag concurrent in our cvs repository
The only change since I imported it (tag=BUC_2_1)
is to add an ant script to build and run tests.
I'd suggest something like JBoss_BUC_2_1

2) Get a Javassist release with the 
lastest annotation fixes.
This is only necessary when purge=true
but purge=true is very desirable for memory reasons.

3) Update buildmagic to provide the retro and retrocheck
tasks to all projects (if they desire it)

4) Use it in JBossWS in jboss-head

5) Backport to JBoss4 the 
* JBossRetro runtime classes
* JBossWS binaries 
* javassist
* backport-concurrent-util

6) Test it in JBoss4 with JDK1.4
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4

[Ryan Campbell]

As a part of 5:

backport-concurrent and jbossretro-rt are both needed in

1. The client dir
2. server/all/lib

Correct?

-Original Message-
From: Adrian Brock 
Sent: Friday, March 17, 2006 7:03 AM
To: jboss-development
Cc: QA
Subject: Re: JBossRetro, JBossWS and JDK1.4

I missed one

1a) Tag and release JBossRetro

On Fri, 2006-03-17 at 12:59 +, Adrian Brock wrote:
> Let's move this discussion here so we make sure everybody 
> is "on the same page".
> 
> I want to get this done before 4.0.4CR2
> so the community has a chance to test it,
> rather than dumping it on them in a final release.
> 
> http://jira.jboss.com/jira/browse/JBBUILD-188
> 
> We need to come up with a roadmap to define who is doing what.
> 
> The tasks that need are:
> 
> 1) Tag concurrent in our cvs repository
> The only change since I imported it (tag=BUC_2_1)
> is to add an ant script to build and run tests.
> I'd suggest something like JBoss_BUC_2_1
> 
> 2) Get a Javassist release with the 
> lastest annotation fixes.
> This is only necessary when purge=true
> but purge=true is very desirable for memory reasons.
> 
> 3) Update buildmagic to provide the retro and retrocheck
> tasks to all projects (if they desire it)
> 
> 4) Use it in JBossWS in jboss-head
> 
> 5) Backport to JBoss4 the 
> * JBossRetro runtime classes
> * JBossWS binaries 
> * javassist
> * backport-concurrent-util
> 
> 6) Test it in JBoss4 with JDK1.4
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4

[Ryan Campbell]

Ok, I am adding the subtasks to JBBUILD-188

-Original Message-
From: Scott M Stark 
Sent: Friday, March 17, 2006 9:55 AM
To: Adrian Brock; jboss-development
Cc: QA
Subject: RE: JBossRetro, JBossWS and JDK1.4

I agree. The point of the CR2 is to get a release with jbossws with a
jbossretro 1.4.x binary compatible drop for testing by users. The
release will wait for this to happen. The JBBUILD-188 does not have all
of the subtasks so they need to be added for assignment in order to get
a jbossws snapshot.

> -Original Message-
> From: Adrian Brock 
> Sent: Friday, March 17, 2006 5:00 AM
> To: jboss-development
> Cc: QA
> Subject: JBossRetro, JBossWS and JDK1.4
> 
> Let's move this discussion here so we make sure everybody is 
> "on the same page".
> 
> I want to get this done before 4.0.4CR2
> so the community has a chance to test it, rather than dumping 
> it on them in a final release.
> 
> http://jira.jboss.com/jira/browse/JBBUILD-188
> 
> We need to come up with a roadmap to define who is doing what.
> 
> The tasks that need are:
> 
> 1) Tag concurrent in our cvs repository
> The only change since I imported it (tag=BUC_2_1) is to add 
> an ant script to build and run tests.
> I'd suggest something like JBoss_BUC_2_1
> 
> 2) Get a Javassist release with the
> lastest annotation fixes.
> This is only necessary when purge=true
> but purge=true is very desirable for memory reasons.
> 
> 3) Update buildmagic to provide the retro and retrocheck 
> tasks to all projects (if they desire it)
> 
> 4) Use it in JBossWS in jboss-head
> 
> 5) Backport to JBoss4 the
> * JBossRetro runtime classes
> * JBossWS binaries
> * javassist
> * backport-concurrent-util
> 
> 6) Test it in JBoss4 with JDK1.4
> --
> 
> Adrian Brock
> Chief Scientist
> JBoss Inc.
> 
> 
> 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-head-testsuite-1.5 Build Failed

[Ryan Campbell]

This is fixed.

 









From: Scott M Stark 
Sent: Friday, March 17, 2006 9:27
AM
To: '[EMAIL PROTECTED]'; jboss-development@lists.sourceforge.net
Subject: RE:
jboss-head-testsuite-1.5 Build Failed



 

This is not accessible due to an
java.lang.OutOfMemoryError



 







From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 17, 2006 3:36
AM
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]; Andy Oliver; Adrian Brock;
[EMAIL PROTECTED]; [EMAIL PROTECTED]; Alexey Loubyansky; Anil Saldhana; Bill Decoste; Bela Ban; Bill Burke;
Brian Stansberry; Ben Wang; Charles
Crouch; [EMAIL PROTECTED]; Clebert Suconic;
Darran Lofthouse; Dimitris
Andreadis; [EMAIL PROTECTED]; Gavin King; [EMAIL PROTECTED]; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net;
[EMAIL PROTECTED]; Jason T. Greene; Kabir Khan; Luc
 Texier; [EMAIL PROTECTED]; Ovidiu Feodorov;
[EMAIL PROTECTED]; QA; Rajesh Rajasekaran;
Ryan Campbell; [EMAIL PROTECTED]; Ruel Loehr;
[EMAIL PROTECTED]; Scott M Stark; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Thomas
Heute; Thomas Diesler; Tim Fox; Tom
Elrod
Subject: jboss-head-testsuite-1.5
Build Failed
Importance: High

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-1.5?log=log20060317051437





 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit code: 1
  See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 03/17/2006 05:14:37
  
 
 
  
  Time
  to build: 73 minutes 5 seconds
  
 
 
  
  Last
  changed: 12/31/2005 16:46:08
  
 
 
  
  Last
  log entry: call isOpen() when
  obtaining session so that HEM registers with EM with TXset
  cglib_use_reflection flag to false
  
 




 




 
  
   
  
 




 




 
  
   Unit Tests: (0)
   Total Errors and Failures: (0) 
  
 
 
  
  
  
   

 

   
  
  
  
  
  
   
  
  
   
  
  
   
  
 
 
  
   
  
  
   
  
  
   
  
  
   
  
 
 
  
   
  
  
   
  
  
   
  
 




  




 
  
   
  
 




 

[JBoss-dev] FW: [jboss-cvs] build/jboss ...

[Ryan Campbell]

We need a JIRA task in the JBAS project for any 3rd party library
upgrades so that they show up in the changelog, right?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Francisco Reverbel
Sent: Thursday, March 16, 2006 12:02 AM
To: [EMAIL PROTECTED]
Subject: [jboss-cvs] build/jboss ...

  User: reverbel
  Date: 06/03/16 01:01:30

  Modified:jbossTag: Branch_4_0 build-thirdparty.xml
  Log:
  JacORB upgrade to release 2.2.3.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.83  +1 -1  build/jboss/build-thirdparty.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: build-thirdparty.xml
  ===
  RCS file: /cvsroot/jboss/build/jboss/build-thirdparty.xml,v
  retrieving revision 1.1.2.82
  retrieving revision 1.1.2.83
  diff -u -b -r1.1.2.82 -r1.1.2.83
  --- build-thirdparty.xml  6 Mar 2006 06:23:25 -   1.1.2.82
  +++ build-thirdparty.xml  16 Mar 2006 06:01:30 -  1.1.2.83
  @@ -87,7 +87,7 @@
 
 
 
  -  
  +  
 
 
 
  
  
  


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
jboss-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-cvs-commits


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Synching up on webservice/retro tasks for

[Ryan Campbell]

I see that Thomas actually fixed these a few hours ago.  I've forced a
cruisecontrol run to see where we actually are.

-Original Message-
From: Ryan Campbell 
Sent: Wednesday, March 15, 2006 5:27 PM
To: Jason T. Greene; 'Thomas Diesler'
Cc: 'jboss-development@lists.sourceforge.net'
Subject: RE: Synching up on webservice/retro tasks for 


The webservices tests in the head testsuite are failing.  Testing a
retrotranslated jbossws14.sar in jboss-4.0/testsuite produces the same
errors.  Can someone from the WS team look at this?



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Synching up on webservice/retro tasks for

[Ryan Campbell]

The webservices tests in the head testsuite are failing.  Testing a
retrotranslated jbossws14.sar in jboss-4.0/testsuite produces the same
errors.  Can someone from the WS team look at this?


Testsuite: org.jboss.test.webservice.attachment.AttachmentDIITestCase
Tests run: 6, Failures: 0, Errors: 6, Time elapsed: 2.594 sec

Testcase: testSendMimeImageGIF took 0.767 sec
Caused an ERROR
Call invocation failed: Property key not present:
javax.xml.ws.addressing.context.outbound; nested exception is:
java.lang.IllegalArgumentException: Property key not present:
javax.xml.ws.addressing.context.outbound
java.rmi.RemoteException: Call invocation failed: Property key not
present: javax.xml.ws.addressing.context.outbound; nested exception is:
java.lang.IllegalArgumentException: Property key not present:
javax.xml.ws.addressing.context.outbound
at
org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:738)
at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:409)
at
org.jboss.test.webservice.attachment.AttachmentDIITestCase.sendAndValida
teMimeMessage(AttachmentDIITestCase.java:255)
at
org.jboss.test.webservice.attachment.AttachmentDIITestCase.testSendMimeI
mageGIF(AttachmentDIITestCase.java:134)
at
junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: java.lang.IllegalArgumentException: Property key not present:
javax.xml.ws.addressing.context.outbound
at
org.jboss.ws.handler.MessageContextImpl.assertPropertyKey(MessageContext
Impl.java:113)
at
org.jboss.ws.handler.MessageContextImpl.getProperty(MessageContextImpl.j
ava:67)
at
org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:671)
... 24 more


From: Ryan Campbell 
Sent: Tuesday, March 14, 2006 3:39 PM
To: Scott M Stark; '[EMAIL PROTECTED]';
'jboss-development@lists.sourceforge.net'
Subject: RE: Synching up on webservice/retro tasks for 

Ok, I ran the webservices tests against a jbossretro-weaved
jbossws14.sar and all the tests passed.

Todo:

- create a 1.0.RC1 for backport-concurrent, jbossretro so they can be
added to the repository
- officially integrate jbossretro into the jboss-head/webservices build 
- Create an 1.0.RC3 for jbossws14 from the jbossretro build
- Integrate it with 4.0

This should be done by tomorrow, unless there are any objections.



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Synching up on webservice/retro tasks for

[Ryan Campbell]

It looks like I jumped the gun and posted before checking my work.
There are some problems with the jbossretro weaved version that I'll
work out on the forums.

But the plan below should stand.

From: Ryan Campbell 
Sent: Tuesday, March 14, 2006 3:39 PM
To: Scott M Stark; '[EMAIL PROTECTED]';
'jboss-development@lists.sourceforge.net'
Subject: RE: Synching up on webservice/retro tasks for 

Ok, I ran the webservices tests against a jbossretro-weaved
jbossws14.sar and all the tests passed.

Todo:

- create a 1.0.RC1 for backport-concurrent, jbossretro so they can be
added to the repository
- officially integrate jbossretro into the jboss-head/webservices build 
- Create an 1.0.RC3 for jbossws14 from the jbossretro build
- Integrate it with 4.0

This should be done by tomorrow, unless there are any objections.


From: Scott M Stark 
Sent: Monday, March 13, 2006 9:58 AM
To: '[EMAIL PROTECTED]'; jboss-development@lists.sourceforge.net
Subject: Synching up on webservice/retro tasks for 

The majority of the issues for the 4.0.4CR2 release due out this Friday
are webservice issues related to integrating the jbossws stack into the
server. Starting with this issue and traversing all links should define
what needs to be done:

http://jira.jboss.com/jira/browse/JBAS-2816

A big one is getting a new jbossretro j2se1.4 compatible binary:
http://jira.jboss.com/jira/browse/JBAS-2510

Getting these done along with the webservice testsuite running is what I
would like to focus on this week.



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Synching up on webservice/retro tasks for

[Ryan Campbell]

Ok, I ran the webservices tests against a jbossretro-weaved
jbossws14.sar and all the tests passed.

 

Todo:

 

- 
create a
1.0.RC1 for backport-concurrent, jbossretro so they can be added to the
repository

- 
officially
integrate jbossretro into the jboss-head/webservices build 

- 
Create an
1.0.RC3 for jbossws14 from the jbossretro build

- 
Integrate
it with 4.0

 

This should be done by tomorrow, unless
there are any objections.

 









From: Scott M Stark 
Sent: Monday, March 13, 2006 9:58
AM
To: '[EMAIL PROTECTED]'; jboss-development@lists.sourceforge.net
Subject: Synching up on
webservice/retro tasks for 



 

The majority of the issues for the 4.0.4CR2 release due out
this Friday are webservice issues related to integrating the jbossws stack into
the server. Starting with this issue and traversing all links should define
what needs to be done:

 

http://jira.jboss.com/jira/browse/JBAS-2816

 

A big one is getting a new jbossretro j2se1.4 compatible
binary:

http://jira.jboss.com/jira/browse/JBAS-2510

 

Getting these done along with the webservice testsuite
running is what I would like to focus on this week.

 

RE: [JBoss-dev] JBossCache 1.3.0.Beta2 released

[Ryan Campbell]

This is compiled with jdk1.5.  What are
the plans for making this compatible with jdk 1.4 so that it can be integrated
with jboss-head?

 









From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ruel
 Loehr
Sent: Monday, March 13, 2006 5:59
PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] JBossCache
1.3.0.Beta2 released



 

The 1.3.0.Beta2 release of
JBossCache is now available from sourceforge: 


http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=401350

 

Ruel Loehr

JBoss QA

 

 

[JBoss-dev] RE: Where is server.loader defined?

[Ryan Campbell]

These classes are built in the test
module.  So you will have to build this before calling testsuite/build.xml’s
–projecthelp.

 

I believe the loaderref is just a reference
to a shared classloader.  From ant docs “Use this to
allow multiple tasks/types to be loaded with the same loader, so they can call
each other.”  It is defined
upon first usage.

 









From: Scott M Stark 
Sent: Sunday, March 12, 2006 4:07
PM
To: jboss-development@lists.sourceforge.net;
'[EMAIL PROTECTED]'
Subject: Where is server.loader
defined?



 



In one workspace I just updated, I can't run a simple
-projecthelp due to





 





[EMAIL PROTECTED] testsuite]$ ant -projecthelp
Buildfile: build.xml
Overriding previous definition of reference to xdoclet.task.classpath
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\build.xml:468: The following error
occurred while executing this line:
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\imports\server-config.xml:45: taskdef
class org.jboss.ant.taskdefs.server.ConfigManagerTask cannot be found





 





I can't find where the server.loader loaderref for the
associated taskdef is defined. Another clean checkout works fine, but I still
can't find where the server.loader is defined there either.





 

RE: [JBoss-dev] possible builder error during 3 minute window

[Ryan Campbell]

This is probably an charset/encoding problem?, try "unset LANG" and then
rebuild.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Clebert Suconic
Sent: Thursday, March 09, 2006 1:16 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] possible builder error during 3 minute window

Sorry about this...

I was using IBM JDK by accident:

[EMAIL PROTECTED] csuconic]$ java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build
pxi32devifx-20060124)
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32
j9vmxi3223ifx-20060124 (JIT enabled)
J9VM - 20051027_03723_lHdSMR
JIT  - 20051027_1437_r8
GC   - 20051020_AA)
JCL  - 20060120a
[

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Clebert Suconic
Sent: Thursday, March 09, 2006 12:55 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] possible builder error during 3 minute window

I have a fresh checkou of Branch_4_0, and I have a build failure, but
not on WebServices

BUILD FAILED
/home/csuconic/jboss-4.0.x/server/build.xml:274: Failed to copy
/home/csuconic/jboss-4.0.x/server/src/resources/org/jboss/verifier/EJB21
Messages.properties to
/home/csuconic/jboss-4.0.x/server/output/resources/org/jboss/verifier/EJ
B21Messages.properties due to null


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jason T. Greene
Sent: Thursday, March 09, 2006 12:06 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] possible builder error during 3 minute window

Due to differing library dependencies on my system versus current
thridparty, I accidentally committed code that would break the build. It
was only broken for about a 3 minute window. So if you see a compile
error in webservices just cvs update the module.

-Jason


Jason T. Greene
Developer - Web Services
JBoss Inc.
 



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-cache-testsuite Build Completed With Testsuite Errors

[Ryan Campbell]

Ben,

 

Once these errors are resolved, we are
ready to release 1.3.0 beta.

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 28, 2006
8:14 PM
To: Dev - JBossCache; QA;
jboss-development@lists.sourceforge.net
Subject: jboss-cache-testsuite
Build Completed With Testsuite Errors
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060228203858




 
  
  TESTS
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build
  Successful - Tests completed with errors or failures.
  
 
 
  
  Date
  of build: 02/28/2006 20:38:58
  
 
 
  
  Time
  to build: 34 minutes 37 seconds
  
 
 
  
  Last
  changed: 12/28/2005 10:48:11
  
 
 
  
  Last
  log entry: Add the 1.2.4SP1
  changelog notes.
  
 




 

[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors

[Ryan Campbell]

Rajesh, can we put jboss-head at the end?

If there is only one failure on jboss-head, perhaps we could raise the
issue for the portal team to fix.  Having Portal 2.4 compatible with
Jboss 5.0 would be a nice thing to have if it's easy.

If it's a big deal to fix, we should remove jboss-head from the matrix
so we can have a clean build.

-Original Message-
From: Julien Viet 
Sent: Wednesday, February 22, 2006 3:38 PM
To: Rajesh Rajasekaran
Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun;
jboss-development@lists.sourceforge.net; QA; Julien Viet;
[EMAIL PROTECTED]; Thomas Heute
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

jboss-head (JBoss 5) is not today a target for us but we can test it of 
course.

Here is the list that I would like to see :

- Branch_4_0
- 4.0.4RC1 (later 4.0.4)
- 4.0.3SP1 (already done)


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors

[Ryan Campbell]

> should we make the portlet test case extends it ?
 
Well, as Rajesh pointed out it is the junitreport task which blanks the
XML reports, so I was wrong on my point #2.  Rajesh is trying to narrow
this down and will followup with what he finds.

-Original Message-
From: Julien Viet 
Sent: Monday, February 20, 2006 5:53 PM
To: Ryan Campbell
Cc: Rajesh Rajasekaran; Julien Viet; QA; [EMAIL PROTECTED];
jboss-development@lists.sourceforge.net
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

yes they don't extend TestCase because we only use the

public static Test suite() { }

method as the class itself is not really a test but rather a suite
provider.

should we make the portlet test case extends it ?



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors

[Ryan Campbell]

I see two things here:

1. The xml reports are empty, causing the XML validation errors.  I
guess no one has even looked at these yet?!

2.  The Portlet test cases don't extend org.junit.TestCase, they extend
java.lang.Object.  That might work in your IDE, but I doubt we should
expect AntRunner to put it up with it.

-Original Message-
From: Rajesh Rajasekaran 
Sent: Monday, February 20, 2006 5:22 PM
To: Julien Viet
Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA
Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

I guess portal uses an old version of junit(from 2001). The newer
version might solve the problem. 
Anyways these are the errors I get.

[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.dispatcher.spec.DispatcherTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletconfig.PortletConfigTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletinterface.PortletInterfaceTestCase.xml is not a
valid XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletmode.PortletModeTestCase.xml is not a valid XML
document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletrequest.PortletRequestTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletsession.PortletSessionTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.preferences.PreferencesTestCase.xml is not a valid XML
document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.renderresponse.RenderResponseTestCase.xml is not a valid
XML document. It is possibly corrupted.



-Original Message-
From: Julien Viet 
Sent: Monday, February 20, 2006 4:41 PM
To: Rajesh Rajasekaran
Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien
Viet
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

how can we do to improve that (i.e fix the wellformedness) ?

Rajesh Rajasekaran wrote:
> The junit reports (xml) for the portlet tests are not well formed.
> 
> Hence the portlet test results are not accounted in the HTML reports
shown.
> 
> The common and format tests pass 100%.
> 
> Please refer the link below for the portlet test reports.
> 
>
http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-2.4-testsuite/2
0060220170427/jboss-4.0.3SP1-logs/results/testfailures
> 
>  
> 
> Please let me know if you have the same problem.
> 
>  
> 
> Thanks
> 
> Rajesh
> 
>  
> 
>  
> 
>

> 
> *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> *Sent:* Monday, February 20, 2006 4:07 PM
> *To:* [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien 
> Viet; QA
> *Subject:* jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors
> *Importance:* High
> 
>  
> 
> View results here -> 
>
http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuit
e?log=log20060220170427
> 
> *TESTS FAILED*
> 
> *Ant Error 
> Message:
*/services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: 
> The following error occurred while executing this line: 
> /services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The 
> following error occurred while executing this line: 
> /services/cruisecontrol/work/scripts/build-jboss-portal.xml:199: The 
> following error occurred while executing this line: 
> /services/cruisecontrol/work/scripts/build-common-targets.xml:11:
Build 
> Successful - Tests completed with errors or failures.
> 
> *Date of build: *02/20/2006 17:04:27
> 
> *Time to build: *1 minute 58 seconds
> 
> *Last changed: *02/20/2006 09:17:02
> 
> *Last log entry: *JBPORTAL-608 : Timed content is not serializable and

> raise issues in http session re

RE: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk

[Ryan Campbell]

Actually, it looks like our post to the
Jacorb list was a pretty bad post.  We will correct this.

 









From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan Campbell
Sent: Monday, February 13, 2006
5:12 PM
To: jboss-development@lists.sourceforge.net
Cc: Francisco Reverbel
Subject: RE: [JBoss-dev] FW: Could
not run jacorb on 64 bit jdk



 

Francisco,

 

Just to make it clear, we are trying to
build JBoss on 64bit JVM’s and we get this fatal exception when trying to
run the jacorb parser:

 

Exception in thread "main" java.lang.VerifyError: (class: org/jacorb/idl/parser,method:  signature: ()V) Call to wrong initialization method 

 

Can you patch this?  We aren’t
getting a response from the jacorb list.

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Rajesh Rajasekaran
Sent: Monday, February 13, 2006
5:04 PM
To: jboss-development@lists.sourceforge.net
Cc: Francisco Reverbel
Subject: [JBoss-dev] FW: Could not
run jacorb on 64 bit jdk



 

 

 









From: Rajesh Rajasekaran 
Sent: Friday, February 10, 2006
12:05 PM
To: '[EMAIL PROTECTED]'
Subject: Could not run jacorb on
64 bit jdk



 

This is related to the bug #468

http://www.jacorb.org/cgi-bin/bugzilla/long_list.cgi?buglist=468

 

We are trying to support Jboss on 64 bit jdk’s and
this bug is a major blocker.

A fix for this ASAP would help us proceed with our process.

 

Thanks

Rajesh 

JBoss QA

RE: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk

[Ryan Campbell]

Francisco,

 

Just to make it clear, we are trying to
build JBoss on 64bit JVM’s and we get this fatal exception when trying to
run the jacorb parser:

 

Exception in thread "main" java.lang.VerifyError: (class: org/jacorb/idl/parser,method:  signature: ()V) Call to wrong initialization method 

 

Can you patch this?  We aren’t
getting a response from the jacorb list.

 









From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rajesh
 Rajasekaran
Sent: Monday, February 13, 2006
5:04 PM
To: jboss-development@lists.sourceforge.net
Cc: Francisco Reverbel
Subject: [JBoss-dev] FW: Could not
run jacorb on 64 bit jdk



 

 

 









From: Rajesh Rajasekaran 
Sent: Friday, February 10, 2006
12:05 PM
To: '[EMAIL PROTECTED]'
Subject: Could not run jacorb on
64 bit jdk



 

This is related to the bug #468

http://www.jacorb.org/cgi-bin/bugzilla/long_list.cgi?buglist=468

 

We are trying to support Jboss on 64 bit jdk’s and
this bug is a major blocker.

A fix for this ASAP would help us proceed with our process.

 

Thanks

Rajesh 

JBoss QA

[JBoss-dev] qRE: jboss-4.0-testsuite Build Failed

[Ryan Campbell]

I just fixed this. It was failing due to
the changes in the compatibility matrix tests, sorry.

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 08, 2006
11:05 PM
To: Andy Oliver; Adrian Brock; Alexey Loubyansky; Anil Saldhana; Bill Decoste; Bela Ban; Bill Burke; Brian Stansberry; Ben Wang;
[EMAIL PROTECTED]; Clebert Suconic;
Dimitris Andreadis; Gavin King; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; jboss-development@lists.sourceforge.net;
[EMAIL PROTECTED]; Jason T. Greene; Jim Moran; Kabir Khan; Luc Texier; Noël Rocher; Norman Richards;
[EMAIL PROTECTED]; QA; Ryan Campbell; Remy Maucherat; Ruel Loehr; Sacha
Labourey; Scott M Stark; [EMAIL PROTECTED]; Stan
 Silvert; Steve Ebersole; Thomas
 Heute; Thomas Diesler; Tom Elrod; [EMAIL PROTECTED]
Subject: jboss-4.0-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060208234527




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit code: 1
  See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 02/08/2006 23:45:27
  
 
 
  
  Time
  to build: 16 minutes 14 seconds
  
 
 
  
  Last
  changed: 12/30/2005 02:15:51
  
 
 
  
  Last
  log entry: [JBAS-2142] Support
  marshalling of state transfer during web app deployment
  
 




 

Accepted: [JBoss-dev] Maven2 discussion

[Ryan Campbell]

BEGIN:VCALENDAR
METHOD:REPLY
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:(GMT-06.00) Central Time (US & Canada)
X-MICROSOFT-CDO-TZID:11
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=4;BYDAY=1SU
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20060207T001658Z
DTSTART;TZID="(GMT-06.00) Central Time (US & Canada)":20060208T09
SUMMARY:Accepted: [JBoss-dev] Maven2 discussion
UID:04008200E00074C5B7101A82E008905F2284492BC601000
 010007AD3E23387F0E54BBDA4311EDA6FC1FC
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE;CN="Ryan Campbell
 ":MAILTO:[EMAIL PROTECTED]
ORGANIZER:MAILTO:jboss-development@lists.sourceforge.net
LOCATION:virtual
DTEND;TZID="(GMT-06.00) Central Time (US & Canada)":20060208T10
SEQUENCE:0
PRIORITY:5
CLASS:
CREATED:20060208T025433Z
LAST-MODIFIED:20060208T025433Z
STATUS:TENTATIVE
TRANSP:OPAQUE
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-CDO-REPLYTIME:20060208T025411Z
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-OWNERAPPTID:889595862
END:VEVENT
END:VCALENDAR

[JBoss-dev] RE: WebService tests timeout

[Ryan Campbell]

I have also seen these fail occasionally with
503, bad gateway errors.

 









From: Dimitris
Andreadis 
Sent: Friday, February 03, 2006
5:11 AM
To: [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net
Cc: Thomas Diesler
Subject: WebService tests timeout



 

I've noticed 2 webservices tests that
timeout (and fail) occasionally at 60 seconds when
contacting external webservices:

 

org.jboss.test.jbossnet.external.ExternalUnitTestCase

org.jboss.test.jbossnet.external.RedeployExternalUnitTestCase

 

Is this timeout configurable? I seem to be
getting a response in just about one minute. Is this "normal" for WS
:)

 

Thanks


Translates text of up to 5k in length, between a variety
of languages.













 







From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 03 February, 2006 01:45
To: Adrian
 Brock; Clebert Suconic;
Dimitris Andreadis; jboss-development@lists.sourceforge.net;
QA; Ryan Campbell
Subject: jboss-3.2-testsuite Build
Completed With Testsuite Errors
Importance: High

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060202175301





 
  
  TESTS
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235:
  The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26:
  Build Successful - Tests completed with errors or failures.
  
 
 
  
  Date
  of build: 02/02/2006 17:53:01
  
 
 
  
  Time
  to build: 50 minutes 27 seconds
  
 
 
  
  Last
  changed: 02/02/2006 14:17:10
  
 
 
  
  Last
  log entry: JBAS-2768, change
  tests that produce varying resutls based on jdk/os platform to logging
  warning messages rather than code assertions
  
 




 




 
  
   
  
 




 




 
  
   Unit Tests:
  (1847)  Total Errors and Failures: (2) 
  
 
 
  
  
  
   

testFederated


org.jboss.test.jbossnet.external.ExternalUnitTestCase

   
   

testFederated


org.jboss.test.jbossnet.external.RedeployExternalUnitTestCase

   
  
  
  
  
  
   
  
  
   
  
  
   
  
 
 
  
   
  
  
   
  
  
   
  
  
   
  
 
 
  
   
  
  
   
  
  
   
  
 




 




 
  
   Modifications
  since last build:  (first 50 of 14) 
  
 
 
  
  1.2.2.20
  
  
  modified
  
  
  dimitris
  
  
  testsuite/src/main/org/jboss/test/cmp2/commerce/QueryTest.java
  
  
  JBAS-2768, change tests
  that produce varying resutls based on jdk/os platform to logging warning
  messages rather than code assertions
  
 
 
  
  1.1.2.1
  
  
  modified
  
  
  csuconic
  
  
  testsuite/src/main/org/jboss/test/guid/GUIDTestCase.java
  
  
  Renaming GUIDTest to
  the correct name, so it can be part of the testsuite
  
 
 
  
  1.11.2.10
  
  
  modified
  
  
  dimitris
  
  
  server/src/main/org/jboss/invocation/MarshalledInvocation.java
  
  
  JBAS-2767,
  Conditionally set useFullHashMode to true, when SerialVersion.version ==
  SerialVersion.JBOSS_402
  
 
 
  
  1.165.2.198
  
  
  modified
  
  
  rcampbell
  
  
  testsuite/build.xml
  
  
  added 4.0.3SP1 to
  compat matrix
  
 
 
  
  1.1.2.16
  
  
  modified
  
  
  rcampbell
  
  
  testsuite/imports/server-config.xml
  
  
  JBAS-2758: pass
  serialization flag to jboss startup *and* shutdown
  
 
 
  
  1.165.2.197
  
  
  modified
  
  
  rcampbell
  
  
  testsuite/build.xml
  
  
  JBAS-2758: pass
  serialization flag to jboss startup *and* shutdown
  
 
 
  
  1.2.2.22
  
  
  modified
  
  
  adrian
  
  
  messaging/src/main/org/jboss/mq/server/JMSDestinationManager.java
  
  
  [JBAS-2762] - Avoid
  infinite loop when there is no state manager.
  
 
 
  
  1.4.2.3
  
  
  modified
  
  
  dimitris
  
  
  jmx/src/main/javax/management/MBeanServerConnection.java
  
  
  synch with 4.x
  
 
 
  
  1.165.2.196
  
  
  modified
  
  
  rcampbell
  
  
  testsuite/build.xml
  
  
  JBAS-2758: add usage of
  org.jboss.j2ee.Serialization flag to compatibility matrix
  
 
 
  
  1.1.4.3
  
  
  modified
  
  
  dimitris
  
  
  testsuite/src/main/org/jboss/test/jbossmx/performance/TestCase.java
  
  
  fix compatibility test
  failures
  
 
 
  
  1.1.4.3
  
  
  modified
  
  
  dimitris
  
  
  testsuite/src/main/org/jboss/test/jbossmx/implementation/TestCase.java
  
  
  fix compatibility test
  failures
  
 
 
  
  1.2.4.4
  
  
  modified
  
  
  dimitris
  
  
  testsuite/src/main/org/jboss/test/jbossmx/compliance/TestCase.java
  
  
  fix compatibility test
  failures
  
 
 
  
  1.1.4.2
  
  
  modified
  
  
  dimitris
  
  
  common/src/main/org/jboss/util/id/GUID.java
  
  
  JBAS-2718, define a
  serialVersionUID for GUID and introduce SerialVersion. The default for 3.2..x
  will be legacy compatibility (3.2.x and maybe 4.0.0/4.0.1) which can be
  overriden by defining org.jboss.j2ee.Serialization for 4.0.2+ compatibility
  (the opposite of the 4.0.x branch)
  
 
 
  
  1.2.4.2
  
  
  modified
  
  
  dimit

[JBoss-dev] RE: jboss-3.2-testsuite Build Failed

[Ryan Campbell]

This is ignorable, all tests passed.

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 01, 2006
10:54 AM
To: Dimitris Andreadis; jboss-development@lists.sourceforge.net; QA
Subject: jboss-3.2-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060201110410




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:142: The
  following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:173:
  The value of attribute "todir" associated with an element type
  "copy" must not contain the '<' character.
  
 
 
  
  Date
  of build: 02/01/2006 11:04:10
  
 
 
  
  Time
  to build: 48 minutes 0 seconds
  
 
 
  
  Last
  changed: 02/01/2006 07:18:46
  
 
 
  
  Last
  log entry: fix compatibility test
  failures
  
 




 




 
  
  
  
   

 Unit Tests:
(1847)  Total Errors and Failures: (0) 

   
   

All Tests Passed 


 


 

   
   



 
  
   
  
 





 


 


 

   
   

 


 


 


 

   
   

 


 


 

   
  
  
   
  
  
   

 Modifications
since last build:  (first 50 of 5) 

   
   

1.1.4.3


modified


dimitris


testsuite/src/main/org/jboss/test/jbossmx/performance/TestCase.java


fix compatibility
test failures

   
   

1.1.4.3


modified


dimitris


testsuite/src/main/org/jboss/test/jbossmx/implementation/TestCase.java


fix compatibility
test failures

   
   

1.2.4.4


modified


dimitris


testsuite/src/main/org/jboss/test/jbossmx/compliance/TestCase.java


fix compatibility
test failures

   
   

1.1.4.2


modified


dimitris


common/src/main/org/jboss/util/id/GUID.java


JBAS-2718, define a
serialVersionUID for GUID and introduce SerialVersion. The default for
3.2..x will be legacy compatibility (3.2.x and maybe 4.0.0/4.0.1) which can
be overriden by defining org.jboss.j2ee.Serialization for 4.0.2+
compatibility (the opposite of the 4.0.x branch)

   
   

1.2.4.2


modified


dimitris


common/src/main/org/jboss/util/id/SerialVersion.java


JBAS-2718, define a
serialVersionUID for GUID and introduce SerialVersion. The default for
3.2..x will be legacy compatibility (3.2.x and maybe 4.0.0/4.0.1) which can
be overriden by defining org.jboss.j2ee.Serialization for 4.0.2+
compatibility (the opposite of the 4.0.x branch)

   
  
  
   
  
  
   

 

   
  
  
  
  
 




 

[JBoss-dev] RE: ejb3-4.0-testsuite Build Failed

[Ryan Campbell]

Yes, this is Branch_4_0.  Thanks, Tom.

-Original Message-
From: Tom Elrod 
Sent: Tuesday, January 31, 2006 1:28 PM
To: Tom Elrod
Cc: Ryan Campbell; Tom Elrod; Kabir Khan; Bill Burke;
jboss-development@lists.sourceforge.net
Subject: Re: ejb3-4.0-testsuite Build Failed

I think I get the mis-match now.  This is being build out of JBoss 4.x 
branch, right?  If so, then the code for jbossas-remoting.jar is not 
there.  There is an issue for this (JBAS-2698), which I will work on
today.

Tom Elrod wrote:
> The class that is not being found is within jbossas-remoting.jar.
This 
> is part of JBossAS code base and not remoting.  Only way this would be

> called to be loaded is if was configured to use the JBossAS security 
> domain via configuration.  So am guessing the jar was excluded from
the 
> build?
> 
> Ryan Campbell wrote:
> 
>>  
>>
>> The ejb3-ssl-advanced test server is broken:
>>
>>  
>>
>> 2006-01-30 20:09:06,202 DEBUG [org.jboss.deployment.SARDeployer] 
>> create operation failed for package 
>>
file:/services/cruisecontrol/checkout/ejb3-4.0-testsuite/build/output/jb
oss-4.0.4RC1/server/ejb3-ssl-advanced/deploy/ejb3.deployer/ 
>>
>>
>> org.jboss.deployment.DeploymentException: No ClassLoaders found for: 
>> org.jboss.remoting.security.domain.DomainServerSocketFactoryService;
- 
>> nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders 
>> found for: 
>> org.jboss.remoting.security.domain.DomainServerSocketFactoryService)
>>
>> at 
>>
org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:19
6) 
>>
>>
>> at 
>>
org.jboss.system.ServiceController.install(ServiceController.java:226)
>>
>>  
>>
>>  
>>
>>  
>>
>>

>>
>> *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> *Sent:* Monday, January 30, 2006 7:12 PM
>> *To:* Adrian Brock; Bill Decoste; Bill Burke; Gavin King; 
>> jboss-development@lists.sourceforge.net; Kabir Khan; QA; Ruel Loehr; 
>> Scott M Stark; Thomas Diesler
>> *Subject:* ejb3-4.0-testsuite Build Failed
>> *Importance:* High
>>
>>  
>>
>> View results here -> 
>>
http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=lo
g20060130193339 
>>
>>
>> *BUILD FAILED*
>>
>> *Ant Error Message: 
>>
*/services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: 
>> Exit code: 1 See tests.log in Build Artifacts for details.
>>
>> *Date of build: *01/30/2006 19:33:39
>>
>> *Time to build: *37 minutes 18 seconds
>>
>> *Last changed: *12/31/2005 16:46:08
>>
>> *Last log entry: *call isOpen() when obtaining session so that HEM 
>> registers with EM with TXset cglib_use_reflection flag to false
>>
>>  
>>
> 
> 
> 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: ejb3-4.0-testsuite Build Failed

[Ryan Campbell]

 

The ejb3-ssl-advanced test server is
broken: 

 

2006-01-30 20:09:06,202 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/services/cruisecontrol/checkout/ejb3-4.0-testsuite/build/output/jboss-4.0.4RC1/server/ejb3-ssl-advanced/deploy/ejb3.deployer/org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.remoting.security.domain.DomainServerSocketFactoryService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.remoting.security.domain.DomainServerSocketFactoryService)    at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)    at org.jboss.system.ServiceController.install(ServiceController.java:226)

 

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Monday, January 30, 2006
7:12 PM
To: Adrian
 Brock; Bill Decoste; Bill Burke; Gavin King; jboss-development@lists.sourceforge.net; Kabir Khan;
QA; Ruel Loehr; Scott M Stark; Thomas Diesler
Subject: ejb3-4.0-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060130193339




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83:
  Exit code: 1 See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 01/30/2006 19:33:39
  
 
 
  
  Time
  to build: 37 minutes 18 seconds
  
 
 
  
  Last
  changed: 12/31/2005 16:46:08
  
 
 
  
  Last
  log entry: call isOpen() when
  obtaining session so that HEM registers with EM with TXset
  cglib_use_reflection flag to false
  
 




 

RE: [JBoss-dev] JIRA Downtime

[Ryan Campbell]

JIRA is up again; the downtime is
complete.

 









From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan Campbell
Sent: Monday, January 30, 2006
11:59 AM
To: jboss-development@lists.sourceforge.net
Cc: The Core
Subject: [JBoss-dev] JIRA Downtime



 

jira.jboss.com will be going down at 1 PM EST to apply a
critical fix.  Downtime should not be more than 15 minutes.

 

Thanks,

Ryan

[JBoss-dev] JIRA Downtime

[Ryan Campbell]

jira.jboss.com will be going down at 1 PM EST to apply a
critical fix.  Downtime should not be more than 15 minutes.

 

Thanks,

Ryan

[JBoss-dev] RE: jboss-4.0-jdk-matrix Build Failed

[Ryan Campbell]

Strange errors on the build machine
(checking these), but I’m getting the following build error on clean
checkout of jboss-4.0.x

 

/home/rcampbell/tmp/jboss-4.0.x/build/build.xml:913:
The following error occurred while executing this line:

/home/rcampbell/tmp/jboss-4.0.x/build/build-thirdparty.xml:124:
A versioning problem exists:

Component: hibernate is at version: 3.1.2

 but it is also required to be compatible
with: [EMAIL PROTECTED], version=3.1.1}]

 by: hibernate-annotations  

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Saturday, January 28, 2006
11:10 AM
To: jboss-development@lists.sourceforge.net;
QA; Scott M Stark
Subject: jboss-4.0-jdk-matrix
Build Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20060128115204




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:216:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:50: Exit code: 1
  See compile.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 01/28/2006 11:52:04
  
 
 
  
  Time
  to build: 14 minutes 13 seconds
  
 
 
  
  Last
  changed: 01/28/2006 11:19:11
  
 
 
  
  Last
  log entry: JBAS-2707, update to
  hibernate 3.1.2
  
 




 




 
  
  
  
   

 Unit Tests:
(0)  Total Errors and Failures: (0) 

   
   



 
  
   
  
 





 


 


 

   
   

 


 


 


 

   
   

 


 


 

   
  
  
   
  
  
   

 Modifications
since last build:  (first 50 of 1) 

   
   

1.1.2.68


modified


starksm


build/build-thirdparty.xml


JBAS-2707, update to
hibernate 3.1.2

   
   





   
  
  
   
  
  
   

 

   
  
  
  
  
 




 

RE: [JBoss-dev] FW: jboss-remoting-testsuite-1.5 Thread Dump

[Ryan Campbell]

Correction.  The test is still waiting for
the count to reach the expectation, or encounter an error.  Since none of these
are occurring, the test waits forever. 

 









From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan Campbell
Sent: Tuesday, January 24, 2006
10:17 AM
To: Tom Elrod
Cc: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] FW:
jboss-remoting-testsuite-1.5 Thread Dump



 

Tom,

 

Here is the stack trace from a hung
remoting testsuite on jdk 1.5.  It looks like all of the threads have
exited, but the test is still trying to increment the count, and hasn’t
found an exception.  Perhaps the catch block should be expanded to include
any throwable?  Rajesh is testing to see if this allows the test to fail
instead of hanging.

 

ie, 

   catch(Throwable e)   {  error = true;  assertTrue("Error: " + e.getMessage(), false);   }

 

 









From: Rajesh Rajasekaran 
Sent: Monday, January 23, 2006
4:54 PM
To: Ryan Campbell
Subject: RE: jboss-remoting-testsuite-1.5
Build Completed With Testsuite Errors



 

Stack trace of thread dump

 

    [junit] Running
org.jboss.test.remoting.util.PortUtilTestCase

    [junit] Full thread
dump Java HotSpot(TM) Server VM (1.5.0_03-b07 mixed mode):

 

    [junit] "Low
Memory Detector" daemon prio=1 tid=0x8df3a4e0 nid=0x4ec5 runnable
[0x..0x]

 

    [junit]
"CompilerThread1" daemon prio=1 tid=0x8df39140 nid=0x4ec4 waiting on
condition [0x..0x8da79788]

 

    [junit]
"CompilerThread0" daemon prio=1 tid=0x8df38200 nid=0x4ec3 waiting on
condition [0x..0x8dafa708]

 

    [junit]
"AdapterThread" daemon prio=1 tid=0x8df37280 nid=0x4ec2 waiting on
condition [0x..0x]

 

    [junit] "Signal
Dispatcher" daemon prio=1 tid=0x8df36460 nid=0x4ec1 waiting on condition
[0x..0x]

 

    [junit]
"Finalizer" daemon prio=1 tid=0x8df2cad0 nid=0x4ec0 in Object.wait()
[0x8de7e000..0x8de7e770]

   
[junit] at java.lang.Object.wait(Native Method)

    [junit]
- waiting on <0x925138d0> (a java.lang.ref.ReferenceQueue$Lock)

   
[junit] at
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)

   
[junit] - locked <0x925138d0> (a
java.lang.ref.ReferenceQueue$Lock)

   
[junit] at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)

   
[junit] at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

 

    [junit] "Reference
Handler" daemon prio=1 tid=0x8df2be90 nid=0x4ebf in Object.wait()
[0x8deff000..0x8deff6f0]

    [junit]
at java.lang.Object.wait(Native Method)

   
[junit] - waiting on <0x9254a538> (a
java.lang.ref.Reference$Lock)

   
[junit] at java.lang.Object.wait(Object.java:474)

   
[junit] at
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)

   
[junit] - locked <0x9254a538> (a
java.lang.ref.Reference$Lock)

 

    [junit]
"main" prio=1 tid=0x0805d188 nid=0x4eb7 waiting on condition
[0xbfffb000..0xbfffc118]

   
[junit] at java.lang.Thread.sleep(Native Method)

   
[junit] at
org.jboss.test.remoting.util.PortUtilTestCase.testFindingFreePorts(PortUtilTestCase.java:83)

   
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

   
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

   
[junit] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   
[junit] at
java.lang.reflect.Method.invoke(Method.java:585)

   
[junit] at
junit.framework.TestCase.runTest(TestCase.java:154)

   
[junit] at
junit.framework.TestCase.runBare(TestCase.java:127)

   
[junit] at
junit.framework.TestResult$1.protect(TestResult.java:106)

   
[junit] at
junit.framework.TestResult.runProtected(TestResult.java:124)

   
[junit] at
junit.framework.TestResult.run(TestResult.java:109)

   
[junit] at
junit.framework.TestCase.run(TestCase.java:118)

   
[junit] at
junit.framework.TestSuite.runTest(TestSuite.java:208)

   
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)

   
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:289)

   
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:656)

   
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:558)

 

    [junit] "VM
Thread" prio=1 tid=0x8df29310 nid=0x4ebe runnable

 

    [junit] "GC task
thread#0 (ParallelGC)" prio=1 tid=0x080e3930 nid=0x4eba runnable

 

    [junit] "GC task
thread#1 (ParallelGC)" prio=1 tid=0x080e3d18 nid=0x4ebb runnable

 

    [junit] "GC task
thread#2 (ParallelGC)" prio=1 tid=0x080e4100 nid=0x4ebc runnable

[JBoss-dev] FW: jboss-remoting-testsuite-1.5 Thread Dump

[Ryan Campbell]

Tom,

 

Here is the stack trace from a hung remoting
testsuite on jdk 1.5.  It looks like all of the threads have exited, but
the test is still trying to increment the count, and hasn’t found an exception. 
Perhaps the catch block should be expanded to include any throwable? 
Rajesh is testing to see if this allows the test to fail instead of hanging.

 

ie, 

   catch(Throwable e)   {  error = true;  assertTrue("Error: " + e.getMessage(), false);   }

 

 









From: Rajesh Rajasekaran 
Sent: Monday, January 23, 2006
4:54 PM
To: Ryan Campbell
Subject: RE:
jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors



 

Stack trace of thread dump

 

    [junit] Running
org.jboss.test.remoting.util.PortUtilTestCase

    [junit] Full thread
dump Java HotSpot(TM) Server VM (1.5.0_03-b07 mixed mode):

 

    [junit] "Low
Memory Detector" daemon prio=1 tid=0x8df3a4e0 nid=0x4ec5 runnable
[0x..0x]

 

    [junit]
"CompilerThread1" daemon prio=1 tid=0x8df39140 nid=0x4ec4 waiting on
condition [0x..0x8da79788]

 

    [junit]
"CompilerThread0" daemon prio=1 tid=0x8df38200 nid=0x4ec3 waiting on
condition [0x..0x8dafa708]

 

    [junit]
"AdapterThread" daemon prio=1 tid=0x8df37280 nid=0x4ec2 waiting on
condition [0x..0x]

 

    [junit] "Signal
Dispatcher" daemon prio=1 tid=0x8df36460 nid=0x4ec1 waiting on condition
[0x..0x]

 

    [junit]
"Finalizer" daemon prio=1 tid=0x8df2cad0 nid=0x4ec0 in Object.wait()
[0x8de7e000..0x8de7e770]

   
[junit] at java.lang.Object.wait(Native Method)

   
[junit] - waiting on <0x925138d0> (a
java.lang.ref.ReferenceQueue$Lock)

   
[junit] at
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)

   
[junit] - locked <0x925138d0> (a
java.lang.ref.ReferenceQueue$Lock)

   
[junit] at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)

   
[junit] at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

 

    [junit] "Reference
Handler" daemon prio=1 tid=0x8df2be90 nid=0x4ebf in Object.wait()
[0x8deff000..0x8deff6f0]

   
[junit] at java.lang.Object.wait(Native Method)

   
[junit] - waiting on <0x9254a538> (a
java.lang.ref.Reference$Lock)

   
[junit] at java.lang.Object.wait(Object.java:474)

   
[junit] at
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)

   
[junit] - locked <0x9254a538> (a
java.lang.ref.Reference$Lock)

 

    [junit]
"main" prio=1 tid=0x0805d188 nid=0x4eb7 waiting on condition
[0xbfffb000..0xbfffc118]

   
[junit] at java.lang.Thread.sleep(Native Method)

   
[junit] at org.jboss.test.remoting.util.PortUtilTestCase.testFindingFreePorts(PortUtilTestCase.java:83)

   
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

   
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    [junit]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   
[junit] at
java.lang.reflect.Method.invoke(Method.java:585)

   
[junit] at
junit.framework.TestCase.runTest(TestCase.java:154)

   
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)

   
[junit] at
junit.framework.TestResult$1.protect(TestResult.java:106)

   
[junit] at
junit.framework.TestResult.runProtected(TestResult.java:124)

   
[junit] at junit.framework.TestResult.run(TestResult.java:109)

   
[junit] at
junit.framework.TestCase.run(TestCase.java:118)

   
[junit] at
junit.framework.TestSuite.runTest(TestSuite.java:208)

   
[junit] at
junit.framework.TestSuite.run(TestSuite.java:203)

   
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:289)

   
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:656)

   
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:558)

 

    [junit] "VM
Thread" prio=1 tid=0x8df29310 nid=0x4ebe runnable

 

    [junit] "GC task
thread#0 (ParallelGC)" prio=1 tid=0x080e3930 nid=0x4eba runnable

 

    [junit] "GC task
thread#1 (ParallelGC)" prio=1 tid=0x080e3d18 nid=0x4ebb runnable

 

    [junit] "GC task
thread#2 (ParallelGC)" prio=1 tid=0x080e4100 nid=0x4ebc runnable

 

    [junit] "GC task
thread#3 (ParallelGC)" prio=1 tid=0x080e48e0 nid=0x4ebd runnable

 

    [junit] "VM
Periodic Task Thread" prio=1 tid=0x8df3ba00 nid=0x4ec6 waiting on
condition

 









From: Ryan Campbell 
Sent: Monday, January 23, 2006
2:57 PM
To: Tom Elrod
Cc: QA
Subject: RE:
jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors



 

 

I guess this is an intermittent problem?   

[JBoss-dev] RE: jboss-4.0-testsuite Build Timed Out

[Ryan Campbell]

Since several builds timed out, I’m
going to rerun them.  I found some hung test processes, so perhaps there was
some conflict. 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, January 20, 2006
1:10 AM
To: Andy Oliver; Adrian Brock;
Alexey Loubyansky; Anil Saldhana; Bill Decoste; Bela Ban; Bill Burke;
[EMAIL PROTECTED]; Ben Wang; [EMAIL PROTECTED]; Clebert
Suconic; Dimitris Andreadis; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; [EMAIL PROTECTED];
Jason T. Greene; Jim Moran; Kabir Khan; Luc Texier; Noël Rocher; Norman
Richards; [EMAIL PROTECTED]; QA; Ryan Campbell; Remy Maucherat; Ruel Loehr;
Sacha Labourey; Scott M Stark; [EMAIL PROTECTED]; Stan Silvert; Steve
Ebersole; Thomas Diesler; Tom Elrod; [EMAIL PROTECTED]
Subject: jboss-4.0-testsuite Build
Timed Out
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log2006012750




 
  
  BUILD
  TIMED OUT
  
 
 
  
  Ant
  Error Message: build
  timeout
  
 
 
  
  Date
  of build: 01/20/2006 00:07:50
  
 
 
  
  Time
  to build: 
  
 
 
  
  Last
  changed: 12/30/2005 02:15:51
  
 
 
  
  Last
  log entry: [JBAS-2142] Support
  marshalling of state transfer during web app deployment
  
 




 

RE: [JBoss-dev] Push to finalizing 3.2.8

[Ryan Campbell]

Yes, just assigned it to myself.  I'll test from the 3.2 branch.

-Original Message-
From: Dimitris Andreadis 
Sent: Friday, January 20, 2006 11:52 AM
To: jboss-development@lists.sourceforge.net
Cc: Ryan Campbell
Subject: RE: [JBoss-dev] Push to finalizing 3.2.8


Ryan, are you taking this task? I suppose testing this can be done in
either the 3.x or 4.x branch.

Cheers
/D

http://jira.jboss.com/jira/browse/JBAS-2503

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Ryan Campbell
> Sent: 20 January, 2006 02:08
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] Push to finalizing 3.2.8
> 
> I believe so. 
> 
> 1. Create datasource for thin driver pointed at oracle 9i 2. 
> Deploy the OracleThinPersistenceManager 2. Run the 
> jboss-all-config-tests target
> 
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Adrian Brock
> Sent: Thursday, January 19, 2006 12:56 PM
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] Push to finalizing 3.2.8
> 
> On Thu, 2006-01-19 at 13:30, Ryan Campbell wrote:
> > QA has installed Oracle 9i and can run the JBossMQ testsuite against
> it.
> > 
> 
> Do you know how to test it from the information on the task?
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of 
> > Adrian Brock
> > Sent: Thursday, January 19, 2006 11:29 AM
> > To: jboss-development@lists.sourceforge.net
> > Subject: Re: [JBoss-dev] Push to finalizing 3.2.8
> > 
> > On http://jira.jboss.com/jira/browse/JBAS-2503
> > 
> > This is optional for 3.2.8 final. 
> > 
> > I've tested it with Oracle 10 but it really needs somebody 
> with access 
> > to Oracle8/9 to run the JBossMQ testsuite against it.
> > 
> > On Thu, 2006-01-19 at 11:52, Scott M Stark wrote:
> > > Dimitris is going to be driving a finalization of the 
> legacy 3.2.8 
> > > release. There still are 11 outstanding issues with several
> unassigned
> > > so he will be contacting the reporters and following up 
> here to get
> > them
> > > assigned.
> > >  
> > > The big outstanding integration issue is the targeted binary 
> > > compatibility between the standard remote interfaces (JMS, ejb 
> > > transports, webservices). I expect that we need to drill down into
> > these
> > > stacks to resolve any incompatibilities that show up.
> > > 
> > > 
> > > Scott Stark
> > > VP Architecture & Technology
> > > JBoss Inc.
> > > 
> > >  
> > > 
> > > 
> > > ---
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through
> log
> > files
> > > for problems?  Stop!  Download the new AJAX search engine 
> that makes 
> > > searching your log files as easy as surfing the  web.  DOWNLOAD
> > SPLUNK!
> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
> > > ___
> > > JBoss-Development mailing list
> > > JBoss-Development@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> --
> 
> Adrian Brock
> Chief Scientist
> JBoss Inc.
>  
> 
> 
> 
> ---
> This SF.net email is sponsored by: Splunk Inc. Do you grep 
> through log files for problems?  Stop!  Download the new AJAX 
> search engine that makes searching your log files as easy as 
> surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&;
> dat=121642
> ___
> JBoss-Development mailing list
> JBoss-Development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 
> ---
> This SF.net email is sponsored by: Splunk Inc. Do you grep 
> through log files for problems?  Stop!  Download the new AJAX 
> search engine that makes searching your log files as easy as 
> surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> ___
> JBoss-Development mailing list
> JBoss-Development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] Push to finalizing 3.2.8

[Ryan Campbell]

I believe so. 

1. Create datasource for thin driver pointed at oracle 9i
2. Deploy the OracleThinPersistenceManager
2. Run the jboss-all-config-tests target


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Thursday, January 19, 2006 12:56 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] Push to finalizing 3.2.8

On Thu, 2006-01-19 at 13:30, Ryan Campbell wrote:
> QA has installed Oracle 9i and can run the JBossMQ testsuite against
it.
> 

Do you know how to test it from the information on the task?

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Adrian Brock
> Sent: Thursday, January 19, 2006 11:29 AM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev] Push to finalizing 3.2.8
> 
> On http://jira.jboss.com/jira/browse/JBAS-2503
> 
> This is optional for 3.2.8 final. 
> 
> I've tested it with Oracle 10 but it really needs somebody 
> with access to Oracle8/9 to run the JBossMQ testsuite against it.
> 
> On Thu, 2006-01-19 at 11:52, Scott M Stark wrote:
> > Dimitris is going to be driving a finalization of the legacy 3.2.8
> > release. There still are 11 outstanding issues with several
unassigned
> > so he will be contacting the reporters and following up here to get
> them
> > assigned.
> >  
> > The big outstanding integration issue is the targeted binary
> > compatibility between the standard remote interfaces (JMS, ejb
> > transports, webservices). I expect that we need to drill down into
> these
> > stacks to resolve any incompatibilities that show up.
> > 
> > 
> > Scott Stark
> > VP Architecture & Technology
> > JBoss Inc.
> >  
> >  
> > 
> > 
> > ---
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through
log
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD
> SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
> > ___
> > JBoss-Development mailing list
> > JBoss-Development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
-- 
 
Adrian Brock
Chief Scientist
JBoss Inc.
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] Push to finalizing 3.2.8

[Ryan Campbell]

QA has installed Oracle 9i and can run the JBossMQ testsuite against it.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Thursday, January 19, 2006 11:29 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] Push to finalizing 3.2.8

On http://jira.jboss.com/jira/browse/JBAS-2503

This is optional for 3.2.8 final. 

I've tested it with Oracle 10 but it really needs somebody 
with access to Oracle8/9 to run the JBossMQ testsuite against it.

On Thu, 2006-01-19 at 11:52, Scott M Stark wrote:
> Dimitris is going to be driving a finalization of the legacy 3.2.8
> release. There still are 11 outstanding issues with several unassigned
> so he will be contacting the reporters and following up here to get
them
> assigned.
>  
> The big outstanding integration issue is the targeted binary
> compatibility between the standard remote interfaces (JMS, ejb
> transports, webservices). I expect that we need to drill down into
these
> stacks to resolve any incompatibilities that show up.
> 
> 
> Scott Stark
> VP Architecture & Technology
> JBoss Inc.
>  
>  
> 
> 
> ---
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD
SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
> ___
> JBoss-Development mailing list
> JBoss-Development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jboss-development
-- 
 
Adrian Brock
Chief Scientist
JBoss Inc.
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-head-jdk-matrix Build Failed

[Ryan Campbell]

module-webservice14: BUILD FAILED/services/cruisecontrol/checkout/jboss-head/build/build.xml:631: The following error occurred while executing this line:/services/cruisecontrol/checkout/jboss-head/build/build-distr.xml:1432: /services/cruisecontrol/checkout/jboss-head/build/${jboss.jbossws.lib} not found.

 

 









From: Ryan Campbell 
Sent: Tuesday, January 10, 2006
4:23 PM
To: '[EMAIL PROTECTED]'; Anil Saldhana;
[EMAIL PROTECTED]; Dimitris Andreadis;
jboss-development@lists.sourceforge.net; QA; Rajesh Rajasekaran; Scott M Stark;
Thomas Diesler
Subject: RE: jboss-head-jdk-matrix
Build Failed



 

Webservices is breaking the build in a 1.4
JDK:

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 10, 2006
4:20 PM
To: Anil Saldhana;
[EMAIL PROTECTED]; Dimitris Andreadis; jboss-development@lists.sourceforge.net;
QA; Rajesh Rajasekaran; Scott M Stark; Thomas Diesler
Subject: jboss-head-jdk-matrix
Build Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110171308




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:179:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:50: Exit code: 1
  See compile.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 01/10/2006 17:13:08
  
 
 
  
  Time
  to build: 4 minutes 49 seconds
  
 
 
  
  Last
  changed: 01/10/2006 17:04:34
  
 
 
  
  Last
  log entry: JBAS-2280, log a
  warning when undeploying not deployed packages
  
 




 




 
  
  
  
   

 Unit Tests:
(0)  Total Errors and Failures: (0) 

   
   



 
  
   
  
 





 


 


 

   
   

 


 


 


 

   
   

 


 


 

   
  
  
   
  
  
   

 Modifications
since last builds:  (first 50 of 15) 

   
   

1.85


modified


dimitris


system/src/main/org/jboss/deployment/MainDeployer.java


JBAS-2280, log a
warning when undeploying not deployed packages

   
   

1.9


modified


bstansberry


testsuite/src/main/org/jboss/test/cluster/test/DRMTestCase.java


Disable
testConflictingAddRemoveDeadlock.

   
   

1.10


modified


starksm


common/src/main/org/jboss/xb/binding/sunday/unmarshalling/SchemaBindingResolver.java


Fix the
resolveAsLSInput javadoc

   
   

1.16


modified


starksm


common/src/main/org/jboss/util/Classes.java


Fix the implicit
StringBuffer creation within the displayClassInfo method

   
   

1.16


modified


dimitris


connector/src/etc/example-config/hsqldb-ds.xml


JBAS-2371, Specifying
a bind address for Hypersonic in memory database

   
   

1.4


modified


dimitris


connector/src/etc/example-config/hsqldb-encrypted-ds.xml


JBAS-2371, Specifying
a bind address for Hypersonic in memory database

   
   

1.38


modified


rrajasekaran


tools/etc/cruisecontrol/templates/projects.xml


Updated
jboss-seam-testsuite to gather test results

   
   

1.2


modified


rrajasekaran


tools/etc/cruisecontrol/scripts/index-jboss-seam.html


Updated
jboss-seam-testsuite to gather test results

   
   

1.3


modified


rrajasekaran


tools/etc/cruisecontrol/scripts/build-jboss-seam-testsuite.xml


Updated
jboss-seam-testsuite to gather test results

   
   

1.11


modified


asaldhana


tomcat/src/main/org/jboss/web/tomcat/tc5/WebCtxLoader.java


Use the local variable
'jar'

   
   

1.10


modified


asaldhana


tomcat/src/main/org/jboss/web/tomcat/tc5/WebCtxLoader.java


JBAS-2538: The war
WebCtxLoader is not limiting WEB-INF/lib classpath contents to jars

   
   

1.34


modified


dimitris


varia/src/main/org/jboss/jdbc/HypersonicDatabase.java


JBAS-2371, Specifying
a bind address for Hypersonic in memory database

   
   

1.12


modified


dimitris


varia/src/main/org/jboss/jdbc/HypersonicDatabaseMBean.java


JBAS-2371, Specifying
a bind address for Hypers

[JBoss-dev] RE: jboss-head-jdk-matrix Build Failed

[Ryan Campbell]

Webservices is breaking the build in a 1.4
JDK:

 

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 10, 2006
4:20 PM
To: Anil Saldhana;
[EMAIL PROTECTED]; Dimitris Andreadis;
jboss-development@lists.sourceforge.net; QA; Rajesh Rajasekaran; Scott M Stark;
Thomas Diesler
Subject: jboss-head-jdk-matrix
Build Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110171308




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:179:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:50: Exit code: 1
  See compile.log in Build Artifacts for details.
  
 
 
  
  Date
  of build: 01/10/2006 17:13:08
  
 
 
  
  Time
  to build: 4 minutes 49 seconds
  
 
 
  
  Last
  changed: 01/10/2006 17:04:34
  
 
 
  
  Last
  log entry: JBAS-2280, log a
  warning when undeploying not deployed packages
  
 




 




 
  
  
  
   

 Unit Tests:
(0)  Total Errors and Failures: (0) 

   
   



 
  
   
  
 





 


 


 

   
   

 


 


 


 

   
   

 


 


 

   
  
  
   
  
  
   

 Modifications
since last builds:  (first 50 of 15) 

   
   

1.85


modified


dimitris


system/src/main/org/jboss/deployment/MainDeployer.java


JBAS-2280, log a
warning when undeploying not deployed packages

   
   

1.9


modified


bstansberry


testsuite/src/main/org/jboss/test/cluster/test/DRMTestCase.java


Disable
testConflictingAddRemoveDeadlock.

   
   

1.10


modified


starksm


common/src/main/org/jboss/xb/binding/sunday/unmarshalling/SchemaBindingResolver.java


Fix the resolveAsLSInput
javadoc

   
   

1.16


modified


starksm


common/src/main/org/jboss/util/Classes.java


Fix the implicit
StringBuffer creation within the displayClassInfo method

   
   

1.16


modified


dimitris


connector/src/etc/example-config/hsqldb-ds.xml


JBAS-2371, Specifying
a bind address for Hypersonic in memory database

   
   

1.4


modified


dimitris


connector/src/etc/example-config/hsqldb-encrypted-ds.xml


JBAS-2371, Specifying
a bind address for Hypersonic in memory database

   
   

1.38


modified


rrajasekaran


tools/etc/cruisecontrol/templates/projects.xml


Updated
jboss-seam-testsuite to gather test results

   
   

1.2


modified


rrajasekaran


tools/etc/cruisecontrol/scripts/index-jboss-seam.html


Updated
jboss-seam-testsuite to gather test results

   
   

1.3


modified


rrajasekaran


tools/etc/cruisecontrol/scripts/build-jboss-seam-testsuite.xml


Updated
jboss-seam-testsuite to gather test results

   
   

1.11


modified


asaldhana


tomcat/src/main/org/jboss/web/tomcat/tc5/WebCtxLoader.java


Use the local
variable 'jar'

   
   

1.10


modified


asaldhana


tomcat/src/main/org/jboss/web/tomcat/tc5/WebCtxLoader.java


JBAS-2538: The war
WebCtxLoader is not limiting WEB-INF/lib classpath contents to jars

   
   

1.34


modified


dimitris


varia/src/main/org/jboss/jdbc/HypersonicDatabase.java


JBAS-2371, Specifying
a bind address for Hypersonic in memory database

   
   

1.12


modified


dimitris


varia/src/main/org/jboss/jdbc/HypersonicDatabaseMBean.java


JBAS-2371, Specifying
a bind address for Hypersonic in memory database

   
   

1.84


modified


tdiesler


webservice/build.xml


Remove dependency on
jbossxb, jbossws repository versions

   
   

1.48


modified


tdiesler


build/build-thirdparty.xml


Remove dependency on
jbossxb, jbossws repository versions

   
  
  
   
  
  
   

 

   
  
  
  
  
 




 

RE: [JBoss-dev] maven2 prototype build in QA lab

[Ryan Campbell]

Obviously, you don’t need the QA lab
if you have maven2 and svn installed.

 











From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ruel Loehr
Sent: Tuesday, January 03, 2006
5:49 PM
To:
jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] maven2
prototype build in QA lab



 

I have setup a prototype build of JBoss using Maven2 in the
QA lab.   This snapshot of ongoing work currently builds the minimal
version of JBossAS.

 

Anyone with QA (dev01, 02, or 03) lab access can check out
and execute this build with the following instructions:

 

svn co https://svn.labs.jboss.com/trunk/labs/jbossbuild/projects/jboss/ buildtestcd buildtestcd buildmvn install    

 

This purpose of this prototype is to determine what effort would
be required in the conversion of our existing build to Maven2.   At
this point, the key items to take notice of are the buildfiles, entitled
‘pom.xml’.

 

The related discussion with further in depth comments can be
seen here:

 

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73148&start=10

 

For those with interest, please take a look, and let us know
via the build forums your praises or concerns.

 

 

 

Ruel Loehr

JBoss QA

 

-

512-347-7840 ext 2011

Yahoo: ruelloehr

Skype: ruelloehr

AOL: dokoruel

 

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

[Ryan Campbell]

The testsuite build timed out (went longer
than 2 hours).  The following tests timed out as well:

 

    [junit] Test
org.jboss.test.deadlock.test.BeanStressTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.hello.test.HelloClusteredHttpStressTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.hello.test.HelloHttpStressTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.hello.test.HelloTimingStressTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.jbossmq.perf.OILInvocationLayerStressTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.jca.test.CachedConnectionBankStressTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.jca.test.HAConnectionFactoryUnitTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase FAILED
(timeout)

    [junit] Test
org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.jca.test.PSCacheUnitTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.jca.test.RemoteDSUnitTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.jca.test.SecurityContextUnitTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase FAILED
(timeout)

    [junit] Test
org.jboss.test.jmx.test.RedeployStressTestCase FAILED (timeout)

    [junit] Test
org.jboss.test.tm.test.TxTimeoutUnitTestCase FAILED

 

Not sure what to make of this, am forcing
the build again.

 











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, September 09, 2005
5:35 PM
To:
jboss-development@lists.sourceforge.net; QA
Subject: jboss-4.0-testsuite Build
Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050909163227




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: build
  timeout
  
 
 
  
  Date
  of build: 09/09/2005 16:32:27
  
 
 
  
  Time
  to build: 
  
 
 
  
  Last
  changed: 09/09/2005 15:19:15
  
 




 

RE: [JBoss-dev] 4.0.3RC2

[Ryan Campbell]

> I'd much rather see false negatives than false positives.
> That way I/we can at least look at the problem to see whether
> is a cruisecontrol issue or a JBoss issue.

Yes, I agree.  We will fix this.
 
> I'd also like to see it fail the build when there are tests
> failing that are not known issues:
> http://jira.jboss.com/jira/browse/JBAS-1879

We do fail when there are test failures, as can be seen from this
jboss-head-testsuite failure on 8/2: 

http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite?log=
log20050729032543

The remaining task is to verify that badtests.excludes is up to date as
Scott mentions in JBAS-1879.

> And just maybe (?) we'd have a teststuite in jboss-head
> that isn't completely broken:
> http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-jdk-
> matrix/20050815095512/results/index.html

This is failing due to OutOfMemoryErrors, which are hard to see from the
logs we provide.  You can only see this in server/all/server.log.  We
need to add build/ouput/**/*.log to the "Build Artifacts". 

http://jira.jboss.com/jira/browse/JBQA-142



---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] 4.0.3RC2

[Ryan Campbell]

This is failing because the ejb3-4.0-testsuite was not updated to run
against the 4.0.x alias.

So it is just a problem with cruisecontrol, not with
ejb3/build-tests.xml

> -Original Message-
> From: Bill Burke
> Sent: Monday, August 15, 2005 10:25 AM
> To: Adrian Brock
> Cc: jboss-development@lists.sourceforge.net; QA
> Subject: Re: [JBoss-dev] 4.0.3RC2
> 
> Looks like somebody bleeped up the build again.  I know Branch_4_0
> compiled fine for me before I left on vacation.
> 
> Adrian Brock wrote:
> > A small amount of research shows the last ejb3 4.x tests,
> > resulted in no tests being run?
> > http://cruisecontrol.jboss.com/cc/artifacts/ejb3-4.0-
> testsuite/20050812094631/results/index.html
> >
> > Because the compile failed.
> > http://cruisecontrol.jboss.com/cc/artifacts/ejb3-4.0-
> testsuite/20050812094631/compileejb3.log
> >
> > Why isn't this problem getting posted to jboss-dev?
> >
> > On Mon, 2005-08-15 at 10:42, Adrian Brock wrote:
> >
> >>Most likely, you are seeing a problem with the upgrade of
hypersonic?
> >>
> >>But, if you are just going to post "IT DOES WORK", I'll post my
> >>standard LART:
> >>http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp
> >>
> >>On Mon, 2005-08-15 at 09:37, [EMAIL PROTECTED] wrote:
> >>
> >>>Doh, I knew that.  Instead I reverted to 403rc1 and like all my
weird
> >>>RMI problems and all my weird jdbc errors
> >>>vanished.  This is a really simple example app I might add.  What
> >>>happened in ejb3 between 1 and 2?
> >>>
> >>>Max Rydahl Andersen wrote:
> >>>
> >>>
> Disable jdbc batching and you should be able to get an exception
> message  for
> the concrete entity that fails and why.
> 
> /max
> 
> 
> >Anyone else seeing this kinda thing w/ejb3->hypersonic?
> >
> >2005-08-15 01:34:21,654 DEBUG
> >[org.hibernate.persister.entity.AbstractEntityPersister]
Inserting
> >entity: [org.trijug.entity.Due#0]
> >2005-08-15 01:34:21,655 DEBUG
[org.hibernate.jdbc.AbstractBatcher]
> >Executing batch size: 1
> >2005-08-15 01:34:21,656 DEBUG
[org.hibernate.jdbc.AbstractBatcher]
> >about  to close PreparedStatement (open PreparedStatements: 1,
> >globally: 1)
> >2005-08-15 01:34:21,656 DEBUG
[org.hibernate.jdbc.AbstractBatcher]
> >closing statement
> >2005-08-15 01:34:21,656 DEBUG
[org.hibernate.jdbc.ConnectionManager]
> >aggressively releasing JDBC connection
> >2005-08-15 01:34:21,657 DEBUG
[org.hibernate.jdbc.ConnectionManager]
> >closing JDBC connection [ (open PreparedStatements: 0, globally:
0)
> >(open ResultSets: 0, globally: 0)]
> >2005-08-15 01:34:21,657 DEBUG
> >[org.hibernate.util.JDBCExceptionReporter]  Could not execute
JDBC
> >batch update [insert into Account (firstname,  lastname, email,
> >addressL1, addressL2, city, state, zip, joined, id)  values (?,
?, ?,
> >?, ?, ?, ?, ?, ?, ?)]
> >java.sql.BatchUpdateException: failed batch
> >at org.hsqldb.jdbc.jdbcStatement.executeBatch(Unknown
Source)
> >at
> >org.hsqldb.jdbc.jdbcPreparedStatement.executeBatch(Unknown
Source)
> >at
>
>org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(Wrapp
ed
> Statement.java:484)
> >
> >at
>
>org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.j
av
> a:57)
> >
> >at
>
>org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.jav
a:
> 175)
> >
> >at
>
>org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher
.j
> ava:75)
> >
> >at
>
>org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher
.j
> ava:70)
> >
> >at
>
>org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBa
tc
> her.java:151)
> >
> >at
>
>org.hibernate.persister.entity.AbstractEntityPersister.insert(Abstr
ac
> tEntityPersister.java:1910)
> >
> >at
>
>org.hibernate.persister.entity.AbstractEntityPersister.insert(Abstr
ac
> tEntityPersister.java:2287)
> >
> >at
>
>org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.
ja
> va:48)
> >
> >at
> >org.hibernate.engine.ActionQueue.execute(ActionQueue.java:243)
> >at
>
>org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:22
7)
> >at
>
>org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:14
0)
> >at
>
>org.hibernate.event.def.AbstractFlushingEventListener.performExecut
io
> ns(AbstractFlushingEventListener.java:284)
> >
> >at
>
>org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFl
us
> hEventListener.java:27)
> >
> >at
org.hibernate.impl.SessionImpl.flush(SessionImpl.java:750)
> >at
>
>org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityMan
ag
> erImpl.java:185)
> >
> >at
>
>org.jboss.ej

RE: [JBoss-dev] 4.0.3RC2

[Ryan Campbell]

It looks as though cruisecrontrol is not marking the build as failed, so
a failure notice was not sent.

We will look into this and also verify we don't have other false
positives. 

> -Original Message-
> From: Adrian Brock
> Sent: Monday, August 15, 2005 10:08 AM
> To: jboss-development@lists.sourceforge.net
> Cc: QA
> Subject: Re: [JBoss-dev] 4.0.3RC2
> 
> A small amount of research shows the last ejb3 4.x tests,
> resulted in no tests being run?
> http://cruisecontrol.jboss.com/cc/artifacts/ejb3-4.0-
> testsuite/20050812094631/results/index.html
> 
> Because the compile failed.
> http://cruisecontrol.jboss.com/cc/artifacts/ejb3-4.0-
> testsuite/20050812094631/compileejb3.log
> 
> Why isn't this problem getting posted to jboss-dev?
> 
> On Mon, 2005-08-15 at 10:42, Adrian Brock wrote:
> > Most likely, you are seeing a problem with the upgrade of
hypersonic?
> >
> > But, if you are just going to post "IT DOES WORK", I'll post my
> > standard LART:
> > http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp
> >
> > On Mon, 2005-08-15 at 09:37, [EMAIL PROTECTED] wrote:
> > > Doh, I knew that.  Instead I reverted to 403rc1 and like all my
weird
> > > RMI problems and all my weird jdbc errors
> > > vanished.  This is a really simple example app I might add.  What
> > > happened in ejb3 between 1 and 2?
> > >
> > > Max Rydahl Andersen wrote:
> > >
> > > >
> > > > Disable jdbc batching and you should be able to get an exception
> > > > message  for
> > > > the concrete entity that fails and why.
> > > >
> > > > /max
> > > >
> > > >> Anyone else seeing this kinda thing w/ejb3->hypersonic?
> > > >>
> > > >> 2005-08-15 01:34:21,654 DEBUG
> > > >> [org.hibernate.persister.entity.AbstractEntityPersister]
Inserting
> > > >> entity: [org.trijug.entity.Due#0]
> > > >> 2005-08-15 01:34:21,655 DEBUG
[org.hibernate.jdbc.AbstractBatcher]
> > > >> Executing batch size: 1
> > > >> 2005-08-15 01:34:21,656 DEBUG
[org.hibernate.jdbc.AbstractBatcher]
> > > >> about  to close PreparedStatement (open PreparedStatements: 1,
> > > >> globally: 1)
> > > >> 2005-08-15 01:34:21,656 DEBUG
[org.hibernate.jdbc.AbstractBatcher]
> > > >> closing statement
> > > >> 2005-08-15 01:34:21,656 DEBUG
> [org.hibernate.jdbc.ConnectionManager]
> > > >> aggressively releasing JDBC connection
> > > >> 2005-08-15 01:34:21,657 DEBUG
> [org.hibernate.jdbc.ConnectionManager]
> > > >> closing JDBC connection [ (open PreparedStatements: 0,
globally: 0)
> > > >> (open ResultSets: 0, globally: 0)]
> > > >> 2005-08-15 01:34:21,657 DEBUG
> > > >> [org.hibernate.util.JDBCExceptionReporter]  Could not execute
JDBC
> > > >> batch update [insert into Account (firstname,  lastname, email,
> > > >> addressL1, addressL2, city, state, zip, joined, id)  values (?,
?,
> ?,
> > > >> ?, ?, ?, ?, ?, ?, ?)]
> > > >> java.sql.BatchUpdateException: failed batch
> > > >> at org.hsqldb.jdbc.jdbcStatement.executeBatch(Unknown
> Source)
> > > >> at
> > > >> org.hsqldb.jdbc.jdbcPreparedStatement.executeBatch(Unknown
Source)
> > > >> at
> > > >>
>
org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedSta
te
> ment.java:484)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:5
7)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:175
)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java
:7
> 5)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java
:7
> 0)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBatcher
.j
> ava:151)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEn
ti
> tyPersister.java:1910)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEn
ti
> tyPersister.java:2287)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:
48
> )
> > > >>
> > > >> at
> > > >> org.hibernate.engine.ActionQueue.execute(ActionQueue.java:243)
> > > >> at
> > > >>
> org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:227)
> > > >> at
> > > >>
> org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140)
> > > >> at
> > > >>
>
org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(
Ab
> stractFlushingEventListener.java:284)
> > > >>
> > > >> at
> > > >>
>
org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEv
en
> tListener.java:27)
> > > >>
> > > >> at
> org.hibernate.impl.SessionImpl.flush(SessionImpl.java:750)
> > > >> at
> > > >>
>
org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityManagerI
mp
> l.java:185)
> > > >>
> > > >> at
> > > >>
>
org.jboss.ejb

[JBoss-dev] RE: jboss-head-jdk-matrix Build Failed

[Ryan Campbell]

The change to MappingObjectModelProvider was incompatible with j2se 1.4 [execmodules] /scratch/cruisecontrol/checkout/jboss-head/common/src/main/org/jboss/xb/binding/MappingObjectModelProvider.java:182: cannot resolve symbol[execmodules] symbol  : constructor IllegalStateException (java.lang.String,java.lang.Exception)[execmodules] location: class java.lang.IllegalStateException[execmodules]  throw new IllegalStateException("Failed to provide value for " + localName + " from " + o, e);[execmodules]    ^[execmodules] /scratch/cruisecontrol/checkout/jboss-head/common/src/main/org/jboss/xb/binding/MappingObjectModelProvider.java:195: cannot resolve symbol[execmodules] symbol  : constructor IllegalStateException (java.lang.String,java.lang.Exception)[execmodules] location: class java.lang.IllegalStateException[execmodules]  throw new IllegalStateException("Failed to provide value for " + localName + " from " + o, e);

 

 











From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]

Sent: Thursday, July 21, 2005
12:09 PM
To: jboss-development@lists.sourceforge.net;
QA
Subject: jboss-head-jdk-matrix
Build Failed
Importance: High



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050721125938




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:65:
  The following error occurred while executing this line:
  /home/cruisecontrol/work/scripts/build-jboss-head.xml:39: Exit code: 1 See
  compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/
  
 
 
  
  Date
  of build: 07/21/2005 12:59:38
  
 
 
  
  Time
  to build: 6 minutes 42 seconds
  
 
 
  
  Last
  changed: 07/21/2005 12:38:56
  
 
 
  
  Last
  log entry: More debugging.Be
  strict on marshalling failures.
  
 




 




 
  
  
  
   

 Unit Tests:
(0)  Total Errors and Failures: (0) 

   
   



 
  
   
  
 





 


 


 

   
   

 


 


 


 

   
   

 


 


 

   
  
  
   
  
  
   

 Modifications
since last builds:  (first 50 of 8) 

   
   

1.6


modified


tdiesler


common/src/main/org/jboss/xb/binding/MappingObjectModelProvider.java


More debugging.Be
strict on marshalling failures.

   
   

1.1


added


tdiesler


webservice/test/etc/tst.policy


Add security manager

   
   

1.56


modified


tdiesler


webservice/test/build.xml


Add security manager

   
   

1.47


modified


rloehr


jbossas/jbossbuild.xml


changed cvs property
to be parameterized

   
   

1.1


added


rloehr


jbossas/local.properties


no message

   
   

1.33


modified


starksm


connector/src/resources/stylesheets/ConnectionFactoryTemplate.xsl


Fix for (JBAS-2033)
ConnectionFactoryTemplate.xsl contains invalid markup.

   
   

1.83


modified


bill


ejb3/build-test.xml


change test class
directory

   
   

1.33


modified


bill


ejb3/build.xml


change test class
directory

   
  
  
   
  
  
   

 

   
  
  
  
  
 




 

[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-16) Use component-info to determine source repository information

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBBUILD-16?page=history ]

Ryan Campbell updated JBBUILD-16:
-

Description: 
Allow a component to expose its exports via a component-info.xml which other 
components will import as dependencies.

The cvs repo location, module & branch information need to be stored in a 
component's component-info.xml.  This build.xml will be stored along with the 
component's artifacts in the build repository.

This has significant impact on the synchronize lifecycle as the component-info 
for each component will need to be downloaded, and then each component will 
need to be synchronized based on that potentially updated information.

  was:
The cvs repo location, module & branch information need to be stored in a 
component's build.xml.  This build.xml will be stored along with the 
component's artifacts in the build repository.

This has significant impact on the synchronize lifecycle as the component-info 
for each component will need to be downloaded, and then each component will 
need to be synchronized based on that potentially updated information.


Updated to include most recent required funtionality.

> Use component-info to determine source repository information
> -
>
>  Key: JBBUILD-16
>  URL: http://jira.jboss.com/jira/browse/JBBUILD-16
>  Project: JBoss Build System
>     Type: Feature Request
> Reporter: Ryan Campbell
> Assignee: Ryan Campbell
>  Fix For: milestone-3

>
>
> Allow a component to expose its exports via a component-info.xml which other 
> components will import as dependencies.
> The cvs repo location, module & branch information need to be stored in a 
> component's component-info.xml.  This build.xml will be stored along with the 
> component's artifacts in the build repository.
> This has significant impact on the synchronize lifecycle as the 
> component-info for each component will need to be downloaded, and then each 
> component will need to be synchronized based on that potentially updated 
> information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1628) Naming SimpleUnitTestCase failures

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBAS-1628?page=history ]

Ryan Campbell reassigned JBAS-1628:
---

Assign To: Scott M Stark

> Naming SimpleUnitTestCase failures
> --
>
>  Key: JBAS-1628
>  URL: http://jira.jboss.com/jira/browse/JBAS-1628
>  Project: JBoss Application Server
> Type: Bug
>   Components: Naming
> Versions:  JBossAS-4.0.2RC1
>  Environment: qa lab
> Reporter: Ryan Campbell
> Assignee: Scott M Stark

>
>
> testHaPartitionName and testDiscoveryPort are both failing due to a 
> SocketTimeoutException:
> http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite/20050323024613/results/org/jboss/test/naming/test/SimpleUnitTestCase.html
> org.jboss.test.naming.test.SimpleUnitTestCase.testHaPartitionName is failing:
> testHaParitionName: 
> avax.naming.CommunicationException: Receive timed out [Root exception is 
> java.net.SocketTimeoutException: Receive timed out]
>   at 
> org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302)
>   at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1382)
>   at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
> ...
> at 
> org.jboss.test.naming.test.SimpleUnitTestCase.testHaParitionName(SimpleUnitTestCase.java:224)
> testDiscoveryPort is failing at the same point:
> ...
> at 
> org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:265)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1666) Unit Test Failure: testSRPLoginWithAuxChallenge

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBAS-1666?page=history ]

Ryan Campbell reassigned JBAS-1666:
---

Assign To: Scott M Stark

> Unit Test Failure: testSRPLoginWithAuxChallenge
> ---
>
>  Key: JBAS-1666
>  URL: http://jira.jboss.com/jira/browse/JBAS-1666
>  Project: JBoss Application Server
> Type: Bug
>   Components: Security
>  Environment: win xp, linux
> Reporter: Pushkala Iyer
> Assignee: Scott M Stark

>
>
> We are seeing this test fail in multiple environments. As this is required 
> for the 4.0.2 Final release, can you please take a look at it? Thanks,
> Test Case: org.jboss.test.security.test.SRPLoginModuleUnitTestCase
> Test : testSRPLoginWithAuxChallenge
>  
> StackTrace:
> Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt 
> aux challenge
> junit.framework.AssertionFailedError: Unable to complete login: Failed to 
> complete SRP login, msg=Failed to encrypt aux challenge
>   at 
> org.jboss.test.security.test.SRPLoginModuleUnitTestCase.testSRPLoginWithAuxChallenge(SRPLoginModuleUnitTestCase.java:128)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>   at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>   at junit.extensions.TestSetup.run(TestSetup.java:23)
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1668) Unit test failure: testJBossEditors (PropertyEditorsUnitTestCase)

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBAS-1668?page=history ]

Ryan Campbell reassigned JBAS-1668:
---

Assign To: Scott M Stark

> Unit test failure: testJBossEditors (PropertyEditorsUnitTestCase)
> -
>
>  Key: JBAS-1668
>  URL: http://jira.jboss.com/jira/browse/JBAS-1668
>  Project: JBoss Application Server
> Type: Bug
>  Environment: win xp, linux
> Reporter: Pushkala Iyer
> Assignee: Scott M Stark

>
>
> We're seeing this test fail in multiple environments, can you please take a 
> look at it.  This is for the 4.0.2 Final release.
> The testJBossEditors test of the 
> org.jboss.test.util.test.PropertyEditorsUnitTestCase
> fails due to an assertion failure.
> StackTrace:
> junit.framework.AssertionFailedError: Transform of Tue Jan  4 23:38:21 PST 
> 2005 equals Tue Jan 04 23:38:21 CST 2005, output=Wed Jan 05 01:38:21 CST 2005
>   at 
> org.jboss.test.util.test.PropertyEditorsUnitTestCase.doTests(PropertyEditorsUnitTestCase.java:226)
>   at 
> org.jboss.test.util.test.PropertyEditorsUnitTestCase.testJBossEditors(PropertyEditorsUnitTestCase.java:200)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at sun.reflect.DelegatingMethodAccessorImpl

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Resolved: (HIBERNATE-13) testEjbInterception Unit Test failure

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ]
 
Ryan Campbell resolved HIBERNATE-13:


Resolution: Done

Well, it works now. Thanks, Steve.

> testEjbInterception Unit Test failure
> -
>
>  Key: HIBERNATE-13
>  URL: http://jira.jboss.com/jira/browse/HIBERNATE-13
>  Project: Hibernate
> Type: Bug
>  Environment: win xp sp2
> Reporter: Pushkala Iyer
> Assignee: Ryan Campbell

>
>
> The following test is failing in the 4.0 branch and needs to be resolved 
> before the 4.0.2 Final release.  We've tested this in multiple environments 
> and received the same error.
> Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase
> Test : testEjbInterception
> Stack Trace: 
> RemoteException occurred in server thread; nested exception is: 
> java.rmi.ServerException: RuntimeException; nested exception is: 
> org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested 
> throwable: (net.sf.hibernate.HibernateException: Unable to locate 
> SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
> java.rmi.ServerException: RemoteException occurred in server thread; nested 
> exception is: 
>   java.rmi.ServerException: RuntimeException; nested exception is: 
>   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
> nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
> SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
>   at sun.rmi.transport.Transport$1.run(Transport.java:148)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
>   at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
>   at java.lang.Thread.run(Thread.java:534)
>   at 
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>   at 
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
>   at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown 
> Source)
>   at 
> org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
>   at 
> org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
>   at 
> org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
>   at 
> org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
>   at 
> org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
>   at 
> org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
>   at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
>   at $Proxy2.storeUser(Unknown Source)
>   at 
> org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>   at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>   at junit.extensions.TestSetup.run(TestSetup.java:23)
> Caused by: java.rmi.ServerException: RuntimeException; nested exception is: 
>   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
> nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
> SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
>   at 
> org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386)
>   at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
>   at 
> org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
>   at 
> org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
>   at org.jboss.ejb.Container.invoke(Container.java:873)
>   at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at 
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedD

[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1523) JBAS-30 - txtimers created via Servlet init get duplicated

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBAS-1523?page=history ]

Ryan Campbell reassigned JBAS-1523:
---

Assign To: Pushkala Iyer  (was: JBoss QA Lead)

Pushkala, please drop this in your jboss-4.0.0 and run the testsuite.  If it 
creates no additional failures, please resolve the issue.

> JBAS-30 - txtimers created via Servlet init get duplicated
> --
>
>  Key: JBAS-1523
>  URL: http://jira.jboss.com/jira/browse/JBAS-1523
>  Project: JBoss Application Server
> Type: Support Patch
> Versions: JBossAS-4.0.0 Final
> Reporter: Luc Texier
> Assignee: Pushkala Iyer
>  Attachments: jboss_jar-patched.jar
>
>
> Some customers have expressed the wish to get the issue fixed in JBossAS 4.0.0

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-13) testEjbInterception Unit Test failure

[Ryan Campbell (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-13?page=comments#action_12316776 ]
 
Ryan Campbell commented on HIBERNATE-13:


I'm still seeing this after applying Steve's fix from yesterday.

The root exception is:

Caused by: javax.naming.NameNotFoundException: hibernate not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:491)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:499)
at org.jnp.server.NamingServer.getObject(NamingServer.java:505)
at org.jnp.server.NamingServer.lookup(NamingServer.java:249)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at 
org.jboss.hibernate.session.HibernateContext.locateSessionFactory(HibernateContext.java:241)

Looking  at hibernate/src/etc/hibernate-service.xml it looks as though the 
session factory name may have changed from java:/hibernate/SessionFactory to 
java:/hibernate/HibernateFactory?  Of course, the error is with hibernate not 
being bound, but I'm just wondering if the test is broken due to a config 
change w/ hibernate?



> testEjbInterception Unit Test failure
> -
>
>  Key: HIBERNATE-13
>  URL: http://jira.jboss.com/jira/browse/HIBERNATE-13
>  Project: Hibernate
> Type: Bug
>  Environment: win xp sp2
> Reporter: Pushkala Iyer
> Assignee: Steve Ebersole

>
>
> The following test is failing in the 4.0 branch and needs to be resolved 
> before the 4.0.2 Final release.  We've tested this in multiple environments 
> and received the same error.
> Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase
> Test : testEjbInterception
> Stack Trace: 
> RemoteException occurred in server thread; nested exception is: 
> java.rmi.ServerException: RuntimeException; nested exception is: 
> org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested 
> throwable: (net.sf.hibernate.HibernateException: Unable to locate 
> SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
> java.rmi.ServerException: RemoteException occurred in server thread; nested 
> exception is: 
>   java.rmi.ServerException: RuntimeException; nested exception is: 
>   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
> nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
> SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
>   at sun.rmi.transport.Transport$1.run(Transport.java:148)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
>   at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
>   at java.lang.Thread.run(Thread.java:534)
>   at 
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>   at 
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
>   at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown 
> Source)
>   at 
> org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
>   at 
> org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
>   at 
> org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
>   at 
> org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
>   at 
> org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
>   at 
> org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
>   at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
>   at $Proxy2.storeUser(Unknown Source)
>   at 
> org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>   at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>   at junit.extensions.TestSetup.run(TestS

[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-13) testEjbInterception Unit Test failure

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ]

Ryan Campbell reassigned HIBERNATE-13:
--

Assign To: Steve Ebersole  (was: Gavin King)

> testEjbInterception Unit Test failure
> -
>
>  Key: HIBERNATE-13
>  URL: http://jira.jboss.com/jira/browse/HIBERNATE-13
>  Project: Hibernate
> Type: Bug
>  Environment: win xp sp2
> Reporter: Pushkala Iyer
> Assignee: Steve Ebersole

>
>
> The following test is failing in the 4.0 branch and needs to be resolved 
> before the 4.0.2 Final release.  We've tested this in multiple environments 
> and received the same error.
> Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase
> Test : testEjbInterception
> Stack Trace: 
> RemoteException occurred in server thread; nested exception is: 
> java.rmi.ServerException: RuntimeException; nested exception is: 
> org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested 
> throwable: (net.sf.hibernate.HibernateException: Unable to locate 
> SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
> java.rmi.ServerException: RemoteException occurred in server thread; nested 
> exception is: 
>   java.rmi.ServerException: RuntimeException; nested exception is: 
>   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
> nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
> SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
>   at sun.rmi.transport.Transport$1.run(Transport.java:148)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
>   at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
>   at java.lang.Thread.run(Thread.java:534)
>   at 
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>   at 
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
>   at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown 
> Source)
>   at 
> org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
>   at 
> org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
>   at 
> org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
>   at 
> org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
>   at 
> org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
>   at 
> org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
>   at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
>   at $Proxy2.storeUser(Unknown Source)
>   at 
> org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>   at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>   at junit.extensions.TestSetup.run(TestSetup.java:23)
> Caused by: java.rmi.ServerException: RuntimeException; nested exception is: 
>   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
> nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
> SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
>   at 
> org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386)
>   at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
>   at 
> org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
>   at 
> org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
>   at org.jboss.ejb.Container.invoke(Container.java:873)
>   at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at 
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
>   at org.jboss

[JBoss-dev] [JBoss JIRA] Updated: (HIBERNATE-13) testEjbInterception Unit Test failure

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ]

Ryan Campbell updated HIBERNATE-13:
---

Description: 
The following test is failing in the 4.0 branch and needs to be resolved before 
the 4.0.2 Final release.  We've tested this in multiple environments and 
received the same error.

Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase

Test : testEjbInterception

Stack Trace: 

RemoteException occurred in server thread; nested exception is: 
java.rmi.ServerException: RuntimeException; nested exception is: 
org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested 
throwable: (net.sf.hibernate.HibernateException: Unable to locate 
SessionFactory in JNDI under name [java:/hibernate/SessionFactory])

java.rmi.ServerException: RemoteException occurred in server thread; nested 
exception is: 

  java.rmi.ServerException: RuntimeException; nested exception is: 

  org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
SessionFactory in JNDI under name [java:/hibernate/SessionFactory])

  at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
  at sun.rmi.transport.Transport$1.run(Transport.java:148)
  at java.security.AccessController.doPrivileged(Native Method)
  at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
  at 
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
  at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
  at java.lang.Thread.run(Thread.java:534)
  at 
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
  at 
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
  at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
  at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown 
Source)
  at 
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
  at 
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
  at 
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
  at 
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
  at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
  at 
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
  at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
  at $Proxy2.storeUser(Unknown Source)
  at 
org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
  at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
  at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: java.rmi.ServerException: RuntimeException; nested exception is: 
  org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
  at 
org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386)
  at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
  at 
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
  at 
org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
  at org.jboss.ejb.Container.invoke(Container.java:873)
  at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
  at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
  at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
  at 
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:805)
  at 
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406)
  at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
  at sun.rmi.transport.Transport$

[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1284) SOAP SAAJ JBOSS implementation attachments bug

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBAS-1284?page=history ]

Ryan Campbell reassigned JBAS-1284:
---

Assign To: Jason T. Greene  (was: Jason T. Greene)

> SOAP SAAJ JBOSS implementation attachments bug
> --
>
>  Key: JBAS-1284
>  URL: http://jira.jboss.com/jira/browse/JBAS-1284
>  Project: JBoss Application Server
> Type: Feature Request
>   Components: Web Services service
> Versions: JBossAS-4.0.1 Final
>  Environment: Windows-XP SP2
> Reporter: Frank Balba
> Assignee: Jason T. Greene
> Priority: Minor

>
>
> Using JBOSS-SAAJ implementation, no attachments could get through within a 
> SOAP message.
> Creating attachments and adding them to a SOAP message will result a fine 
> SOAP message on the client side however once it arrives to a dedicated 
> servlet the received attachmentpart returns 'null' for 
> attachmentPart.getContentType(). Using another SAAJ package (not the one 
> included with JBOSS 4.0.1) eliminates this problem.
> Frank

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-58) Cleanup of Common Module

[Ryan Campbell (JIRA)]

Cleanup of Common Module


 Key: JBBUILD-58
 URL: http://jira.jboss.com/jira/browse/JBBUILD-58
 Project: JBoss Build System
Type: Task
Reporter: Ryan Campbell
 Assigned to: Ryan Campbell 


>From Scott:

There is a lot of unused utility classes along with obsolete functionality that 
is duplicating the jdk 1.4 behavior that I would like to get cleaned up 
jboss4.0+. Examples of such classes are:

org.jboss.util.Coercible and all of org.jboss.util.coerce
org.jboss.util.DirectoryBuilder
org.jboss.util.MethodHashing
org.jboss.util.Mu*
org.jboss.util.collection.* much of this is now duplicate functionality
org.jboss.net.sockets.RMI* is an unused experiement in multiplexing
org.jboss.net.sockets.Timeout* is now obsolete functionality supported by the 
JDK sockets
org.jboss.util.property.* is mostly unused
org.jboss.util.stream.*
org.jboss.xml.* should be incorported into the org.jboss.xml.* jbossxb 
framework at some point

Before proceeding, modify this description with the precise list of classes to 
remove and get approval from affected developers.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-32) build for deployment

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBBUILD-32?page=history ]

Ryan Campbell updated JBBUILD-32:
-

Description: 
Environment: 
Fix Version: milestone-1
 (was: milestone-2)

Moving to milestone-1 to compensate for cache build being delayed.

> build for deployment
> 
>
>  Key: JBBUILD-32
>  URL: http://jira.jboss.com/jira/browse/JBBUILD-32
>  Project: JBoss Build System
> Type: Sub-task
> Reporter: Ryan Campbell
> Assignee: Ryan Campbell
>  Fix For: milestone-1

>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-27) build for cache

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBBUILD-27?page=history ]

Ryan Campbell updated JBBUILD-27:
-

Description: 
Environment: 
Fix Version: milestone-2
 (was: milestone-1)

delaying until milestone 2 until I know what to do with this module.

> build for cache
> ---
>
>  Key: JBBUILD-27
>  URL: http://jira.jboss.com/jira/browse/JBBUILD-27
>  Project: JBoss Build System
> Type: Sub-task
> Reporter: Ryan Campbell
> Assignee: Ryan Campbell
>  Fix For: milestone-2

>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-3) Add support for pre & post-compilation tasks

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBBUILD-3?page=history ]
 
Ryan Campbell resolved JBBUILD-3:
-

Resolution: Done

rmic, javacc have been implemented.  Additional pre & post processors will be 
implemented as needed, but the concept has been proven.

> Add support for pre &  post-compilation tasks
> -
>
>  Key: JBBUILD-3
>  URL: http://jira.jboss.com/jira/browse/JBBUILD-3
>  Project: JBoss Build System
>     Type: Task
> Reporter: Ryan Campbell
>  Fix For: milestone-1

>
>
> A component should be able to declare source which should be processed before 
> or after compilation like rmic, javacc, or aopc.
> I belive this will work like the junit tests do.  IE, a component declares 
> some source which needs rmic (along with parameters), and tasks.xml declares 
> a targetdef for rmic when it finds input requiring it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-17) execant is broken on windows

[Ryan Campbell (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBBUILD-17?page=history ]
 
Ryan Campbell resolved JBBUILD-17:
--

Resolution: Done

> execant is broken on windows
> 
>
>  Key: JBBUILD-17
>  URL: http://jira.jboss.com/jira/browse/JBBUILD-17
>  Project: JBoss Build System
> Type: Bug
> Reporter: Ryan Campbell
>  Fix For: milestone-1

>
>
> When I tried to execute synchronize, I received an IOException: CreateProcess 
> ant -f jbossbuild.xml synchronize.after error=2
> From what I can tell, error=2 is file not found.  I think this is because of 
> the way execant is implemented using the exec task.
>  executable="ant"
>  >
> 
>  
> For windows it should be:
>  executable="cmd"
>  >
> 
>  
> So to fix this, we just need to do some conditional processing using the os 
> family information like in testsuite/imports/server-config.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development