I have trouble coming up with a failing test for this. This is what I tried
(and it passed):
|public void testDurableSubscriptionWithPeriodsInName() throws Exception
|{
| ConnectionFactory cf =
(ConnectionFactory)ic.lookup(ConnectionFactory);
| Topic topic =
I got it - have to undeploy/redeploy the topic to get the error.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4059889#4059889
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059889
Fixed. http://jira.jboss.com/jira/browse/JBMESSAGING-1008 is the issue, for
future reference.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4059915#4059915
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059915
I'm using Seam from CVS (checked out today, June 30th). I have a component that
has a property of type DataModel. I'm not using @DataModel annotation.
The problem is that the contents of my DataModel are not being shown on a page.
The culprit seems to be ManagedEntityIdentityInterceptor which
Some more information - this seems to be related to
http://jira.jboss.com/jira/browse/JBSEAM-586. Commenting out the bits where the
interceptor calls setWrappedData on the datamodel makes the problem go away.
View the original post :
See this thread: http://www.jboss.com/index.html?module=bbop=viewtopict=110947
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4058079#4058079
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058079
I'll fix those, thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4058225#4058225
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058225
___
jboss-user mailing list
I think it would be a nice addition to the page actions mechanism if it was
possible to specify that a certain component is to be instantiated when the
page is visited, unless the component already exists. This would allow me to
put some initialization code for a page into that component's
Created http://jira.jboss.com/jira/browse/JBMESSAGING-994 for the security
issue.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4055533#4055533
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4055533
I have created a JIRA issue (http://jira.jboss.com/jira/browse/JBMESSAGING-993)
for the first problem you describe (temporary destinations should not be bound
to JNDI). As I investigate the other problems you mentioned I will create more
issues if needed.
View the original post :
Is there a class I could use to parse a deployment descriptor such as the one
below? I need to get the attribute values programmatically (for testing
purposes).
Thanks,
Sergey
server
|
|!-- Standard bisocket connector - the bisocket transport only opens
connection from client-server
Tim, please correct me if I'm wrong on this:
I don't think there's anything in the JMS spec about behavior of clustering and
failover. In any case, you only need to re-lookup the connection factory if the
entire cluster goes down and is restarted later, not if just one node fails.
Basically,
I investigated this with help from Tim. The example worked fine for me,
transparent failover was really transparent, and non-transparent failover also
worked.
To make it handle the situation when the entire cluster goes down, I modified
the example to re-lookup the connection factory from JNDI
Hi Ron,
actually, this exception only occurs near the point where the test suite hangs,
so it might be useful, don't take it out just yet :)
Sergey
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4047792#4047792
Reply to the post :
Hi,
when I run the full JBoss Messaging test suite on my machine (Windows XP SP2,
JDK 1.5.0_11) it often hangs on a test. Running that test alone works fine. I
suspect remoting may be the cause of the lock up. Can you offer any advice in
debugging this problem?
Thanks,
Sergey
View the
Yes, BridgeTest.testStressSameServer_DuplicatesOk_P_50 was the one that I found
hung up today in the morning. I'll try looking in the logs next time, though
I'm not sure what to look for.
Why does the problem only happen on Windows? Tim runs messaging tests on Linux
and says they work fine
I re-ran the tests and looked in the logs this time. I can't really tell
anything from them so far, but there is this error I have also seen under many
different circumstances:
| 00:41:57,328 DEBUG @WorkerThread#82[127.0.0.1:3127] [ServerThread]
WorkerThread#82[127.0.0.1:3127] closing
I'm trying to get into JBoss Messaging and I decided to start by retrieving SVN
trunk and running its test cases. I am able to start the tests according to the
instructions on the Wiki and see them run, but they take a very long time to
execute.
The Wiki page says they should finish in about
I'm trying to get into JBoss Messaging and I decided to start by retrieving SVN
trunk and running its test cases. I am able to start the tests according to the
instructions on the Wiki and see them run, but they take a very long time to
execute.
The Wiki page says they should finish in about
I found a test that seems to take a lot of time:
ConnectionTest.testManyConnections (running as remote test). It has been
running for about half an hour for me already. Given that it doesn't do much,
I'm puzzled as to why it runs so slow.
View the original post :
MySQL 5.0. Should I try a different one? HSQL seemed to be about as slow.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4028416#4028416
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4028416
The ConnectionTest timed out, the rest are fine.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4028435#4028435
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4028435
___
jboss-user
Latest update:
Thanks to Clebert, I managed to run ConnectionTest.testManyConnections by
itself. The test is simply createConnection()/close() in a loop, 1000 times.
I then looked at the logs it produces, and from there it looks like the client
makes 300 connections successfully, and blocks on
23 matches
Mail list logo
