Re: [JBoss-dev] Tomcat/JMS Classes not found

2001-07-04 Thread Vinay Menon

Guess as long as it is intended and more importantly 'documented' somewhere
users are not going to get surprised!

Vinay
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: Dev @ JBoss [EMAIL PROTECTED]
Sent: Wednesday, July 04, 2001 12:03 AM
Subject: Re: [JBoss-dev] Tomcat/JMS Classes not found


  [Configuration] org.jboss.configuration.ConfigurationException: missing
  required
   attribute: QueueFactoryRef when I start up the server.
 

 The MDB support is assuming that both QueueFactoryRef and TopicFactoryRef
 are non-null.   I added this to make it clear what the problem is instead
of
 the MDB sub-system throwing non-helpful NullPointerExceptions.

 --jason


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


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



[JBoss-dev] xml config for Log4j

2001-07-04 Thread Jason Dillon

How about using the xml configuration file for Log4j as the default?  At the
very, very least it is nicer to look at in Emacs with font-lock, at best it
makes more of the JBoss config xml... wow. =]

I was also hoping to change the default JBoss category format to something
like this:

%c{1} [%t] %-5p - %m%n

This provides a little more information than what is currently there, which
I find to be very useful when debugging distributed systems.

--jason



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



[JBoss-dev] [ jboss-Change Notes-438469 ] JMSProviderLoader required attributes

2001-07-04 Thread noreply

Change Notes item #438469, was opened at 2001-07-04 01:41
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detailatid=381174aid=438469group_id=22866

Category: None
Group: v2.5 (Rabbit Hole)
Status: Open
Priority: 5
Submitted By: Jason Dillon (user57)
Assigned to: Nobody/Anonymous (nobody)
Summary: JMSProviderLoader required attributes

Initial Comment:
QueueFactoryRef and TopicFactoryRef are now required
attributes of the JMSProviderLoader MBean.  These
should be the jndi name of the connection factory of
the appropriate type.

Previously if either of these values was null then a
NullPointerException could be thrown from inside one of
the jms sub-systems.

--

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detailatid=381174aid=438469group_id=22866

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



[JBoss-dev] How to delete serialized session beans? / feature request?

2001-07-04 Thread Schouten, Andreas

Hello!

I don't get an answer to this question in jBoss-user.

 How to delete the .ser files from the filesystem?
 I found that they are neither removed on ejbActivate nor ejbRemouve.

Is there indeed no way to delete the files? Would it be a problem deleting
the .ser file at ejbActivate by the container?

Thanks!

Andreas 



If you have received this e-mail in error or wish to read our e-mail disclaimer 
statement and monitoring policy, please refer to
http://www.drkw.com/disc/email/ or contact the sender.

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



Re: [JBoss-dev] jboss daily test results

2001-07-04 Thread Chris Kimpton

Hi,

--- Jason Dillon [EMAIL PROTECTED] wrote:
 I don't get this.  When you run jbosstest/dist/bin/jmsratest.sh all
 of the
 tests succeed.  This test only fails when it is run as part of the
 full
 test suite.  It looks like a test that runs before this one mucks
 with
 something.  I checked that all of the tests in this suite run
 correctly in
 any order with a fresh JBoss instance.  I will see if I can track
 down the
 problem later =(
 
 --jason
 

It is intermittent as well - some days they all fail, some days they
all work - there are some other tests that seem to be rarely/never
get through - I get a total of around 94 tests when I run the same
thing manually...

What is jmsra anyway - some RA feature of JMS ?

Thanks,
Chris

=
Need somewhere to Live in London - http://freeflats.com

__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

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




RE: [JBoss-dev] How to delete serialized session beans? / feature request?

2001-07-04 Thread Schouten, Andreas

I'd a look at

org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.activateSession(
StatefulSessionEnterpriseContext ctx)

it reads the file but does't delete it:

// Load state
 in = new SessionObjectInputStream(ctx, new FileInputStream(new
File(dir, ctx.getId()+.ser)));
 
 ctx.setInstance(in.readObject());
 
 in.close();
 
 // Call bean

Would it violate somsing else, if this snap would be replaced by

 // Load state
File file = new File(dir, ctx.getId()+.ser);
 in = new SessionObjectInputStream(ctx, new FileInputStream(file));
 
 ctx.setInstance(in.readObject());
 
 file.delete();
 in.close();
 
 // Call bean
 ?

Andreas

 -Original Message-
 From: Schouten, Andreas [SMTP:[EMAIL PROTECTED]]
 Sent: 04 July 2001 10:59
 To:   [EMAIL PROTECTED]
 Subject:  [JBoss-dev] How to delete serialized session beans? /
 feature request?
 
 Hello!
 
 I don't get an answer to this question in jBoss-user.
 
  How to delete the .ser files from the filesystem?
  I found that they are neither removed on ejbActivate nor ejbRemouve.
 
 Is there indeed no way to delete the files? Would it be a problem deleting
 the .ser file at ejbActivate by the container?
 
 Thanks!
 
 Andreas 
 
 
 
 If you have received this e-mail in error or wish to read our e-mail
 disclaimer statement and monitoring policy, please refer to
 http://www.drkw.com/disc/email/ or contact the sender.
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-development

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



Re: [JBoss-dev] jboss daily test results

2001-07-04 Thread Jason Dillon


 It is intermittent as well - some days they all fail, some days they
 all work - there are some other tests that seem to be rarely/never
 get through - I get a total of around 94 tests when I run the same
 thing manually...

From a few hours of looking into I would say there is something wrong... I
just can't tell if the test is wrong or if the sub-system is wrong.

 What is jmsra anyway - some RA feature of JMS ?

Of course it is =)

--jason


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



[JBoss-dev] might have it...

2001-07-04 Thread Jason Dillon

could be too soon to say.  if this checks out when I am actually awake we
will know for sure.

--jason


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



RE: [JBoss-dev] xml config for Log4j

2001-07-04 Thread marc fleury

Now that I (almost) done with the container synchronization rewrite, I am
going to commit the JBoss 3.0 code that I have on my laptop, if I remember
correctly I move most of the stuff to services.xml (the old jboss.jcml) and
log4j should go there,  will try to commit this piece by next tuesday

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
|Dillon
|Sent: Wednesday, July 04, 2001 4:16 AM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] xml config for Log4j
|
|
|How about using the xml configuration file for Log4j as the
|default?  At the
|very, very least it is nicer to look at in Emacs with font-lock, at best it
|makes more of the JBoss config xml... wow. =]
|
|I was also hoping to change the default JBoss category format to something
|like this:
|
|%c{1} [%t] %-5p - %m%n
|
|This provides a little more information than what is currently there, which
|I find to be very useful when debugging distributed systems.
|
|--jason
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development



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



[JBoss-dev] I'm 51402

2001-07-04 Thread Aaron Mulder

So what do I have to do to get SourceForge to recognize me instead
of calling me 51402?  I've ssh'd to cvs.jboss.sourceforge.net
  jboss.sourceforge.net, which I thought was supposed to register the
account, and I do get a prompt with my username...  But when I check in, I
get:

[EMAIL PROTECTED]'s password:
Checking in main/org/jboss/metadata/MethodMetaData.java;
/cvsroot/jboss/jboss/src/main/org/jboss/metadata/MethodMetaData.java,v
--  MethodMetaData.java
new revision: 1.8.4.1; previous revision: 1.8
done
2001-07-04 07:33:37 Failed to get user name for uid 51402
Processing log script arguments...
Mailing the commit message...

Thanks,
Aaron (aka Jean Valjean)


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



RE: [JBoss-dev] I'm 51402

2001-07-04 Thread marc fleury

I always thought you were number 6...
But I guess you're not a number
you are a free man

I'm a prisoner

a href=http://www.retroweb.com/prisoner.html;never mind/a

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron
|Mulder
|Sent: Wednesday, July 04, 2001 10:41 AM
|To: jBoss Developer
|Subject: [JBoss-dev] I'm 51402
|
|
|   So what do I have to do to get SourceForge to recognize me instead
|of calling me 51402?  I've ssh'd to cvs.jboss.sourceforge.net
|  jboss.sourceforge.net, which I thought was supposed to register the
|account, and I do get a prompt with my username...  But when I check in, I
|get:
|
|[EMAIL PROTECTED]'s password:
|Checking in main/org/jboss/metadata/MethodMetaData.java;
|/cvsroot/jboss/jboss/src/main/org/jboss/metadata/MethodMetaData.java,v
|--  MethodMetaData.java
|new revision: 1.8.4.1; previous revision: 1.8
|done
|2001-07-04 07:33:37 Failed to get user name for uid 51402
|Processing log script arguments...
|Mailing the commit message...
|
|Thanks,
|   Aaron (aka Jean Valjean)
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development


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



Re: [JBoss-dev] xml config for Log4j

2001-07-04 Thread Scott M Stark

Last I checked the xml config did not support custom priorities which is why
I'm not using it.

- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 04, 2001 1:15 AM
Subject: [JBoss-dev] xml config for Log4j


 How about using the xml configuration file for Log4j as the default?  At
the
 very, very least it is nicer to look at in Emacs with font-lock, at best
it
 makes more of the JBoss config xml... wow. =]

 I was also hoping to change the default JBoss category format to something
 like this:

 %c{1} [%t] %-5p - %m%n

 This provides a little more information than what is currently there,
which
 I find to be very useful when debugging distributed systems.

 --jason



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



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



[JBoss-dev] container-cache-conf 1/1

2001-07-04 Thread Vincent Harcq

A simple question,
In JBOSS config file on container-cache-conf, I define
min-capacity1/min-capacity and max-capacity1/max-capacity, instead
of 10 / 100 (for example).
And if 1/1 solve a problem that appear on 10/100, do I have found a problem
in the cache ?

I have seen a lot of discussion on the cache these last weeks, I did a clean
check out to test some problems I have, they did not disappear.
If I could help by providing some examples, I will be please to do so.
Regards.
Vincent.


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



[JBoss-dev] Web Site DTDs Missing

2001-07-04 Thread Aaron Mulder

Just a little while ago there was a file on the web site:

http://www.jboss.org/doco_files/jboss_2_4.dtd

But now it's gone.  The 2.2 one (jboss.dtd) is still there.  Was
this intentional?
It looks like some of the latest DTDs claim that the URL should be

http://www.jboss.org/j2ee/dtd/  (e.g. jboss_2_4.dtd)

And some claim that the URL should be

http://www.jboss.org/j2ee/dtds/ (e.g. jboss_web.dtd)

But neither of those appear to exist on the web site either.  Can
we *please* pick one and then *create it*?  I assume we'd like the web
site generation routine to check out the newest copies and use them,
rather than checking the DTDs into the newsite module as well.  Then
again, since the DTDs on the web site are supposed to be the stable
ones, perhaps we *should* check them in separately so they only get
updated for major releases.  Can whoever maintiains the web site
generation speak up?
Finally, if we're going to version the DTDs, then we should
probably version jboss_web.dtd.

Thanks,
Aaron


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



RE: [JBoss-dev] container-cache-conf 1/1

2001-07-04 Thread marc fleury

honestly this doesn't really help, too complex a business scenario, bean a
calls b calls c calls d calls e calls f then something goes wrong...

can you minimize the repro case? like something simpler?

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Vincent Harcq
|Sent: Wednesday, July 04, 2001 1:01 PM
|To: [EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] container-cache-conf 1/1
|
|
|Hi,
|
|Test1:
|
|I have a servlet calling a sfsb calling a slsb calling a entity bean A on
|which I run a setX().This setX() runs himself another setY() on another
|entity bean B.
|From my web page I change the value on the attribute.  I can see
|it is saved
|in the db.
|But the getX() of my entity bean always return the old value.
|
|Now I start another web browser, I access the same entity bean.  I see the
|new value.
|
|Now I come back to the first browser, I access the same entity
|bean.  Bingo.
|It is the good value.
|
|Test 2:
|Now I set the cache to 1/1.  Everything works OK.
|
|Test 3:
|If I remove the link with the other entity bean everything is OK.
|
|Vincent.
|PS: I can post a ejb jar and a client. . .  In fact I will have to
|write the
|client, give some time.
|
|
| Hey Vincent,
|
|  A simple question,
|  In JBOSS config file on container-cache-conf, I define
|  min-capacity1/min-capacity and
|  max-capacity1/max-capacity, instead
|  of 10 / 100 (for example).
|  And if 1/1 solve a problem that appear on 10/100, do I have
|  found a problem
|  in the cache ?
|
| Maybe, and maybe not :) Can you expand on this ?
|
|  I have seen a lot of discussion on the cache these last
|  weeks, I did a clean
|  check out to test some problems I have, they did not disappear.
|  If I could help by providing some examples, I will be please to do so.
|
| Please do. Just post them on the dev-list, I guess it supports
|attachments
|
| Simon
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development



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



Re: [JBoss-dev] MORE: mdb tests are causing jmsra tests to fail

2001-07-04 Thread Peter Antman

On Wed, 4 Jul 2001, Jason Dillon wrote:

 It looks like a left over MDB was still attached to queue/testQueue and was
 eating messages.  I was confused about this, but I guess JBossMQ is doing a
 good job at not starving any listeners, which would explain the sometimes
 working behavor that I was seeing.
 
 So I modified the MDB test to undeploy its support applications after all
 the other tests ran.  The running the mdb test and then the jmsra test would
 succeed (ala mdbtest.sh  jmsratest.sh).

Hm, I have never run the complete tests, therefore I never stumbled on the
problem. Another way of solving the probem is ofcourse to let for example
jmsra use some of the other queues that are defined in a standard
jbossmw.xml file.


  
 I tried running the full test (ala sh ./build.sh -f run_tests.xml) but
 started getting odd server hangs while the application was being undeployed.
 It looked like it was going to just stay wedged, but would eventually
 continue with some messages about lost connections and such (I don't have
 the exact output... anymore... it scrolled... damn all that Address
 passivation fluff).

Hm, hard for me to say anyting about it. I have not tested JMS and MDB at
al since Hiram made the latest changes to the ServerSessionPool stuff.

//Peter
 
 So, I have fixed another problem, which led to yet another problem.  Not to
 mention getting the build system to correctly handle an added nested class
 and then waiting for it to completly rebuild the testsuite each time.
 
 On that note, I am almost finished with a simple build system.  Actually I
 spent most of last week toying with ant to get it to cooperate with me.  I
 am using my lgpl class library bliss as a test currently.  I plan on
 converting all projects at work (which currently use an older version) to
 this shortly and I think that it would be especially useful to this project.
 
 I am not really sure if anyone else is working on something like this.  I
 remember seeing some email from Marc about something.
 
 When it gets closer to finished (mid next week) I will explain a little
 more.
 
 --jason
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 http://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]
http://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] comments on new instance interceptors and locking

2001-07-04 Thread marc fleury

Excellent!

frankly I will try to read tonight, finishing up the stateful stuff (minor
rewrite).

read real fast: the wait() as opposed to wait(5000), I know :) I do it on
purpose, if there is a lock I WANT TO KNOW ABOUT IT.  In fact wait(5000)
only makes things cosmetically better, a missed notify is bad and we would
need to see it. That's all.

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Bill
|Burke
|Sent: Wednesday, July 04, 2001 4:34 PM
|To: Jboss-Development@Lists. Sourceforge. Net
|Subject: [JBoss-dev] comments on new instance interceptors and locking
|
|
|Hey Marc,
|
|I looked over the new Entity Interceptors and locking and have a few
|comments
|
|- There is a race condition when an Entity is re-entrant.   In
|EntityInstanceInterceptor.invoke you set the context's transaction in the
|synchronized(ctx) block rather than in the synchronized(ctx.getTxLock())
|block.  Thus it is possible for 2 different threads in 2 different
|transactions to get through the first Tx synchronized block and both do
|ctx.setTransaction(...).  I suggest maybe that you put the
|synchronized(ctx)
|block inside the synchronized(ctx.getTxLock()) block.  I hope I'm making
|sense here.
|
|
|- In EntitytInstanceInterceptor.invoke in the finally block.  If an
|exception is thrown, you should do a ctx.getTxLock().notifyAll() as well as
|ctx.notifyAll().  An exception could happen in loadEntity, thus, no Sync
|would be registered with the TM, thus threads waiting on ctx.getTxLock()
|would never be awakened.
|
|- I really think that doing a wait() rather than a wait(5000) is a really
|really bad idea.  If a transaction timeout happens, I don't think a thread
|that is in a ctx.wait() or a ctx.getTxLock().wait() will ever wakeup and
|actually do a rollback and release all it's locked entities and resources.
|I am VERY unfamiliar with the TM code, but take a look at
|TxCapsule.timedOut().  This method only marks the transaction as ROLLING
|back and does nothing else.  I can find no where in the jboss
|codebase where
|Thread.interrupt() is called in relation to transaction timeouts.
|(I'd test
|out this theory myself, but I'm on vacation and won't really be able to
|until Monday.)
|
|I guess there is 2 solutions here.  One, have transaction timeouts
|interrupt
|their threads, or Two, have a wait(5000) block in EntityInstanceInterceptor
|as well as:
|
|// Maybe my transaction already expired?
|if (mi.getTransaction() != null  mi.getTransaction().getStatus() ==
|Status.STATUS_MARKED_ROLLBACK)
| throw new RuntimeException(Transaction marked for rollback,
|possibly a
|timeout);
|
|at the beginning of your while(ctx==null) loop.  Actually, it
|would probably
|be best to have a wait(Tx.timeout) instead of just 5000.
|
|Anyways, FREEZING, is very very bad in itself.  Yeah sure, JBoss might not
|have any deadlocks, but you really want to be able to recover from
|Application deadlock.
|
|
|- I'll probably open up a different email thread on this, but maybe all the
|locks should be pulled out of EnterpriseContext and be managed by some
|LockManager.  If multiple instances for option B and C is ever
|implemented(I'd like to tackle this), they'll have to use a different
|locking mechanism because you wouldn't be able to synchronize on ctx and
|ctx.getTxLock().
|
|
|Well, I hope I'm making sense here.  It's the 4th and I have a
|belly full of
|beer and BBQ.
|
|Regards,
|
|Bill
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development



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



Re: [JBoss-dev] MORE: mdb tests are causing jmsra tests to fail

2001-07-04 Thread Jason Dillon

 Hm, I have never run the complete tests, therefore I never stumbled on the
 problem. Another way of solving the probem is ofcourse to let for example
 jmsra use some of the other queues that are defined in a standard
 jbossmw.xml file.

There is a QueueBean from the MDB tests that is still attached to the
queue/testQueue which is breaking the jmsra tests.  I think I have this
fixed ala undeploy.  Need to make sure though =)

If this works then it might be a good idea to deploy/test/undeploy for all
tests to avoid any problems like this in the future.  It would also be a
good test for deploy/undeploy.

--jason

  I tried running the full test (ala sh ./build.sh -f run_tests.xml) but
  started getting odd server hangs while the application was being undeployed.
  It looked like it was going to just stay wedged, but would eventually
  continue with some messages about lost connections and such (I don't have
  the exact output... anymore... it scrolled... damn all that Address
  passivation fluff).

 Hm, hard for me to say anyting about it. I have not tested JMS and MDB at
 al since Hiram made the latest changes to the ServerSessionPool stuff.

I think that this was caused by a bug that I introduced in the
test.util.Deploy class... I think.  I have not gotten to look into the
EOFException proplem more... which is what I really need fixed (for work).
Perhaps I will have some time to look at that tonight.  I was hoping that
the test failure was related, but I do not think there is a direct relation.

By the way, what is up with the topic to queue adapter thingy?  I was
confused by this, as well as the test for a topic using queue stuff, so I
split up the queue/topic tests, or rather I abstracted the jms resource
access from the test... not in the best way either, but it will work for
now.

--jason


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



[JBoss-dev] Stateful tweaking

2001-07-04 Thread marc fleury

coding it as we speak (like bill 4th of july belly full of beer and bbq, man
these Southern clubs are weird)

Ok reading the spec.

1- It is clear that an invocation on remove or create in a transactional
context throws a Remove Exception (7.6 last point).  It also says that it
does it because it wants to keep the state diagram EASY a few pages before
(no other reason stated)... wow that's strange, again to me it makes little
sense.

anyway

2- Still in the points of 7.6 you will find that if a rollback occurred the
bean instance may need to reset its conversational state back to the value
it had at teh beginning of the transaction.  Which very clearly indicates
that the bean is still active.  This also applies to the CMT+Sync case (we
are talking about after completion).  My conclusion on this is the following
but the spec is really superficial on this (the points are messy):

BMT: don't do jack since the bean knows that the transaction commits or not,
CMT+sync: notify and don't do more since the bean now knows that the
transaction rolled back
CMT no sync: here we could argue that the bean should be removed, I would in
fact agree since there is no callback and the bean is un-ware.  We are not
selection states based on transactional resolution.  I would argue that this
case could call for a transactional cache that automatically sets state N or
N+1 depending on commit or rollback.  They are purely symmetrical just move
to the next one if you commit (N+1) or not (N) if you rollback.

but for now I will add the 3 lines that implement the first part and do
nothing about the second since most cases are ok and the last one is really
an added feature.

ANYONE FANCY A COOL ADD-ON??? hmmm? a transactional cache for stateful beans
:) hmmm?  I would sell it $10 a pop, non spec required but clearly very
cool, ok you want me to spell it out? get on your keyboard and fucking
develop that fast transactional stateful cache, come on!

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of marc
|fleury
|Sent: Tuesday, July 03, 2001 5:46 PM
|To: [EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] remove transactional
|
|
||Danny O' is right about not trashing the Stateful bean on a
||rollback.  I was
||only thinking about Entities when I made that comment(as was probably
||Danch).  Actually, the spec infers that a Stateful bean is not registered
||with the TM unless it implements SessionSynchronization.
|
|yes that is the CMT+sync case I was refering to, the BMT case is even more
|clear cut imho...
|
|time to commit (without that part, I need to refresh on the spec)
|
|marcf
|
||
||Regards,
||Bill
||
|| -Original Message-
|| From: [EMAIL PROTECTED]
|| [mailto:[EMAIL PROTECTED]]On Behalf Of marc
|| fleury
|| Sent: Tuesday, July 03, 2001 4:52 PM
|| To: [EMAIL PROTECTED]
|| Subject: RE: [JBoss-dev] remove transactional
||
||
|| so
||
|| fifteen minute time lapse
||
|| is the create the same? cannot be transactional??? or just remove?
||
|| having problems with the new code as we speak
||
|| marcf
||
|| |-Original Message-
|| |From: [EMAIL PROTECTED]
|| |[mailto:[EMAIL PROTECTED]]On Behalf Of marc
|| |fleury
|| |Sent: Tuesday, July 03, 2001 4:26 PM
|| |To: [EMAIL PROTECTED]
|| |Subject: RE: [JBoss-dev] remove transactional
|| |
|| |
|| |chill pill bill...
|| |
|| |there is more fire coming, although when we volley back and
|| forth like this
|| |you must account for delivery lag,
|| |
|| |so everyone take a chill pill bill for 15 mins, when you come
|| back we are
|| |all synchronized :)
|| |
|| |ready ? so where are we, the requirements seems contradictorial
|| at least to
|| |me (but I didnt' take the chill pill and I want to finish the commits)
|| |
|| |marcf
|| |
|| ||-Original Message-
|| ||From: [EMAIL PROTECTED]
|| ||[mailto:[EMAIL PROTECTED]]On
|Behalf Of Bill
|| ||Burke
|| ||Sent: Tuesday, July 03, 2001 4:09 PM
|| ||To: [EMAIL PROTECTED]
|| ||Subject: RE: [JBoss-dev] remove transactional
|| ||
|| ||
|| ||Just in case you didn't see the last email,
|| ||
|| ||statefulbean.remove() results in an exception when the bean is
|| ||participating
|| ||within a transaction.  This is not allowed.  Please see the spec!
|| ||
|| ||Bill
|| ||
|| || -Original Message-
|| || From: [EMAIL PROTECTED]
|| || [mailto:[EMAIL PROTECTED]]On
|| Behalf Of marc
|| || fleury
|| || Sent: Tuesday, July 03, 2001 3:54 PM
|| || To: [EMAIL PROTECTED]
|| || Subject: RE: [JBoss-dev] remove transactional
|| ||
|| ||
|| || fair enough, by popular demand
|| ||
|| || remove() is not a transactional operation then,
|| ||
|| || you call it? the stateful bean is gone, gone I tell you!
|| ||
|| || marcf
|| ||
|| || |-Original Message-
|| || |From: [EMAIL PROTECTED]
|| || |[mailto:[EMAIL PROTECTED]]On
|| |Behalf Of danch
|| || |(Dan Christopherson)
|| || |Sent: Tuesday, July 03, 2001 3:35 PM
|| || |To: [EMAIL PROTECTED]
|| || |Subject: Re: [JBoss-dev] remove transactional
|| || |
|| 

RE: [JBoss-dev] Stateful tweaking

2001-07-04 Thread marc fleury

|Ok reading the spec.
|
|1- It is clear that an invocation on remove or create in a transactional
|context throws a Remove Exception (7.6 last point).  It also says that it
|does it because it wants to keep the state diagram EASY a few
|pages before
|(no other reason stated)... wow that's strange, again to me it makes little
|sense.

ok done and tested commiting with the cache working properly (afaict)

marcf
|
|anyway
|
|2- Still in the points of 7.6 you will find that if a rollback
|occurred the
|bean instance may need to reset its conversational state back to the value
|it had at teh beginning of the transaction.  Which very clearly indicates
|that the bean is still active.  This also applies to the CMT+Sync case (we
|are talking about after completion).  My conclusion on this is the
|following
|but the spec is really superficial on this (the points are messy):
|
|BMT: don't do jack since the bean knows that the transaction
|commits or not,
|CMT+sync: notify and don't do more since the bean now knows that the
|transaction rolled back
|CMT no sync: here we could argue that the bean should be removed,
|I would in
|fact agree since there is no callback and the bean is un-ware.  We are not
|selection states based on transactional resolution.  I would argue
|that this
|case could call for a transactional cache that automatically sets
|state N or
|N+1 depending on commit or rollback.  They are purely symmetrical just move
|to the next one if you commit (N+1) or not (N) if you rollback.
|
|but for now I will add the 3 lines that implement the first part and do
|nothing about the second since most cases are ok and the last one is really
|an added feature.
|
|ANYONE FANCY A COOL ADD-ON??? hmmm? a transactional cache for
|stateful beans
|:) hmmm?  I would sell it $10 a pop, non spec required but clearly very
|cool, ok you want me to spell it out? get on your keyboard and fucking
|develop that fast transactional stateful cache, come on!
|
|marcf
|
||-Original Message-
||From: [EMAIL PROTECTED]
||[mailto:[EMAIL PROTECTED]]On Behalf Of marc
||fleury
||Sent: Tuesday, July 03, 2001 5:46 PM
||To: [EMAIL PROTECTED]
||Subject: RE: [JBoss-dev] remove transactional
||
||
|||Danny O' is right about not trashing the Stateful bean on a
|||rollback.  I was
|||only thinking about Entities when I made that comment(as was probably
|||Danch).  Actually, the spec infers that a Stateful bean is not registered
|||with the TM unless it implements SessionSynchronization.
||
||yes that is the CMT+sync case I was refering to, the BMT case is even more
||clear cut imho...
||
||time to commit (without that part, I need to refresh on the spec)
||
||marcf
||
|||
|||Regards,
|||Bill
|||
||| -Original Message-
||| From: [EMAIL PROTECTED]
||| [mailto:[EMAIL PROTECTED]]On Behalf Of marc
||| fleury
||| Sent: Tuesday, July 03, 2001 4:52 PM
||| To: [EMAIL PROTECTED]
||| Subject: RE: [JBoss-dev] remove transactional
|||
|||
||| so
|||
||| fifteen minute time lapse
|||
||| is the create the same? cannot be transactional??? or just remove?
|||
||| having problems with the new code as we speak
|||
||| marcf
|||
||| |-Original Message-
||| |From: [EMAIL PROTECTED]
||| |[mailto:[EMAIL PROTECTED]]On
|Behalf Of marc
||| |fleury
||| |Sent: Tuesday, July 03, 2001 4:26 PM
||| |To: [EMAIL PROTECTED]
||| |Subject: RE: [JBoss-dev] remove transactional
||| |
||| |
||| |chill pill bill...
||| |
||| |there is more fire coming, although when we volley back and
||| forth like this
||| |you must account for delivery lag,
||| |
||| |so everyone take a chill pill bill for 15 mins, when you come
||| back we are
||| |all synchronized :)
||| |
||| |ready ? so where are we, the requirements seems contradictorial
||| at least to
||| |me (but I didnt' take the chill pill and I want to finish the commits)
||| |
||| |marcf
||| |
||| ||-Original Message-
||| ||From: [EMAIL PROTECTED]
||| ||[mailto:[EMAIL PROTECTED]]On
||Behalf Of Bill
||| ||Burke
||| ||Sent: Tuesday, July 03, 2001 4:09 PM
||| ||To: [EMAIL PROTECTED]
||| ||Subject: RE: [JBoss-dev] remove transactional
||| ||
||| ||
||| ||Just in case you didn't see the last email,
||| ||
||| ||statefulbean.remove() results in an exception when the bean is
||| ||participating
||| ||within a transaction.  This is not allowed.  Please see the spec!
||| ||
||| ||Bill
||| ||
||| || -Original Message-
||| || From: [EMAIL PROTECTED]
||| || [mailto:[EMAIL PROTECTED]]On
||| Behalf Of marc
||| || fleury
||| || Sent: Tuesday, July 03, 2001 3:54 PM
||| || To: [EMAIL PROTECTED]
||| || Subject: RE: [JBoss-dev] remove transactional
||| ||
||| ||
||| || fair enough, by popular demand
||| ||
||| || remove() is not a transactional operation then,
||| ||
||| || you call it? the stateful bean is gone, gone I tell you!
||| ||
||| || marcf
||| ||
||| || |-Original Message-
||| || |From: [EMAIL PROTECTED]
||| || |[mailto:[EMAIL PROTECTED]]On
||| |Behalf Of danch
||| || |(Dan Christopherson)
||| || 

RE: [JBoss-dev] container-cache-conf 1/1

2001-07-04 Thread Vincent Harcq

Yes!
I have a simple example that shows my problem.
It is linked to my previous deseperation (remember?) as well.
It is one client, one session bean, two entity beans, two detail objects.

Client calls SB to add EB 1
Client calls SB to add EB 2
Client calls SB to modify(old) EB 2
Client calls SB to read EB 2 (*)
Client calls SB to modify(new) EB 2
Client calls SB to read EB 2 (*) == old data is shown but new is in the
DB

Why ?

Because EB 2 access(fbpk + remote-method) EB 1 in (*).  The cache of EB 1
touch the one of EB 2 somewhere.

With min-capacity and max-capacity set to 1 everything is OK.  The
Passivation clean the cache.

What do I do next ?
I could add it to jbosstest so you can have a look (please, it's driving me
mad for 2 months now)

TIA.
Vincent.

 -Message d'origine-
 De : [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]De la part de marc
 fleury
 Envoyé : mercredi 4 juillet 2001 21:09
 À : [EMAIL PROTECTED]
 Objet : RE: [JBoss-dev] container-cache-conf 1/1


 honestly this doesn't really help, too complex a business scenario, bean a
 calls b calls c calls d calls e calls f then something goes wrong...

 can you minimize the repro case? like something simpler?

 marcf

 |-Original Message-
 |From: [EMAIL PROTECTED]
 |[mailto:[EMAIL PROTECTED]]On Behalf Of
 |Vincent Harcq
 |Sent: Wednesday, July 04, 2001 1:01 PM
 |To: [EMAIL PROTECTED]
 |Subject: RE: [JBoss-dev] container-cache-conf 1/1
 |
 |
 |Hi,
 |
 |Test1:
 |
 |I have a servlet calling a sfsb calling a slsb calling a entity bean A on
 |which I run a setX().This setX() runs himself another setY()
 on another
 |entity bean B.
 |From my web page I change the value on the attribute.  I can see
 |it is saved
 |in the db.
 |But the getX() of my entity bean always return the old value.
 |
 |Now I start another web browser, I access the same entity bean.
 I see the
 |new value.
 |
 |Now I come back to the first browser, I access the same entity
 |bean.  Bingo.
 |It is the good value.
 |
 |Test 2:
 |Now I set the cache to 1/1.  Everything works OK.
 |
 |Test 3:
 |If I remove the link with the other entity bean everything is OK.
 |
 |Vincent.
 |PS: I can post a ejb jar and a client. . .  In fact I will have to
 |write the
 |client, give some time.
 |
 |
 | Hey Vincent,
 |
 |  A simple question,
 |  In JBOSS config file on container-cache-conf, I define
 |  min-capacity1/min-capacity and
 |  max-capacity1/max-capacity, instead
 |  of 10 / 100 (for example).
 |  And if 1/1 solve a problem that appear on 10/100, do I have
 |  found a problem
 |  in the cache ?
 |
 | Maybe, and maybe not :) Can you expand on this ?
 |
 |  I have seen a lot of discussion on the cache these last
 |  weeks, I did a clean
 |  check out to test some problems I have, they did not disappear.
 |  If I could help by providing some examples, I will be please
 to do so.
 |
 | Please do. Just post them on the dev-list, I guess it supports
 |attachments
 |
 | Simon
 |
 |
 |
 |___
 |Jboss-development mailing list
 |[EMAIL PROTECTED]
 |http://lists.sourceforge.net/lists/listinfo/jboss-development



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



_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


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



[JBoss-dev] jboss daily build failed - in cvs module: jbosssx

2001-07-04 Thread chris


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

Buildfile: build.xml

init:

error:
 [echo] jboss.home = ../jboss/dist is not a valid JBoss server cvs dist structure

BUILD FAILED

/home/lubega/jbossro/jbosssx/src/build/build.xml:36: Override/edit the jboss.home 
property and build the dist

Total time: 1 second

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



[JBoss-dev] jboss daily javadocs build failed - in cvs module: jbosssx

2001-07-04 Thread chris


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

Buildfile: build.xml

init:

error:
 [echo] jboss.home = ../jboss/dist is not a valid JBoss server cvs dist structure

BUILD FAILED

/home/lubega/jbossro/jbosssx/src/build/build.xml:36: Override/edit the jboss.home 
property and build the dist

Total time: 1 second

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



RE: [JBoss-dev] jboss daily build failed - in cvs module: jboss

2001-07-04 Thread marc fleury

uh wait, I thought I commited that...

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|[EMAIL PROTECTED]
|Sent: Wednesday, July 04, 2001 9:33 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] jboss daily build failed - in cvs module: jboss
|
|
|
|=
|==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
|=
|
|Buildfile: build.xml
|
|init:
| [echo] build.compiler = classic
| [echo] java.home = /opt/jdk1.3_sun/jre
| [echo] user.home = /home/lubega
| [echo] java.class.path =
|../../lib/ant-1.3.jar:../../lib/awt.jar:../../lib/codegen.jar:../..
/lib/crimson.jar:../../lib/javac.jar:../../lib/jaxp.jar:../../lib/jmxri.jar:
../../lib/xmlbeans.j|ar:../../build/classes
| [echo]
|
|prepare:
|[mkdir] Created dir: /home/lubega/jbossro/jboss/build
|
|compile:
|[mkdir] Created dir: /home/lubega/jbossro/jboss/build/classes
|[javac] Compiling 556 source files to
|/home/lubega/jbossro/jboss/build/classes
|[javac]
|/home/lubega/jbossro/jboss/src/main/org/jboss/ejb/plugins/EntityIns
|tanceCache.java:77: Method getLock(java.lang.Object) not found in
|class org.jboss.ejb.plugins.AbstractInstanceCache.
|[javac]return super.getLock(id);
|[javac]^
|[javac]
|/home/lubega/jbossro/jboss/src/main/org/jboss/ejb/plugins/EntityIns
|tanceCache.java:85: Method removeLock(java.lang.Object) not found
|in class org.jboss.ejb.plugins.AbstractInstanceCache.
|[javac]super.removeLock(id);
|[javac]^
|[javac]
|/home/lubega/jbossro/jboss/src/main/org/jboss/ejb/plugins/StatefulS
|essionInstanceCache.java:134: Method removeLock(java.lang.Object)
|not found in class org.jboss.ejb.plugins.StatefulSessionInstanceCache.
|[javac]removeLock(key);
|[javac]  ^
|[javac] Note: 5 files use or override a deprecated API.
|Recompile with -deprecation for details.
|[javac] 3 errors, 1 warning
|
|BUILD FAILED
|
|/home/lubega/jbossro/jboss/src/build/build.xml:116: Compile
|failed, messages should have been provided.
|
|Total time: 1 minute 18 seconds
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development



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



[JBoss-dev] jboss daily test failed

2001-07-04 Thread chris


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


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



RE: [JBoss-dev] jboss daily build failed - in cvs module: jboss

2001-07-04 Thread marc fleury

it's there, in flight commit :)


marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of marc
|fleury
|Sent: Wednesday, July 04, 2001 9:45 PM
|To: [EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] jboss daily build failed - in cvs module: jboss
|
|
|uh wait, I thought I commited that...
|
|marcf
|
||-Original Message-
||From: [EMAIL PROTECTED]
||[mailto:[EMAIL PROTECTED]]On Behalf Of
||[EMAIL PROTECTED]
||Sent: Wednesday, July 04, 2001 9:33 PM
||To: [EMAIL PROTECTED]
||Subject: [JBoss-dev] jboss daily build failed - in cvs module: jboss
||
||
||
||=
||==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
||=
||
||Buildfile: build.xml
||
||init:
|| [echo] build.compiler = classic
|| [echo] java.home = /opt/jdk1.3_sun/jre
|| [echo] user.home = /home/lubega
|| [echo] java.class.path =
||../../lib/ant-1.3.jar:../../lib/awt.jar:../../lib/codegen.jar:../..
|/lib/crimson.jar:../../lib/javac.jar:../../lib/jaxp.jar:../../lib/j
|mxri.jar:
|../../lib/xmlbeans.j|ar:../../build/classes
|| [echo]
||
||prepare:
||[mkdir] Created dir: /home/lubega/jbossro/jboss/build
||
||compile:
||[mkdir] Created dir: /home/lubega/jbossro/jboss/build/classes
||[javac] Compiling 556 source files to
||/home/lubega/jbossro/jboss/build/classes
||[javac]
||/home/lubega/jbossro/jboss/src/main/org/jboss/ejb/plugins/EntityIns
||tanceCache.java:77: Method getLock(java.lang.Object) not found in
||class org.jboss.ejb.plugins.AbstractInstanceCache.
||[javac]   return super.getLock(id);
||[javac]   ^
||[javac]
||/home/lubega/jbossro/jboss/src/main/org/jboss/ejb/plugins/EntityIns
||tanceCache.java:85: Method removeLock(java.lang.Object) not found
||in class org.jboss.ejb.plugins.AbstractInstanceCache.
||[javac]   super.removeLock(id);
||[javac]   ^
||[javac]
||/home/lubega/jbossro/jboss/src/main/org/jboss/ejb/plugins/StatefulS
||essionInstanceCache.java:134: Method removeLock(java.lang.Object)
||not found in class org.jboss.ejb.plugins.StatefulSessionInstanceCache.
||[javac]   removeLock(key);
||[javac] ^
||[javac] Note: 5 files use or override a deprecated API.
||Recompile with -deprecation for details.
||[javac] 3 errors, 1 warning
||
||BUILD FAILED
||
||/home/lubega/jbossro/jboss/src/build/build.xml:116: Compile
||failed, messages should have been provided.
||
||Total time: 1 minute 18 seconds
||
||___
||Jboss-development mailing list
||[EMAIL PROTECTED]
||http://lists.sourceforge.net/lists/listinfo/jboss-development
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development


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



RE: [JBoss-dev] comments on new instance interceptors and locking

2001-07-04 Thread marc fleury


|I believe the solution there is to re-check the tx in ctx inside the else
|reentrant block and break with a null context to make a 1 loop (no wait)
|back in the synchronized(ctx.getLock()), that will work a wait.

done in cvs

||- In EntitytInstanceInterceptor.invoke in the finally block.  If an
||exception is thrown, you should do a ctx.getTxLock().notifyAll()
|as well as
||ctx.notifyAll().  An exception could happen in loadEntity, thus, no Sync
||would be registered with the TM, thus threads waiting on ctx.getTxLock()
||would never be awakened.
|
|that is correct, good catch, forgot pure and simple (that check at line 278
|!ctx.isTxSynchronized() that right there tells me free everyone).  I
|didn't catch that in test since we don't test failure of server db,
|interesting... we should, we should nip connections

done in cvs


||locks should be pulled out of EnterpriseContext and be managed by some
||LockManager.  If multiple instances for option B and C is ever
||implemented(I'd like to tackle this), they'll have to use a different
||locking mechanism because you wouldn't be able to synchronize on ctx and
||ctx.getTxLock().
|
|yes, that is XP, I am not going to complicate the code until we really need
|to.  You will notice that I left the lock stuff commented but not removed
|for that purpose, it is a very possible we use this in the future, but the
|first thing I wanted to get going is the bare bones version.

commented last traces of locks in cache, feel free to use back in old
version ctxLock instead of ctx as long as the logic is the same shoul be
fine

keep it coming,

marcf



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



Re: [JBoss-dev] comments on new instance interceptors and locking

2001-07-04 Thread Georg Rehfeld

Hi Bill and Marc and all others,

Bill:
 I looked over the new Entity Interceptors and locking and have a
 few comments

My reverence to Bill for this excellent code review. And ditto to
Marc for the excellent code to review. Most points you discuss
I'm barely able to follow, not to mention suggestions. And the
one point 'upsetting' me (not really) 'wait() vs.
wait(some_time)' was cleared by Marc: in the testing phase he
wants to see the hang, in production code there WILL be a timeout
to protect against client introduced deadlock situations.

Whats left to me? Just let you know, that I'm watching, what you
are doing here, still learning; might be some big brother is
watching you too, at last the whole world is looking at that,
not literally at every code line, but at JBoss as a very good EJB
server and focussing on usability.

Marc to Bill:
| hey thanks, I feel I am in a fighter plane and I am working on
| oxygen supply, not much to breeze in that code so I am always
| happy to see a fellow bomber plane fly by, feel less alone.

Hey, Bill actually impresses me as a wingman (?), accompanying
you as near as possible having an eye at your back! And remember,
if you ever make it back to your base, there are others to feed
you! If you get lost in the skyes, may be Bill catches you up.

Bill concluded:
 I'll probably open up a different email thread on this, but maybe
 all the locks should be pulled out of EnterpriseContext and be
 managed by some LockManager. If multiple instances for option B
 and C is ever implemented(I'd like to tackle this), they'll have
 to use a different locking mechanism because you wouldn't be able
 to synchronize on ctx and ctx.getTxLock().

Yes, let's have multiple instances! I'll try to be a usefull
member of the groundcrew for that.

best regards
Georg
 ___   ___
| + | |__Georg Rehfeld  Woltmanstr. 12 20097 Hamburg
|_|_\ |___   [EMAIL PROTECTED]   +49 (40) 23 53 27 10



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



RE: [JBoss-dev] I'm 51402

2001-07-04 Thread marc fleury

|   So what do I have to do to get SourceForge to recognize me instead
|of calling me 51402?  I've ssh'd to cvs.jboss.sourceforge.net

uh yeah... it is calling me 48247 and we don't see the cvs commit messages,
not good,

I do hope that it DOES check the stuff though :(

(yes it does I just checked)

in the mean time I guess it means no cvs commit messages :(

marcf




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