Nope :-(
We are still using jboss 4.2.1 which runs fine with this configuration.
Cheers,
Martin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128320#4128320
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128320
jboss 4.2.2, messaging 1.4.0SP3, non-clustered
The same application works fine with jboss 4.2.1
anonymous wrote :
| 2008-01-15 11:42:35,076 ERROR
[org.jboss.resource.adapter.jms.inflow.JmsServerSession] Unexpected error
delivering message delegator->JBos
| sMessage[738523295]:NON-PERSISTE
I tried it, but it makes no difference
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120027#4120027
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120027
___
jboss-user maili
we are running this in production with jboss4.2.1 and messaging 1.4.0 since
last summer. I basically just switched to newer versions.
That problem is new.
How can I increase the number od connections?
Thanks,
Martin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtop
jboss 4.2.2, messaging 1.4.0SP3, non-clustered
I'm not sure if this is related to messaging or ejb3...
anonymous wrote :
| 2008-01-15 11:42:35,076 ERROR
[org.jboss.resource.adapter.jms.inflow.JmsServerSession] Unexpected error
delivering message delegator->JBos
| sMessage[738523295]:NON-PE
After several days (7-11) we get the following exception.
At the time of the exception there about 1000 threads, but
exactly this jboss had more threads earlier in its lifetime.
The server is running Linux, jdk 1.6.0_02, jboss 4.2.1 and jboss-messaging
1.4.2.CR1.
Best regards,
Martin
anonymous
Tim,
YES! that fixes the problem!
Thank you very much.
Will the fix make it into 1.4.0.CR2?
Cheers,
Martin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070049#4070049
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p
We are using jboss 4.2.1, and Messaging 1.4.0CR1
We have a lot of servlets that listen to topics or produce into queues and
sooner or later the messaging is completely stuck.
Here is a sample stacktrace where the thread wants to create a new session.
This is were most of the threads are blocked
I just got this again. The real bad thing is that jboss didn't recover and
produced the Exception over and over. Only a restart helped :-(
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986105#3986105
Reply to the post :
http://www.jboss.com/index.html?
We see the same number of creates and commits.
It is a EJB3 MDB which sends new messages and accesses the database in the
onMessage() method.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984870#3984870
Reply to the post :
http://www.jboss.com/index.html?
Hi,
we are using jboss 404 with messaging 1.0.1.GA and EJB3
The queue in question is non persistent and does not grow,
so the messages do get delivered and processed fast enough.
We observe the heap growing with instances of TxState and ArrayLists which
belong to TxState, see output of heap an
We had the same problem, but adding
messageListenerInterface=MessageListener.class
to the MessageDriven annotation fixes it.
It's what the spec requires...
Cheers,
Martin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983496#3983496
Reply to the post :
h
No. We had it several times that one day, but not since then.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973825#3973825
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973825
___
We get this Exception on jboss 4.0.4GA with ejb3 config and messaging
1.0.1.CR4, using ejb3 mdb while putting many messages into a queue concurrently
on a SMP server with 4 CPUs.
Unfortunately we are not able to reproduce this reliably, but I would be happy
to answer any question about the cont
Tim,
thanks for the hint, I'll switch immediately to CR4 persistence manager
configuration!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964974#3964974
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964974
_
we encounter the same problem with CR4:
anonymous wrote :
| 2006-08-14 13:17:10,204 DEBUG [org.jboss.jms.server.destination.Queue]
Starting jboss.messaging.destination:service=Queue,name=acd-call-signal
| s
| 2006-08-14 13:17:10,206 DEBUG
[org.jboss.messaging.core.plugin.JDBCPersistenceMa
sounds good!
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960299#3960299
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960299
___
jboss-user mailing list
jboss-user
17 matches
Mail list logo