Any chance to compare those numbers with the ones given by the activemq
mbeans?
Thx, Eric
On 19/02/2013 10:42, Farooq Ahmed wrote:
Hi Eric,
i have used jmxterm-1.0-alpha-4-uber jmx cli,
"You mean to 'push out' the queue.
The mail you send triggers the pending mails to go out?"
Yes this new mail push the earlier mail out but itself gets stuck in
spool,to which a new mail after 30 sec pushes out and that mail gets struck
and soon...
Can you guide me how to figure out the reason as to why the size attribute
value is 5 and the browse List only contains 3 mails details.
Also Why The mail which gets stuck in spool its count is incremented in
attribure Size but its details are not present in browse List..?
Regards,
Farooq
On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles <e...@apache.org> wrote:
Hi Farooq,
On 18/02/2013 12:39, Farooq Ahmed wrote:
Hi Eric,
Here is the output which i get when i use Bean
org.apache.james:name=queue,**queue=outgoing,type=component
$>bean org.apache.james:name=queue,**queue=outgoing,type=component
#bean is set to org.apache.james:name=queue,**
queue=outgoing,type=component
$>info
#mbean = org.apache.james:name=queue,**queue=outgoing,type=component
#class name = org.apache.james.queue.**library.MailQueueManagement
# attributes
%0 - Size (long, r)
# operations
%0 - java.util.List browse()
%1 - long clear()
%2 - long flush()
%3 - long removeWithName(java.lang.**String p1)
%4 - long removeWithRecipient(java.lang.**String p1)
%5 - long removeWithSender(java.lang.**String p1)
#there's no notifications
$>get Size
#mbean = org.apache.james:name=queue,**queue=outgoing,type=component:
Size = 7;
Cool, it seems like you have found a JXM CLI which works fine.
Which one is it?
Let me know if you need any further details.
can you educate me as to Size= 7 is the no of mails still in outgoing
spool
or is some default size of outgoing queue.
It is the number of pending mails in the queue.
So you have 7 mails waiting to be sent to the outside world/
Also note that do deal with this spooling problem, the workaround that we
did temporarily is that we created an application that sends an email to
some email address every 30 sec.
You mean to 'push out' the queue.
The mail you send triggers the pending mails to go out?
Thx, Eric
Regards,
Farooq
On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <e...@apache.org> wrote:
Hi,
Maybe the cloud's firewall blocks your requests.
For JMX command line, type 'jmx cli' in google and experiment (tried one
of these long time ago).
Thx, Eric
On 18/02/2013 10:11, Farooq Ahmed wrote:
Hi Eric,
I tried remotely connecting to JMX using Jconsole and remote jmx
connection
method specified on http://james.apache.org/****
server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
<ht**tp://james.apache.org/server/**3/config-system.html<http://james.apache.org/server/3/config-system.html>
But i could not get connected to jmx on my email server.
Note that the server where i have deployed james is on azure cloud PAS
network and is Ubunto system.
Is there any mechanism where i can observe the message queue contents on
local ubunto system using ssh only.
Regards,
Farooq
On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
ajay.navg...@centralogic.net
wrote:
---------- Forwarded message ----------
From: Eric Charles <e...@apache.org>
Date: Tue, Feb 12, 2013 at 7:52 PM
Subject: Re: James Server SMTP Spooling Issue
To: James Users List <server-user@james.apache.org>
Hi,
You mean you the newly spooled mails 'push-out' the remaining ones.
After that, the latest one remains stucked in the queu?
If such, that's very strange and we never saw that before.
Do you use JMX to inspect the queue content/size?
Thx, Eric
On 12/02/2013 11:45, Ajay Navgale wrote:
Hi,
We are using james 3.0 beta4.
We have an issue while sending an email. There is always one outgoing
mail
left in spool and is delivered when any new outgoing mail is to be
sent.
Now previous mail gets delivered and this recent once sits in the
spool.
This is happening for Remote delivery.
Can anyone throw some light on this.
Thanks & Regards,
Ajay
------------------------------******--------------------------**
--**
--**---------
To unsubscribe, e-mail: server-user-unsubscribe@james.******apache.org
<
server-user-**unsubscribe@**james.apache.org<unsubscr...@james.apache.org>
<server-user-**unsubscr...@james.apache.org<server-user-unsubscr...@james.apache.org>
For additional commands, e-mail: server-user-help@james.apache.**
****org<
server-user-help@james.**apach**e.org <http://apache.org> <
server-user-help@james.**apache.org<server-user-h...@james.apache.org>
------------------------------****----------------------------**
--**---------
To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
server-user-**unsubscr...@james.apache.org<server-user-unsubscr...@james.apache.org>
For additional commands, e-mail: server-user-help@james.apache.****org<
server-user-help@james.**apache.org <server-user-h...@james.apache.org>>
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
server-user-unsubscribe@james.**apache.org<server-user-unsubscr...@james.apache.org>
For additional commands, e-mail:
server-user-help@james.apache.**org<server-user-h...@james.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
