Re: [JBoss-dev] message redelivery & MDB TX timeout with NotSupported

[Peter Antman]

On  9 Sep, Jason Dillon wrote:
>> > So, the first question is why does an MDB with NotSupported cause TX
>> > timeouts?
>>
>> Hiram is the one who did the transaction parts of the MDB, but I would
>> geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
>> that is), the flags only determins under what TX context the bean is
>> invoked. This mean there will allways be a transaction going on under
>> the hood.
> 
> Is that by design... that NotSupported still runs with a TX?

Yes, but remember. The receipt is under a transaction, but not the bean.

> 
> I don't really have time to look into this more.  I think that changing the
> MDB to use a non-xa cf with NotSupported works but I am not 100% on
> that.  I hope that is the case at least =|

Thats true, it should work fine.

//Peter
> 
>> > Second, why does a message get redelivered to my MDB, but does not have its
>> > getJMSRedelivered() set to true?
>>
>> That was fixed in JBossMQ during the time I implemented the Dead Letter
>> Queue handler, which was commited after the RH stuff. There is a change
>> note about it.
> 
> Great.  Thanks.
> 
> --jason
> 
> 
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development

-- 
Jobba hos oss: http://www.tim.se/weblab

Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems ArchitectWWW: http://www.tim.se
Email: [EMAIL PROTECTED]WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] JINI - JavaGroups - Whatever: real issue?

[Rickard Öberg]

Sacha Labourey wrote:
> Nevertheless, as you probably know, when doing clustering we also need some
> "advanced" communication semantics. We need to be able to know which message
> has been received by which member in which order (for example). A cluster
> where invocations cannot be received in the same order by each node, when
> you do not know which node has received which message, ... is not a very
> usefull cluster IMHO.

You are making way too many assumptions about how to implement the
cluster here. There is no inherent need for what you describe.

>  And this is JavaGroups job. JG provides memberhip
> protocol, state transfer protocol, group views, group communication, ... JG
> also provides a kind of discovery ;) : you create a group with a particular
> name, and you then are able to use extended communication semantic in the
> group, get state transfer events, membership events, ...

There is a lot of complexity inherent in what you describe above. I
doubt that most of that will be useful. And I'm assuming we're talking
about clustering the EJB container here. For the JMS stuff the above
will be more interesting.

KISS.

> (because we do need this communication semantic).

Can you explain why and where this is needed? It seems like this depends
on a particular implementation strategy.

/Rickard

-- 
Rickard Öberg
Software Development Specialist
xlurc - Xpedio Linköping Ubiquitous Research Center
Author of "Mastering RMI"
Email: [EMAIL PROTECTED]

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Automated JBoss Testsuite Results

[chris]

JBoss daily test results

SUMMARY

Number of tests run:   212



Successful tests:  80

Errors:87

Failures:  45





[time of test: 10 September 2001 5:41 GMT]
[java.version: 1.3.1]
[java.vendor: Blackdown Java-Linux Team]
[java.vm.version: Blackdown-1.3.1-FCS]
[java.vm.name: Classic VM]
[java.vm.info: green threads, nojit]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.3-12]

See http://lubega.com for full details

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS

[details not shown - as this makes the mail too big to reach the sf mailing list]



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Automated JBoss Testsuite Results

[chris]

JBoss daily test results

SUMMARY

Number of tests run:   208



Successful tests:  86

Errors:78

Failures:  44





[time of test: 10 September 2001 4:29 GMT]
[java.version: 1.3.1]
[java.vendor: Blackdown Java-Linux Team]
[java.vm.version: Blackdown-1.3.1-FCS]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.3-12]

See http://lubega.com for full details

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS

[details not shown - as this makes the mail too big to reach the sf mailing list]



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/rollinglogged PersistenceManager.java

[David Maplesden]

  User: dmaplesden
  Date: 01/09/09 20:26:44

  Modified:src/main/org/jboss/mq/pm/rollinglogged
PersistenceManager.java
  Log:
  fix (lack of) persistence bug for durable subscribers to topics
  
  Revision  ChangesPath
  1.7   +5 -1  
jbossmq/src/main/org/jboss/mq/pm/rollinglogged/PersistenceManager.java
  
  Index: PersistenceManager.java
  ===
  RCS file: 
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/rollinglogged/PersistenceManager.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- PersistenceManager.java   2001/09/04 02:22:29 1.6
  +++ PersistenceManager.java   2001/09/10 03:26:44 1.7
  @@ -32,7 +32,7 @@
*  This class manages all persistence related services.
*
* @author David Maplesden ([EMAIL PROTECTED])
  - * @version$Revision: 1.6 $
  + * @version$Revision: 1.7 $
*/
   public class PersistenceManager extends ServiceMBeanSupport implements 
org.jboss.mq.pm.PersistenceManager, PersistenceManagerMBean
   {
  @@ -490,6 +490,10 @@
 for (int j = 0; j < messages.length; j++)
 {
messages[j].persistData = info;
  + if (dest instanceof org.jboss.mq.SpyTopic)
  + {
  +messages[j].durableSubscriberID = 
((org.jboss.mq.SpyTopic)dest).getDurableSubscriptionID();
  + }
q.restoreMessage(messages[j]);
 }
  }
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Automated JBoss Testsuite Results

[chris]

JBoss daily test results

SUMMARY

Number of tests run:   223



Successful tests:  90

Errors:87

Failures:  46





[time of test: 10 September 2001 3:27 GMT]
[java.version: 1.3.0]
[java.vendor: IBM Corporation]
[java.vm.version: 1.3.0]
[java.vm.name: Classic VM]
[java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)]
[os.name: Linux]
[os.arch: x86]
[os.version: 2.4.3-12]

See http://lubega.com for full details

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS

[details not shown - as this makes the mail too big to reach the sf mailing list]



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] message redelivery & MDB TX timeout with NotSupported

[Jason Dillon]

> >I don't really have time to look into this more.  I think that changing the
> >MDB to use a non-xa cf with NotSupported works but I am not 100% on
> >that.  I hope that is the case at least =|
> >
>
> What's going on thats giving you all this grief???

I have a MDB, which performs some actions that take longer than the TX
timeout, and only one message may be processed by one machine at a time.

I need to redesign this so that there is a JMX service which pulls
messages when the machine is available rather than using an MDB.

If I don't run into problems with the non-xa cf then all is well.  I was
just concered that this might be a larger problem.

--jason


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/xdocs/howto howtopetstore.xml

[Tom Coleman]

  User: tmcsys  
  Date: 01/09/09 16:06:14

  Modified:src/xdocs/howto howtopetstore.xml
  Log:
  Add JBoss-Jetty Deployment information
  
  Revision  ChangesPath
  1.4   +9 -11 manual/src/xdocs/howto/howtopetstore.xml
  
  Index: howtopetstore.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtopetstore.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- howtopetstore.xml 2001/09/01 00:56:48 1.3
  +++ howtopetstore.xml 2001/09/09 23:06:14 1.4
  @@ -1,4 +1,5 @@
   
  +
   
   
Deploying the Pet Store 1.1.2 Demo in JBoss
  @@ -13,8 +14,9 @@
Introduction
The Pet Store sample application (demo) is a relatively robust, 
well-documented demonstration of J2EE technology and concepts. It implements MVC 
(Model-View-Controller) architecture.
The Pet Store demo can allow developers to gain familiarity with 
J2EE concepts including application portability, a key J2EE design objective.
  - The Pet Store has been successfully deployed in JBoss 2.4 BETA 
configured to use Embedded Tomcat 3.2.2 using Sun 1.3 jdk on RH Linux 6.2. The steps 
provided below apply to JBoss 2.4 BETA Rel_2_4_0_23.
  - 
  + The Pet Store has been most recently deployed using the 
JBoss-Jetty package, http://www.jboss.org/binary.jsp";>JBoss-2.4.0_Jetty-3.1.RC8-1. If you use 
the JBoss-Jetty package, you will have to add Pet Store DB Pools to the jboss.jcml 
file in the jboss/conf/jetty directory.
  + The Pet Store had previously been deployed using a JBoss 2.4 
BETA configured to use Embedded Tomcat 3.2.2. The specific release used was JBoss 2.4 
BETA Rel_2_4_0_23.
  + Both deployments were on a RH Linux 6.2 system using the Sun 1.3 
jdk.

Outstanding Deployment Issues
Please post your experiences with deploying the Pet Store in 
JBoss to the jboss-user mailing list.
  @@ -24,17 +26,12 @@
   
   
The Admin Client
  - The Admin application apparently needs some work on the 
deployment descriptors.  Please post your experences with the Admin application to the 
mailing list.
  -
  -
  - Jetty Deployment
  - The Pet Store should deploy using Jetty.  Please post 
your experences with deploying the Pet Store using Jetty to the mailing list.
  + We need JBoss deployment descriptors for the Admin 
application.  If you have successfully deployed the Admin application using JBoss, 
please post them to one of the Forums or to the jboss-user mailing list.
   
   
Pet Store Security
The current release of the Pet Store handles security at 
the application level.  It does require that you configure JBoss or Tomcat security 
services.
   
  -



  @@ -61,8 +58,9 @@
Running the Pet Store demo in JBoss requires 
several minor changes to deployment files in the Pet Store application (.ear) file. 
The patch is currently available in the documentation files section of the manual, it 
is named jps112-01.zip.


  - Configure JBoss to use Embedded Tomcat
  - You need a servlet container to run the 
petstore. These instructions use Tomcat 3.2.2. You can either use a bundled binary 
JBoss + Tomcat, or see the instructions to configure JBoss to use Embedded Tomcat in 
.
  + Configure JBoss
  + You need a servlet container to run the Java Pet 
Store. If you're using the JBoss-Jetty or JBoss-Tomcat releases, the server is 
preconfigured.
  + If you're using a stand-alone JBoss release with 
Tomcat, see the structions to configure JBoss to use Embedded Tomcat in .


Select a Database
  @@ -104,7 +102,7 @@


Add JARS to JBoss
  - Copy your DB driver JAR to the lib/extdirectory 
of your JBoss installation ($JBOSS_HOME). 
  + Copy your DB driver JAR to the lib/ext directory 
of your JBoss installation ($JBOSS_HOME). 
For Cloudscape, copy client.jar and RmiJdbc.jar 
to the lib/ext directory. 
Copy tools.jar from the J2 SDK to the lib/ext 
directory of your JBoss installation ($JBOSS_HOME).

  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] message redelivery & MDB TX timeout with NotSupported

[Hiram Chirino]

> > > So, the first question is why does an MDB with NotSupported cause TX
> > > timeouts?
> >
> > Hiram is the one who did the transaction parts of the MDB, but I would
> > geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
> > that is), the flags only determins under what TX context the bean is
> > invoked. This mean there will allways be a transaction going on under
> > the hood.
>
>Is that by design... that NotSupported still runs with a TX?
>

The reason you have tx running is cause when you use a XAConnectionFactory, 
sessions are allways transacted.  What happens with a NotSupported, is that 
the transaction that the message came in with will be dissasociated from the 
thread before we call the onMessage method.  After the onMessage returns, 
the original transaction is commited ( to do the message acknowlegment. )


>I don't really have time to look into this more.  I think that changing the
>MDB to use a non-xa cf with NotSupported works but I am not 100% on
>that.  I hope that is the case at least =|
>

What's going on thats giving you all this grief???

Regards, Hiram



_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] message redelivery & MDB TX timeout with NotSupported

[Jason Dillon]

> > So, the first question is why does an MDB with NotSupported cause TX
> > timeouts?
>
> Hiram is the one who did the transaction parts of the MDB, but I would
> geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
> that is), the flags only determins under what TX context the bean is
> invoked. This mean there will allways be a transaction going on under
> the hood.

Is that by design... that NotSupported still runs with a TX?

I don't really have time to look into this more.  I think that changing the
MDB to use a non-xa cf with NotSupported works but I am not 100% on
that.  I hope that is the case at least =|

> > Second, why does a message get redelivered to my MDB, but does not have its
> > getJMSRedelivered() set to true?
>
> That was fixed in JBossMQ during the time I implemented the Dead Letter
> Queue handler, which was commited after the RH stuff. There is a change
> note about it.

Great.  Thanks.

--jason


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] [ jboss-Change Notes-459830 ] sar deploying/undeploying modifications

[David Maplesden]

Cool, I know it might seem like I suddenly disappeared but I have been
working on my idea too.  I will get your stuff from CVS and see if I can
integrate the two mechanisms.

David

> -Original Message-
> From: marc fleury [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, September 09, 2001 5:39 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] [ jboss-Change Notes-459830 ] sar
> deploying/undeploying modifications
> 
> 
> excellent! good work david
> 
> marcf
> 
> 
> |-Original Message-
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of
> |[EMAIL PROTECTED]
> |Sent: Saturday, September 08, 2001 1:23 PM
> |To: [EMAIL PROTECTED]
> |Subject: [JBoss-dev] [ jboss-Change Notes-459830 ] sar
> |deploying/undeploying modifications
> |
> |
> |Change Notes item #459830, was opened at 2001-09-08 10:22
> |You can respond by visiting: 
> |http://sourceforge.net/tracker/?func=detail&atid=381174&aid=459830&;
> |group_id=22866
> |
> |Category: None
> |Group: v3.0 (Rabbit Hole)
> |Status: Open
> |Priority: 5
> |Submitted By: David Jencks (d_jencks)
> |Assigned to: Nobody/Anonymous (nobody)
> |Summary: sar deploying/undeploying modifications
> |
> |Initial Comment:
> |I've added some tests of service deployment
> |functionality (in testsuite, ./build.sh -Dtest-jmx
> |test) that test undeployment and repeated deployment of
> |*-service.xml and .sar files. I've also changed the
> |ServiceDeployer (mostly) and ServiceController and
> |ServiceLibraries to make undeploy work better and to
> |track sar dependencies and enable recursive deploy and
> |undeploy of .sar (and .jar) packages.
> |
> |
> |-
> -
> |
> |You can respond by visiting: 
> |http://sourceforge.net/tracker/?func=detail&atid=381174&aid=459830&;
> |group_id=22866
> |
> |___
> |Jboss-development mailing list
> |[EMAIL PROTECTED]
> |https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: newsite/src/docs binary.jsp changelog_2_4_beta.jsp

[Scott M Stark]

  User: starksm 
  Date: 01/09/09 10:13:30

  Modified:src/docs binary.jsp changelog_2_4_beta.jsp
  Log:
  Update the binary release page and change log page for 2.4.1
  
  Revision  ChangesPath
  1.3   +11 -43newsite/src/docs/binary.jsp
  
  Index: binary.jsp
  ===
  RCS file: /cvsroot/jboss/newsite/src/docs/binary.jsp,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- binary.jsp2001/09/08 15:12:09 1.2
  +++ binary.jsp2001/09/09 17:13:30 1.3
  @@ -4,7 +4,6 @@
  
   

  -
TAKE OUR SURVEY
With 50,000 downloads per month, JBoss is quickly becoming the force to reckon 
with in the industry. 
To help us gather usage and production statistics and, in the process, better 
serve you, please 
  @@ -16,13 +15,9 @@
DOWNLOAD THE JBOSS SERVER PRODUCTS TODAY!
   

  -  JBoss 2.4.0 is our current stable version. It will run on both
  +  JBoss 2.4.1 is our current stable version. It will run on both
 1.2.2 and 1.3 JVMs.
   
  -
  -  JBoss 2.4.0 final release is available for those who wish to test
  -  the upcoming release.
  -  

 This is our full suite of products and it is likely to be all you will
 need to try out our technology. If you need a servlet container, we
  @@ -43,15 +38,15 @@
 Packages   Size   Date
 
 
  -http://prdownloads.sourceforge.net/jboss/JBoss-2.4.0.zip";>JBoss-2.4.0.zip
  -8109497
  -August 21, 2001
  +http://prdownloads.sourceforge.net/jboss/JBoss-2.4.1.zip";>JBoss-2.4.1.zip
  +8378769
  +Setempter 9, 2001
 
   
 
  -http://prdownloads.sourceforge.net/jboss/JBoss-2.4.0_Tomcat-3.2.3.zip";>JBoss-2.4.0_Tomcat-3.2.3.zip
  -11415568
  -August 21, 2001
  +http://prdownloads.sourceforge.net/jboss/JBoss-2.4.1_Tomcat-3.2.3.zip";>JBoss-2.4.1_Tomcat-3.2.3.zip
  +9016518
  +Setempter 9, 2001
 
   
 
  @@ -61,9 +56,11 @@
 
   
   
  -
  + http://www.jboss.org/survey/index.jsp";>
  +   the time to fill out the survey,
  + 
   
  -Change Log for version 2.4.0 
Beta.
  +Change Log for version 2.4.x.
   
   JBoss 2.2.2
   
  @@ -138,36 +135,7 @@
   
 The older JBoss versions (2.2 and 2.2.1) are 
 http://sourceforge.net/project/showfiles.php?group_id=22866";>available here.
  -  
  -
   
  Oh, and remember we love you.
   
  
  
  
  1.2   +101 -7newsite/src/docs/changelog_2_4_beta.jsp
  
  Index: changelog_2_4_beta.jsp
  ===
  RCS file: /cvsroot/jboss/newsite/src/docs/changelog_2_4_beta.jsp,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- changelog_2_4_beta.jsp2001/08/30 22:29:19 1.1
  +++ changelog_2_4_beta.jsp2001/09/09 17:13:30 1.2
  @@ -5,21 +5,116 @@
   
   
   
  -JBOSS 2.4 BETA RELEASE
  +
  +JBOSS 2.4.1 Release
   
  +[ #459941 ] Allow child CLs acess to java:comp 
  +
  +The java:comp ENC object factory has been updated to 
  +allow access to the context from a thread context 
  +ClassLoader that has as its parent the ClassLoader 
  +that first created the java:comp ENC. This simplifies 
  +access to the ENC in situations where new ClassLoaders 
  +are created as is the case for web container 
  +integration services. 
  +
   
  -415088  Display LinkRef targets in JNDIView 
  +[ #459938 ] Add deploy/undeploy JMX events
  +
  +Incorporated a change suggested by F.Brier that addes 
  +JMX event notifications for pre/post deploy() and 
  +pre/post undeploy() of J2EE archives. The event type is 
  +org.jboss.deployment.DeploymentNotification, which is 
  +also the class of the Notification object. 
  +
  +
  +[ #459936 ] Fix JSP include of security content
   
  +Fix a security problem that showed up in the 2.4.0 
  +release. The issue is that if a secured JSP page 
  +includes a sequence of jsp includes like: 
  +
  +
  + 
  + 
  + 
  + 
  + 
  + 
  + 
  + 
  + 
  + 
  + 
  + 
  +
  +
  +where test.jsp looks up a secured stateless session 
  +bean, only the first include succeeds. The later 
  +includes fail because the security association of the 
  +servlet request thread was lost. 
   
  +
   
  - Added support for displaying the node that LinkRef 
  - JNDI nodes point to. This allows one to see what 
  - 

Re: [JBoss-dev] message redelivery & MDB TX timeout with NotSupported

[pra]

On  7 Sep, Jason Dillon wrote:
> Has there been any work on JBossMQ message redelivery recently?
> 
> I have an MDB, which has all of its methods set to NotSupported, using a
> custom container-configuration, which only allows one message to be
> processed at a time (jboss dd attached).
> 
> It processes a message, which could take longer than the TX timeout, so I it
> can not run inside of a TX.
> 
> I am still getting warnings:
> 
>   WARN  org.jboss.tm.TxCapsule [Thread-8] () - Transaction XidImpl
>   [FormatId=257, GlobalId=eng-ecr4a//0, BranchQual=] timed out.
>   status=STATUS_ACTIVE
> 
> For each warning the message being processes seems to reapear back into the
> queue, though Message.getJMSRedelivered() will never return true.
> 
> This is running in JBoss pre-3.0, which was built very shortly before the RH
> bit were commited, so it may be possible that this have been fixed in newer
> versions?  I did not seen any change logs, specific to this, so I think that
> it might be a bug in HEAD too.
> 
> So, the first question is why does an MDB with NotSupported cause TX
> timeouts?

Hiram is the one who did the transaction parts of the MDB, but I would
geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
that is), the flags only determins under what TX context the bean is
invoked. This mean there will allways be a transaction going on under
the hood.

> 
> Second, why does a message get redelivered to my MDB, but does not have its
> getJMSRedelivered() set to true?

That was fixed in JBossMQ during the time I implemented the Dead Letter
Queue handler, which was commited after the RH stuff. There is a change
note about it.

//Peter
> 
> --jason

-- 

Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems ArchitectWWW: http://www.tim.se
Email: [EMAIL PROTECTED]WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Build instructions????

[Scott M Stark]

>P.S. I did download the 2.4.1 binary zip file.  It is very unfriendly to
set
>directory permissions to mode 664. That makes it unreadable.  And it makes
>me wonder if you've actually tried to use your distributions before you
>release them.

Java does not have a notion of file executable permissions and so zip
archives do not contain this information. The Ant build process creates zip
files using the Java classes. Use the JDK jar -xf to extract the files
and the permissions on directories are set correctly.




___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Automated JBoss Testsuite Results

[chris]

JBoss daily test results

SUMMARY

Number of tests run:   208



Successful tests:  86

Errors:78

Failures:  44





[time of test: 9 September 2001 14:12 GMT]
[java.version: 1.3.1]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.3.1-b24]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.3-12]

See http://lubega.com for full details

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS

[details not shown - as this makes the mail too big to reach the sf mailing list]



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Build instructions????

[Peter Fagerlund]

on 1-09-09 11.47, Dean Anderson at [EMAIL PROTECTED] wrote:

> Could someone post somewhere instructions on how to build jboss?

What is Buildmagic 

Buildmagic is a collection of extension tasks for Ant v1.3/1.4 and a general
methodology for organization of build control files. It was designed to
allow aggregation of one or more source modules into one logical project,
yet still retain each modules individuality (so that the same module could
be incorporated into another project or worked on independently of a
project). 


*Buildmagic User's Guide [pdf] Http://jboss.org/bm-usersguide.pdf


> Is there a stable version of the source code available via ftp?

try the 2.4.0 http://jboss.org/binary.jsp --comes with source

> Should I start looking for another App server?

Yes You can ... but why ? ...

> Whats up?

The development of 3.0 is up ... alot is beeing tweeked and upgraded - in
fact most ;-) 

> P.S. I did download the 2.4.1 binary zip file.  It is very unfriendly to set
> directory permissions to mode 664. That makes it unreadable.  And it makes
> me wonder if you've actually tried to use your distributions before you
> release them.

hmmm ... yes - perhaps formalise the release with an "internal" acceptance
phase - as of now We are all doing the internal acceptance phase -heh ...

This suggest the open slot for somebody to make a DASH-O and GUI config of
stable versions ...

what would You pay for that ? ...

/peter_f


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Automated JBoss Testsuite Results

[chris]

JBoss daily test results

SUMMARY

Number of tests run:   212



Successful tests:  80

Errors:87

Failures:  45





[time of test: 9 September 2001 13:3 GMT]
[java.version: 1.3.1]
[java.vendor: Blackdown Java-Linux Team]
[java.vm.version: Blackdown-1.3.1-FCS]
[java.vm.name: Classic VM]
[java.vm.info: green threads, nojit]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.3-12]

See http://lubega.com for full details

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS

[details not shown - as this makes the mail too big to reach the sf mailing list]



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Automated JBoss Testsuite Results

[chris]

JBoss daily test results

SUMMARY

Number of tests run:   208



Successful tests:  86

Errors:78

Failures:  44





[time of test: 9 September 2001 11:56 GMT]
[java.version: 1.3.1]
[java.vendor: Blackdown Java-Linux Team]
[java.vm.version: Blackdown-1.3.1-FCS]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.3-12]

See http://lubega.com for full details

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS

[details not shown - as this makes the mail too big to reach the sf mailing list]



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Management/Deployment - partial failure in theBORG cube

[Peter Fagerlund]

on 1-09-08 23.29, Trevor Squires at [EMAIL PROTECTED] wrote:

> a) centralised management and deployment within a single cluster only.
> b) centralised management and deployment across clusters.

a) then b) will follow ...

I am toy'ing with the idea of losly coupled JBoss Execution areas - where an
admin of a JBoss instance/s can dedicate part of the excecution area for
colocation of resources ... for R&D or for a fee ... that would involve the
managment of statistic tick counts for the colocator and resource holder.

/peter_f


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Build instructions????

[Dean Anderson]

Could someone post somewhere instructions on how to build jboss?

Is there a stable version of the source code available via ftp?

I managed to get it to build using some cvs tip of about 2 weeks ago, but it
wouldn't run due to the following problem with the JAXP package.

Foolishly, I thought I'd update my cvs tree.  Now the included ant has the
same problem, and I can't build now...

Should I start looking for another App server?

Whats up?

P.S. I did download the 2.4.1 binary zip file.  It is very unfriendly to set
directory permissions to mode 664. That makes it unreadable.  And it makes
me wonder if you've actually tried to use your distributions before you
release them.

--Dean


 JBoss Bootstrap Environment

 JAVA: /usr/local/jdk1.3.1/bin/java


AVA_OPTS:  -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.crimson.jax
p.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache
.crimson.jaxp.SAXParserFactoryImpl

 CLASSPATH:
/home2/dean/src/jboss/jboss-all/build/output/jboss-2.5alpha-DEV//bin/run.jar



jboss.home = /home2/dean/src/jboss/jboss-all/build/output/jboss-2.5alpha-DEV
Using JAAS LoginConfig:
file:/home2/dean/src/jboss/jboss-all/build/output/jboss-2.5alpha-DEV/conf/de
fault/auth.conf
Using configuration "default"
[root] Started Log4jService,
config=file:/home2/dean/src/jboss/jboss-all/build/output/jboss-2.5alpha-DEV/
conf/default/log4j.properties
[Info] Java version: 1.3.1,Sun Microsystems Inc.
[Info] Java VM: Java HotSpot(TM) Client VM 1.3.1-b24,Sun Microsystems Inc.
[Info] System: Linux 2.2.14-5.0smp,i386
[Shutdown] Shutdown hook added
[Default] Runtime error
[Default] javax.xml.parsers.FactoryConfigurationError:
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
[Default]   at
javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.
java:80)
[Default]   at
org.jboss.configuration.ConfigurationService.loadConfiguration(Configuration
Service.java:424)
[Default]   at java.lang.reflect.Method.invoke(Native Method)
[Default]   at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Default]   at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Default]   at org.jboss.Main.(Main.java:201)
[Default]   at org.jboss.Main$1.run(Main.java:115)
[Default]   at java.security.AccessController.doPrivileged(Native Method)
[Default]   at org.jboss.Main.main(Main.java:111)
[Default] JBoss pre-3.0 [RABBIT-HOLE] Started in 0m:2s
[Shutdown] Shutting down all services
[Default] Shutting down
[ServiceControl] Stopping 0 MBeans
[ServiceControl] Stopped 0 services
[ServiceControl] Destroying 0 MBeans
[ServiceControl] Destroyed 0 services
[Shutdown] Shutdown complete
[Default] Shutdown complete


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Automated JBoss Testsuite Results

[chris]

JBoss daily test results

SUMMARY

Number of tests run:   223



Successful tests:  90

Errors:87

Failures:  46





[time of test: 9 September 2001 10:54 GMT]
[java.version: 1.3.0]
[java.vendor: IBM Corporation]
[java.vm.version: 1.3.0]
[java.vm.name: Classic VM]
[java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)]
[os.name: Linux]
[os.arch: x86]
[os.version: 2.4.3-12]

See http://lubega.com for full details

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS

[details not shown - as this makes the mail too big to reach the sf mailing list]



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [ jboss-Patches-459959 ] bug fixed in castorjdo MBean

[noreply]

Patches item #459959, was opened at 2001-09-09 01:32
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376687&aid=459959&group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: bug fixed in castorjdo MBean

Initial Comment:
The castorjdo MBean did not unbind itself in a correct
way from the JNDI namespace. This is corrected in a
self explaining way with the path appended.

--

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376687&aid=459959&group_id=22866

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [ jboss-Patches-459958 ] bug fixed in castorjdo MBean

[noreply]

Patches item #459958, was opened at 2001-09-09 01:32
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376687&aid=459958&group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: bug fixed in castorjdo MBean

Initial Comment:
The castorjdo MBean did not unbind itself in a correct
way from the JNDI namespace. This is corrected in a
self explaining way with the path appended.

--

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376687&aid=459958&group_id=22866

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: jboss/src/client jbossmq-client.jar

[Scott M Stark]

  User: starksm 
  Date: 01/09/09 00:39:17

  Modified:src/client Tag: Branch_2_4 jbossmq-client.jar
  Log:
  Merge the JBossMQ Rel_2_4_1_9 changes
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.6.4.4   +365 -360  jboss/src/client/Attic/jbossmq-client.jar
  
<>
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: jboss/src/lib jbossmq.jar

[Scott M Stark]

  User: starksm 
  Date: 01/09/09 00:39:18

  Modified:src/lib  Tag: Branch_2_4 jbossmq.jar
  Log:
  Merge the JBossMQ Rel_2_4_1_9 changes
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.8.4.4   +478 -475  jboss/src/lib/Attic/jbossmq.jar
  
<>
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: jbosstest/src/build/subprojects build-web.xml

[Scott M Stark]

  User: starksm 
  Date: 01/09/09 00:34:51

  Modified:src/build/subprojects Tag: Branch_2_4 build-web.xml
  Log:
  Update web test jars
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.5.2.2   +1 -0  jbosstest/src/build/subprojects/Attic/build-web.xml
  
  Index: build-web.xml
  ===
  RCS file: /cvsroot/jboss/jbosstest/src/build/subprojects/Attic/build-web.xml,v
  retrieving revision 1.5.2.1
  retrieving revision 1.5.2.2
  diff -u -r1.5.2.1 -r1.5.2.2
  --- build-web.xml 2001/07/09 01:06:01 1.5.2.1
  +++ build-web.xml 2001/09/09 07:34:51 1.5.2.2
  @@ -55,6 +55,7 @@
   

   
  +   
  
  
   
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development