No CPU overhead, unless you have multiple consumers, and each consumer uses a
thread or two.
On several installs, we use 100+ queues with no problem.
JBossMQ is weak when it comes to large messages and more messages than can fit
within memory. Also, client thread management isn't so hot --
The reason they can't talk is due to the serialization differences, but these
have been fixed in later versions.
Upgrade 3.2.3 to a newer version (3.2.7) with serialization compatibility.
If you can't do a full upgrade, then it's probably a pretty complicated job.
You may be able to create
If the serialization is different between versions, you can't really do what
you describe without changing the underlying bytes in the message, namely
changing the Serialization ID to match.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3897281#3897281
Reply
I found in
[url=https://sourceforge.net/tracker/?func=detailatid=381174aid=631825group_id=22866[/url]
the following:
anonymous wrote :
| 2. For some reason, previous versions of JBoss mapped java.lang
| .Object to a JDBC type of JAVA_OBJECT, and then proceeded to
| serialize the object
Normally message processing within MDB's is 'wrapped' into a container managed
transaction. Maybe larger messages are just getting reprocessed again and again
due to a transaction timeout ? So increasing the default transaction timeout
value (default 5 min I guess) of the Jboss transaction
Session per thread. Sessions aren't supposedly thread safe anyway.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3896679#3896679
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3896679
(The end of the message dissappeared...)
I have tried changing the BLOB_TYPE and MESSAGEBLOB -fields type and the
mapping in standardjaws.xml (CMP1.1 used), but nothing seems to help.
I quess somebody has solved the problem and would appreciate some help how to
solve the problem.
If necessary
Thanks for the detailed and meaningful answer.
Yaron G.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3896455#3896455
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3896455
try to open a telnet and check if the object that the JNDI is with sending to
you has the right number.
try this:
telnet 172.16.96.179 1099
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3896510#3896510
Reply to the post :
http://www.jboss.com/index.html?module=bbop=viewtopict=69532
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3895983#3895983
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3895983
Thanks a lot for the info.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3896084#3896084
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3896084
---
SF.Net email is
Dave,
Although you can modify the JMS data in the database itself, it's probably not
recommend.
You should write an MDB or something (MBean?) that reads messages from the DLQ
and then sends them to the original queue.
If you would like this sort of thing build into JBoss, we've been talking
Can you file a JIRA report? XidFactoryImpl.setBaseGlobalId should in fact do
argument checking.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3896132#3896132
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3896132
jchen0516 wrote : We found a problem on JMS. I am not sure if it is my
configuration problem. I wrote a simple MDB. At client side, when I put a small
size ObjectMessage into the queue, MDB works fine. Only one MDB pickups and
processes the message for one time. However, when I put a big size
ok its because there are parellal mdb receivers.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3895748#3895748
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3895748
---
When you say you have packaged your MDB in your ear, i assume that you
mentioned the necessary details about your MDB in the deployment descriptors as
well. One of them being the jndi name of the queue on which this MDB will be
listening. So, once the message is there in that particular queue,
Hi Jai,
do u mean to say me that I need to specify my mdb module in application.xml of
the ear file.. if so, is that to be done in the same manner as like that of
mentioning my session bean details in the deployment descriptor ..??
Then where shud I specify the jndi name of the queue.. shud i
You will be making entries for the MDB in ejb-jar.xml and jboss.xml
In your ejb-jar.xml you will have something like the following:
!-- Message Driven Beans --
| message-driven
| description![CDATA[!-- begin-xdoclet-definition
--]]/description
|
|
No, client side persistence is not currently available.
You can use a HA, mostly custered solution and create two servers.
If you really want to have this feature, it's possible to serialize the
messages to disk and upon reconnect, load and send them back. (This would have
to be done
If i cancel / remove my queue receiver then i can see the messages in
queuebrowser. My question is regarding the following scenario:
1. I have a queue sender and a receiver
2. I configure my sender to send more messages than the receiver can accept at
any point of time
3. I see that the
This is to do with JNDI lookups, not JMS, and more specifically it's a simple
socket connect/network issue.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3895620#3895620
Reply to the post :
I understand this is a JNDI lookup issue, and that it is some type network
issue. However, I am unable to resolve the issue, and it is JBoss that is
throwing the exception on the server side. This has been a known issue with
multi-homed boxes, and suggestions for fixes have been offered...of
anyone else have this problem? Or any ideas what it could be ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3895140#3895140
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3895140
Thread-29 daemon prio=1 tid=0x086bb7d8 nid=0x5187 in Object.wait()
[8e603000..8e6038c8]
at java.lang.Object.wait(Native Method)
- waiting on 0x4b110c70 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:429)
at
I found navigating this site for an answer to this problem very frustrating and
confusing, as much was contrdictory and it was often difficult to see which
version of JBoss it applied to, but the answer I found was that you can specify
the mdb-user and mdb-passwd tags in the jboss.xml file and
Have a look at this link:
http://wiki.jboss.org/wiki/Wiki.jsp?page=WhatIsTheCorrectWayToMakeADurableSubscription
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3894830#3894830
Reply to the post :
Geert,
Sorry, I do not have the answer but... I am very very interested in it... Have
you made any progress?
Also, whether you use JAAS or the createConnection with password, can the
consumer of the message know who sent it? Typically do you know of any means
to allow an MDB to have the
Reason why you are getting the exception is :
anonymous wrote : The security methods--getCallerPrincipal() and
isCallerInRole()--also throw a RuntimeException if invoked on a
MessageDrivenContext. When an MDB services a JMS message there is no caller,
so there is no security context to be
anonymous wrote : FAQ means the question has been asked too many times,
| nobody is interested in answering repeat questions from lazy users.
This isn't helpful.
1) FAQ means a series of questions and answers.
see: http://en.wikipedia.org/wiki/Faq
it does NOT mean your explanation, which has a
anonymous wrote : Also, whether you use JAAS or the createConnection with
password, can the consumer of the message know who sent it?
I guess jaikiran is right, it doesn't make sense in JMS to transport the
security context outside of the message. If you want to transport it, you'd
have to
this is working:
jboss.xml
| jboss
|enterprise-beans
| securefalse/secure
| message-driven
| ejb-nameDocImportProcessorEJB/ejb-name
| local-jndi-namelocal/DocImportProcessorEJB/local-jndi-name
|
I believe jbossmq-state.xml under server/default/conf is the file you are
looking for
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3894704#3894704
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3894704
yes, I was found it, but the DurableSubscriptions tags are empty. I'm using
Hermes to administrate the JBossMQ, but when I trying to create a
DurableSubscription I got the same error. Can you tell me what I should do to
grant privilege to some user?.
View the original post :
I am having the same problem as you.
I have 3 schedulers which are creating about 2 jms connections per second and
close them 2 seconds later. The amount of threads (readtasks and writetasks)
created by JBoss grows rapidly to 4 hundred when it stops growing. If we
decrease the creation rate
http://jira.jboss.com/jira/browse/JBAS-1337
http://jira.jboss.com/jira/browse/JBAS-1338
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3894729#3894729
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3894729
[EMAIL PROTECTED] wrote : http://jira.jboss.com/jira/browse/JBAS-1337
| http://jira.jboss.com/jira/browse/JBAS-1338
|
Ok.
We are going to re-use the jms connections avoiding creating them.
Greetings
View the original post :
Hi,
I'm having the same problem. Did you solve it ?
Ricardo
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3894759#3894759
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3894759
http://jira.jboss.com/jira/browse/JBAS-2159
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3894771#3894771
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3894771
---
If you're doing a remote (TCP) connection to WMQ then just the java classes, if
you want a native bind to a colocated WMQ manager then the .so/DLL is also
needed.
Colin,
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3894439#3894439
Reply to the post :
Finally got around to doing some tracing - I turned on the TRACE logging for
the TraceInterceptor. I can see subscriptions and unsubsciptions being logged.
The problem is that the ID identifing any particular subscription are bogus -
always -2147483648 which is min int. Based on this
I was looking at trying to do the same thing and figured out from the docs that
this was the solution so I would very interested to learn how to associate an
MDB with a specific invoker-proxy-binding.
I have tried:
| mbean code=org.jboss.mq.server.jmx.Topic
|
Unfortunately we received no help with this problem. We checked all connections
and objects were being closed and destroyed and still the sockets on each MDB
remained.
The only solution for us was to move these tasks away from the MDB to a servlet
which received the object, fired off a new
Hi,
I tried out setting the redelivery limit on the queue as you mentioned in the
above post. I am using JBoss-3.2.3. I got the following error:
13:55:16,215 INFO [ServiceConfigurator] Problem configuring service
jboss.mq.destination:service=Queue,name=MyQueue
|
Maybe for 3.2.3 you can set it in the standardjboss.xml file?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893802#3893802
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3893802
This would mean that i would be changing the value of redelivery limit of ALL
queues on that particular server, right? I would have preffered it to be
application specific setting. Is there any other way, i can achieve this?
Thank you
View the original post :
thank you for reply.
here is allready a topic about this problem:
http://jira.jboss.com/jira/browse/JBAS-2130;jsessionid=303313B824CF61FCB73C015CEE8EF391?page=comments
suggested workaround:
| message-driven
| [...]
| local-jndi-namelocal/docImportProcessorEJB/local-jndi-name
|
Could you elaborate this? How exactly can you perform such a trace?
Thanks,
//Andreas
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893587#3893587
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3893587
anonymous wrote : You guys crack me up. Don't you have something better to do
than look at none problems? Which part about DEBUG don't you understand?
I have to say, I'm not easily shocked, but when I saw your email address and
the way you replied, it made Hani seem a bit more right about you
Hi,
we are having the same problem. Do you resolve it? How?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893707#3893707
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3893707
If you use an MDB, if the message fails it should go to the DLQ, you can
configure this to happen after one try. (This isn't transactionally safe, from
what I've heard.)
Alternatively, you could check the 'redelivered' flag on the message in an MDB.
So:
1. MDB receives message
2. Do database
Keywords: log4j, jboss logging, tracing interceptor
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893728#3893728
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3893728
http://www.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureAnMDBToTalkToARemoteQueue
The server can automatically reconnect for you.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893730#3893730
Reply to the post :
Are you unable to use search? What browser are you using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893732#3893732
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3893732
You'll (unfortunately) have to query the MBean server and check each registered
MBean.
The names have to be tagged with a unique id, since the the same named EJB can
be present.
I don't really know the particulrs. I would have expected, if there were
conflicts something like instance=1 to
genman wrote : The server can automatically reconnect for you.
Yes, I know that and it does reconnect automatically, but I need to bo notified
of a connection loss / reconnection. I want server B to ask server A to send
some datas when the MDB is reconnected, otherwise I end up with loosing
Hi
I am also facing the same problem.
I am using samples given in the JBoss distribution as per the JBossMQWiki.
However when I use testQueue then I get ClassCastException and if I use queue A
then I get Queue not bound exception.
==
Here is my code:
Please post the code in which you are sending the message
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893145#3893145
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3893145
If you are getting a ClassCastException post the Exception stack trace and
message.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893164#3893164
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3893164
Exception in thread main java.lang.ClassCastException: javax.naming.Reference
at QClient.main(QClient.java:33)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893172#3893172
Reply to the post :
I found the reason for this. It has nothing to do with ClassCastException
actually.
The JMS client was not able to connect to JBoss server hence I was not getting
the Queue type object and thus the ClassCastException.
Putting jbossall-client.jar in the classpath solved the problem.
View the
Here is the code snippet
package movie.ejb;
import java.rmi.*;
import javax.ejb.*;
import javax.jms.*;
import javax.naming.*;
/**
* @ejb.bean
* name=MessageController
* extends=javax.ejb.MovieSessionBean
* view-type=remote
* jndi-name=movie.ejb.MessageControllerHome
* description=EJB
Yes the fact the ClassCastException mentions javax.naming.Reference is enough
information to realise you had jars missing on your classpath.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893203#3893203
Reply to the post :
Instead of the following, use Required as the transaction type
@ejb.transaction
| * type=Supports
Instead, use:
@ejb.transaction
| * type=Required
I think this might work. Try it out
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893205#3893205
Reply
Try this code it will work:
public void browseQ() throws JMSException {
QueueConnection queueConnection = null;
QueueSession queueSession = null;
QueueBrowser queueBrowser=null;
queueConnection =
Hi
What is this QueueFactory is it from jacorb.jar ? (in that jar there was such a
class with no getInstance() method...)
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893237#3893237
Reply to the post :
Hi, I am using Jboss and have configured JAAS authentication. When I try to
create a Receiver for the temporary queue I am getting follwoing exception:
anonymous wrote : javax.jms.JMSSecurityException: Connection not authorized to
subscribe to destination: JMS_TQ8
When I try to create queue
subvert wrote : Is it possible re-send messages in the existing DLQ?
Create an MDB (transacted) that parses the Message property
DLQHandler.JBOSS_ORIG_DESTINATION and creates a QueueSender, then sends the
message to this queue.
There are no JMX controls for this.
View the original post :
So, one solution is to replace the queue's DLQ with a custom MDB and resend the
Message to the original queue. I really don't like the idea of getting caught
in an endless loop sucking up bandwidth and other resources.
I guess I will have to create a DLQ MDB which persists the messages to a
I'm a little confused by your request. Are you asking how to limit the number
of retries? If so, set the RedeliveryLimit attribute for your Queue's MBean.
The message will proceed to the DLQ after the RedeliveryLimit is met.
View the original post :
Right now I'd settle for understanding what's wrong and hearing either
confirmation that there is a bug in 4.0.2 or an example of a workaround for it.
Even this doesn't work:
| public class SubscriberTxBean
| implements MessageDrivenBean, MessageListener
| {
| private static
You should define a private field serialVersionUID at your class, then you
wouldn't have this issue any more.
serialVersionUIDs are calculated during runtime, and not to having then
specified can make your UIDs to change.
Look at serializatio's specification for more details.
View the
Ahh...that explains a lot.
Thank you very much!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3892288#3892288
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3892288
Is it possible re-send messages in the existing DLQ?
For instance, the network connection may be down for an extended period of time
(longer than the MDB's configured RedeliveryDelay and RedeliveryLimit) and the
messages start making their way to the DLQ. Once my network connection is back,
I
That's an option we'll consider if a patch becomes available. Until then, does
anyone have any suspicion as to the cause or possible way around it?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3892098#3892098
Reply to the post :
erik777 - it seems simple enough to create a delegate class. Basically, create
an MDB class that wraps another (does not subclass).
anonymous wrote : if a patch becomes available
I suggest you write your own.
View the original post :
Moved to user forum
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891986#3891986
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891986
---
SF.Net email is Sponsored by
Hi,
I tried passing this value through -D but of no use. UIL2Service still binds at
IP 0.0.0.0:Port Which is the default settings.
Sachin
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3892010#3892010
Reply to the post :
erik - when JBoss has a bug in it, it's fairly easy to come up with your
own patched .jar file and build a custom installation.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891890#3891890
Reply to the post :
c.f. TextMessage, also ObjectMessage if your XML tree is Serializable (JDom.)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891891#3891891
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891891
The client count should immediately decrease after a client has properly closed
its connection. You can turn on tracing (use the tracing interceptor) to verify
that for every open, you have a corresponding close.
View the original post :
jdni.properties - jndi.properties ? You can turn on debug and see if you're
actually talking to JBoss.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891893#3891893
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891893
There are downloadable examples that should work. There are three key
properties to set in the initial context.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891894#3891894
Reply to the post :
If there's something with ${ } around it, you can supply a System property, i.e.
./run.sh -Dfoo=bar
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891913#3891913
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891913
From what I understand u cannot do that purely by configuration, i.e. set up
different Persistance Managers for different destinations. Looks like the
invoker is tied to a specific Persistance Manager...
Thereis another post on this:
I'm getting this in 4.0.2, only I can't find a workaround. In my case, two
conrete MDBs subclass an abstract one that contains the onMessage(), declared
public void onMessage(javax.jms.Message message)
To try to get around the validation error, I subclassed and had the conrete
classes call
If you are going to post questions about your code please also post a code
sample to show what your client is doing.
Also there are a lot of different tutorials out there, if you have been
referring to a tutorial post the link to it with your question.
What is your client, is it a stand
Read that. Done that. While I'm still trying to learn things on my own, perhaps
you can answer my 1st question.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891602#3891602
Reply to the post :
Turn off DEBUG?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891494#3891494
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891494
---
SF.Net email is Sponsored by
Hi guys.
I am really in troubles here, I saw some tutorials and MDB example and I am
sure that my jboss.xml and ejb-jar.xml are correct. But when I try to run the
client I got the error: cound't create JNDI context:
jndi.naming.NameNotFoundException: jms not bound
are there another dd
Thanks,
Does this exception represent any problem or can this be ignored by just
truning off the DEBUG mode of the log?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891547#3891547
Reply to the post :
Thanks genman, I assume you mean the RedeliveryDelay attribute, and thus my
queue definition will be somewhat like this:
| mbean code=org.jboss.mq.server.jmx.Queue
name=jboss.mq.destination:service=Queue,name=Activities2
| depends
Anyone?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891361#3891361
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891361
---
SF.Net email is Sponsored by the Better
http://wiki.jboss.org/wiki/Wiki.jsp?page=IGetXAConnectionFactoryNotBoundHowDoIFixIt
Search got me an answer in about 2 seconds...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891365#3891365
Reply to the post :
You're right. But you should always verify yourself by testing.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891366#3891366
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891366
We've got a new wiki that explains in details how to integrate with WSMQ
http://wiki.jboss.org/wiki/Wiki.jsp?page=IntegrationWithWebSphereMQSeries
Part II is coming soon. We're still having issues with the buggy XA
implementation of WSMQ when it is used as the JMS provider of the MDB container.
Take a look at the attributes of a Queue in the JMX console.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891098#3891098
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891098
Is there any reason why you can't post a clear and proof-read message?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891099#3891099
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891099
Either something in your MDB class's constructor (should do nothing) is failing
or ejbCreate() is failing. Put try { xxx } catch (Throwable t) {
t.printStackTrace(); } around your ejbCreate calls.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891102#3891102
Thank you!
I had Spring injecting a POJO service in the onEjbCreate method and it was
reading the wrong context.xml file and I was getting a class cast exception.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891126#3891126
Reply to the post :
http://jira.jboss.com/jira/browse/JBAS-1805
This was fixed for 4.0.3...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891135#3891135
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891135
901 - 1000 of 4014 matches
Mail list logo
