The question was very specifically regarding oracle. Oracle very specifically states
in their documentation that result sets are not closed when the connection is closed.
Blame Oracle for their jdbc driver.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=38431
Here's my security manager mbean:
|
|
|
|
|
| jbossmq
| jboss.mq:service=DestinationManager
|
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839336#3839336
Reply to the post :
http://www.jboss.
So, changing to OIL didn't resolve the issue, I still had the security manager
disabled.
I tried defining my queue as above, without the dependency on the security manager,
but the result was the same - user null is NOT authenticated.
I just don't understand why it's not working... :(
View th
Here's what I found out regarding this:
The user: null is NOT authenticated was happening 30 minutes after the server started
- the default for the JaasSecurityManagerService cache.
We were using the JVM IL (I don't know why. I guess we assumed it would have the best
performance).
Setting the
Here's the full stack trace, if it helps any:
javax.jms.JMSSecurityException: User: null is NOT authenticated
at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:232)
at
org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.j
We're having an issue with our queue where we are unable to send messages to it after
a period of inactivity. We're using JBoss 3.2.3 (on Windows)
The mq trace log has the following:
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] Connection Initializing
2004-06-17 13:02:39,207 TRACE [or
