[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger -Dinstall.id=testbuild release
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 5 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger clean
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 7 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10

2002-10-07 Thread Remy Maucherat

Liam Magee wrote:
 Hi Thomas,
 
 I haven't looked deeply into Tomcat MBean support, this is the next
 natural step for integration b/w JBoss and Tomcat. 

I think it would be beneficial to stop using Embedded eventually 
(whatever JBoss needs to do should be doable using a host configurator 
and similar hooks), so that little or no code duplication is needed.

I'll make changes on the Tomcat side (either in future 4.1.x releases, 
or in Tomcat 5.0.x) and the JBoss/Tomcat build script to allow 
customizing the classloader and directory structure if people are 
interested in getting an integration with a neater packaging ala 
Jetty/JBoss (many components and libraries are also not useful to JBoss 
and could be removed, thus making the download archive much smaller).

Remy



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger -Dinstall.id=testbuild release
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 6 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10

2002-10-07 Thread Nick Betteridge

This would be excellent if you could do this

Nick

Remy Maucherat wrote:
 
 Liam Magee wrote:
  Hi Thomas,
 
  I haven't looked deeply into Tomcat MBean support, this is the next
  natural step for integration b/w JBoss and Tomcat.
 
 I think it would be beneficial to stop using Embedded eventually
 (whatever JBoss needs to do should be doable using a host configurator
 and similar hooks), so that little or no code duplication is needed.
 
 I'll make changes on the Tomcat side (either in future 4.1.x releases,
 or in Tomcat 5.0.x) and the JBoss/Tomcat build script to allow
 customizing the classloader and directory structure if people are
 interested in getting an integration with a neater packaging ala
 Jetty/JBoss (many components and libraries are also not useful to JBoss
 and could be removed, thus making the download archive much smaller).
 
 Remy
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger clean
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 7 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger -Dinstall.id=testbuild release
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 5 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger clean
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 7 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger -Dinstall.id=testbuild release
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 6 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger clean
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 7 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-614116 ] Oracle XA pooling/repeated rollback

2002-10-07 Thread noreply

Bugs item #614116, was opened at 2002-09-24 17:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=614116group_id=22866

Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Oracle XA pooling/repeated rollback

Initial Comment:

I've been trying to isolate some problems I've been
having with transaction roll-backs and message-driven
beans. Basically, when a transaction is rolled-back
a number of times in the onMessage() body
(by calling MessageDrivenContext.setRollbackOnly()
5-10 times in succession),
the message is re-delivered to the MDB, but the Oracle
Connection is no longer in a good state.

This problem manifests itself when using a very small
connection pool (say 1-5) connections.

Example code snippet:

public void onMessage(javax.jms.Message jmsMessage)
{
 Connection c = null;
try {
 TextMessage tm = (TextMessage)jmsMessage;
 String text = tm.getText();
 c = ds.getConnection();
 PreparedStatement s = c.prepareStatement(insert into test values (?));
 s.setString(1, text);
 s.executeUpdate();
 mdc.setRollbackOnly();
} catch (Exception e) {
 throw new EJBException(e);
} finally {
 if (c != null) {
 try { c.close(); }
 catch (Exception e) {
   e.printStackTrace();
 }
}


First I see it works for a few times. It rolls-back successfully
about 5 or 6 times. Then, for no reason, I see:

15:50:44,922 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//4, 
BranchQual=] errorCode=XAER_RMERR
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.allowGlobalTxnModeOnly(OracleXAResource.java:1069)
 at oracle.jdbc.xa.OracleXAResource.suspendStacked(OracleXAResource.java:296)
 at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:381)
 at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1237)
 at org.jboss.tm.TxCapsule.delistResource(TxCapsule.java:579)
 at org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:92)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.delist(XATxConnectionManager.java:284)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.connectionClosed(XATxConnectionManager.java:331)
 at 
org.jboss.resource.adapter.jdbc.BaseManagedConnection.fireConnectionEvent(BaseManagedConnection.java:152)
 at 
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.fireConnectionEvent(XAManagedConnection.java:215)
 at 
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection$1.connectionClosed(XAManagedConnection.java:127)
 at 
oracle.jdbc.pool.OraclePooledConnection.callListener(OraclePooledConnection.java:482)
 at 
oracle.jdbc.pool.OraclePooledConnection.logicalClose(OraclePooledConnection.java:445)
 at oracle.jdbc.driver.OracleConnection.logicalClose(OracleConnection.java:2900)
 at oracle.jdbc.driver.OracleConnection.close(OracleConnection.java:1418)
 at com.proteusmobile.smx.AMDB.onMessage(AMDB.java:140)

Later:

15:50:44,929 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//4, 
BranchQual=] errorCode=XAER_RMERR
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.allowGlobalTxnModeOnly(OracleXAResource.java:1069)
 at oracle.jdbc.xa.OracleXAResource.suspendStacked(OracleXAResource.java:296)
 at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:381)
 at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1237)
 at org.jboss.tm.TxCapsule.endResources(TxCapsule.java:1312)
 at org.jboss.tm.TxCapsule.rollback(TxCapsule.java:440)
 at org.jboss.tm.TransactionImpl.rollback(TransactionImpl.java:83)
 at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:301)
 at 
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:603)
 at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:417)
 at org.jboss.mq.SpySession.run(SpySession.java:259)
 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:655)
 at java.lang.Thread.run(Thread.java:479)

And then, I can no longer get a connection:

15:50:44,971 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//5, 
BranchQual=] errorCode=XAER_PROTO
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.disallowLocalTxnMode(OracleXAResource.java:1045)
 at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:153)
 at org.jboss.tm.TxCapsule.startResource(TxCapsule.java:1180)
 at org.jboss.tm.TxCapsule.enlistResource(TxCapsule.java:679)
 at org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:102)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.enlist(XATxConnectionManager.java:262)
 at 

RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread marc fleury

WTF?

marc f

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]] On 
 Behalf Of [EMAIL PROTECTED]
 Sent: Monday, October 07, 2002 8:15 AM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
 
 
 
 =
 ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR 
 DETAILS= 
 =
 
 JAVA VERSION DETAILS
 java version 1.4.0_01
 Java(TM) 2 Runtime Environment, Standard Edition (build 
 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, 
 mixed mode)
 
 =
 
 HERE ARE THE LAST 50 LINES OF THE LOG FILE
 
 build.sh: build.sh: No such file or directory
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf 
 ___
 Jboss-development mailing list [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread Sacha Labourey

It is a new undocummented feature. Cool, huh?

 -Message d'origine-
 De : [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]De la part de marc
 fleury
 Envoye : lundi, 7 octobre 2002 14:51
 A : [EMAIL PROTECTED]
 Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
 
 
 WTF?
 
 marc f
 
  -Original Message-
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]] On 
  Behalf Of [EMAIL PROTECTED]
  Sent: Monday, October 07, 2002 8:15 AM
  To: [EMAIL PROTECTED]
  Cc: [EMAIL PROTECTED]
  Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
  
  
  
  =
  ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR 
  DETAILS= 
  =
  
  JAVA VERSION DETAILS
  java version 1.4.0_01
  Java(TM) 2 Runtime Environment, Standard Edition (build 
  1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, 
  mixed mode)
  
  =
  
  HERE ARE THE LAST 50 LINES OF THE LOG FILE
  
  build.sh: build.sh: No such file or directory
  
  
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf 
  ___
  Jboss-development mailing list [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread Lennart Petersson

It's the ultimate solution of the build mess  - simplify you know :)

/Lennart

måndagen den 7 oktober 2002 kl 14.55 skrev Sacha Labourey:

 It is a new undocummented feature. Cool, huh?

 -Message d'origine-
 De : [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]De la part de 
 marc
 fleury
 Envoye : lundi, 7 octobre 2002 14:51
 A : [EMAIL PROTECTED]
 Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed


 WTF?

 marc f

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]] On
 Behalf Of [EMAIL PROTECTED]
 Sent: Monday, October 07, 2002 8:15 AM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed



 =
 ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR
 DETAILS=
 =

 JAVA VERSION DETAILS
 java version 1.4.0_01
 Java(TM) 2 Runtime Environment, Standard Edition (build
 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03,
 mixed mode)

 =

 HERE ARE THE LAST 50 LINES OF THE LOG FILE

 build.sh: build.sh: No such file or directory


 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list 
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development




 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread Peter Fagerlund

 =

 HERE ARE THE LAST 50 LINES OF THE LOG FILE

 build.sh: build.sh: No such file or directory

When doing a clean co jboss-all the folder dloaded comes as jboss and 
not as jboss-all as expected. This probably freaks out some script at 
lubega ?

/peter_f



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10

2002-10-07 Thread Liam Magee

I would be happy to assist with any future integration efforts with
Tomcat. Is there a to-do list of any kind for this?

Regards,

Liam.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Remy
Maucherat
Sent: Monday, October 07, 2002 6:19 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10


Liam Magee wrote:
 Hi Thomas,
 
 I haven't looked deeply into Tomcat MBean support, this is the next 
 natural step for integration b/w JBoss and Tomcat.

I think it would be beneficial to stop using Embedded eventually 
(whatever JBoss needs to do should be doable using a host configurator 
and similar hooks), so that little or no code duplication is needed.

I'll make changes on the Tomcat side (either in future 4.1.x releases, 
or in Tomcat 5.0.x) and the JBoss/Tomcat build script to allow 
customizing the classloader and directory structure if people are 
interested in getting an integration with a neater packaging ala 
Jetty/JBoss (many components and libraries are also not useful to JBoss 
and could be removed, thus making the download archive much smaller).

Remy



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf ___
Jboss-development mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] HEAD Build: numerous failure

2002-10-07 Thread Sacha Labourey

Hello,

Is it just me? I am trying to compile jboss-all from HEAD (I did a fresh
checkout a few minutes ago) on windows 2000 and I get lots of errors which
change over time i.e the compiler (1.4.0) makes an exception and, if I start
again the build process, it goes further, ... then it is an RMI compiler
errror (couldn't read LOC header), then it is a set of silent break, etc. At
the end (after 4-5 restart, it is build successfuly)

Cheers,


Sacha



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] HEAD and STARTED JMX notification

2002-10-07 Thread Sacha Labourey

Hello,

In ProxyFactoryHA (which extends ProxyFactory), I subscribe to the STARTED
(and STOPPING) JMX notifications that is raised by the related EJB
container. Nevertheless, while everything is fine in Branch_3_2, it fails on
HEAD: I received the STARTED notification *before* my ProxyFactoryHA.start()
is called. Is someone working on this (David?)

Cheers,


Sacha



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-614116 ] Oracle XA pooling/repeated rollback

2002-10-07 Thread noreply

Bugs item #614116, was opened at 2002-09-24 19:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=614116group_id=22866

Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Oracle XA pooling/repeated rollback

Initial Comment:

I've been trying to isolate some problems I've been
having with transaction roll-backs and message-driven
beans. Basically, when a transaction is rolled-back
a number of times in the onMessage() body
(by calling MessageDrivenContext.setRollbackOnly()
5-10 times in succession),
the message is re-delivered to the MDB, but the Oracle
Connection is no longer in a good state.

This problem manifests itself when using a very small
connection pool (say 1-5) connections.

Example code snippet:

public void onMessage(javax.jms.Message jmsMessage)
{
 Connection c = null;
try {
 TextMessage tm = (TextMessage)jmsMessage;
 String text = tm.getText();
 c = ds.getConnection();
 PreparedStatement s = c.prepareStatement(insert into test values (?));
 s.setString(1, text);
 s.executeUpdate();
 mdc.setRollbackOnly();
} catch (Exception e) {
 throw new EJBException(e);
} finally {
 if (c != null) {
 try { c.close(); }
 catch (Exception e) {
   e.printStackTrace();
 }
}


First I see it works for a few times. It rolls-back successfully
about 5 or 6 times. Then, for no reason, I see:

15:50:44,922 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//4, 
BranchQual=] errorCode=XAER_RMERR
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.allowGlobalTxnModeOnly(OracleXAResource.java:1069)
 at oracle.jdbc.xa.OracleXAResource.suspendStacked(OracleXAResource.java:296)
 at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:381)
 at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1237)
 at org.jboss.tm.TxCapsule.delistResource(TxCapsule.java:579)
 at org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:92)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.delist(XATxConnectionManager.java:284)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.connectionClosed(XATxConnectionManager.java:331)
 at 
org.jboss.resource.adapter.jdbc.BaseManagedConnection.fireConnectionEvent(BaseManagedConnection.java:152)
 at 
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.fireConnectionEvent(XAManagedConnection.java:215)
 at 
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection$1.connectionClosed(XAManagedConnection.java:127)
 at 
oracle.jdbc.pool.OraclePooledConnection.callListener(OraclePooledConnection.java:482)
 at 
oracle.jdbc.pool.OraclePooledConnection.logicalClose(OraclePooledConnection.java:445)
 at oracle.jdbc.driver.OracleConnection.logicalClose(OracleConnection.java:2900)
 at oracle.jdbc.driver.OracleConnection.close(OracleConnection.java:1418)
 at com.proteusmobile.smx.AMDB.onMessage(AMDB.java:140)

Later:

15:50:44,929 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//4, 
BranchQual=] errorCode=XAER_RMERR
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.allowGlobalTxnModeOnly(OracleXAResource.java:1069)
 at oracle.jdbc.xa.OracleXAResource.suspendStacked(OracleXAResource.java:296)
 at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:381)
 at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1237)
 at org.jboss.tm.TxCapsule.endResources(TxCapsule.java:1312)
 at org.jboss.tm.TxCapsule.rollback(TxCapsule.java:440)
 at org.jboss.tm.TransactionImpl.rollback(TransactionImpl.java:83)
 at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:301)
 at 
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:603)
 at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:417)
 at org.jboss.mq.SpySession.run(SpySession.java:259)
 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:655)
 at java.lang.Thread.run(Thread.java:479)

And then, I can no longer get a connection:

15:50:44,971 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//5, 
BranchQual=] errorCode=XAER_PROTO
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.disallowLocalTxnMode(OracleXAResource.java:1045)
 at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:153)
 at org.jboss.tm.TxCapsule.startResource(TxCapsule.java:1180)
 at org.jboss.tm.TxCapsule.enlistResource(TxCapsule.java:679)
 at org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:102)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.enlist(XATxConnectionManager.java:262)
 at 

[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread marc fleury

he he he, 

actual LOL

we don't have a build problem anymore, that fucking piece of radioactive
dunk just went boom...

marc f

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]] On 
 Behalf Of Lennart Petersson
 Sent: Monday, October 07, 2002 9:15 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
 
 
 It's the ultimate solution of the build mess  - simplify you know :)
 
 /Lennart
 
 måndagen den 7 oktober 2002 kl 14.55 skrev Sacha Labourey:
 
  It is a new undocummented feature. Cool, huh?
 
  -Message d'origine-
  De : [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]De la part de
  marc
  fleury
  Envoye : lundi, 7 octobre 2002 14:51
  A : [EMAIL PROTECTED]
  Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
 
 
  WTF?
 
  marc f
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]] On 
 Behalf Of 
  [EMAIL PROTECTED]
  Sent: Monday, October 07, 2002 8:15 AM
  To: [EMAIL PROTECTED]
  Cc: [EMAIL PROTECTED]
  Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
 
 
 
  
 
  =
  ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR
  DETAILS=
  
 =
 
  JAVA VERSION DETAILS
  java version 1.4.0_01
  Java(TM) 2 Runtime Environment, Standard Edition (build
  1.4.0_01-b03) Java HotSpot(TM) Client VM (build 
 1.4.0_01-b03, mixed 
  mode)
 
  
 
  =
 
  HERE ARE THE LAST 50 LINES OF THE LOG FILE
 
  build.sh: build.sh: No such file or directory
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf 
  ___
  Jboss-development mailing list 
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf 
  ___
  Jboss-development mailing list 
 [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread marc fleury

But seriously now, can anyone get Chris on the line, he needs to clean
the disk and checkout... this is embarassing

marc f

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]] On 
 Behalf Of Lennart Petersson
 Sent: Monday, October 07, 2002 9:15 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
 
 
 It's the ultimate solution of the build mess  - simplify you know :)
 
 /Lennart
 
 måndagen den 7 oktober 2002 kl 14.55 skrev Sacha Labourey:
 
  It is a new undocummented feature. Cool, huh?
 
  -Message d'origine-
  De : [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]De la part de
  marc
  fleury
  Envoye : lundi, 7 octobre 2002 14:51
  A : [EMAIL PROTECTED]
  Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
 
 
  WTF?
 
  marc f
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]] On 
 Behalf Of 
  [EMAIL PROTECTED]
  Sent: Monday, October 07, 2002 8:15 AM
  To: [EMAIL PROTECTED]
  Cc: [EMAIL PROTECTED]
  Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
 
 
 
  
 
  =
  ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR
  DETAILS=
  
 =
 
  JAVA VERSION DETAILS
  java version 1.4.0_01
  Java(TM) 2 Runtime Environment, Standard Edition (build
  1.4.0_01-b03) Java HotSpot(TM) Client VM (build 
 1.4.0_01-b03, mixed 
  mode)
 
  
 
  =
 
  HERE ARE THE LAST 50 LINES OF THE LOG FILE
 
  build.sh: build.sh: No such file or directory
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf 
  ___
  Jboss-development mailing list 
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf 
  ___
  Jboss-development mailing list 
 [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Somebody forgot to check in sun-jaxp directories into branch_3_0

2002-10-07 Thread Bill Burke

BUILD FAILED:

Common module


...thirdparty\sun-jaxp\lib not found.


Bill


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Re: [jboss-cvs] contrib/jboss.net build.xml

2002-10-07 Thread Scott M Stark

Whoa, not this nonsense off. The 3.0 build structure is NOT changing. If
it has its going back!!!


Scott Stark
Chief Technology Officer
JBoss Group, LLC


- Original Message - 
From: Sacha Labourey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, October 07, 2002 10:14 AM
Subject: [jboss-cvs] contrib/jboss.net build.xml


   User: slaboure
   Date: 02/10/07 10:14:46
 
   Modified:jboss.net Tag: Branch_3_0 build.xml
   Log:
   Jason, thirdparty structure has been flattened, right? Then we need to flatten 
definitions in build.xml files aswell
   
   Revision  ChangesPath
   No   revision
   
   
   No   revision
   
   
   1.18.2.1  +8 -8  contrib/jboss.net/build.xml
   
   Index: build.xml
   ===
   RCS file: /cvsroot/jboss/contrib/jboss.net/build.xml,v
   retrieving revision 1.18
   retrieving revision 1.18.2.1
   diff -u -r1.18 -r1.18.2.1
   --- build.xml 23 Mar 2002 21:11:00 - 1.18
   +++ build.xml 7 Oct 2002 17:14:46 - 1.18.2.1
   @@ -12,7 +12,7 @@
!----
!-- == --

   -!-- $Id: build.xml,v 1.18 2002/03/23 21:11:00 ejort Exp $ --
   +!-- $Id: build.xml,v 1.18.2.1 2002/10/07 17:14:46 slaboure Exp $ --

project default=main name=JBoss/JBoss.Net

   @@ -70,7 +70,7 @@
!-- = --

!-- Java API for XML Processing (JAXP) --
   -property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   +property name=sun.jaxp.root value=${project.thirdparty}/sun-jaxp/
property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
path id=sun.jaxp.classpath
  fileset dir=${sun.jaxp.lib}
   @@ -79,7 +79,7 @@
/path

!-- Java Authentication and Authorization API  --
   -property name=sun.jaas.root value=${project.thirdparty}/sun/jaas/
   +property name=sun.jaas.root value=${project.thirdparty}/sun-jaas/
property name=sun.jaas.lib value=${sun.jaas.root}/lib/
path id=sun.jaas.classpath
  fileset dir=${sun.jaas.lib}
   @@ -88,30 +88,30 @@
/path

!-- Servlets --
   -property name=sun.servlet.root value=${project.thirdparty}/sun/servlet/
   +property name=sun.servlet.root value=${project.thirdparty}/sun-servlet/
property name=sun.servlet.lib value=${sun.servlet.root}/lib/
path id=sun.servlet.classpath
  pathelement path=${sun.servlet.lib}/servlet.jar/
/path

!-- Log4j --
   -property name=apache.log4j.root 
value=${project.thirdparty}/apache/log4j/
   +property name=apache.log4j.root 
value=${project.thirdparty}/apache-log4j/
property name=apache.log4j.lib value=${apache.log4j.root}/lib/
path id=apache.log4j.classpath
  pathelement path=${apache.log4j.lib}/log4j.jar/
/path

!-- JUnit --
   -property name=junit.junit.root value=${project.thirdparty}/junit/junit/
   +property name=junit.junit.root value=${project.thirdparty}/junit-junit/
property name=junit.junit.lib value=${junit.junit.root}/lib/
path id=junit.junit.classpath
  pathelement path=${junit.junit.lib}/junit.jar/
/path

!-- Axis --
   -property name=apache.axis.root value=${project.thirdparty}/apache/axis/
   +property name=apache.axis.root value=${project.thirdparty}/apache-axis/
property name=apache.axis.lib value=${apache.axis.root}/lib/
   -property name=ibm.wsdl4j.root value=${project.thirdparty}/ibm/wsdl4j/
   +property name=ibm.wsdl4j.root value=${project.thirdparty}/ibm-wsdl4j/
property name=ibm.wsdl4j.lib value=${ibm.wsdl4j.root}/lib/
path id=apache.axis.classpath
  fileset dir=${apache.axis.lib}
   
   
   
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 jboss-cvs-commits mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-cvs-commits
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] README :: Thirdparty structure changed

2002-10-07 Thread Scott M Stark

This has broken the existing 3.0 and 3.2 build structures. Fix these changes
immediately as we are not going through the production branch build
files to accommodate this change.

I also changed the jboss-all alias to checkout its content into the jboss-all
directory as this had been changed to jboss.


Scott Stark
Chief Technology Officer
JBoss Group, LLC


- Original Message - 
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 06, 2002 8:05 PM
Subject: [JBoss-dev] README :: Thirdparty structure changed


 Hi... me again ;)
 
 I finally got around to fixing, or rather getting around an unfortunate 
 side-effect of the CVS 'update' command.  The previous behavior would cause 
 local clients to download the entire thirdparty/* module (which is time and 
 space consuming).
 
 CVS is not desgined to handle nested structures very well, so I modified the 
 _project_thirdparty cvs modules to flatten the directory structure.
 
 I also had to update the libraries.ent file to use the new root directories 
 for each library.
 
 So, what this means to you is that you need to do the following:
 
  1) Re-checkout the project you are working with OR:
 
a) Remove the thirdparty sub-directory
 
b) Check out the _project_thirdparty module.  So for the 'jboss-all' 
   project, you would checkout _jboss-all_thirdparty
 
  2) Ensure that your 'tools' module is up to date.
 
 That's it.
 
 Unix users working on jboss-all (HEAD) you can execute the following from 
 the jboss-all project directory:
 
   rm -rf thirdparty
   cvs get _jboss-all_thirdparty
   cvs update tools
 
 Let me know if you have any questions, comments or problems.
 
 Please no flames *whimper*...
 
 --jason



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Over zealous deployers

2002-10-07 Thread David Jencks

The last time I looked at the .ear deployer I thought it was only deploying
modules explictly referenced in application.xml and jboss-app.xml, and
packages from manifest classpaths.  Anything else is a mistake.  Lots of
people have messed with this code and it keeps breaking.  I suggest if you
want to put your $0.02 in the most valuable place to start would be with
some unit tests so we can find out when someone breaks it again.

Fixing it once is easy.  Noticing when it is broken again is not.

The other deployers usually deploy everything in sight, which is usually
correct behavior.

thanks
david jencks

On 2002.10.06 05:43:15 -0400 Matt Goodall wrote:
 See below ...
 
 On Sun, 2002-10-06 at 03:14, Jason Dillon wrote:
  Hrm... so what is it there for I wonder?  If you remove it does
 deployment 
  still function?
 
 When I realised what isDeployable() was for I changed it to
 unconditionally return false to see what the effect would be. On
 startup, deployment of some of the .rar and .sar files failed. I think
 they are fixed by adding the dependent JARs that were automatically
 deployed to the manifest classpath.
 
 EAR files would not deploy since modules are only deployed when the
 modules file has passed the isDeployable() test. It *does* work when the
 EAR file is unpacked as a directory though.
 
  
  --jason
  
  
  On 5 Oct 2002, Larry Sanderson wrote:
  
   No.  I noticed this deplyment behaviour when I was working on the
   deployable directories, and I wanted to remove it then.
   
   As I recall, nobody else really thought it was a problem, and it was
   left in primarily to deply jar files nested within a sar archive. 
   (Please, correct me if I am wrong here - it was a long time ago)
 
 As mentioned above. I think the SARs can be fixed by correcting the
 manifest classpath.
 
   
   However, I did modify the ear deployer to only deploy those archives
   mentioned in application.xml.  Unless this has been modified since,
 ear
   files are not searched for deployable entities (although jar, sar,
 rar,
   ... archives are).
 
 Hmm ok, I'll take a look at a newer version as I've only really played
 with 3.0.2 so far. Do you remember what release your change first
 appeared in?
 
 I hope to have a better look this evening. I'll report back with more
 detailed findings then hopefully.
 
 Thanks for the info so far.
 
 Cheers, Matt
 
   
   -Larry
   
   On Sat, 2002-10-05 at 18:05, Jason Dillon wrote:
I am not positive, but I think this might be part of the deployable
 
directories support.

--jason


On 6 Oct 2002, Matt Goodall wrote:

 Hi,
 
 I'm new (about 1.5 hours altogether) to the JBoss source code so
 forgive
 me, and correct me, if I've got some of this wrong ...
 
 When I deploy an EAR the deployer deploys that EAR and *all*
 files
 contained inside if they are one of the types listed in
 SubDeployerSupport.isDeployable(). It actually calls
 isDeployable() for
 *every* file in the EAR including files like META-INF/MANIFEST.MF
 and
 META-INF/application.xml! I've also seen isDeployable() get
 called for
 every .class in a JAR.
 
 I found this problem on 3.0.2 but it still seems to be there in
 the
 latest CVS code. I'm pretty sure this is bug #589808; it's also
 been
 discussed in the web forums.
 
 I'm not sure why the deployer(s) work like this. Can someone
 explain it?
 Is there a good reason for it that I have not seen yet?
 
 (Another related issue is that EARDeployer behaves differently
 depending
 on whether the EAR is an archive or an unpacked directory.)
 
 My understanding is that only modules, i.e. the EAR and the
 modules
 listed in application.xml in this case, should be deployed and
 only
 dependent JARs listed in the manifest classpath should be loaded
 at all.
 
 I would like to fix this as it's stopping me moving up to 3.x. I
 think
 the following is necessary:
 
 1. Look at the other deployers to see what they're doing.
 2. Remove isDeployable() and any uses of it.
 3. Fix any of the standard SAR/RAR/etc that haven't got a correct
 manifest classpath.
 4. Fix the EARDeployer to deploy just the application.xml
 modules.
 
 I suspect that this change will improve deployment and startup
 time
 slightly (no directory scans and string comparisons) but, more
 importantly, it will make JBoss behave correctly.
 
 One of the big problems with fixing this is that it will break
 applications in 3.x that have not been packaged correctly. For
 that
 reason, it may be best to introduce the fix based on some
 configuration
 property and leave the current behaviour as default.
 
 Any comments before I start on this would be most welcome.
 
 Cheers, Matt
 
 



---
This sf.net email is 

Re: [JBoss-dev] Over zealous deployers

2002-10-07 Thread David Jencks

There's a sorter in MainDeployer.

I strongly recommend using depends elements.

david jencks

On 2002.10.05 22:33:15 -0400 Jason Dillon wrote:
 Again, I am not positive, but I believe the order is determined by the
 XML 
 impl, when it returns a NodeList.  From what I can tell the order is
 fairly 
 random.
 
 The only way I could get deployments to order correctlt was to use the
 JBoss 
 depends tag (in jboss.xml in each of the members of the EAR) and depend
 on 
 the dependent deployed services in the other JAR files.
 
 --jason
 
 
  Actually, this brings up a question I've meant to ask for a while - how
  do you guys determine the order for which modules are deployed when
  declared in an application.xml file? I had asked a few days ago how to
  control the order of deployment of ears and wars (currently separate in
  the deploy dir). But, without changing my deploy scripts in Ant, I
  wanted to see what the algorithm was (or where the code lives) that
  determines the order. I was thinking that if the war was defined last
 in
  the application.xml, it might get deployed last and thus my cheezy,
  x-appserver SessionContextListener would fire after all EJBs are
  deployed (Mbeans are out, as I don't have good mbean support in the
  jboss foe servers). 
  
  Thanks,
  James
  
  
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] README :: Thirdparty structure changed

2002-10-07 Thread Bill Burke

All and all I think big structural changes and any big code changes, or any
big features should be forbidden from being added to a production branch.
IMHO, they shouldn't be allowed for any branched version as a branch means
we are trying to stabalize.

BTW, you've really hosed me so fix it!

Bill

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Scott
 M Stark
 Sent: Monday, October 07, 2002 2:58 PM
 To: [EMAIL PROTECTED]
 Cc: Jason Dillon
 Subject: Re: [JBoss-dev] README :: Thirdparty structure changed


 This has broken the existing 3.0 and 3.2 build structures. Fix
 these changes
 immediately as we are not going through the production branch build
 files to accommodate this change.

 I also changed the jboss-all alias to checkout its content into
 the jboss-all
 directory as this had been changed to jboss.

 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 

 - Original Message -
 From: Jason Dillon [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, October 06, 2002 8:05 PM
 Subject: [JBoss-dev] README :: Thirdparty structure changed


  Hi... me again ;)
 
  I finally got around to fixing, or rather getting around an unfortunate
  side-effect of the CVS 'update' command.  The previous behavior
 would cause
  local clients to download the entire thirdparty/* module (which
 is time and
  space consuming).
 
  CVS is not desgined to handle nested structures very well, so I
 modified the
  _project_thirdparty cvs modules to flatten the directory structure.
 
  I also had to update the libraries.ent file to use the new root
 directories
  for each library.
 
  So, what this means to you is that you need to do the following:
 
   1) Re-checkout the project you are working with OR:
 
 a) Remove the thirdparty sub-directory
 
 b) Check out the _project_thirdparty module.  So for the
 'jboss-all'
project, you would checkout _jboss-all_thirdparty
 
   2) Ensure that your 'tools' module is up to date.
 
  That's it.
 
  Unix users working on jboss-all (HEAD) you can execute the
 following from
  the jboss-all project directory:
 
rm -rf thirdparty
cvs get _jboss-all_thirdparty
cvs update tools
 
  Let me know if you have any questions, comments or problems.
 
  Please no flames *whimper*...
 
  --jason



 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] README :: Thirdparty structure changed

2002-10-07 Thread David Jencks

This wasn't a code change, it was a change to  how jboss is checked out
from cvs.  I think maybe Jason forgot that there is no branching available
in CVSROOT.

Basically the problem is that cvs sucks.

I think the solution is to have jboss-all-3_0, jboss-all-3_2, and
jboss-all-4_0 targets that check out the appropriate structure for each
release.  We won't change the production targets, newer ones can be subject
to improvement.

david jencks

On 2002.10.07 15:19:40 -0400 Bill Burke wrote:
 All and all I think big structural changes and any big code changes, or
 any
 big features should be forbidden from being added to a production branch.
 IMHO, they shouldn't be allowed for any branched version as a branch
 means
 we are trying to stabalize.
 
 BTW, you've really hosed me so fix it!
 
 Bill
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of
 Scott
  M Stark
  Sent: Monday, October 07, 2002 2:58 PM
  To: [EMAIL PROTECTED]
  Cc: Jason Dillon
  Subject: Re: [JBoss-dev] README :: Thirdparty structure changed
 
 
  This has broken the existing 3.0 and 3.2 build structures. Fix
  these changes
  immediately as we are not going through the production branch build
  files to accommodate this change.
 
  I also changed the jboss-all alias to checkout its content into
  the jboss-all
  directory as this had been changed to jboss.
 
  
  Scott Stark
  Chief Technology Officer
  JBoss Group, LLC
  
 
  - Original Message -
  From: Jason Dillon [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Sunday, October 06, 2002 8:05 PM
  Subject: [JBoss-dev] README :: Thirdparty structure changed
 
 
   Hi... me again ;)
  
   I finally got around to fixing, or rather getting around an
 unfortunate
   side-effect of the CVS 'update' command.  The previous behavior
  would cause
   local clients to download the entire thirdparty/* module (which
  is time and
   space consuming).
  
   CVS is not desgined to handle nested structures very well, so I
  modified the
   _project_thirdparty cvs modules to flatten the directory structure.
  
   I also had to update the libraries.ent file to use the new root
  directories
   for each library.
  
   So, what this means to you is that you need to do the following:
  
1) Re-checkout the project you are working with OR:
  
  a) Remove the thirdparty sub-directory
  
  b) Check out the _project_thirdparty module.  So for the
  'jboss-all'
 project, you would checkout _jboss-all_thirdparty
  
2) Ensure that your 'tools' module is up to date.
  
   That's it.
  
   Unix users working on jboss-all (HEAD) you can execute the
  following from
   the jboss-all project directory:
  
 rm -rf thirdparty
 cvs get _jboss-all_thirdparty
 cvs update tools
  
   Let me know if you have any questions, comments or problems.
  
   Please no flames *whimper*...
  
   --jason
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: build.sh: No such file or directory


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] README :: Thirdparty structure changed

2002-10-07 Thread Bill Burke

the directory structure and module structure is fucking fine!  Why fucking
change it!

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of David
 Jencks
 Sent: Monday, October 07, 2002 4:04 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] README :: Thirdparty structure changed


 This wasn't a code change, it was a change to  how jboss is checked out
 from cvs.  I think maybe Jason forgot that there is no branching available
 in CVSROOT.

 Basically the problem is that cvs sucks.

 I think the solution is to have jboss-all-3_0, jboss-all-3_2, and
 jboss-all-4_0 targets that check out the appropriate structure for each
 release.  We won't change the production targets, newer ones can
 be subject
 to improvement.

 david jencks

 On 2002.10.07 15:19:40 -0400 Bill Burke wrote:
  All and all I think big structural changes and any big code changes, or
  any
  big features should be forbidden from being added to a
 production branch.
  IMHO, they shouldn't be allowed for any branched version as a branch
  means
  we are trying to stabalize.
 
  BTW, you've really hosed me so fix it!
 
  Bill
 
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]On Behalf Of
  Scott
   M Stark
   Sent: Monday, October 07, 2002 2:58 PM
   To: [EMAIL PROTECTED]
   Cc: Jason Dillon
   Subject: Re: [JBoss-dev] README :: Thirdparty structure changed
  
  
   This has broken the existing 3.0 and 3.2 build structures. Fix
   these changes
   immediately as we are not going through the production branch build
   files to accommodate this change.
  
   I also changed the jboss-all alias to checkout its content into
   the jboss-all
   directory as this had been changed to jboss.
  
   
   Scott Stark
   Chief Technology Officer
   JBoss Group, LLC
   
  
   - Original Message -
   From: Jason Dillon [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Sent: Sunday, October 06, 2002 8:05 PM
   Subject: [JBoss-dev] README :: Thirdparty structure changed
  
  
Hi... me again ;)
   
I finally got around to fixing, or rather getting around an
  unfortunate
side-effect of the CVS 'update' command.  The previous behavior
   would cause
local clients to download the entire thirdparty/* module (which
   is time and
space consuming).
   
CVS is not desgined to handle nested structures very well, so I
   modified the
_project_thirdparty cvs modules to flatten the directory
 structure.
   
I also had to update the libraries.ent file to use the new root
   directories
for each library.
   
So, what this means to you is that you need to do the following:
   
 1) Re-checkout the project you are working with OR:
   
   a) Remove the thirdparty sub-directory
   
   b) Check out the _project_thirdparty module.  So for the
   'jboss-all'
  project, you would checkout _jboss-all_thirdparty
   
 2) Ensure that your 'tools' module is up to date.
   
That's it.
   
Unix users working on jboss-all (HEAD) you can execute the
   following from
the jboss-all project directory:
   
  rm -rf thirdparty
  cvs get _jboss-all_thirdparty
  cvs update tools
   
Let me know if you have any questions, comments or problems.
   
Please no flames *whimper*...
   
--jason
  
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread Jason Dillon

The nightly build is not very inteligent...

--jason


On Mon, 7 Oct 2002, Sacha Labourey wrote:

 It is a new undocummented feature. Cool, huh?
 
  -Message d'origine-
  De : [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]De la part de marc
  fleury
  Envoye : lundi, 7 octobre 2002 14:51
  A : [EMAIL PROTECTED]
  Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
  
  
  WTF?
  
  marc f
  
   -Original Message-
   From: [EMAIL PROTECTED] 
   [mailto:[EMAIL PROTECTED]] On 
   Behalf Of [EMAIL PROTECTED]
   Sent: Monday, October 07, 2002 8:15 AM
   To: [EMAIL PROTECTED]
   Cc: [EMAIL PROTECTED]
   Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
   
   
   
   =
   ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR 
   DETAILS= 
   =
   
   JAVA VERSION DETAILS
   java version 1.4.0_01
   Java(TM) 2 Runtime Environment, Standard Edition (build 
   1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, 
   mixed mode)
   
   =
   
   HERE ARE THE LAST 50 LINES OF THE LOG FILE
   
   build.sh: build.sh: No such file or directory
   
   
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf 
   ___
   Jboss-development mailing list [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
   
  
  
  
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Somebody forgot to check in sun-jaxp directoriesinto branch_3_0

2002-10-07 Thread Jason Dillon

I had forgot about the branches wrt to thirdparty flattening... for some 
reason I was convinced that I did not need to change any of the build files 
for these.

I think we need seperate module defs for these, so they can rev 
independently.

--jason


On Mon, 7 Oct 2002, Bill Burke wrote:

 BUILD FAILED:
 
 Common module
 
 
 ...thirdparty\sun-jaxp\lib not found.
 
 
 Bill
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Re: [jboss-cvs] contrib/jboss.net build.xml

2002-10-07 Thread Jason Dillon

I know it is not changing... I was not planning on it changing either.

I beleive we need a jboss-3.0 and a jboss-3.2 module which sets up the 
correct structure, with out limiting the change for head.

--jason


On Mon, 7 Oct 2002, Scott M Stark wrote:

 Whoa, not this nonsense off. The 3.0 build structure is NOT changing. If
 it has its going back!!!
 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 
 - Original Message - 
 From: Sacha Labourey [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, October 07, 2002 10:14 AM
 Subject: [jboss-cvs] contrib/jboss.net build.xml
 
 
User: slaboure
Date: 02/10/07 10:14:46
  
Modified:jboss.net Tag: Branch_3_0 build.xml
Log:
Jason, thirdparty structure has been flattened, right? Then we need to flatten 
definitions in build.xml files aswell

Revision  ChangesPath
No   revision


No   revision


1.18.2.1  +8 -8  contrib/jboss.net/build.xml

Index: build.xml
===
RCS file: /cvsroot/jboss/contrib/jboss.net/build.xml,v
retrieving revision 1.18
retrieving revision 1.18.2.1
diff -u -r1.18 -r1.18.2.1
--- build.xml 23 Mar 2002 21:11:00 - 1.18
+++ build.xml 7 Oct 2002 17:14:46 - 1.18.2.1
@@ -12,7 +12,7 @@
 !----
 !-- == --
 
-!-- $Id: build.xml,v 1.18 2002/03/23 21:11:00 ejort Exp $ --
+!-- $Id: build.xml,v 1.18.2.1 2002/10/07 17:14:46 slaboure Exp $ --
 
 project default=main name=JBoss/JBoss.Net
 
@@ -70,7 +70,7 @@
 !-- = --
 
 !-- Java API for XML Processing (JAXP) --
-property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
+property name=sun.jaxp.root value=${project.thirdparty}/sun-jaxp/
 property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
 path id=sun.jaxp.classpath
   fileset dir=${sun.jaxp.lib}
@@ -79,7 +79,7 @@
 /path
 
 !-- Java Authentication and Authorization API  --
-property name=sun.jaas.root value=${project.thirdparty}/sun/jaas/
+property name=sun.jaas.root value=${project.thirdparty}/sun-jaas/
 property name=sun.jaas.lib value=${sun.jaas.root}/lib/
 path id=sun.jaas.classpath
   fileset dir=${sun.jaas.lib}
@@ -88,30 +88,30 @@
 /path
 
 !-- Servlets --
-property name=sun.servlet.root 
value=${project.thirdparty}/sun/servlet/
+property name=sun.servlet.root 
value=${project.thirdparty}/sun-servlet/
 property name=sun.servlet.lib value=${sun.servlet.root}/lib/
 path id=sun.servlet.classpath
   pathelement path=${sun.servlet.lib}/servlet.jar/
 /path
 
 !-- Log4j --
-property name=apache.log4j.root 
value=${project.thirdparty}/apache/log4j/
+property name=apache.log4j.root 
value=${project.thirdparty}/apache-log4j/
 property name=apache.log4j.lib value=${apache.log4j.root}/lib/
 path id=apache.log4j.classpath
   pathelement path=${apache.log4j.lib}/log4j.jar/
 /path
 
 !-- JUnit --
-property name=junit.junit.root 
value=${project.thirdparty}/junit/junit/
+property name=junit.junit.root 
value=${project.thirdparty}/junit-junit/
 property name=junit.junit.lib value=${junit.junit.root}/lib/
 path id=junit.junit.classpath
   pathelement path=${junit.junit.lib}/junit.jar/
 /path
 
 !-- Axis --
-property name=apache.axis.root 
value=${project.thirdparty}/apache/axis/
+property name=apache.axis.root 
value=${project.thirdparty}/apache-axis/
 property name=apache.axis.lib value=${apache.axis.root}/lib/
-property name=ibm.wsdl4j.root value=${project.thirdparty}/ibm/wsdl4j/
+property name=ibm.wsdl4j.root value=${project.thirdparty}/ibm-wsdl4j/
 property name=ibm.wsdl4j.lib value=${ibm.wsdl4j.root}/lib/
 path id=apache.axis.classpath
   fileset dir=${apache.axis.lib}



  
  
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  jboss-cvs-commits mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-cvs-commits
  
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 jboss-cvs-commits mailing list
 [EMAIL PROTECTED]
 

Re: [JBoss-dev] README :: Thirdparty structure changed

2002-10-07 Thread Jason Dillon

 This has broken the existing 3.0 and 3.2 build structures. Fix these changes
 immediately as we are not going through the production branch build
 files to accommodate this change.

I will do.  Like I said before I did not believe it would affect the 3.x 
builds... but I should have not made that assumption.  My appologies.


 I also changed the jboss-all alias to checkout its content into the jboss-all
 directory as this had been changed to jboss.

Yeah, I was hoping to start tranisition away to the target namespace... but 
it appears that some people are less adaptable than others.

--jason


 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 
 - Original Message - 
 From: Jason Dillon [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, October 06, 2002 8:05 PM
 Subject: [JBoss-dev] README :: Thirdparty structure changed
 
 
  Hi... me again ;)
  
  I finally got around to fixing, or rather getting around an unfortunate 
  side-effect of the CVS 'update' command.  The previous behavior would cause 
  local clients to download the entire thirdparty/* module (which is time and 
  space consuming).
  
  CVS is not desgined to handle nested structures very well, so I modified the 
  _project_thirdparty cvs modules to flatten the directory structure.
  
  I also had to update the libraries.ent file to use the new root directories 
  for each library.
  
  So, what this means to you is that you need to do the following:
  
   1) Re-checkout the project you are working with OR:
  
 a) Remove the thirdparty sub-directory
  
 b) Check out the _project_thirdparty module.  So for the 'jboss-all' 
project, you would checkout _jboss-all_thirdparty
  
   2) Ensure that your 'tools' module is up to date.
  
  That's it.
  
  Unix users working on jboss-all (HEAD) you can execute the following from 
  the jboss-all project directory:
  
rm -rf thirdparty
cvs get _jboss-all_thirdparty
cvs update tools
  
  Let me know if you have any questions, comments or problems.
  
  Please no flames *whimper*...
  
  --jason
 
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] README :: Thirdparty structure changed

2002-10-07 Thread Jason Dillon

If you READ me email you would understand that the module structure has not 
changed, only the thirparty directory has.

People bitch left and right that cvs update downloads stuff which is not 
needed.  All I did was fix the problem.

TRUE I did forget about the production branch... I am human and make 
mistakes.  So chill dude.

--jason


On Mon, 7 Oct 2002, Bill Burke wrote:

 the directory structure and module structure is fucking fine!  Why fucking
 change it!
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of David
  Jencks
  Sent: Monday, October 07, 2002 4:04 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] README :: Thirdparty structure changed
 
 
  This wasn't a code change, it was a change to  how jboss is checked out
  from cvs.  I think maybe Jason forgot that there is no branching available
  in CVSROOT.
 
  Basically the problem is that cvs sucks.
 
  I think the solution is to have jboss-all-3_0, jboss-all-3_2, and
  jboss-all-4_0 targets that check out the appropriate structure for each
  release.  We won't change the production targets, newer ones can
  be subject
  to improvement.
 
  david jencks
 
  On 2002.10.07 15:19:40 -0400 Bill Burke wrote:
   All and all I think big structural changes and any big code changes, or
   any
   big features should be forbidden from being added to a
  production branch.
   IMHO, they shouldn't be allowed for any branched version as a branch
   means
   we are trying to stabalize.
  
   BTW, you've really hosed me so fix it!
  
   Bill
  
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
   Scott
M Stark
Sent: Monday, October 07, 2002 2:58 PM
To: [EMAIL PROTECTED]
Cc: Jason Dillon
Subject: Re: [JBoss-dev] README :: Thirdparty structure changed
   
   
This has broken the existing 3.0 and 3.2 build structures. Fix
these changes
immediately as we are not going through the production branch build
files to accommodate this change.
   
I also changed the jboss-all alias to checkout its content into
the jboss-all
directory as this had been changed to jboss.
   

Scott Stark
Chief Technology Officer
JBoss Group, LLC

   
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 06, 2002 8:05 PM
Subject: [JBoss-dev] README :: Thirdparty structure changed
   
   
 Hi... me again ;)

 I finally got around to fixing, or rather getting around an
   unfortunate
 side-effect of the CVS 'update' command.  The previous behavior
would cause
 local clients to download the entire thirdparty/* module (which
is time and
 space consuming).

 CVS is not desgined to handle nested structures very well, so I
modified the
 _project_thirdparty cvs modules to flatten the directory
  structure.

 I also had to update the libraries.ent file to use the new root
directories
 for each library.

 So, what this means to you is that you need to do the following:

  1) Re-checkout the project you are working with OR:

a) Remove the thirdparty sub-directory

b) Check out the _project_thirdparty module.  So for the
'jboss-all'
   project, you would checkout _jboss-all_thirdparty

  2) Ensure that your 'tools' module is up to date.

 That's it.

 Unix users working on jboss-all (HEAD) you can execute the
following from
 the jboss-all project directory:

   rm -rf thirdparty
   cvs get _jboss-all_thirdparty
   cvs update tools

 Let me know if you have any questions, comments or problems.

 Please no flames *whimper*...

 --jason
   
   
   
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 ---
 This sf.net email is 

Re: [JBoss-dev] README :: Thirdparty structure changed

2002-10-07 Thread David Jencks

CVS can't handle thirdparty only including some of the subdirectories.  On
checkout you get one set of stuff, if you update you get much more.  Jason
was trying to make the set of stuff you get from checkout and update the
same.  I think its really important to ensure this, whether or not Jason's
fix is the best possible.  I think fixing it (at least in head) is more
important than keeping the directory structure the same.  If you have a way
to fix the problem while keeping the structure the same, I think that would
be better.  I don't have such a way.

thanks
david jencks

On 2002.10.07 16:28:09 -0400 Bill Burke wrote:
 the directory structure and module structure is fucking fine!  Why
 fucking
 change it!
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of
 David
  Jencks
  Sent: Monday, October 07, 2002 4:04 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] README :: Thirdparty structure changed
 
 
  This wasn't a code change, it was a change to  how jboss is checked out
  from cvs.  I think maybe Jason forgot that there is no branching
 available
  in CVSROOT.
 
  Basically the problem is that cvs sucks.
 
  I think the solution is to have jboss-all-3_0, jboss-all-3_2, and
  jboss-all-4_0 targets that check out the appropriate structure for each
  release.  We won't change the production targets, newer ones can
  be subject
  to improvement.
 
  david jencks
 
  On 2002.10.07 15:19:40 -0400 Bill Burke wrote:
   All and all I think big structural changes and any big code changes,
 or
   any
   big features should be forbidden from being added to a
  production branch.
   IMHO, they shouldn't be allowed for any branched version as a branch
   means
   we are trying to stabalize.
  
   BTW, you've really hosed me so fix it!
  
   Bill
  
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
   Scott
M Stark
Sent: Monday, October 07, 2002 2:58 PM
To: [EMAIL PROTECTED]
Cc: Jason Dillon
Subject: Re: [JBoss-dev] README :: Thirdparty structure changed
   
   
This has broken the existing 3.0 and 3.2 build structures. Fix
these changes
immediately as we are not going through the production branch build
files to accommodate this change.
   
I also changed the jboss-all alias to checkout its content into
the jboss-all
directory as this had been changed to jboss.
   

Scott Stark
Chief Technology Officer
JBoss Group, LLC

   
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 06, 2002 8:05 PM
Subject: [JBoss-dev] README :: Thirdparty structure changed
   
   
 Hi... me again ;)

 I finally got around to fixing, or rather getting around an
   unfortunate
 side-effect of the CVS 'update' command.  The previous behavior
would cause
 local clients to download the entire thirdparty/* module (which
is time and
 space consuming).

 CVS is not desgined to handle nested structures very well, so I
modified the
 _project_thirdparty cvs modules to flatten the directory
  structure.

 I also had to update the libraries.ent file to use the new root
directories
 for each library.

 So, what this means to you is that you need to do the following:

  1) Re-checkout the project you are working with OR:

a) Remove the thirdparty sub-directory

b) Check out the _project_thirdparty module.  So for the
'jboss-all'
   project, you would checkout _jboss-all_thirdparty

  2) Ensure that your 'tools' module is up to date.

 That's it.

 Unix users working on jboss-all (HEAD) you can execute the
following from
 the jboss-all project directory:

   rm -rf thirdparty
   cvs get _jboss-all_thirdparty
   cvs update tools

 Let me know if you have any questions, comments or problems.

 Please no flames *whimper*...

 --jason
   
   
   
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  

RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread Jason Dillon

Does anyone know where the scripts for these tests are kept?

--jason


On Mon, 7 Oct 2002, marc fleury wrote:

 But seriously now, can anyone get Chris on the line, he needs to clean
 the disk and checkout... this is embarassing
 
 marc f
 
  -Original Message-
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]] On 
  Behalf Of Lennart Petersson
  Sent: Monday, October 07, 2002 9:15 AM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
  
  
  It's the ultimate solution of the build mess  - simplify you know :)
  
  /Lennart
  
  måndagen den 7 oktober 2002 kl 14.55 skrev Sacha Labourey:
  
   It is a new undocummented feature. Cool, huh?
  
   -Message d'origine-
   De : [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]De la part de
   marc
   fleury
   Envoye : lundi, 7 octobre 2002 14:51
   A : [EMAIL PROTECTED]
   Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
  
  
   WTF?
  
   marc f
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]] On 
  Behalf Of 
   [EMAIL PROTECTED]
   Sent: Monday, October 07, 2002 8:15 AM
   To: [EMAIL PROTECTED]
   Cc: [EMAIL PROTECTED]
   Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
  
  
  
   
  
   =
   ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR
   DETAILS=
   
  =
  
   JAVA VERSION DETAILS
   java version 1.4.0_01
   Java(TM) 2 Runtime Environment, Standard Edition (build
   1.4.0_01-b03) Java HotSpot(TM) Client VM (build 
  1.4.0_01-b03, mixed 
   mode)
  
   
  
   =
  
   HERE ARE THE LAST 50 LINES OF THE LOG FILE
  
   build.sh: build.sh: No such file or directory
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf 
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf 
   ___
   Jboss-development mailing list 
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf 
   ___
   Jboss-development mailing list 
  [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] HEAD Build: numerous failure

2002-10-07 Thread Jason Dillon

What errors do you get specifically Sacha?

--jason


On Mon, 7 Oct 2002, Sacha Labourey wrote:

 Hello,
 
 Is it just me? I am trying to compile jboss-all from HEAD (I did a fresh
 checkout a few minutes ago) on windows 2000 and I get lots of errors which
 change over time i.e the compiler (1.4.0) makes an exception and, if I start
 again the build process, it goes further, ... then it is an RMI compiler
 errror (couldn't read LOC header), then it is a set of silent break, etc. At
 the end (after 4-5 restart, it is build successfuly)
 
 Cheers,
 
 
   Sacha
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] README :: Thirdparty structure changed

2002-10-07 Thread Jason Dillon

I do not believe it is possible due to the manner in which CVS works.

Sorry for the chaos... I will resolve these issues w/o breaking anything.  
*sigh*

--jason


On Mon, 7 Oct 2002, David Jencks wrote:

 CVS can't handle thirdparty only including some of the subdirectories.  On
 checkout you get one set of stuff, if you update you get much more.  Jason
 was trying to make the set of stuff you get from checkout and update the
 same.  I think its really important to ensure this, whether or not Jason's
 fix is the best possible.  I think fixing it (at least in head) is more
 important than keeping the directory structure the same.  If you have a way
 to fix the problem while keeping the structure the same, I think that would
 be better.  I don't have such a way.
 
 thanks
 david jencks
 
 On 2002.10.07 16:28:09 -0400 Bill Burke wrote:
  the directory structure and module structure is fucking fine!  Why
  fucking
  change it!
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]On Behalf Of
  David
   Jencks
   Sent: Monday, October 07, 2002 4:04 PM
   To: [EMAIL PROTECTED]
   Subject: Re: [JBoss-dev] README :: Thirdparty structure changed
  
  
   This wasn't a code change, it was a change to  how jboss is checked out
   from cvs.  I think maybe Jason forgot that there is no branching
  available
   in CVSROOT.
  
   Basically the problem is that cvs sucks.
  
   I think the solution is to have jboss-all-3_0, jboss-all-3_2, and
   jboss-all-4_0 targets that check out the appropriate structure for each
   release.  We won't change the production targets, newer ones can
   be subject
   to improvement.
  
   david jencks
  
   On 2002.10.07 15:19:40 -0400 Bill Burke wrote:
All and all I think big structural changes and any big code changes,
  or
any
big features should be forbidden from being added to a
   production branch.
IMHO, they shouldn't be allowed for any branched version as a branch
means
we are trying to stabalize.
   
BTW, you've really hosed me so fix it!
   
Bill
   
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of
Scott
 M Stark
 Sent: Monday, October 07, 2002 2:58 PM
 To: [EMAIL PROTECTED]
 Cc: Jason Dillon
 Subject: Re: [JBoss-dev] README :: Thirdparty structure changed


 This has broken the existing 3.0 and 3.2 build structures. Fix
 these changes
 immediately as we are not going through the production branch build
 files to accommodate this change.

 I also changed the jboss-all alias to checkout its content into
 the jboss-all
 directory as this had been changed to jboss.

 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 

 - Original Message -
 From: Jason Dillon [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, October 06, 2002 8:05 PM
 Subject: [JBoss-dev] README :: Thirdparty structure changed


  Hi... me again ;)
 
  I finally got around to fixing, or rather getting around an
unfortunate
  side-effect of the CVS 'update' command.  The previous behavior
 would cause
  local clients to download the entire thirdparty/* module (which
 is time and
  space consuming).
 
  CVS is not desgined to handle nested structures very well, so I
 modified the
  _project_thirdparty cvs modules to flatten the directory
   structure.
 
  I also had to update the libraries.ent file to use the new root
 directories
  for each library.
 
  So, what this means to you is that you need to do the following:
 
   1) Re-checkout the project you are working with OR:
 
 a) Remove the thirdparty sub-directory
 
 b) Check out the _project_thirdparty module.  So for the
 'jboss-all'
project, you would checkout _jboss-all_thirdparty
 
   2) Ensure that your 'tools' module is up to date.
 
  That's it.
 
  Unix users working on jboss-all (HEAD) you can execute the
 following from
  the jboss-all project directory:
 
rm -rf thirdparty
cvs get _jboss-all_thirdparty
cvs update tools
 
  Let me know if you have any questions, comments or problems.
 
  Please no flames *whimper*...
 
  --jason



 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
   
   
   
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.

[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger clean
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 6 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-614116 ] Oracle XA pooling/repeated rollback

2002-10-07 Thread noreply

Bugs item #614116, was opened at 2002-09-24 17:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=614116group_id=22866

Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Oracle XA pooling/repeated rollback

Initial Comment:

I've been trying to isolate some problems I've been
having with transaction roll-backs and message-driven
beans. Basically, when a transaction is rolled-back
a number of times in the onMessage() body
(by calling MessageDrivenContext.setRollbackOnly()
5-10 times in succession),
the message is re-delivered to the MDB, but the Oracle
Connection is no longer in a good state.

This problem manifests itself when using a very small
connection pool (say 1-5) connections.

Example code snippet:

public void onMessage(javax.jms.Message jmsMessage)
{
 Connection c = null;
try {
 TextMessage tm = (TextMessage)jmsMessage;
 String text = tm.getText();
 c = ds.getConnection();
 PreparedStatement s = c.prepareStatement(insert into test values (?));
 s.setString(1, text);
 s.executeUpdate();
 mdc.setRollbackOnly();
} catch (Exception e) {
 throw new EJBException(e);
} finally {
 if (c != null) {
 try { c.close(); }
 catch (Exception e) {
   e.printStackTrace();
 }
}


First I see it works for a few times. It rolls-back successfully
about 5 or 6 times. Then, for no reason, I see:

15:50:44,922 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//4, 
BranchQual=] errorCode=XAER_RMERR
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.allowGlobalTxnModeOnly(OracleXAResource.java:1069)
 at oracle.jdbc.xa.OracleXAResource.suspendStacked(OracleXAResource.java:296)
 at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:381)
 at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1237)
 at org.jboss.tm.TxCapsule.delistResource(TxCapsule.java:579)
 at org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:92)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.delist(XATxConnectionManager.java:284)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.connectionClosed(XATxConnectionManager.java:331)
 at 
org.jboss.resource.adapter.jdbc.BaseManagedConnection.fireConnectionEvent(BaseManagedConnection.java:152)
 at 
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.fireConnectionEvent(XAManagedConnection.java:215)
 at 
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection$1.connectionClosed(XAManagedConnection.java:127)
 at 
oracle.jdbc.pool.OraclePooledConnection.callListener(OraclePooledConnection.java:482)
 at 
oracle.jdbc.pool.OraclePooledConnection.logicalClose(OraclePooledConnection.java:445)
 at oracle.jdbc.driver.OracleConnection.logicalClose(OracleConnection.java:2900)
 at oracle.jdbc.driver.OracleConnection.close(OracleConnection.java:1418)
 at com.proteusmobile.smx.AMDB.onMessage(AMDB.java:140)

Later:

15:50:44,929 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//4, 
BranchQual=] errorCode=XAER_RMERR
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.allowGlobalTxnModeOnly(OracleXAResource.java:1069)
 at oracle.jdbc.xa.OracleXAResource.suspendStacked(OracleXAResource.java:296)
 at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:381)
 at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1237)
 at org.jboss.tm.TxCapsule.endResources(TxCapsule.java:1312)
 at org.jboss.tm.TxCapsule.rollback(TxCapsule.java:440)
 at org.jboss.tm.TransactionImpl.rollback(TransactionImpl.java:83)
 at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:301)
 at 
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:603)
 at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:417)
 at org.jboss.mq.SpySession.run(SpySession.java:259)
 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:655)
 at java.lang.Thread.run(Thread.java:479)

And then, I can no longer get a connection:

15:50:44,971 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//5, 
BranchQual=] errorCode=XAER_PROTO
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.disallowLocalTxnMode(OracleXAResource.java:1045)
 at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:153)
 at org.jboss.tm.TxCapsule.startResource(TxCapsule.java:1180)
 at org.jboss.tm.TxCapsule.enlistResource(TxCapsule.java:679)
 at org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:102)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.enlist(XATxConnectionManager.java:262)
 at 

[JBoss-dev] RE: [jboss-group] jmx/src/resources/test/log4j is hosed

2002-10-07 Thread Jason Dillon

How about providing some more information so others can try to help the
situation a?

--jason


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On
 Behalf Of Bill Burke
 Sent: Monday, October 07, 2002 2:58 PM
 To: Jboss-Dev
 Cc: Jboss-Group@Jboss. Org
 Subject: [jboss-group] jmx/src/resources/test/log4j is hosed
 
 I hang when get latest at this directory.  What is going on I
can't do
 work
 
 Bill
 
 ___
 jboss-group mailing list
 [EMAIL PROTECTED]
 https://secure.jboss.org/mailman/listinfo/jboss-group



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] RE: RMIAdaptorService still won't compile

2002-10-07 Thread Bill Burke

Branch_3_0 BTW.  Come on! Fix this shit!

 -Original Message-
 From: Bill Burke [mailto:[EMAIL PROTECTED]]
 Sent: Monday, October 07, 2002 5:42 PM
 To: Jboss-Group@Jboss. Org
 Cc: Jboss-Dev
 Subject: RMIAdaptorService still won't compile
 
 
 line 39: should be declared abstract; it does not define getJndiName()
 
 line 76: cannot resolve symbol OBJECT_NAME
 
 
 Bill


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-614116 ] Oracle XA pooling/repeated rollback

2002-10-07 Thread noreply

Bugs item #614116, was opened at 2002-09-24 19:56
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=614116group_id=22866

Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Oracle XA pooling/repeated rollback

Initial Comment:

I've been trying to isolate some problems I've been
having with transaction roll-backs and message-driven
beans. Basically, when a transaction is rolled-back
a number of times in the onMessage() body
(by calling MessageDrivenContext.setRollbackOnly()
5-10 times in succession),
the message is re-delivered to the MDB, but the Oracle
Connection is no longer in a good state.

This problem manifests itself when using a very small
connection pool (say 1-5) connections.

Example code snippet:

public void onMessage(javax.jms.Message jmsMessage)
{
 Connection c = null;
try {
 TextMessage tm = (TextMessage)jmsMessage;
 String text = tm.getText();
 c = ds.getConnection();
 PreparedStatement s = c.prepareStatement(insert into test values (?));
 s.setString(1, text);
 s.executeUpdate();
 mdc.setRollbackOnly();
} catch (Exception e) {
 throw new EJBException(e);
} finally {
 if (c != null) {
 try { c.close(); }
 catch (Exception e) {
   e.printStackTrace();
 }
}


First I see it works for a few times. It rolls-back successfully
about 5 or 6 times. Then, for no reason, I see:

15:50:44,922 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//4, 
BranchQual=] errorCode=XAER_RMERR
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.allowGlobalTxnModeOnly(OracleXAResource.java:1069)
 at oracle.jdbc.xa.OracleXAResource.suspendStacked(OracleXAResource.java:296)
 at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:381)
 at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1237)
 at org.jboss.tm.TxCapsule.delistResource(TxCapsule.java:579)
 at org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:92)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.delist(XATxConnectionManager.java:284)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.connectionClosed(XATxConnectionManager.java:331)
 at 
org.jboss.resource.adapter.jdbc.BaseManagedConnection.fireConnectionEvent(BaseManagedConnection.java:152)
 at 
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.fireConnectionEvent(XAManagedConnection.java:215)
 at 
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection$1.connectionClosed(XAManagedConnection.java:127)
 at 
oracle.jdbc.pool.OraclePooledConnection.callListener(OraclePooledConnection.java:482)
 at 
oracle.jdbc.pool.OraclePooledConnection.logicalClose(OraclePooledConnection.java:445)
 at oracle.jdbc.driver.OracleConnection.logicalClose(OracleConnection.java:2900)
 at oracle.jdbc.driver.OracleConnection.close(OracleConnection.java:1418)
 at com.proteusmobile.smx.AMDB.onMessage(AMDB.java:140)

Later:

15:50:44,929 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//4, 
BranchQual=] errorCode=XAER_RMERR
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.allowGlobalTxnModeOnly(OracleXAResource.java:1069)
 at oracle.jdbc.xa.OracleXAResource.suspendStacked(OracleXAResource.java:296)
 at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:381)
 at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1237)
 at org.jboss.tm.TxCapsule.endResources(TxCapsule.java:1312)
 at org.jboss.tm.TxCapsule.rollback(TxCapsule.java:440)
 at org.jboss.tm.TransactionImpl.rollback(TransactionImpl.java:83)
 at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:301)
 at 
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:603)
 at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:417)
 at org.jboss.mq.SpySession.run(SpySession.java:259)
 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:655)
 at java.lang.Thread.run(Thread.java:479)

And then, I can no longer get a connection:

15:50:44,971 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, 
GlobalId=eross.m-qube.com//5, 
BranchQual=] errorCode=XAER_PROTO
javax.transaction.xa.XAException
 at oracle.jdbc.xa.OracleXAResource.disallowLocalTxnMode(OracleXAResource.java:1045)
 at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:153)
 at org.jboss.tm.TxCapsule.startResource(TxCapsule.java:1180)
 at org.jboss.tm.TxCapsule.enlistResource(TxCapsule.java:679)
 at org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:102)
 at 
org.jboss.resource.connectionmanager.XATxConnectionManager$XAConnectionEventListener.enlist(XATxConnectionManager.java:262)
 at 

[JBoss-dev] RMIAdaptorService still won't compile

2002-10-07 Thread Bill Burke

line 39: should be declared abstract; it does not define getJndiName()

line 76: cannot resolve symbol OBJECT_NAME


Bill


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger clean
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 8 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-619969 ] SQL Server substring syntax is wrong

2002-10-07 Thread noreply

Bugs item #619969, was opened at 2002-10-07 17:15
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=619969group_id=22866

Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Vinh Nguyen (softwaremasters)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQL Server substring syntax is wrong

Initial Comment:
The function mapping for substring for SQL Server (both 
7 and 2K) in standardjbosscmp-jdbc.xml is currently:

substring(?1 FROM ?2 FOR ?3)

This is incorrect. The correct syntax for the substring 
function is:

substring(?1, ?2, ?3)

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=619969group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger -Dinstall.id=testbuild release
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 6 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jmx/src/resources/test/log4j is hosed

2002-10-07 Thread Bill Burke

I hang when get latest at this directory.  What is going on I can't do
work

Bill



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] RE: [jboss-group] jmx/src/resources/test/log4j is hosed

2002-10-07 Thread Bill Burke

try there is no other information CVS hangs for me.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jason
 Dillon
 Sent: Monday, October 07, 2002 6:14 PM
 To: [EMAIL PROTECTED]; 'Jboss-Dev'
 Cc: 'Jboss-Group@Jboss. Org'
 Subject: [JBoss-dev] RE: [jboss-group] jmx/src/resources/test/log4j is
 hosed
 
 
 How about providing some more information so others can try to help the
 situation a?
 
 --jason
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
 On
  Behalf Of Bill Burke
  Sent: Monday, October 07, 2002 2:58 PM
  To: Jboss-Dev
  Cc: Jboss-Group@Jboss. Org
  Subject: [jboss-group] jmx/src/resources/test/log4j is hosed
  
  I hang when get latest at this directory.  What is going on I
 can't do
  work
  
  Bill
  
  ___
  jboss-group mailing list
  [EMAIL PROTECTED]
  https://secure.jboss.org/mailman/listinfo/jboss-group
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] jmx/src/resources/test/log4j is hosed

2002-10-07 Thread Jason Dillon

What is the CVS command you are using, so I can try to reproduce.

--jason


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:jboss-
 [EMAIL PROTECTED]] On Behalf Of Bill Burke
 Sent: Monday, October 07, 2002 2:58 PM
 To: Jboss-Dev
 Cc: Jboss-Group@Jboss. Org
 Subject: [JBoss-dev] jmx/src/resources/test/log4j is hosed
 
 I hang when get latest at this directory.  What is going on I
can't do
 work
 
 Bill
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] RE: [jboss-group] jmx/src/resources/test/log4j is hosed

2002-10-07 Thread Jason Dillon

Oh... well that is quite a different problem... which is out of my
control.  Does it hang every time?  Are you having any connectivity
problems to sf.net?

--jason


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:jboss-
 [EMAIL PROTECTED]] On Behalf Of Bill Burke
 Sent: Monday, October 07, 2002 3:39 PM
 To: [EMAIL PROTECTED]
 Subject: RE: [JBoss-dev] RE: [jboss-group]
jmx/src/resources/test/log4j is
 hosed
 
 try there is no other information CVS hangs for me.
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of
Jason
  Dillon
  Sent: Monday, October 07, 2002 6:14 PM
  To: [EMAIL PROTECTED]; 'Jboss-Dev'
  Cc: 'Jboss-Group@Jboss. Org'
  Subject: [JBoss-dev] RE: [jboss-group] jmx/src/resources/test/log4j
is
  hosed
 
 
  How about providing some more information so others can try to help
the
  situation a?
 
  --jason
 
 
   -Original Message-
   From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
  On
   Behalf Of Bill Burke
   Sent: Monday, October 07, 2002 2:58 PM
   To: Jboss-Dev
   Cc: Jboss-Group@Jboss. Org
   Subject: [jboss-group] jmx/src/resources/test/log4j is hosed
  
   I hang when get latest at this directory.  What is going on I
  can't do
   work
  
   Bill
  
   ___
   jboss-group mailing list
   [EMAIL PROTECTED]
   https://secure.jboss.org/mailman/listinfo/jboss-group
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] jboss-all daily clean failed

2002-10-07 Thread chris


=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

build.sh: Executing: /home/lubega/jbossro/jboss-all/tools/bin/ant -logger 
org.apache.tools.ant.NoBannerLogger clean
Buildfile: build.xml

_buildmagic:init:
Trying to override old definition of task property

BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29:
 taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found

Total time: 6 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Fixing module defintions now for head, 3.0 3.2

2002-10-07 Thread Jason Dillon

I have to modify CVSROOT/modules to test, so please be patient if
something does not function.  I will make sure that all jboss-* projects
function by the days end.

--jason



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] README :: JBoss Projects Build System

2002-10-07 Thread Jason Dillon

I have just verified that all of the branches for the currently active
JBoss versions build correctly out of the box.

I did however need to make some modifications to the CVSROOT/modules
file to make this work correctly and to help prevent future fuckups
(probably by me) when changing the structure of a project (which should
not other branches a project).

To make use of this I have setup 3 new project definitions in
CVSROOT/modules:

  jboss-3.0 - The JBoss 3.0.x project structure definition
  jboss-3.2 - The JBoss 3.2.x  ''
  jboss-2.4 - The JBoss 2.4.x  ''

Unfortunately CVS does not allow branch tags (or any tags) to be
specified in the module definition, so you must still specific '-r
branch' on the command line.  The above simply specifies the correct
structure for the project.

For example, to check out the latest JBoss 3.0.x you would:

  cvs get -r Branch_3_0 jboss-3.0

For JBoss 3.2 you would:

  cvs get -r Branch_3_2 jboss-3.2

Keep in mind that you should use the correct project definition even
when checking out non-branch tags as well.

'jboss-all' is still the HEAD branch.  I think that we should eventually
change this name to 'jboss' or 'jboss-head', since it does not really
contain 'all' of the modules anymore.  But this can wait until later.

I am currently working on making the JBoss 2.4 project independent of
other structure changes, but I have not completed it yet.  The current
branch will build as it did before; I have changed nothing that would
affect that.

 * * *

I am really sorry about the mess I created last night.  I don't know
why, but I had convinced myself that the other branches would work fine.
Before I stopped for the evening I thought about that issue for a bit
and decided things were okay.

Anyways, I am really sorry for the trouble.  I hope to avoid such messes
in the future.

Your humble build system slave (AKA. That guy who always breaks things),
 
--jason



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 7-October-2002

2002-10-07 Thread scott . stark


Number of tests run:   942



Successful tests:  938
Errors:2
Failures:  2



[time of test: 7 October 2002 15:33 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
[java.vm.version: 1.3.1_03-69]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Mac OS X]
[os.arch: ppc]
[os.version: 10.2.1]

See http://lubega.com/testarchive/${build.uid} for details of this test.

See http://lubega.com for general test information.

NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.
Remember - if a test becomes broken after your changes - fix it or fix the test!





Oh dear - still got some errors!



Thanks for all your effort - we really do love you!




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10

2002-10-07 Thread Scott M Stark

If you look at the Embedded usage in the JBoss service it is not doing much.
Being able to run off a sar with the minimum elements from tomcat would be
good, but I want to keep the ability to run with a pristine tomcat dist.


Scott Stark
Chief Technology Officer
JBoss Group, LLC


- Original Message - 
From: Remy Maucherat [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, October 07, 2002 1:19 AM
Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10


 Liam Magee wrote:
  Hi Thomas,
  
  I haven't looked deeply into Tomcat MBean support, this is the next
  natural step for integration b/w JBoss and Tomcat. 
 
 I think it would be beneficial to stop using Embedded eventually 
 (whatever JBoss needs to do should be doable using a host configurator 
 and similar hooks), so that little or no code duplication is needed.
 
 I'll make changes on the Tomcat side (either in future 4.1.x releases, 
 or in Tomcat 5.0.x) and the JBoss/Tomcat build script to allow 
 customizing the classloader and directory structure if people are 
 interested in getting an integration with a neater packaging ala 
 Jetty/JBoss (many components and libraries are also not useful to JBoss 
 and could be removed, thus making the download archive much smaller).
 
 Remy



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development