Yes that is what it looks like. I have not specified default user id and
passowrd parameters in the cf object stored in the jndi. If I do specify
some user like guest I get proper error - user not authorized.
I missed to place the stack trace, here it is.
************
[#|2006-01-10T05:22:09.755-0500|SEVERE|sun-appserver-ee8.1|javax.enterprise.system.core.classloading|_ThreadID=13;|LDR5004:
UnExpected error occured while creating ejb container
java.lang.Exception
at
com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:230)
at
com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
at
com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
at
com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)
at
com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:125)
at
com.sun.enterprise.server.HttpServiceApplicationLoader.load(HttpServiceApplicationLoader.java:97)
at
com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:224)
at
com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:164)
at
com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:486)
at
com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:872)
at
com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:856)
at
com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:424)
at
com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at
com.sun.enterprise.ee.admin.mbeans.ServerRuntimeMBean.forwardEvent(ServerRuntimeMBean.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:302)
at
com.sun.enterprise.admin.runtime.BaseRuntimeMBean.invoke(BaseRuntimeMBean.java:383)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
at
javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1341)
at
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.resource.ResourceException: [C4084]: User
authentication failed: user=empty/blank, broker=sadie.east:8787(37767)
at
com.sun.genericra.util.ExceptionUtils.newResourceException(ExceptionUtils.java:68)
at
com.sun.genericra.inbound.InboundJmsResourcePool.initialize(InboundJmsResourcePool.java:83)
at
com.sun.genericra.inbound.EndpointConsumer.initialize(EndpointConsumer.java:119)
at
com.sun.genericra.inbound.EndpointConsumer.start(EndpointConsumer.java:112)
at com.sun.genericra.GenericJMSRA.endpointActivation(GenericJMSRA.java:97)
at
com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:221)
... 39 more
Caused by: com.sun.messaging.jms.JMSSecurityException: [C4084]: User
authentication failed: user=empty/blank, broker=sadie.east:8787(37767)
************
Regards,
Jaideep
Binod wrote:
> Are you saying that , MDB, actually does not use these properties and
> instead it uses
> the properties of the object bound in JNDI?
>
> - Binod.
>
>> Yes I have specified the UserName and Password in the sun-ejb-jar.xml
>>
>> here is the entry that I made.
>>
>> <activation-config-property>
>> <activation-config-property-name>UserName</activation-config-property-name>
>>
>> <activation-config-property-value>name</activation-config-property-value>
>> </activation-config-property>
>> <activation-config-property>
>> <activation-config-property-name>Password</activation-config-property-name>
>>
>> <activation-config-property-value>password</activation-config-property-value>
>>
>> </activation-config-property>
>>
>>
>> Regards,
>> Jaideep
>>
>>
>>
>>
>> Binod wrote:
>>
>>> Hi Jaideep,
>>>
>>>> Hi Binod,
>>>>
>>>> I got struck at a place, can you pls. suggest something here.
>>>>
>>>> In our setup we have four topics and MDBs listening to these
>>>> topics, additionally we have four users privileged to
>>>> subscribe/listen to these topics. We have configured subscription
>>>> type as durable in the MDB.
>>>> We want to have a single connection factory/connector connection
>>>> pool , and have the four mdbs deployed using the genericjmsra.
>>>> I am trying to configure a single durable mdb on one of the
>>>> topics. I am not able to specify the user id password for the
>>>> connection factory. I want to have it set at the time of deployment
>>>> so that I can specify different user ids for all the four MDBs.
>>>
>>>
>>>
>>>
>>> I thought you can specify UserName and Password as explicit
>>> activation-config properties or connection pool property. You dont
>>> need to depend
>>> on bound JNDI object for that. Did you try that?
>>>
>>> thanks,
>>> Binod.
>>>
>>>> I can't specify the user id and password in the cf stored in the
>>>> ldap as that would not allow the other MDB to connect to their
>>>> respective topics.
>>>>
>>>>
>>>> Regards,
>>>> Jaideep
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
>>> For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
>> For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
> For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>