Problem solved. Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256935#4256935
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256935
___
jboss-user mailing list
jboss-u
Yes. I am assuming that this will fix
https://jira.jboss.org/jira/browse/EJBTHREE-1910 and can work with 5.1.0?? As
usual, thanks for your prompt reply.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255622#4255622
Reply to the post :
http://www.jboss.org
Hello,
Any idea when 1.1.16 will be released? Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255334#4255334
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255334
___
I actually just tried JBM 2.0 Beta and it worked correctly. Same code different
JMS implementation. I will see if I can dig deeper.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252716#4252716
Reply to the post :
http://www.jboss.org/index.html?module=bb&op
We use "ConnectionFactory" to create the connection factory which is defined as:
|
| jboss.messaging:service=ServerPeer
| jboss.messaging:service=Connector,transport=bisocket
| jboss.messaging:service=PostOffice
|
|
|
| /ConnectionF
No I did not expect it to set the principal to the context. However, I also did
not expect the send call to "wipe-out" the existing credentials associated with
the calling thread.
| System.out.println("In start of JMS Feed Session:"
| + JBossUtils.getCurrentUsername());
Just to add a couple of things about our configuration, JBM is using the
default "messaging" realm with no changes.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252596#4252596
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=r
Hello,
I hope that this is the right forum for this. We are undergoing an effort to
switch to JBOSS messaging from ActiveMQ (Soon 2.x). Our first effort is to get
our stuff to work with JBM 1.4x and then 2.x. We have noticed that when we
send a message using JMS, the current active principal i
We believe that found the problem area. When we come back from a JMS call, the
currently authenticated user is no longer the one that was active before the
call. This is all on the server.
When we setup the server, we left the JBOSS messaging security settings as is.
We are assuming that "guest
We are having a similar problem with similar setup as yours.
Some of the logs show:
anonymous wrote :
|
| 08:50,153 INFO [STDOUT] (MessageDispatcher [ReportFeed] pool-24-thread-2)
client-login.Logging out from threadMessageDispatcher [ReportFeed]
pool-24-thread-2
| 1
A JIRA should be opened.The JMS connection is no longer valid in between
restarts and the connection listener must be called. Your solution that
involves a server id makes sense.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226486#4226486
Reply to the pos
Tim,
Do we know if the new network library handles this particular issue better than
JBOSS remoting? How far along is 2.0? From the website, it is still Alpha.
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223340#4223340
Reply to the post :
http:/
Tim,
We are trying to avoid cross posting as this is really a remoting issue that
can be tracked here.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=457#457
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223006#4223006
Reply to the post :
Ok. This is pretty lengthy (2 Scenarios. One with long pingPeriod and the other
one with a much shorter one). The ping period is set to 70 seconds the same as
the ping timeout. Server comes back in under 70 seconds from the restart.
Scenario where the server is restarted before ping period. No l
ActiveMQ's solution was above and beyond the TTL. This is a serious issue that
needs to be fixed by the JBOSS folks asap. No respectable messaging middle-ware
should ever be held hostage to a rogue client.
Unfortunately, we had to abandon our migration to JBM from ActiveMQ because of
this issue
We are experiencing the exact same problem on Linux. This is very easy to
reproduce. Have two clients running against a server and pull the network cable
from one of the clients simulating a kernel death. A few seconds later, the
server puts out:
anonymous wrote : 13:07:15,064 WARN [SimpleConn
anonymous wrote : Are you actually seeing a case where "the client's JMS
connection listener does not get called yet the connection is invalid" ?
Yes. Only when the server restarts in a time that is less than the ping period.
anonymous wrote : Make the tt (WaitOnConnectionCheckTimerTask) a clas
Hi Ron,
I think that their might be an issue with your suggestion. perhaps you can
explain this behavior. I took your advice and bumped up the pingperiod to be
more that the timeout and noticed that if we restart the server from under the
client and the server comes back in less time than the p
I think that you are seeing the same problem that is described here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151397
I am attaching a version of ConnectionValidator that fixed the problem for us:
| /*
| * JBoss, Home of Professional Open Source
| * Copyright 2005, JBoss In
Hello,
I think we have stumbled upon a bug in the ConnectionValidator.
Scenario
pingPeriod is set to 10 seconds and pingTimeout is set to 70 seconds, client
leasetime is 70 seconds. Using 2.2 SP11 on JDK 1.6 (Linux)
Ctrl-z the server for more than 20 seconds but less than 70 seconds. When the
Hello,
This topic has been discussed several times before. Basically, the commit order
when a row is inserted into the database and a JMS message notifying interested
listeners of that fact. Given that JTA does not dictate the commit order, the
MDB might get the message first without the row be
Hello,
We downloaded the source for 4.0.5 and tried to run the server but got the
following exception. Looking at the JmsActivationSpec class, it seems to be
missing the maxPoolSize (and minPoolSize) properties. What is the proper way of
specifying those in 4.0.5? Thank you.
Exception
Hello,
We downloaded the source for 4.0.5 and tried to run the server but got the
following exception. Looking at the JmsActivationSpec class, it seems to be
missing the maxPoolSize (and minPoolSize) properties. What is the proper way of
specifying those in 4.0.5? Thank you.
Exception
23 matches
Mail list logo
