Which version of JBoss is that? Please try a 3.2.2RCx
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Paulo Bengero
Sent: vendredi, 15. août 2003 03:15
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JBoss Web Console
Message: 4
Date: Thu,
Sacha, thank you. I downloaded the 3.2.2 and I found the file.
Could I say that if I want to run a new instance of Jboss
named 'test', I
can copy the default folder as test, uncomment the
ServiceBindingManager
in
jboss-service.xml of the test folder, specifying the
'ServerName' I
On Thu, 14 Aug 2003 19:52:55 +0300, Alexey Loubyansky [EMAIL PROTECTED]
wrote:
Hello Stefan,
it should not happen. First, a table is created. Then, foreign key
constraints are generated only if the related table exists.
What JBoss version you are using?
Hi Alex,
Im using the
---
www.cnjx.cn
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio
In the invoker-proxy-binding configuration I still have the following
stanzas under proxy-factory-config:
MaximumSize15/MaximumSize
MaxMessages1/MaxMessages
I wasn't exactly sure what the MaximumSize was doing so I just left it at
15. So, if I switch MaximumSize to 1, this may give me the
Hi Sasha,
That was what I thought as well at some point but my jboss.xml is the
following:
jboss
enterprise-beans
!--
To add beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called jboss-beans.xml that
contains
the
OK, so check your JBoss.xml file as in the current setup you are *not* using
clustering: the invoker is the standard JRMP invoker, not the HA-JRMP
invoker.
Cheers,
sacha
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Simone Milani
Sent:
The JMS specification explicitly states that no assumptions about message delivery order should be made. You have to implement you own delivery order tracking logic ( normally based on tracking the ascending message ID and usage of some kind of message buffering in case of unordered message
Hi Sacha,
It is a SLSB and here is the stack trace of the call:
10:43:21,773 ERROR [LogInterceptor] RuntimeException:
java.lang.RuntimeException: Test
at
com.db.gm.mercury.ejb.session.test.TestBean.getPrimeAtPosition(Unknown
Source)
at
Thanks
for the input, and yes I was aware that you cannot assume any message
ordering. What I am referring to is slightly different and I'm not sure
what the spec has aboutMDBretry implementations. I was
expecting the retry of the messageto be in the same thread as the one that
original
Yes, you have changed the configuration-name and build your own which is now
incompatible with clustering! You should extend the clustered configuration
when building Standard Stateless SessionBean with Security, not inherits
from the default non-clustered one.
-Original Message-
From:
So you're wait is really on the mdb pool not the session pool.
The session pool wait is still there.
You probably still have the default 15 sessions in the pool?
Under load, this will mean you have 1 session delivering its message and
14 waiting for the single instance mdb. Each of those 14
Hello Simone,
Apologies if I am confusing things. I have a Stateless
Session EJB
declared now as
clusteredtrue/clustered.
The code I am running is the following:
TestHome testHome = (TestHome) javax.rmi.PortableRemoteObject.narrow(
ctx.lookup(EJB/Session/Test),
Hi Adrian, Alexy,
The
version of JBoss is 3.0.7 and database I am using is Sybase7.0.3.
I can
explain the scenario in a general way.
The first
scenario I explained is resolved. Actually I had to try only a work
around.
The
solution is set a flag after the ejbCreate(). So in ejbStore() I check
Hi Sacha,
Apologies if I am confusing things. I have a Stateless Session EJB
declared now as
clusteredtrue/clustered.
The code I am running is the following:
TestHome testHome = (TestHome) javax.rmi.PortableRemoteObject.narrow(
ctx.lookup(EJB/Session/Test),
TestHome.class);
Ah, of course. I forgot you can do this in JBoss!
I was going to suggest that JBoss was creating multiple MDB instances
and you were just seeing the effect of having them both process the
incoming messages, but given your config and what Adrian has been
saying it seems I would have been wrong.
Thanks for the info. The jboss-service.xml that sets this incorrectly comes
with the examples from JBoss, Also, I had to add
public void init(Class beanHome, Class beanRemote, Class beanLocalHome,
Class beanLocal, Object securityMgr) throws
InstantiationException
to
On Fri, 2003-08-15 at 13:45, Barlow, Dustin wrote:
In the invoker-proxy-binding configuration I still have the following
stanzas under proxy-factory-config:
MaximumSize15/MaximumSize
MaxMessages1/MaxMessages
I wasn't exactly sure what the MaximumSize was doing so I just left it at
15.
Setting the MaximumSize to 1 does indeed fix the problem, or at least masks
it.
Now, this begs the question of since there is a complete rewrite of JMS in
the 4.0 series, and I am planning to upgrade from the 3.2 series to 4 series
to utilize the new JBossDO implementation, will this same
Hi Sacha,
Thanks very much! It works.
Would it not be a good idea then to throw an error when using a clustered
declared EJB within a non cluster enabled container?
Cheers
Simone
- Original Message -
From: Sacha Labourey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August
On Fri, 2003-08-15 at 16:38, Barlow, Dustin wrote:
Setting the MaximumSize to 1 does indeed fix the problem, or at least masks
it.
Now, this begs the question of since there is a complete rewrite of JMS in
the 4.0 series, and I am planning to upgrade from the 3.2 series to 4 series
to
You're probably running an old JDK. Try installing the latest Java Plug-In from Sun
(http://www.java.com/en/index.jsp).
James
--
James Clover
Lead Engineer, Services Oriented Architecture
james -dot- clover -at- disney -dot- com
-Original Message-
From: Sacha Labourey
JBoss4 implements the integration using JCA1.5 MessageEndpoint
The ConnectionConsumer is no longer used.
You should consider JBoss4 alpha quality software.
And I do. However, that doesn't answer the question of retry behaviour for
MDBs in 4.0. Basically will the implementation in 4.0 for
(B
(B[EMAIL PROTECTED]:GE,!*!*!!%S%8%M%9%^%s$N%5%$%I%S%8%M%9$K$b!*!*(B
(B $B>pJs$OAa$$$b$N>!$A!*!*(B
(B [EMAIL PROTECTED]"$J$?$b;E;v$r$J$/$7:#LdBj$K$J$C$F$$$k(B
$B!!0G6bM;[EMAIL PROTECTED];$s!#(B
$B$3$s$J;~$3$=$=$l$KHw$($FpJsHNGd([EMAIL
On Fri, 2003-08-15 at 19:59, Barlow, Dustin wrote:
JBoss4 implements the integration using JCA1.5 MessageEndpoint
The ConnectionConsumer is no longer used.
You should consider JBoss4 alpha quality software.
And I do. However, that doesn't answer the question of retry behaviour for
MDBs
I've been attempting to get security turned on for a project and have
gotten stumped.
I can get the principal and creds back to the ejb server from my test
java client. It
will even authenticate off of the jboss.UsersRolesLoginModule and/or my
own login module correctly. But for the life of
Adrian Brock wrote:
The order of work is roughly:
1) receive()
2) getSession() and enlist in tx
3) getMDB()
4) onMessage()
5) releaseMDB()
6) commitSession()
Why couldn't the commitSession() be done prior to releaseMDB()? Seems that
if 5 and 6 were flipped, the overall behaviour would be the
e-maili duzgun olarak
goruntuleyemiyorsaniz lutfen buraya tiklayiniz
yibmtzh
wwu dvucajha uecl hwzjtckktms
ogsdqme o
fazxunhnefnfjifv c a b xhlad
aa rpqiemg
nvolusoihjufi wirw
yqanddzjuqxpzic izws cnhbbagwye
xywd nzcqbnhqiz jplw idpbs
gnhc
Hi all,
Please visit our new open-source software development site.
http://www.objectsdevelopment.com
_
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
29 matches
Mail list logo
