[JBoss-user] [JCA/JBoss] - Re: Jboss 3.2.3, Oracle-DS leaking cursors

2004-07-24 Thread gfreemankc
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=bbop=viewtopicp=3843166#3843166

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3843166


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS JBossMQ] - Re: user: NULL is not authenticated

2004-06-19 Thread gfreemankc
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 the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839335#3839335

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839335


---
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS JBossMQ] - Re: user: NULL is not authenticated

2004-06-19 Thread gfreemankc
Here's my security manager mbean:
mbean code=org.jboss.mq.security.SecurityManager 
name=jboss.mq:service=SecurityManager
  | attribute name=DefaultSecurityConfig
  |   security
  | role name=guest read=true write=true create=true/
  |   /security
  | /attribute
  | attribute name=SecurityDomainjbossmq/attribute
  | depends 
optional-attribute-name=NextInterceptorjboss.mq:service=DestinationManager/depends
  |   /mbean
  | 

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839336#3839336

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839336


---
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS JBossMQ] - Re: user: NULL is not authenticated

2004-06-18 Thread gfreemankc
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.java:51)
at 
org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:781)
at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:287)
at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:302)
at org.jboss.mq.Connection.authenticate(Connection.java:876)
at org.jboss.mq.Connection.(Connection.java:238)
at org.jboss.mq.Connection.(Connection.java:315)
at org.jboss.mq.SpyConnection.(SpyConnection.java:60)
at 
org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:116)
at com.ourstuff.MDBMessageSender.init(MDBMessageSender.java:106)
at com.ourstuff.MDBMessageSender.sendEvent(MDBMessageSender.java:28)
at 
com.ourstuff.ProcessObjectServiceBean.sendUpdateNotifications(ProcessObjectServiceBean.java:1878)
at 
com.ourstuff.ProcessObjectServiceBean.setOrCreate(ProcessObjectServiceBean.java:1380)
at 
com.ourstuff.ProcessObjectServiceBean.set(ProcessObjectServiceBean.java:1270)
at 
com.ourstuff.ProcessObjectServiceBean.handleRequest(ProcessObjectServiceBean.java:84)
at sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at 
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:683)
at 
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185)
at 
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:72)
at 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:267)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:128)
at 
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:118)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
at 
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
at 
org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:331)
at org.jboss.ejb.Container.invoke(Container.java:700)
at 
org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:375)
at 
org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:83)
at $Proxy49.handleRequest(Unknown Source)
at 
com.ourstuff.ProcessObjectServiceWrapper.handleRequest(ProcessObjectServiceWrapper.java:66)
at com.ourstuff.ServiceRequestObj.send(ServiceRequestObj.java:114)
at 
com.ourstuff.ProcessCommandServiceBean.set(ProcessCommandServiceBean.java:322)
at 
com.ourstuff.ProcessCommandServiceBean.handleRequest(ProcessCommandServiceBean.java:120)
at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at 
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:683)
at 
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185)
at 
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:72)
at 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:320)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:128)
at 
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:118)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
at 
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
at 
org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:331)
at org.jboss.ejb.Container.invoke(Container.java:700)
at 
org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:375)
at 
org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:83)
at $Proxy50.handleRequest(Unknown Source)
at 

[JBoss-user] [Messaging, JMS JBossMQ] - Re: user: NULL is not authenticated

2004-06-18 Thread gfreemankc
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 DefaultCacheTimeout on the JaasSecurityManagerService to zero reproduced 
the error on the first message sent.

Modifying the JMS configuration to use the OIL IL resolved the issue (as well as a 
weird Hibernate/JBoss error about returning an unknown connection).

So, it _seems_ that the JVM IL only authenticates on server startup, and not during 
actual connections (haven't finished digging through the JBoss code yet).  Is this a 
defect, or just my mis-understanding of the JVM IL?


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839298#3839298

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839298


---
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS JBossMQ] - user: NULL is not authenticated

2004-06-17 Thread gfreemankc
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 [org.jboss.mq.Connection] Getting the serverIL
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] [EMAIL PROTECTED]
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] Authenticating
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.Connection] Authenticating user null
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : 
authenticate
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.security.ServerSecurityInterceptor] 
Autenticating user null/null
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.security.SecurityManager] Username: null 
is authenticated
2004-06-17 13:02:39,207 TRACE [org.jboss.mq.security.SecurityManager] Adding group : 
class org.jboss.security.NestableGroup Roles(members:guest)

The very next call (at a later time) has:
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] Connection Initializing
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] Getting the serverIL
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] [EMAIL PROTECTED]
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] Authenticating
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.Connection] Authenticating user null
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : 
authenticate
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.security.ServerSecurityInterceptor] 
Autenticating user null/null
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.sm.file.DynamicLoginModule] logout
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.security.SecurityManager] User: null is 
NOT authenticated
2004-06-17 13:20:53,408 TRACE [org.jboss.mq.server.TracingInterceptor] EXCEPTION : 
authenticate: 
javax.jms.JMSSecurityException: User: null is NOT authenticated


The thing I finde peculiar is the logout message.

The message sending code is:

QueueConnectionFactory queueFactory = (QueueConnectionFactory)
  | context.lookup(factoryName);
  | 
  | queueConnection = queueFactory.createQueueConnection();
  | 
and fails on the createQueueConnection() call (if it's not obvious).

The destination is configured as:

mbean code=org.jboss.mq.server.jmx.Queue
  |  name=jboss.mq.destination:service=Queue,name=myEvents
  | depends 
optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends
  | depends 
optional-attribute-name=SecurityManagerjboss.mq:service=SecurityManager/depends
  | attribute name=SecurityConf
  |   security
  | role name=guest read=true write=true/
  | role name=publisher read=true write=true create=false/
  |   /security
  | /attribute
  |   /mbean
We are also using the oracle persistence manager for our messages, and the 
conf/jbossmq-state.xml is unmodified:


  | User
  | Nameguest/Name
  | Passwordguest/Password
  | /User
  | *** Stuff removed ***
  | Role name=guest
  | UserNameguest/UserName
  | UserNamejohn/UserName
  | /Role
  | 
I hope I've provided the right amount of info, but please let me know if I left out a 
critical piece of info..

Best Regards


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839136#3839136

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839136


---
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user