ECTED]>
Sent: Monday, January 20, 2003 1:19 PM
Subject: Alternative JMS Providers (Was: Re: [JBoss-user] jms issues)
>
> On Wednesday, Jan 15, 2003, at 03:44 Europe/Amsterdam, Ed Brown wrote:
>
> >
> > Quoting "Gary S. Cuozzo" <[EMAIL PROTECTED]>:
> >
&
Quoting Stefan Arentz <[EMAIL PROTECTED]>:
>
> On Wednesday, Jan 15, 2003, at 03:44 Europe/Amsterdam, Ed Brown wrote:
>
> >
> > Quoting "Gary S. Cuozzo" <[EMAIL PROTECTED]>:
> >
> >> hey all,
> >> I'm doing some testing on my application, and having some issues
> with
> >> the JMS service.
> >
D]]
> Sent: Monday, January 20, 2003 3:19 PM
> To: [EMAIL PROTECTED]
> Subject: Alternative JMS Providers (Was: Re: [JBoss-user] jms issues)
>
>
>
> On Wednesday, Jan 15, 2003, at 03:44 Europe/Amsterdam, Ed Brown wrote:
>
> >
> > Quoting "Gary S. Cuozzo&qu
On Wednesday, Jan 15, 2003, at 03:44 Europe/Amsterdam, Ed Brown wrote:
Quoting "Gary S. Cuozzo" <[EMAIL PROTECTED]>:
hey all,
I'm doing some testing on my application, and having some issues with
the JMS service.
The JBoss implementation of JMS is not optimal. That's a nice way of
saying t
3 12:37 PM
Subject: Re: [JBoss-user] jms issues
Quoting Peter Fagerlund <[EMAIL PROTECTED]>:
torsdagen den 16 januari 2003 kl 03.49 skrev Ed Brown:
Here are the list of problems that I ran into when I used the JBoss
implementation:
1. If too many messages were queued up, an
complain because JBoss has served me well, but I would like to use
JMS more frequently in my production environments.
Cheers,
Rob
- Original Message -
From: "Ed Brown" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 12:37 PM
Subject: Re: [
fredagen den 17 januari 2003 kl 21.37 skrev Ed Brown:
1) I suspect a corrupted DB from a not clean shutdown
2) I suspect a corrupted DB from a not clean shutdown
Shutdown was done using "CTRL-C" at the console. Since that was the
way to shut it down, corrupted queues resulting from shutdown w
Quoting Peter Fagerlund <[EMAIL PROTECTED]>:
>
> torsdagen den 16 januari 2003 kl 03.49 skrev Ed Brown:
>
> > Here are the list of problems that I ran into when I used the JBoss
> > implementation:
> >
> > 1. If too many messages were queued up, and the server was stopped and
>
> > restarted,
torsdagen den 16 januari 2003 kl 03.49 skrev Ed Brown:
Here are the list of problems that I ran into when I used the JBoss
implementation:
1. If too many messages were queued up, and the server was stopped and
restarted, the server hung.
2. Sometimes when the server was stopped and restarted
Quoting John Fawcett <[EMAIL PROTECTED]>:
> Hi,
>
> Can you be more specific in your criticism? I am interested in working
> on the Jbossmq codebase.
Here are the list of problems that I ran into when I used the JBoss implementation:
1. If too many messages were queued up, and the server was s
have to pick through.
>
> Thanks,
> fawce
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On
> Behalf Of Ed Brown
> Sent: Tuesday, January 14, 2003 9:45 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] jms issues
>
]] On Behalf Of Ed Brown
Sent: Tuesday, January 14, 2003 9:45 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] jms issues
Quoting "Gary S. Cuozzo" <[EMAIL PROTECTED]>:
> hey all,
> I'm doing some testing on my application, and having some issues with
> the JMS serv
Quoting "Gary S. Cuozzo" <[EMAIL PROTECTED]>:
> hey all,
> I'm doing some testing on my application, and having some issues with
> the JMS service.
The JBoss implementation of JMS is not optimal. That's a nice way of saying that it is
crap.
I strongly suggest you investigate ways of using oth
hey all,
I'm doing some testing on my application, and having some issues with
the JMS service.
I have an EJB application with a web client, all deployed as a single
.ear file. The application processes requests and posts messages to a
single JMS queue.
On another server, I have a MBean with
14 matches
Mail list logo
