RE: [JBoss-user] JBoss Web Console

[Sacha Labourey]

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, 14 Aug 2003 09:12:26 -0500
 From: Stephen Davidson [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] JBoss Web Console
 To: [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 
 Paulo Bengero wrote:
  Have anyone of you used the JBoss web-console? You can 
 access this through
  (assuming localhost is your test server ) 
 http://localhost:8080/web-console/ .
 
  When i pasted that in my url the applet on the left side 
 didn't appear because
  of this exception:
 
  http://localhost:8080/web-console/Invoker 
 java.lang.NoClassDefFoundError:
  com/sun/net/ssl/HttpsURLConnectionat 
 org.jboss.console.remote.Util.
 invoke(Util.java:48)at org.jboss.console.remote.
 
 AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:50)
 at
  
 org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.
  java:104)at org.jboss.console.navtree.ConsoleTreeModel.
 init(ConsoleTreeModel.java:59)   at 
 org.jboss.console.navtree.
AdminTreeBrowser.init(AdminTreeBrowser.java:63) at 
 org.jboss.console.
  navtree.AppletBrowser.start(AppletBrowser.java:51)  at 
 sun.applet.
   AppletPanel.run(Unknown Source)   at 
 java.lang.Thread.run(Unknown Source)
 
  Care to give some help?
 
 
  
  Paulo A. Bengero
  Application Systems Engineer
  Team ORION
  
 Hi Paulo.
 
 Are you using IE/Microsoft JVM combo by any chance?
 There is a way to check, by bringing up the applet
 window in Internet Explorer.  Unfortunately, its been
 so long since I have used IE that I have forgotten
 how to do so.
 
 If you are using MS Java in your browser, you may want
 to look at installing Sun's JVM in place of the one that
 MS has foisted by default on you.
 
 Regards,
 Steve
 
 Ive already done that Steveany more suggestions? This 
 error (java.lang.
 NoClassDefFoundError:
  com/sun/net/ssl/HttpsURLConnection ) is still bugging me. 
 Do i need to add
 any jars or something in my classpath? Anyone out there who 
 has successfully
 used the JBoss WEB Console?
 
 
 Paulo A. Bengero
 Application Systems Engineer
 Team ORION
 
 
 



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

RE: [JBoss-user] Creating a new instance of JBoss

[Sacha Labourey]

  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 want
 to
  run (i.e. port-01, port-02 and so on) and execute the run 
 program passing
  'test' as parameter?

Yes (but why don't you simply try it?)



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Re: [JBoss-user] Deployment Problem: Creating fk-constraints before creating tables...???

[Stefan Schubert]

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 jboss-3.2.0_tomcat-4.1.24 Bundle. Do you know how jboss 
processes the creation process? I thing it parses the cmp-Entries of the 
Entity Bean, and next looks up in the relations section for any cmr-fields 
belonging to the entity and assembles that the create statement.

From what I have seen I guess that jboss tries than to establish the fk- 
constraints belonging to this table, even when the other Beans (i.e. 
Tables) have not bean created yet.
Meanwhile I have rearanged the order in the ejb-jar to fullfill some 
dependencies in this thought creation order. However I haven't come to 
recreate the db-user yet, I will try this over the weekend and will post 
the result log entry in case there are still problems.

Cheers,

Stefan







---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] www.cnjx.cn

[chnmachine]

---



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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

RE: [JBoss-user] MDB Singleton retry semantics

[Barlow, Dustin]

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 behaviour I'm
looking for?

I still am a bit fuzzy on the part where if the retry implementation is just
simply pushing the message back onto the source queue, then there would be
no way to guarantee that no other messages would be in front of that
reposted message correct?  Or am I misunderstanding the MDB retry
implementation in JBossMQ? 

Dustin

 -Original Message-
 From: Adrian Brock [mailto:[EMAIL PROTECTED]
 Sent: Friday, August 15, 2003 6:58 AM
 To: [EMAIL PROTECTED]
 Subject: RE: [JBoss-user] MDB Singleton retry semantics
 
 
 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 sessions
 will have a message attached.
 
 Regards,
 Adrian
 
 On Thu, 2003-08-14 at 21:13, Barlow, Dustin wrote:
  In conf/standardjboss.xml I setup a new invoker-proxy-binding and a
  container-configuration.  Part of the 
 container-configuration includes the
  following stanzas:
  
  container-pool-conf
MaximumSize1/MaximumSize
MinimumSize1/MinimumSize
strictMaximumSizetrue/strictMaximumSize
  /container-pool-conf 
  
  The MDB is deployed using the new invoker-proxy-binding and
  container-configuration and does only consume one message 
 at a time as long
  as there isn't a container transaction rollback.
  
  BTW: I'm using JBoss 3.2.2RC2.
  
  Dustin
  
  -Original Message-
  From: [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: 8/14/2003 2:27 PM
  Subject: RE: [JBoss-user] MDB Singleton retry semantics
  
  How are you enforcing the singleton?
 -- 
  
 Adrian Brock
 Director of Support
 Back Office
 JBoss Group, LLC 
  
 
 
 
 ---
 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 .NET.
 http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet
 _072303_01/01
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user
 


---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Re: [JBoss-user] Load-Balancing Problems

[Simone Milani]

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 session/session, entity/entity and
message-driven/message-driven
   markup for those beans.
 --

  session
 ejb-nameTest/ejb-name
 jndi-nameEJB/Session/Test/jndi-name
 local-jndi-nameEJB/Session/Local/Test/local-jndi-name
 configuration-nameStandard Stateless SessionBean with
Security/configuration-name
 clusteredtrue/clustered
  /session

   /enterprise-beans

   resource-managers
   /resource-managers

 container-configurations
  container-configuration extends=Instance Per Transaction CMP 2.x
EntityBean
 container-nameOptimistic CMP 2.x EntityBean/container-name

locking-policyorg.jboss.ejb.plugins.lock.JDBCOptimisticLock/locking-polic
y
 sync-on-commit-onlytrue/sync-on-commit-only
  /container-configuration
container-configuration extends=Standard Stateless SessionBean
 container-nameStandard Stateless SessionBean with
Security/container-name
 security-domainjava:/jaas/tsar/security-domain
  /container-configuration
   /container-configurations

/jboss
And the partition as the default name.
Any idea?

Thanks!!!

Simone

- Original Message - 
From: Sacha Labourey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August 15, 2003 12:57 PM
Subject: RE: [JBoss-user] Load-Balancing Problems


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: vendredi, 15. août 2003 11:46
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] Load-Balancing Problems


 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
 orImpl.java:39
 )
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at
 org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.i
 nvoke(Stateles
 sSessionContainer.java:646)
 at
 org.jboss.resource.connectionmanager.CachedConnectionIntercept
 or.invoke(Cach
 edConnectionInterceptor.java:186)
 at
 org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invo
 ke(StatelessSe
 ssionInstanceInterceptor.java:72)
 at
 org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(Abstrac
 tTxInterceptor
 .java:84)
 at
 org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxI
 nterceptorCMT.
 java:243)
 at
 org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT
 .java:104)
 at
 org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInter
 ceptor.java:11
 7)
 at
 org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
 at
 org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(Pro
 xyFactoryFinde
 rInterceptor.java:122)
 at
 org.jboss.ejb.StatelessSessionContainer.internalInvoke(Statele
 ssSessionConta
 iner.java:323)
 at org.jboss.ejb.Container.invoke(Container.java:700)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
 java:39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec
 tedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:550)
 at
 org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:
 362)
 at
 sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at
 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
 at sun.rmi.transport.Transport$1.run(Transport.java:148)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
 at
 sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport
 .java:460)
 at
 

RE: [JBoss-user] Load-Balancing Problems

[Sacha Labourey]

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: vendredi, 15. août 2003 11:46
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] Load-Balancing Problems
 
 
 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
 orImpl.java:39
 )
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at
 org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.i
 nvoke(Stateles
 sSessionContainer.java:646)
 at
 org.jboss.resource.connectionmanager.CachedConnectionIntercept
 or.invoke(Cach
 edConnectionInterceptor.java:186)
 at
 org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invo
 ke(StatelessSe
 ssionInstanceInterceptor.java:72)
 at
 org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(Abstrac
 tTxInterceptor
 .java:84)
 at
 org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxI
 nterceptorCMT.
 java:243)
 at
 org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT
 .java:104)
 at
 org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInter
 ceptor.java:11
 7)
 at
 org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
 at
 org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(Pro
 xyFactoryFinde
 rInterceptor.java:122)
 at
 org.jboss.ejb.StatelessSessionContainer.internalInvoke(Statele
 ssSessionConta
 iner.java:323)
 at org.jboss.ejb.Container.invoke(Container.java:700)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
 java:39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec
 tedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:550)
 at
 org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:
 362)
 at 
 sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at
 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
 at sun.rmi.transport.Transport$1.run(Transport.java:148)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
 at
 sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport
 .java:460)
 at
 sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTr
 ansport.java:7
 01)
 at java.lang.Thread.run(Thread.java:534)
 
 
 
 Thanks!
 
 
 Simone
 
 
 
 ---
 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 .NET.
 http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet
 _072303_01/01
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user
 
 
 ---
 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 .NET.
 http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet
 _072303_01/01
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user
 
 
 



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Antwort: RE: [JBoss-user] MDB Singleton retry semantics

[ulf . schroeter]

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 delivery... I know that it's weird to buffer messages that are already buffered :-) 

Relying on the current JBOSS specific implementation behaviour will lead to a unportable / unreliable solution. 

Regards 
Ulf
 






Barlow, Dustin [EMAIL PROTECTED]
Gesendet von: [EMAIL PROTECTED]
14.08.2003 22:33
Bitte antworten an jboss-user


An:'[EMAIL PROTECTED] ' [EMAIL PROTECTED]
Kopie:
Thema:RE: [JBoss-user] MDB Singleton retry semantics


I guess it isn't obvious to me why is readahead important in terms of
efficiency of queue message consumption. Can you elaborate?

Is it possible to configure the container to wait for the ServerSession in
this case? I have already defined a separate invoker-binding and a
container-config for this bean, so I could isolate it to just the singleton
MDB.

I am not sure that having it wait for the ServerSession and then consume the
message would solve the problem. If the retry behaviour of the container is
simply consuming the message and then pushing the message back onto the
source queue again, this still wouldn't guarantee that other messages
wouldn't be in front of that reposted message correct?

Thanks for the help, 

Dustin 


-Original Message-
From: Adrian Brock
To: [EMAIL PROTECTED]
Sent: 8/14/2003 3:11 PM
Subject: Re: [JBoss-user] MDB Singleton retry semantics

That isn't the way it currently works.

The ConnectorConsumer immediatley retrieves the next message
from the queue then waits for a ServerSession from the pool.

Once you've nacked the failed message back into the queue, it will
process the waiting message using the freed session.

It will then ask the queue for the next message which will
be the one you nacked.

To make it work the way you want the ConnectionConsumer
would have to work in the opposite order.
Instead of receiving message(s) and waiting for a
ServerSession. It would wait for a ServerSession then
receive the message.
This is obviously less efficient in the normal use case,
you lose the readahead of the messages.

Regards,
Adrian

On Thu, 2003-08-14 at 19:00, Barlow, Dustin wrote:
 I have a singleton CMT MDB consuming on a JMS queue with a retry
threshold
 set to 3 attempts. I made the assumption that no other messages on
the
 queue would be consumed until the current message being processed
either
 finishes and is consumed, or in the event of a container transaction
 rollback and the retry threshold is reached, the message is consumed
off the
 source queue and pushed to the DLQ.
 
 However, the behaviour I'm seeing is that on the retry, other messages
 sitting on the queue are consumed prior to the retry occurring. The
 singleton is working in terms of only one message at a time being
processed,
 however the retry semantic seems odd to me in that it appears like the
 implementation of the retry logic is just simply pushing the message
back on
 the queue to be consumed again in a different thread later on. 
 
 Is this correct? If so, how do I change that behaviour so that no
other
 messages on the queue are triggered until the message completes its
 processing either by consumed normally, or by being consumed and
pushed to
 the DLQ once the retry threshold is reached?
 
 Dustin
 
 
 ---
 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 .NET.

http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01
/01
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user
-- 
 
Adrian Brock
Director of Support
Back Office
JBoss Group, LLC 
 



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01
/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___

Re: [JBoss-user] Load-Balancing Problems

[Simone Milani]

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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(Stateles
sSessionContainer.java:646)
at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(Cach
edConnectionInterceptor.java:186)
at
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSe
ssionInstanceInterceptor.java:72)
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor
.java:84)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.
java:243)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:104)
at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:11
7)
at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
at
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinde
rInterceptor.java:122)
at
org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionConta
iner.java:323)
at org.jboss.ejb.Container.invoke(Container.java:700)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:550)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:
362)
at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:7
01)
at java.lang.Thread.run(Thread.java:534)



Thanks!


Simone



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

RE: Antwort: RE: [JBoss-user] MDB Singleton retry semantics

[Barlow, Dustin]

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 consumed the message. This doesn't seem to be the case. 
Instead, it appears that the message is just posted back onto the queue, 
reconsumed at a later time in a different "thread", then rinse and repeat until 
the retry threshold is met.

What 
JBoss specific implementation behaviour are you referring 
to?

Dustin

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]Sent: Friday, August 15, 2003 
  7:26 AMTo: [EMAIL PROTECTED]Subject: 
  Antwort: RE: [JBoss-user] MDB Singleton retry 
  semanticsThe 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 delivery... I know that 
  it's weird to buffer messages that are already buffered :-) 
  Relying on the current JBOSS 
  specific implementation behaviour will lead to a unportable / unreliable 
  solution. Regards Ulf  
   
  


  
  "Barlow, Dustin" 
[EMAIL PROTECTED] Gesendet von: 
[EMAIL PROTECTED] 
14.08.2003 22:33 Bitte antworten an jboss-user 
  An:   
 "'[EMAIL PROTECTED] '" 
[EMAIL PROTECTED] Kopie:   

  Thema:RE: [JBoss-user] MDB 
Singleton retry semanticsI guess it isn't obvious to me why is "readahead" 
  important in terms ofefficiency of queue message consumption. Can 
  you elaborate?Is it possible to configure the container to wait for 
  the ServerSession inthis case? I have already defined a separate 
  invoker-binding and acontainer-config for this bean, so I could isolate it 
  to just the singletonMDB.I am not sure that having it wait for the 
  ServerSession and then consume themessage would solve the problem. 
  If the retry behaviour of the container issimply consuming the 
  message and then pushing the message back onto thesource queue again, this 
  still wouldn't guarantee that other messageswouldn't be in front of that 
  reposted message correct?Thanks for the help, Dustin 
  -Original Message-From: Adrian BrockTo: 
  [EMAIL PROTECTED]Sent: 8/14/2003 3:11 PMSubject: Re: 
  [JBoss-user] MDB Singleton retry semanticsThat isn't the way it 
  currently works.The ConnectorConsumer immediatley retrieves the next 
  messagefrom the queue then waits for a ServerSession from the 
  pool.Once you've nacked the failed message back into the queue, it 
  willprocess the waiting message using the freed session.It will 
  then ask the queue for the next message which willbe the one you 
  nacked.To make it work the way you want the 
  ConnectionConsumerwould have to work in the opposite order.Instead of 
  receiving message(s) and waiting for aServerSession. It would wait for a 
  ServerSession thenreceive the message.This is obviously less efficient 
  in the normal use case,you lose the "readahead" of the 
  messages.Regards,AdrianOn Thu, 2003-08-14 at 19:00, 
  Barlow, Dustin wrote: I have a singleton CMT MDB consuming on a JMS 
  queue with a retrythreshold set to 3 attempts. I made the 
  assumption that no other messages onthe queue would be consumed 
  until the current message being processedeither finishes and is 
  consumed, or in the event of a container transaction rollback and the 
  retry threshold is reached, the message is consumedoff the source 
  queue and pushed to the DLQ.  However, the behaviour I'm 
  seeing is that on the retry, other messages sitting on the queue are 
  consumed prior to the retry occurring. The singleton is working 
  in terms of only one message at a time beingprocessed, however the 
  retry semantic seems odd to me in that it appears like the 
  implementation of the retry logic is just simply pushing the messageback 
  on the queue to be consumed again in a different "thread" later on. 
Is this correct? If so, how do I change that behaviour 
  so that noother messages on the queue are triggered until the 
  message completes its processing either by consumed normally, or by 
  being consumed andpushed to the DLQ once the retry threshold is 
  reached?  Dustin   
  --- 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 
  .NET.http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 
  ___ JBoss-user mailing 
  list [EMAIL PROTECTED] 
  

RE: [JBoss-user] Load-Balancing Problems

[Sacha Labourey]

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: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Simone Milani
 Sent: vendredi, 15. août 2003 14:41
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] Load-Balancing Problems
 
 
 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 session/session, entity/entity and
 message-driven/message-driven
markup for those beans.
  --
 
   session
  ejb-nameTest/ejb-name
  jndi-nameEJB/Session/Test/jndi-name
  local-jndi-nameEJB/Session/Local/Test/local-jndi-name
  configuration-nameStandard Stateless SessionBean with
 Security/configuration-name
  clusteredtrue/clustered
   /session
 
/enterprise-beans
 
resource-managers
/resource-managers
 
  container-configurations
   container-configuration extends=Instance Per 
 Transaction CMP 2.x
 EntityBean
  container-nameOptimistic CMP 2.x 
 EntityBean/container-name
 
 locking-policyorg.jboss.ejb.plugins.lock.JDBCOptimisticLock
/locking-polic
 y
  sync-on-commit-onlytrue/sync-on-commit-only
   /container-configuration
 container-configuration extends=Standard Stateless 
 SessionBean
  container-nameStandard Stateless SessionBean with
 Security/container-name
  security-domainjava:/jaas/tsar/security-domain
   /container-configuration
/container-configurations
 
 /jboss
 And the partition as the default name.
 Any idea?
 
 Thanks!!!
 
 Simone
 
 - Original Message - 
 From: Sacha Labourey [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Friday, August 15, 2003 12:57 PM
 Subject: RE: [JBoss-user] Load-Balancing Problems
 
 
 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: vendredi, 15. août 2003 11:46
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-user] Load-Balancing Problems
 
 
  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 
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
  orImpl.java:39
  )
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
  odAccessorImpl
  .java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at
  org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.i
  nvoke(Stateles
  sSessionContainer.java:646)
  at
  org.jboss.resource.connectionmanager.CachedConnectionIntercept
  or.invoke(Cach
  edConnectionInterceptor.java:186)
  at
  org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invo
  ke(StatelessSe
  ssionInstanceInterceptor.java:72)
  at
  org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(Abstrac
  tTxInterceptor
  .java:84)
  at
  org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxI
  nterceptorCMT.
  java:243)
  at
  org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT
  .java:104)
  at
  org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInter
  ceptor.java:11
  7)
  at
  org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
  at
  org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(Pro
  xyFactoryFinde
  rInterceptor.java:122)
  at
  org.jboss.ejb.StatelessSessionContainer.internalInvoke(Statele
  ssSessionConta
  iner.java:323)
  at org.jboss.ejb.Container.invoke(Container.java:700)
  at 
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
  
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
  java:39)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
  odAccessorImpl
  .java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec
  tedMBeanDispat
  cher.java:284)
  at
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:550)
  at
  
 

RE: [JBoss-user] MDB Singleton retry semantics

[Adrian Brock]

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 sessions
will have a message attached.

Regards,
Adrian

On Thu, 2003-08-14 at 21:13, Barlow, Dustin wrote:
 In conf/standardjboss.xml I setup a new invoker-proxy-binding and a
 container-configuration.  Part of the container-configuration includes the
 following stanzas:
 
 container-pool-conf
   MaximumSize1/MaximumSize
   MinimumSize1/MinimumSize
   strictMaximumSizetrue/strictMaximumSize
 /container-pool-conf 
 
 The MDB is deployed using the new invoker-proxy-binding and
 container-configuration and does only consume one message at a time as long
 as there isn't a container transaction rollback.
 
 BTW: I'm using JBoss 3.2.2RC2.
 
 Dustin
 
 -Original Message-
 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: 8/14/2003 2:27 PM
 Subject: RE: [JBoss-user] MDB Singleton retry semantics
 
 How are you enforcing the singleton?
-- 
 
Adrian Brock
Director of Support
Back Office
JBoss Group, LLC 
 



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

RE: [JBoss-user] Load-Balancing Problems

[Sacha Labourey]

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),
TestHome.class);
 
   Test test = testHome.create();
   System.out.println(Hello:  + test.hello());
   for(int i = 0; i  200; i++)
   {
Integer myPrime = test.getPrimeAtPosition(i);
System.out.println(Thread  + 
 Thread.currentThread().getName() +
:\tPrime @ position + i +:  + myPrime);
   }
 
 And all the calls get sent to the same member.

Is that a SLSB or a SFSB? Could you please modify your EJB implementation
(the getPrimeAtPosition method) and instead of computing something simply
do something like throw new RuntimeException(); or something bad like that
and then send me both the exception that you see on the client and on the
server side.

Cheers,



Sacha



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Re: [JBoss-user] ejbCreate() followed by ejbStore() locks, EntityBean!!!

[Muraly R]

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
whether the flag is set, then don't execute the contents of ejbStore().
Please suggest if this work around has any effects. As I see it since,
the data has been inserted in to the DB, the additional update is an
overhead. Please bear my ignorance;-)
The next
scenario I am facing is also with the ejbStore. But here there is no
preceding ejbCreate(). Here it is a setXXX() method which updates the
VO.
Putting
this both scenario's and their behavior, I think its the level of locking
with the DB.

But I am
not able to pinpoint the source of error. Actually I am new to this
platform itself but I am catching up:-). 
Could you
please tell where should I look :
1. for the isolation level(may be I know it, but not familiar with the
term)
2. what is the locking mechanism used?

Thanks for the EXCELLENT Support,
Muraly



At 11:13 14/08/2003 +0300, Alexey Loubyansky wrote:
Hello Muraly,

I am sorry, I would like to help you, but I can't understand what
you
are writting about. Could you rewrite it with EJB terms or post a
testcase reproducing the problem?
Also, please, let us know what JBoss version and database you are
using.

alex

Thursday, August 14, 2003, 9:36:11 AM, Muraly R wrote:

 Hi Gurus,
 I am having a
strange scenario.
 Here I have a Table,
which stores the interfaces of a device.
 When I first
 add the device the trnasaction gets complted successfully.
 In the next
transaction, when I update the device with a new interface,
 and start a transaction to update device details, I can see all the

 existing interface updated correctly. Plus the new interface been
added to 
 the database.
 Here start the
probs.
 Immediatly after the
ejbCreate() for the new interface a call for 
 ejbStore() starts.
 Here a prepared
statement is created and sets the necessary value.
 But the point of
execution, stmt.executeUpdate(), the whole code flow is 
 stuck.
 I tried various
options like 'Insatnce per Transaction EntiyBean' for the 
 EntityBean.

 Could some please
tell me what could I do wrong?

 Cheers
 Muraly



 ---
 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 .NET.

http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]

https://lists.sourceforge.net/lists/listinfo/jboss-user



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Re: [JBoss-user] Load-Balancing Problems

[Simone Milani]

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);

  Test test = testHome.create();
  System.out.println(Hello:  + test.hello());
  for(int i = 0; i  200; i++)
  {
   Integer myPrime = test.getPrimeAtPosition(i);
   System.out.println(Thread  + Thread.currentThread().getName() +
   :\tPrime @ position + i +:  + myPrime);
  }

And all the calls get sent to the same member.

Any idea?

Thanks

Simone
- Original Message - 
From: Sacha Labourey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 14, 2003 5:07 PM
Subject: RE: [JBoss-user] Load-Balancing Problems


What kind of EJB is that?

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Simone Milani
 Sent: jeudi, 14. août 2003 16:52
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] Load-Balancing Problems


 Hi,

 I use 3.2.2RC2 and the default config for round robin.
 to have the call
 span the whole cluster in round robin I need to lookup the
 home every time
 which is not very efficient.  I would like to do the lookup
 and the create
 only one and do round robin after that.  Is it possible?

 Thanks!

 Simone
 - Original Message - 
 From: Sacha Labourey [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, August 13, 2003 8:28 AM
 Subject: RE: [JBoss-user] Load-Balancing Problems


 Then that is very strange as with 3.2.x you should be able to
 re-create your
 home/remote and keep balancing correctly.

  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of
  Christofer Dutz
  Sent: mercredi, 13. août 2003 00:18
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-user] Load-Balancing Problems
 
 
  I am using 3.2.2RC2 ...
 
  Chris
 
  Sacha Labourey wrote:
 
  ... Or use 3.2.x which removes this issue.
  
  
  
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of
  Adrian Brock
  Sent: mardi, 12 août 2003 17:50
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-user] Load-Balancing Problems
  
  
  You are probably doing sessionHome.create() on every request?
  
  This creates a new remote interface proxy, which will
  round-robin all servers. However if you only do one
  invocation it will always use the first server and never get
  to the others.
  
  You can get similar problems with other patterns in your
  RemoteInterface usage depending upon how many servers you have.
  
  One simple solution is to use RandomRobin rather than
  RoundRobin as the load balancing policy.
  
  Regards,
  Adrian
  
  On Tue, 2003-08-12 at 10:41, Christofer Dutz wrote:
  
  
  Hi,
  
  I am having some Problems with load-balancing in JBoss.
  All Beans are set to use the RoundRobin Load-Balancing
  strategy and
  the
  cluster seems to work like a charm.
  I setup the HA-JNDI to work on Port 1100 and setup the
  
  
  client to use
  
  
  this port. Everything seems to work fine, except one thing.
  If I watch the load of the cluster-machines with top I
  
  
  can see the
  
  
  machine that is directly accessed by the Client-Application
  has a load of 100% the other cluster nodes then are only
  
  
  30%. Mabe I'm
  
  
  wrong, but I think that it could be, that the client proxy
  is doing no load-balancing at all and that the 30% are just
  
  
  for syncing.
  
  
  Any Ideas of how I could balance the load over all nodes?
  Any help is realy appreciated.
  
  Christofer Dutz
  
  
  
  
  ---
  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 .NET.
  
  
  
  http://aspnet.click-
  url.com/go/psa0013ave/direct;at.aspnet_072303_
  
  
  01/01
  ___
  JBoss-user mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-user
  
  
  
  ---
  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 .NET.
  http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet
  
  
  _072303_01/01
  ___
  JBoss-user mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-user
  
  
  
  
  
  
  ---
  This SF.Net email sponsored by: Free pre-built ASP.NET sites
  including
  Data Reports, E-commerce, Portals, and Forums are available now.
  Download 

RE: [JBoss-user] MDB Singleton retry semantics

[Danny . Yates]

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.

Rgds,

Dan.

-- 
Danny Yates
 


-Original Message-
From: Barlow, Dustin [mailto:[EMAIL PROTECTED] 
Sent: 14 August 2003 21:14
To: '[EMAIL PROTECTED] '
Subject: RE: [JBoss-user] MDB Singleton retry semantics


In conf/standardjboss.xml I setup a new invoker-proxy-binding and a
container-configuration.  Part of the container-configuration includes the
following stanzas:

container-pool-conf
  MaximumSize1/MaximumSize
  MinimumSize1/MinimumSize
  strictMaximumSizetrue/strictMaximumSize
/container-pool-conf 

The MDB is deployed using the new invoker-proxy-binding and
container-configuration and does only consume one message at a time as long
as there isn't a container transaction rollback.

BTW: I'm using JBoss 3.2.2RC2.

Dustin

-Original Message-
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: 8/14/2003 2:27 PM
Subject: RE: [JBoss-user] MDB Singleton retry semantics

How are you enforcing the singleton?

-- 
Danny Yates
 


-Original Message-
From: Barlow, Dustin [mailto:[EMAIL PROTECTED] 
Sent: 14 August 2003 19:00
To: [EMAIL PROTECTED]
Subject: [JBoss-user] MDB Singleton retry semantics


I have a singleton CMT MDB consuming on a JMS queue with a retry
threshold
set to 3 attempts.  I made the assumption that no other messages on the
queue would be consumed until the current message being processed either
finishes and is consumed, or in the event of a container transaction
rollback and the retry threshold is reached, the message is consumed off
the
source queue and pushed to the DLQ.

However, the behaviour I'm seeing is that on the retry, other messages
sitting on the queue are consumed prior to the retry occurring.  The
singleton is working in terms of only one message at a time being
processed,
however the retry semantic seems odd to me in that it appears like the
implementation of the retry logic is just simply pushing the message
back on
the queue to be consumed again in a different thread later on. 

Is this correct?  If so, how do I change that behaviour so that no other
messages on the queue are triggered until the message completes its
processing either by consumed normally, or by being consumed and pushed
to
the DLQ once the retry threshold is reached?

Dustin


---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01
/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


_ 
Notice to recipient: 
The information in this internet e-mail and any attachments is
confidential
and may be privileged. It is intended solely for the addressee. If you
are
not the intended addressee please notify the sender immediately by
telephone. If you are not the intended recipient, any disclosure,
copying,
distribution or any action taken or omitted to be taken in reliance on
it,
is prohibited and may be unlawful. 

When addressed to external clients any opinions or advice contained in
this
internet e-mail are subject to the terms and conditions expressed in any
applicable governing terms of business or client engagement letter
issued by
the pertinent Bank of America group entity. 

If this email originates from the U.K. please note that Bank of America,
N.A., London Branch, Banc of America Securities Limited and Banc of
America
Futures Incorporated are regulated by the Financial Services Authority.
_ 




---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01
/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]

RE: [JBoss-user] Trying to run SecurityProxy example from JBoss AD

[Steven Harris]

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 EchoSecurityProxy to get it to compile.

-Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2003 7:04 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Trying to run SecurityProxy example from JBoss
AD


It should be:

jboss.security:service=SecurityConfig

Regards,
Adrian

On Thu, 2003-08-14 at 22:38, Steven Harris wrote:
 I'm trying chapter 8 example1 of JBoss AD. It seems to have built the jar
 and sar correctly, but it fails with InstanceNotFoundException:
 jboss.security:name=SecurityConfig is not registered.
  
 The jboss-service.xml in the sar defines the MBean:
 - mbean code=org.jboss.chap8.service.SecurityConfig
 name=jboss.docs.chap8:service=LoginConfig-EX1 
 attribute name=AuthConfigMETA-INF/login-config.xml/attribute 
 attribute
 name=SecurityConfigNamejboss.security:name=SecurityConfig/attribute 
 /mbean 
 
 Here's the console.
 
 8,268 INFO  [MainDeployer] Starting deployment of package:
 file:/C:/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/chap8-ex1.jar
 8,278 INFO  [EJBDeployer] nested deployment:

file:/C:/jboss-3.2.1_tomcat-4.1.24/server/default/tmp/deploy/server/default/
 deploy/chap8-ex1.jar/46.chap8-ex1.jar-contents/chap8-ex1.sar
 8,308 INFO  [SecurityConfig] Creating
 8,308 INFO  [SecurityConfig] Created
 8,639 INFO  [EjbModule] Creating
 8,659 INFO  [EjbModule] Deploying EchoBean
 8,689 INFO  [JaasSecurityManagerService] Created
 [EMAIL PROTECTED]
 8,689 INFO  [JaasSecurityManagerService] setCachePolicy,
 [EMAIL PROTECTED]
 8,689 INFO  [JaasSecurityManagerService] Added chap8-ex1,
 [EMAIL PROTECTED] to map
 8,699 INFO  [StatelessSessionContainer] Creating
 8,709 INFO  [StatelessSessionInstancePool] Creating
 8,709 INFO  [StatelessSessionInstancePool] Created
 8,709 INFO  [SecurityProxyInterceptor] Initialized
 [EMAIL PROTECTED]
 8,709 INFO  [StatelessSessionContainer] Created
 8,709 INFO  [EjbModule] Created
 8,709 INFO  [SecurityConfig] Starting
 8,709 INFO  [SecurityConfig] Using JAAS AuthConfig:

jar:file:/C:/jboss-3.2.1_tomcat-4.1.24/server/default/tmp/deploy/server/defa

ult/deploy/chap8-ex1.jar/46.chap8-ex1.jar-contents/chap8-ex1.sar!/META-INF/l
 ogin-config.xml
 8,709 INFO  [XMLLoginConfig] Starting
 8,749 INFO  [XMLLoginConfig] Started
 8,759 ERROR [SecurityConfig] Starting failed
 anagement.InstanceNotFoundException: jboss.security:name=SecurityConfig is
 not registered.
  at

org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:
 354)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:538)
  at

org.jboss.chap8.service.SecurityConfig.startService(SecurityConfig.java:101)
  at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
 )
  at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
 .java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at

org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
 cher.java:284)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
  at

org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav
 a:966)
  at $Proxy11.start(Unknown Source)
  at org.jboss.system.ServiceController.start(ServiceController.java:392)
  at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
  at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
 .java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at

org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
 cher.java:284)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
  at $Proxy5.start(Unknown Source)
  at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824)
  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
  at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source)
  at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
 .java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at

org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
 cher.java:284)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
  at $Proxy7.deploy(Unknown 

RE: [JBoss-user] MDB Singleton retry semantics

[Adrian Brock]

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.  So, if I switch MaximumSize to 1, this may give me the behaviour I'm
 looking for?
 

It would make it better.

 I still am a bit fuzzy on the part where if the retry implementation is just
 simply pushing the message back onto the source queue, then there would be
 no way to guarantee that no other messages would be in front of that
 reposted message correct?  Or am I misunderstanding the MDB retry
 implementation in JBossMQ? 
 

Let me do a little pseudo code:

1) ConnectionConsumer retrieves message1
2) ConnectionConsumer gets a session which enlists in the transaction
3) ConnectionConsumer asks for next message
4a) Session delivers message1 to the MDB
4b) ConnectionConsumer gets the next message2 and asks for Session
(there are none available so wait)
5) MDB rollsback the transaction which nacks message1 back into the
queue
6) ConnectionConsumer reuses the session for message2
7) ConnectionConsumer asks for next message it is message1

It is step 4b that causes your problem.

NOTE: Other JMS implementations may not implement the ConnectionConsumer
the same way. This is not defined in the spec.

Regards,
Adrian

 Dustin
 
  -Original Message-
  From: Adrian Brock [mailto:[EMAIL PROTECTED]
  Sent: Friday, August 15, 2003 6:58 AM
  To: [EMAIL PROTECTED]
  Subject: RE: [JBoss-user] MDB Singleton retry semantics
  
  
  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 sessions
  will have a message attached.
  
  Regards,
  Adrian
  
  On Thu, 2003-08-14 at 21:13, Barlow, Dustin wrote:
   In conf/standardjboss.xml I setup a new invoker-proxy-binding and a
   container-configuration.  Part of the 
  container-configuration includes the
   following stanzas:
   
   container-pool-conf
 MaximumSize1/MaximumSize
 MinimumSize1/MinimumSize
 strictMaximumSizetrue/strictMaximumSize
   /container-pool-conf 
   
   The MDB is deployed using the new invoker-proxy-binding and
   container-configuration and does only consume one message 
  at a time as long
   as there isn't a container transaction rollback.
   
   BTW: I'm using JBoss 3.2.2RC2.
   
   Dustin
   
   -Original Message-
   From: [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Sent: 8/14/2003 2:27 PM
   Subject: RE: [JBoss-user] MDB Singleton retry semantics
   
   How are you enforcing the singleton?
  -- 
   
  Adrian Brock
  Director of Support
  Back Office
  JBoss Group, LLC 
   
  
  
  
  ---
  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 .NET.
  http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet
  _072303_01/01
  ___
  JBoss-user mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-user
  
 
 
 ---
 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 .NET.
 http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

RE: [JBoss-user] MDB Singleton retry semantics

[Barlow, Dustin]

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 behaviour be in
the 4.0 series as well?

The second issue this brings up is transaction behaviour.

I have a CMT MDB consuming on queue/A.  The MDB fires and calls a CMT SSB
that subsequently pushes a message onto queue/B (JMS access done via a
ConnectionFactory gotten from java:/JmsXA).  For sake of the example I have
two messages sitting on the queue.  The first message is going to write to
queue/B, the second one is going to use a queue browser and lookup what the
message on queue/B that the first message coming from queue/A wrote.

The behaviour I've witnessed is that when message one succeeds and goes into
the final commit stage of the CMT, message two actually fires prior to the
container transaction fully committing message one's work to queue/B.  This
means that message two doesn't see the message on queue/B that message one
wrote to it.

I presume this behaviour is also due to the ConnectionConsumer read-ahead
strategy?  I was under the impression that if I have a singleton MDB, that
the second message on the queue would not be fired until the first message
is fully consumed, and any resources that message had altered would be fully
committed prior to the next message on the queue being consumed by the MDB.
It seems that the commit of the first message is happening async to the
consumption of the second message.  Setting the MaximumSize on the
proxy-factory-config to 1 fixed/masked this scenario as well.

I don't know what the spec has to say about the above scenario, but it seems
to me that if I want true acidity of resources in the case of a singleton
MDB setup, that the second message should not fire until message one had
been consumed and all resources that enlisted in the container transaction
should be actually commited so that message two could see them when it
fires.

Dustin

 -Original Message-
 From: Adrian Brock [mailto:[EMAIL PROTECTED]
 Sent: Friday, August 15, 2003 9:55 AM
 To: [EMAIL PROTECTED]
 Subject: RE: [JBoss-user] MDB Singleton retry semantics
 
 
 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.  So, if I switch MaximumSize to 1, this may give me the 
 behaviour I'm
  looking for?
  
 
 It would make it better.
 
  I still am a bit fuzzy on the part where if the retry 
 implementation is just
  simply pushing the message back onto the source queue, then 
 there would be
  no way to guarantee that no other messages would be in front of that
  reposted message correct?  Or am I misunderstanding the MDB retry
  implementation in JBossMQ? 
  
 
 Let me do a little pseudo code:
 
 1) ConnectionConsumer retrieves message1
 2) ConnectionConsumer gets a session which enlists in the transaction
 3) ConnectionConsumer asks for next message
 4a) Session delivers message1 to the MDB
 4b) ConnectionConsumer gets the next message2 and asks for Session
 (there are none available so wait)
 5) MDB rollsback the transaction which nacks message1 back into the
 queue
 6) ConnectionConsumer reuses the session for message2
 7) ConnectionConsumer asks for next message it is message1
 
 It is step 4b that causes your problem.
 
 NOTE: Other JMS implementations may not implement the 
 ConnectionConsumer
 the same way. This is not defined in the spec.
 
 Regards,
 Adrian
 
  Dustin
  
   -Original Message-
   From: Adrian Brock [mailto:[EMAIL PROTECTED]
   Sent: Friday, August 15, 2003 6:58 AM
   To: [EMAIL PROTECTED]
   Subject: RE: [JBoss-user] MDB Singleton retry semantics
   
   
   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 sessions
   will have a message attached.
   
   Regards,
   Adrian
   
   On Thu, 2003-08-14 at 21:13, Barlow, Dustin wrote:
In conf/standardjboss.xml I setup a new 
 invoker-proxy-binding and a
container-configuration.  Part of the 
   container-configuration includes the
following stanzas:

container-pool-conf
  MaximumSize1/MaximumSize
  MinimumSize1/MinimumSize
  strictMaximumSizetrue/strictMaximumSize
/container-pool-conf 

The MDB is deployed using the new invoker-proxy-binding and
container-configuration and does only consume one message 
   at a time as long
as there isn't a container 

Re: [JBoss-user] Load-Balancing Problems

[Simone Milani]

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 15, 2003 1:58 PM
Subject: RE: [JBoss-user] Load-Balancing Problems


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: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Simone Milani
 Sent: vendredi, 15. août 2003 14:41
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] Load-Balancing Problems


 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 session/session, entity/entity and
 message-driven/message-driven
markup for those beans.
  --

   session
  ejb-nameTest/ejb-name
  jndi-nameEJB/Session/Test/jndi-name
  local-jndi-nameEJB/Session/Local/Test/local-jndi-name
  configuration-nameStandard Stateless SessionBean with
 Security/configuration-name
  clusteredtrue/clustered
   /session

/enterprise-beans

resource-managers
/resource-managers

  container-configurations
   container-configuration extends=Instance Per
 Transaction CMP 2.x
 EntityBean
  container-nameOptimistic CMP 2.x
 EntityBean/container-name

 locking-policyorg.jboss.ejb.plugins.lock.JDBCOptimisticLock
/locking-polic
 y
  sync-on-commit-onlytrue/sync-on-commit-only
   /container-configuration
 container-configuration extends=Standard Stateless
 SessionBean
  container-nameStandard Stateless SessionBean with
 Security/container-name
  security-domainjava:/jaas/tsar/security-domain
   /container-configuration
/container-configurations

 /jboss
 And the partition as the default name.
 Any idea?

 Thanks!!!

 Simone

 - Original Message - 
 From: Sacha Labourey [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Friday, August 15, 2003 12:57 PM
 Subject: RE: [JBoss-user] Load-Balancing Problems


 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: vendredi, 15. août 2003 11:46
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-user] Load-Balancing Problems
 
 
  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
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
  orImpl.java:39
  )
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
  odAccessorImpl
  .java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at
  org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.i
  nvoke(Stateles
  sSessionContainer.java:646)
  at
  org.jboss.resource.connectionmanager.CachedConnectionIntercept
  or.invoke(Cach
  edConnectionInterceptor.java:186)
  at
  org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invo
  ke(StatelessSe
  ssionInstanceInterceptor.java:72)
  at
  org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(Abstrac
  tTxInterceptor
  .java:84)
  at
  org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxI
  nterceptorCMT.
  java:243)
  at
  org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT
  .java:104)
  at
  org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInter
  ceptor.java:11
  7)
  at
  org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
  at
  org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(Pro
  xyFactoryFinde
  rInterceptor.java:122)
  at
  org.jboss.ejb.StatelessSessionContainer.internalInvoke(Statele
  ssSessionConta
  iner.java:323)
  at org.jboss.ejb.Container.invoke(Container.java:700)
  at
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
  java:39)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
  odAccessorImpl
  

RE: [JBoss-user] MDB Singleton retry semantics

[Adrian Brock]

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 utilize the new JBossDO implementation, will this same behaviour be in
 the 4.0 series as well?
 

JBoss4 implements the integration using JCA1.5 MessageEndpoint
The ConnectionConsumer is no longer used.
You should consider JBoss4 alpha quality software.

 The second issue this brings up is transaction behaviour.
 
 I have a CMT MDB consuming on queue/A.  The MDB fires and calls a CMT SSB
 that subsequently pushes a message onto queue/B (JMS access done via a
 ConnectionFactory gotten from java:/JmsXA).  For sake of the example I have
 two messages sitting on the queue.  The first message is going to write to
 queue/B, the second one is going to use a queue browser and lookup what the
 message on queue/B that the first message coming from queue/A wrote.
 
 The behaviour I've witnessed is that when message one succeeds and goes into
 the final commit stage of the CMT, message two actually fires prior to the
 container transaction fully committing message one's work to queue/B.  This
 means that message two doesn't see the message on queue/B that message one
 wrote to it.
 
 I presume this behaviour is also due to the ConnectionConsumer read-ahead
 strategy?  I was under the impression that if I have a singleton MDB, that
 the second message on the queue would not be fired until the first message
 is fully consumed, and any resources that message had altered would be fully
 committed prior to the next message on the queue being consumed by the MDB.
 It seems that the commit of the first message is happening async to the
 consumption of the second message.  Setting the MaximumSize on the
 proxy-factory-config to 1 fixed/masked this scenario as well.
 
 I don't know what the spec has to say about the above scenario, but it seems
 to me that if I want true acidity of resources in the case of a singleton
 MDB setup, that the second message should not fire until message one had
 been consumed and all resources that enlisted in the container transaction
 should be actually commited so that message two could see them when it
 fires.
 

First, QueueBrowsers are not transactional objects.

I don't quite get what you are trying to achieve, if I understand it
correctly, this isn't going to work (even ignoring my comment about the
QueueBrowser).

(A) tx1 processes message1 and commits a message to (B)
(B) tx2 processes that message
(A) tx3 tries to look at the message from the first step but it is
already gone

ACID has nothing to say about this - it is three different transactions.
It is just a plain old race condition. Does tx2 or tx3 run first, who
knows?

You can search for previous discussions on XA commit semantics on this
list.

Regards,
Adrian

 Dustin



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

RE: [JBoss-user] JBoss Web Console

[Clover, James]

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 [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 15, 2003 12:22 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JBoss Web Console


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, 14 Aug 2003 09:12:26 -0500
 From: Stephen Davidson [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] JBoss Web Console
 To: [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 
 Paulo Bengero wrote:
  Have anyone of you used the JBoss web-console? You can
 access this through
  (assuming localhost is your test server )
 http://localhost:8080/web-console/ .
 
  When i pasted that in my url the applet on the left side
 didn't appear because
  of this exception:
 
  http://localhost:8080/web-console/Invoker
 java.lang.NoClassDefFoundError:
  com/sun/net/ssl/HttpsURLConnectionat 
 org.jboss.console.remote.Util.
 invoke(Util.java:48)at org.jboss.console.remote.
 
 AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:50)
 at
  
 org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.
  java:104)at org.jboss.console.navtree.ConsoleTreeModel.
 init(ConsoleTreeModel.java:59)   at 
 org.jboss.console.navtree.
AdminTreeBrowser.init(AdminTreeBrowser.java:63) at 
 org.jboss.console.
  navtree.AppletBrowser.start(AppletBrowser.java:51)  at
 sun.applet.
   AppletPanel.run(Unknown Source)   at 
 java.lang.Thread.run(Unknown Source)
 
  Care to give some help?
 
 
  
  Paulo A. Bengero
  Application Systems Engineer
  Team ORION
  
 Hi Paulo.
 
 Are you using IE/Microsoft JVM combo by any chance?
 There is a way to check, by bringing up the applet
 window in Internet Explorer.  Unfortunately, its been
 so long since I have used IE that I have forgotten
 how to do so.
 
 If you are using MS Java in your browser, you may want
 to look at installing Sun's JVM in place of the one that
 MS has foisted by default on you.
 
 Regards,
 Steve
 
 Ive already done that Steveany more suggestions? This
 error (java.lang.
 NoClassDefFoundError:
  com/sun/net/ssl/HttpsURLConnection ) is still bugging me.
 Do i need to add
 any jars or something in my classpath? Anyone out there who
 has successfully
 used the JBoss WEB Console?
 
 
 Paulo A. Bengero
 Application Systems Engineer
 Team ORION
 
 
 



---
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 .NET. 
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user


---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

RE: [JBoss-user] MDB Singleton retry semantics

[Barlow, Dustin]

 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 singleton MDBs
operate similiar to what we've already discussed here for the 3.2 series.

 First, QueueBrowsers are not transactional objects.

I know and agree.

 
 I don't quite get what you are trying to achieve, if I understand it
 correctly, this isn't going to work (even ignoring my comment 
 about the
 QueueBrowser).
 
 (A) tx1 processes message1 and commits a message to (B)
 (B) tx2 processes that message
 (A) tx3 tries to look at the message from the first step but it is
 already gone
 
 ACID has nothing to say about this - it is three different 
 transactions.
 It is just a plain old race condition. Does tx2 or tx3 run first, who
 knows?
 
 You can search for previous discussions on XA commit semantics on this
 list.
 

There is no MDB or MessageListener attached to the second queue (queue/B).  

I'm basically using the second JMS queue (queue/B) as a temporary object
storage space.  So the message posted to queue/B in the scenario I spelled
out in my prior post would/should be on the queue when the second message
from queue/A triggers.  Apart of message2's business logic does a lookup
(via a QueueBrowser) for the message that the message1 process posted on
queue/B.

Below is a simplified example.

1.  Two messages sitting on queue/A
2.  Singleton MDB attached to queue/A
3.  Message1 triggers from queue/A
4.  The MDB calls a CMT SSB that does some business logic one leg of which
is a post of a new message to queue/B.  
5.  The stack returns back to the MDB successfully and the CMT commit
process begins.
6.  Message2 triggers from queue/A.
7.  The MDB calls a different CMT SSB that looks up (using a QueueBrowser)
on queue/B the data that message1 put on the queue.

In the above scenario, the process triggered by message2 on queue/A doesn't
always see the message posted on queue/B by message1's process.

My observation is that in the case of a singleton MDB setup with a Session
MaxSize greater then one, there seems to be a race condition since the
Session used by message1 has now been freed allowing message2 to be
triggered prior to the container actually finishing its work of committing
all enlisted resources that message1's flow changed (including the post to
queue/B).

Dustin


---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] 5000$B1_$G3+6H$7$^$;$s$+!*!*(B

[5000$B1_$G3+6H$7$^$;$s$+!*!*(B]

 
(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 PROTECTED]>pJs2=;~Be!#(B
$B!!;d$b$3$N>$rHNGd$9$k$H$-Gd$l$k<+?.$O$"$C$?$N$G$9$,$^$5$+$3$s$J$K!*!*(B
$B!!$H;W$C$?$/$i$$CmJ8$,;~$7$S$C$/$j$7$^$7$?!#:#$b$=$N$h$&$J>uBV$,B3$$$F(B
$B!!$$$^$9!#E>Gd$7$F$b$h$$(BCD$B$G$9!#Gc$C$F$7$^$($P5.J}$N9%$-$J$h$&$K;H$C$F(B
$B!!$/[EMAIL PROTECTED](B
$B$5$"!*!!$"$J$?$b>pJsHNGdNsh$C$F$_$^$;$s$+!#(B
$B!!>h$jCY$l$J$$$h$&$K!*!*(B  $BHw$($"$l$PM+$$$J$7!*$G$9$h!#(B
(B
(Bhttp://ginform.jt7.net/
(B
(B
(B---
(BThis SF.Net email sponsored by: Free pre-built ASP.NET sites including
(BData Reports, E-commerce, Portals, and Forums are available now.
(BDownload today and enter to win an XBOX or Visual Studio .NET.
(Bhttp://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
(B___
(BJBoss-user mailing list
(B[EMAIL PROTECTED]
(Bhttps://lists.sourceforge.net/lists/listinfo/jboss-user

RE: [JBoss-user] MDB Singleton retry semantics

[Adrian Brock]

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 in 4.0.  Basically will the implementation in 4.0 for singleton MDBs
 operate similiar to what we've already discussed here for the 3.2 series.
 

Effectively yes. But the pooling is one the details that
still needs to be looked at in jboss4. I don't believe the MDB
strict pooling has been forward ported from 3.2?

  First, QueueBrowsers are not transactional objects.
 
 I know and agree.
 
  
  I don't quite get what you are trying to achieve, if I understand it
  correctly, this isn't going to work (even ignoring my comment 
  about the
  QueueBrowser).
  
  (A) tx1 processes message1 and commits a message to (B)
  (B) tx2 processes that message
  (A) tx3 tries to look at the message from the first step but it is
  already gone
  
  ACID has nothing to say about this - it is three different 
  transactions.
  It is just a plain old race condition. Does tx2 or tx3 run first, who
  knows?
  
  You can search for previous discussions on XA commit semantics on this
  list.
  
 
 There is no MDB or MessageListener attached to the second queue (queue/B).  
 
 I'm basically using the second JMS queue (queue/B) as a temporary object
 storage space.  So the message posted to queue/B in the scenario I spelled
 out in my prior post would/should be on the queue when the second message
 from queue/A triggers.  Apart of message2's business logic does a lookup
 (via a QueueBrowser) for the message that the message1 process posted on
 queue/B.
 
 Below is a simplified example.
 
 1.  Two messages sitting on queue/A
 2.  Singleton MDB attached to queue/A
 3.  Message1 triggers from queue/A
 4.  The MDB calls a CMT SSB that does some business logic one leg of which
 is a post of a new message to queue/B.  
 5.  The stack returns back to the MDB successfully and the CMT commit
 process begins.
 6.  Message2 triggers from queue/A.
 7.  The MDB calls a different CMT SSB that looks up (using a QueueBrowser)
 on queue/B the data that message1 put on the queue.
 
 In the above scenario, the process triggered by message2 on queue/A doesn't
 always see the message posted on queue/B by message1's process.
 
 My observation is that in the case of a singleton MDB setup with a Session
 MaxSize greater then one, there seems to be a race condition since the
 Session used by message1 has now been freed allowing message2 to be
 triggered prior to the container actually finishing its work of committing
 all enlisted resources that message1's flow changed (including the post to
 queue/B).
 

That is correct, the MDB is returned to the pool (but the transaction
has not yet committed). 
Another session waiting for the EJB can start its
work while the previous one goes onto commit.
Setting the ServerSessionPool to MaxSize 1 means that the single session
has to commit before more can be done.

The order of work is roughly:

1) receive()
2) getSession() and enlist in tx
3) getMDB()
4) onMessage()
5) releaseMDB()
6) commitSession()

With MaxSize 1 the wait and release are at 2 and 6 disallowing
concurrency between two different transactions.
With more than one session you gets waits at 3 and 5 with concurrent
transactions. 
Of course, by default there is no wait at 3 
because there is no strict pooling.

Regards,
Adrian

 Dustin
 
 
 ---
 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 .NET.
 http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] Help with security config problem!

[Mark Minnigerode]

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 me I cannot get the
server to see that i have set up method permissions.

My test client is getting a LoginContext succesfully and then just 
calling an echo method on the
ApplicationBean session bean for testing.  When the client calls 
appbeanhome.create() to
get a remote object jboss spits out:



18:15:31,610 ERROR [SecurityInterceptor] No method permissions assigned 
to method=create, interface=HOME
18:15:31,619 ERROR [LogInterceptor] EJBException, causedBy:
java.lang.SecurityException: No method permissions assigned to 
method=create, interface=HOME
.
.
.

After looking  at the jboss source for SecurityInterceptor (and from 
some testing of my
own) it looks like the isVaid() method is getting called correctly. 

Anyone see a mistake in my deploy desc? 

Thanks!

dave

-

Here's my setup:

JBoss 3.2.0, 3.2.1 and 3.2.2RC2

jboss.xml has:
   security-domainjava:/jaas/other/security-domain
   unauthenticated-principalUnknown/unauthenticated-principal
This is also reflected in the login-config.xml file.

ejb-jar.xml has a big pile of beans but these are the ones i've been 
testing against.:

ejb-jar
   enterprise-beans
   session
   ejb-nameApplicationBean/ejb-name
   homecom.dave.gdscs.server.ejb.ApplicationHome/home
   remotecom.dave.gdscs.server.ejb.Application/remote
   ejb-classcom.dave.gdscs.server.ejb.ApplicationBean/ejb-class
   session-typeStateless/session-type
   transaction-typeContainer/transaction-type
   ejb-ref
   ejb-ref-nameejb/NetworkServiceSession/ejb-ref-name
   ejb-ref-typeSession/ejb-ref-type
   
homecom.dave.gdscs.server.net.ejb.NetworkServiceSessionHome/home
   
remotecom.dave.gdscs.server.net.ejb.NetworkServiceSession/remote
   ejb-linkNetworkServiceSession/ejb-link
   /ejb-ref
   security-role-ref
   role-nameUser/role-name
   role-linkUser/role-link
   /security-role-ref
   security-role-ref
   role-nameAdmin/role-name
   role-linkAdmin/role-link
   /security-role-ref
   security-role-ref
   role-nameInternal/role-name
   role-linkInternal/role-link
   /security-role-ref
   security-identityuse-caller-identity//security-identity
   !--
   security-identity
   run-as
   role-nameInternal/role-name
   /run-as
   /security-identity
   --
   /session
   session
   ejb-nameAccountManager/ejb-name
   
homecom.dave.gdscs.server.account.ejb.AccountManagerHome/home
   
remotecom.dave.gdscs.server.account.ejb.AccountManager/remote
   
ejb-classcom.dave.gdscs.server.account.ejb.AccountManagerBean/ejb-class
   session-typeStateless/session-type
   transaction-typeContainer/transaction-type
   ejb-local-ref
   ejb-ref-nameejb/AccountLocalHome/ejb-ref-name
   ejb-ref-typeEntity/ejb-ref-type
   
local-homecom.dave.gdscs.server.account.ejb.AccountLocalHome/local-home
   
localcom.dave.gdscs.server.account.ejb.AccountLocal/local
   ejb-linkAccountBean/ejb-link
   /ejb-local-ref
   security-role-ref
   role-nameUser/role-name
   role-linkUser/role-link
   /security-role-ref
   security-role-ref
   role-nameAdmin/role-name
   role-linkAdmin/role-link
   /security-role-ref
   security-role-ref
   role-nameInternal/role-name
   role-linkInternal/role-link
   /security-role-ref
   security-identity
   run-as
   role-nameInternal/role-name
   /run-as
   /security-identity
   /session
  
   /enterprise-beans

   relationships
!-- removed for space --
   /relationships
   assembely-descriptor
   security-role
   role-nameAdmin/role-name
   /security-role
   security-role
   role-nameUser/role-name
   /security-role
   security-role
   role-nameInternal/role-name
   /security-role
   method-permission
   role-nameInternal/role-name
   role-nameAdmin/role-name
   role-nameUser/role-name
   method
   ejb-nameApplicationBean/ejb-name
   method-name*/method-name
   /method
   method
   ejb-nameAccountManager/ejb-name
   

RE: [JBoss-user] MDB Singleton retry semantics

[Barlow, Dustin]

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 same.  Plus with
a singleton MDB setup, one could take advantage of the read-ahead
optimization by having MaxSize set to a value higher then one, and still
have acidity of CMT between each MDB invocation of onMessage().

Otherwise, you basically have to choke off the pooling at the session level
to keep the async behaviour of the MDB at bay until the session commits.  

Is it done that way because another transactable resource could be enlisted
for which the session would have to commit after releaseMDB()?  Even if the
MDB itself calls a CMT SSB, the releaseMDB() would be presumably done after
the releaseSSB().

IE:

1) receive()
2) getSession() and enlist in tx
3) getMDB()
4) onMessage()
5)  invoke CMT method on SSB()
5) getSSB() and enlist in tx
6) run CMT method
7) releaseSSB()
8) releaseMDB()
9) commitSession()

Dustin


---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] WindowsXP/Ofis2000 Egitim Cdleri

[Egitimcd.com]

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

[JBoss-user] Open-Source

[nfs_ nfs]

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



---
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 .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user