users@genericjmsra.java.net

RE: Re: Issue in glassfish configuration with Tibco EMS and MDB

From: Deepu Syamaladevi Janardhananachary <Deepu.Janardhananachary_at_ust-global.com>
Date: Fri, 27 Nov 2009 11:25:10 +0530

Hi,

 

If I am using glassfish server for some time , it is getting hung every day when checking in the morning. It is found as stopped status. Not even starting when trying through the console. Showing as port conflict. So I changed the ports in the domain.xml. Finally it got started up and worked fine. Now again the next day it is showing the error like this.

 

 

[#|2009-11-26T23:05:43.937-0600|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=1247;_ThreadName=Timer-8;_RequestID=09c97af6-c395-4d81-949f-edfe9c972cc9;|"DPL8011: autodeployment failure while deploying the application : null"|#]

 

[#|2009-11-26T23:05:44.722-0600|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=1251;_ThreadName=Timer-0;_RequestID=8879583a-f9df-4c33-9db4-65a0a3bc9deb;|

java.lang.NullPointerException

      at com.sun.jbi.management.system.AutoAdminTask.pollAutoDirectory(AutoAdminTask.java:1031)

      at com.sun.jbi.management.system.AutoAdminTask.performAutoInstall(AutoAdminTask.java:329)

      at com.sun.jbi.management.system.AutoAdminTask.performAutoFunctions(AutoAdminTask.java:288)

 

 

When tried to start throught he console it is again saying as "There is a conflict on port 8089". If I chavnge this it will work for the time being but tomorrow it will show again the same thing.

 

What to do now?

Do I need to create another domain now?

 

 

Thanks and Regards

Deepu Janardhananachary

 

-----Original Message-----
From: Ramesh.Parthasarathy_at_Sun.COM [mailto:Ramesh.Parthasarathy_at_Sun.COM]
Sent: Monday, November 23, 2009 4:59 PM
To: users_at_genericjmsra.dev.java.net
Cc: Seema Richard
Subject: Re: Issue in glassfish configuration with Tibco EMS and MDB

 

if you have a log statement in your MDB that is trying to log the entire

message object, then remove it and try..

 

-Ramesh

 

Deepu Syamaladevi Janardhananachary wrote:

>

> Hi,

>

> The MDB is working fine now.

>

> Thanks Ramesh

>

> But I am getting an exception after receiving the message in the MDB

>

> I think it is because of this that the message is not getting

> confirmed and so the messages

>

> [#|2009-11-23T04:40:35.671-0600|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=211;_ThreadName=p:

> thread-pool-1; w: 77;_RequestID=445c13e0-dcf1-4033-b69a-d761e0c61b51;|

>

> *java.util.logging.ErrorManager*: 5: Error in formatting Logrecord|#]

>

> [#|2009-11-23T04:40:35.672-0600|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=211;_ThreadName=p:

> thread-pool-1; w: 77;_RequestID=445c13e0-dcf1-4033-b69a-d761e0c61b51;|

>

> *java.lang.IllegalArgumentException: cant parse argument number*

> Header={ JMSMessageID={ID:DICC08.11DB4A8BBB4B595AD:1}

> JMSDestination={Queue[REQUEST2.QUEUE]} JMSReplyTo={null}

> JMSDeliveryMode={PERSISTENT} JMSRedelivered={false}

> JMSCorrelationID={3720021258972826} JMSType={null} JMSTimestamp={Mon

> Nov 23 04:40:26 CST 2009} JMSExpiration={0} JMSPriority={4} }

> Properties={ } Text={hi hello

>

> }

>

> at java.text.MessageFormat.makeFormat(MessageFormat.java:1339)

>

> at java.text.MessageFormat.applyPattern(MessageFormat.java:458)

>

> at java.text.MessageFormat.<init>(MessageFormat.java:350)

>

> at java.text.MessageFormat.format(MessageFormat.java:811)

>

> at

> com.sun.enterprise.server.logging.UniformLogFormatter.uniformLogFormat(UniformLogFormatter.java:329)

>

> Thanks and Regards

>

> Deepu Janardhananachary

>

> -----Original Message-----

> From: Ramesh.Parthasarathy_at_Sun.COM [mailto:Ramesh.Parthasarathy_at_Sun.COM]

> Sent: Friday, November 13, 2009 5:23 PM

> To: users_at_genericjmsra.dev.java.net

> Cc: Seema Richard

> Subject: Re: Issue in glassfish configuration with Tibco EMS and MDB

>

> This is not a username/pwd for creating connection, its asking for

>

> name/pwd for the jndi lookup, you should pass the credentials by setting

>

> it as part of JndiProperties

>

> -Ramesh

>

> Deepu Syamaladevi Janardhananachary wrote:

>

> >

>

> > Hi Ramesh,

>

> >

>

> > I am getting the error like below even after I gave the username and

>

> > password correctly.

>

> >

>

> > I have given the username and password in the genericra through

>

> > adminGUI. It is coming in the domain.xml also.

>

> >

>

> > Do I need to give Username and Password anywhere else?

>

> >

>

> >

> [#|2009-11-13T16:21:29.352+0530|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=46;_ThreadName=Thread-2818;_RequestID=af466d3e-d037-4b70-a191-ede5de83850d;|

>

> >

>

> > javax.resource.spi.InvalidPropertyException: Not permitted: invalid

>

> > name or password

>

> >

>

> > at

>

> >

> com.sun.genericra.util.ExceptionUtils.newInvalidPropertyException(ExceptionUtils.java:42)

>

> >

>

> > at

>

> >

> com.sun.genericra.util.ObjectBuilderFactory$JndiObjectBuilder.createObject(ObjectBuilderFactory.java:100)

>

> >

>

> > at com.sun.genericra.util.ObjectBuilder.build(ObjectBuilder.java:99)

>

> >

>

> > ................

>

> >

>

> > .... . . .

>

> >

>

> > . . . .

>

> >

>

> > Caused by: javax.naming.AuthenticationException: Not permitted:

>

> > invalid name or password [Root exception is

>

> > javax.jms.JMSSecurityException: invalid name or password]

>

> >

>

> > at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:668)

>

> >

>

> > at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)

>

> >

>

> > Thanks and Regards

>

> >

>

> > Deepu

>

> >

>

> > -----Original Message-----

>

> > From: Ramesh.Parthasarathy_at_Sun.COM [mailto:Ramesh.Parthasarathy_at_Sun.COM]

>

> > Sent: Wednesday, November 11, 2009 9:17 PM

>

> > To: Deepu Syamaladevi Janardhananachary

>

> > Cc: users_at_genericjmsra.dev.java.net; Seema Richard

>

> > Subject: Re: Issue in glassfish configuration with Tibco EMS and MDB

>

> >

>

> > As far as i know, the exception is thrown if the Jndi configuration is

>

> >

>

> > not correct

>

> >

>

> > Thanks

>

> >

>

> > -Ramesh

>

> >

>

> > Deepu Syamaladevi Janardhananachary wrote:

>

> >

>

> > > Yes currently in the domain.xml it is exactly looking like what you

>

> > mentioned

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > > Thanks and Regards

>

> >

>

> > > Deepu Janardhananachary

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > >

>

> >

>

> > > -----Original Message-----

>

> >

>

> > > From: Ramesh.Parthasarathy_at_Sun.COM

>

> > [mailto:Ramesh.Parthasarathy_at_Sun.COM]

>

> >

>

> > > Sent: Wednesday, November 11, 2009 8:38 PM

>

> >

>

> > > To: users_at_genericjmsra.dev.java.net

>

> >

>

> > > Cc: Seema Richard

>

> >

>

> > > Subject: Re: Issue in glassfish configuration with Tibco EMS and MDB

>

> >

>

> > >

>

> >

>

> > > Have you fixed the JndiProperties section of ra-config, it should look

>

> >

>

> > > like this

>

> >

>

> > > <property name="JndiProperties"

>

> >

>

> > >

>

> >

> value="java.naming.factory.url.pkgs=com.tibco.tibjms.naming,java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory,java.naming.provider.url=tcp://hostName.com:portNumber"/>

>

> >

>

> > >

>

> >

>

> > > -Ramesh

>

> >

>

> > > Deepu Syamaladevi Janardhananachary wrote:

>

> >

>

> > >

>

> >

>

> > >> I am getting this error when deploying the MDB. How do I need to

>

> >

>

> > >> proceed?

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >> Please advise

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

> [#|2009-11-11T19:16:11.026+0530|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=69;_ThreadName=Thread-2500;ClassName=com.sun.genericra.util.ObjectBuilderFactory;MethodName=debug;_RequestID=27755480-2ff6-4306-bea8-0fa56f4f9edd;|Looking

>

>

> >

>

> >

>

> > >> the JNDI name :null|#]

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

> [#|2009-11-11T19:16:11.026+0530|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=69;_ThreadName=Thread-2500;_RequestID=27755480-2ff6-4306-bea8-0fa56f4f9edd;|

>

> >

>

> > >>

>

> >

>

> > >> javax.resource.spi.InvalidPropertyException

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.genericra.util.ExceptionUtils.newInvalidPropertyException(ExceptionUtils.java:42)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.genericra.util.ObjectBuilderFactory$JndiObjectBuilder.createObject(ObjectBuilderFactory.java:100)

>

> >

>

> > >>

>

> >

>

> > >> at com.sun.genericra.util.ObjectBuilder.build(ObjectBuilder.java:99)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.genericra.inbound.EndpointConsumer.initializeAdministeredObjects(EndpointConsumer.java:333)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.genericra.inbound.EndpointConsumer.<init>(EndpointConsumer.java:74)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> > com.sun.genericra.GenericJMSRA.endpointActivation(GenericJMSRA.java:214)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:252)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:524)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:536)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.server.ApplicationLoader.doLoad(ApplicationLoader.java:188)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:126)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

> com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:744)

>

> >

>

> > >>

>

> >

>

> > >> 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:375)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)

>

> >

>

> > >>

>

> >

>

> > >> 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 sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

>

> >

>

> > >>

>

> >

>

> > >> at java.lang.reflect.Method.invoke(Method.java:585)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)

>

> >

>

> > >>

>

> >

>

> > >> at $Proxy1.invoke(Unknown Source)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:145)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:537)

>

> >

>

> > >>

>

> >

>

> > >> at java.lang.Thread.run(Thread.java:595)

>

> >

>

> > >>

>

> >

>

> > >> Caused by: java.lang.NullPointerException

>

> >

>

> > >>

>

> >

>

> > >> at javax.naming.InitialContext.getURLScheme(InitialContext.java:228)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:277)

>

> >

>

> > >>

>

> >

>

> > >> at javax.naming.InitialContext.lookup(InitialContext.java:351)

>

> >

>

> > >>

>

> >

>

> > >> at

>

> >

>

> > >>

>

> >

> com.sun.genericra.util.ObjectBuilderFactory$JndiObjectBuilder.createObject(ObjectBuilderFactory.java:98)

>

> >

>

> > >>

>

> >

>

> > >> ... 48 more

>

> >

>

> > >>

>

> >

>

> > >> |#]

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >> Thanks and Regards

>

> >

>

> > >>

>

> >

>

> > >> Deepu Janardhananachary

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >> -----Original Message-----

>

> >

>

> > >> From: Ramesh.Parthasarathy_at_Sun.COM

>

> > [mailto:Ramesh.Parthasarathy_at_Sun.COM]

>

> >

>

> > >> Sent: Wednesday, November 11, 2009 9:17 AM

>

> >

>

> > >> To: Deepu Syamaladevi Janardhananachary

>

> >

>

> > >> Cc: users_at_genericjmsra.dev.java.net; Seema Richard

>

> >

>

> > >> Subject: Re: Issue in glassfish configuration with Tibco EMS and MDB

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >> I dont see the "jms/ConnectionFactory" in the MDB at all ....

>

> >

>

> > >>

>

> >

>

> > >> Note, that you have to use deployment descriptor if you are using

>

> >

>

> > >>

>

> >

>

> > >> generic ra, because there are no annotations for specifying a custom

>

> >

>

> > >>

>

> >

>

> > >> resource adapter in EJB3.

>

> >

>

> > >>

>

> >

>

> > >> <property name="JndiProperties"

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

> value="java.naming.factory.url.pkgs\=com.tibco.tibjms.naming,java.naming.factory.initial\=com.tibco.tibjms.naming.TibjmsInitialContextFactory,java.naming.provider.url\=tcp\://hostName.com\:portNumber"/>

>

> >

>

> > >>

>

> >

>

> > >> If you have created the ra-config from admin GUI you dont have to

>

> > escape

>

> >

>

> > >>

>

> >

>

> > >> the "=" or ":"

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >> Thanks

>

> >

>

> > >>

>

> >

>

> > >> -Ramesh

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >> Deepu Syamaladevi Janardhananachary wrote:

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>> Do I need to use both ejb-jar.xml and sun-ejb-jar.xml?

>

> >

>

> > >>>

>

> >

>

> > >>> I am using EJB 3. When I created the workspace in eclipse ganymede,

>

> >

>

> > >>>

>

> >

>

> > >>> only sun-ejb-jar.xml got created automatically.

>

> >

>

> > >>>

>

> >

>

> > >>> Is the domain.xml which I sent last got correct entries?

>

> >

>

> > >>>

>

> >

>

> > >>> Regards,

>

> >

>

> > >>>

>

> >

>

> > >>> Deepu Janardhananachary

>

> >

>

> > >>>

>

> >

>

> > >>> -----Original Message-----

>

> >

>

> > >>>

>

> >

>

> > >>> From: Ramesh [mailto:Ramesh.Parthasarathy_at_Sun.COM]

>

> >

>

> > >>>

>

> >

>

> > >>> Sent: Wed 11/11/2009 6:48 AM

>

> >

>

> > >>>

>

> >

>

> > >>> To: users_at_genericjmsra.dev.java.net

>

> >

>

> > >>>

>

> >

>

> > >>> Cc: Seema Richard

>

> >

>

> > >>>

>

> >

>

> > >>> Subject: Re: Issue in glassfish configuration with Tibco EMS and MDB

>

> >

>

> > >>>

>

> >

>

> > >>>> Is this due to mapping error?

>

> >

>

> > >>>>

>

> >

>

> > >>>> If yes how do I need to mapping?

>

> >

>

> > >>>>

>

> >

>

> > >>> Should be in your ejb-jar xml, the resources (queue and connection

>

> >

>

> > >>>

>

> >

>

> > >>> factory) should be there.

>

> >

>

> > >>>

>

> >

>

> > >>> -Ramesh

>

> >

>

> > >>>

>

> >

>

> > >>> Deepu Syamaladevi Janardhananachary wrote:

>

> >

>

> > >>>

>

> >

>

> > >>>> I have executed the "Configuring the Resource Adapter" portion

> again.

>

> >

>

> > >>>>

>

> >

>

> > >>>> Finally I got entries in the domain.xml

>

> >

>

> > >>>>

>

> >

>

> > >>>> PFA the latest domain.xml

>

> >

>

> > >>>>

>

> >

>

> > >>>> When I deployed the ear I got the error.

>

> >

>

> > >>>>

>

> >

>

> > >>

>

> >

> [#|2009-11-11T00:01:10.870+0530|WARNING|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=24;_ThreadName=Thread-645;_RequestID=76e0b935-3439-43fb-b1e9-28ef1cb84069;|This

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>> bean [MDBTest1] has no resource reference by the name of

>

> >

>

> > >>>>

>

> >

>

> > >>>> [jms/ConnectionFactory]|#]

>

> >

>

> > >>>>

>

> >

>

> > >>

>

> >

> [#|2009-11-11T00:01:10.870+0530|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=24;_ThreadName=Thread-645;jndi-name;jms/ConnectionFactory;_RequestID=76e0b935-3439-43fb-b1e9-28ef1cb84069;|"DPL8007:

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>> Invalid Deployment Descriptors element jndi-name value

>

> >

>

> > >>>>

>

> >

>

> > >>>> jms/ConnectionFactory"|#]

>

> >

>

> > >>>>

>

> >

>

> > >>

>

> >

> [#|2009-11-11T00:01:11.338+0530|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=24;_ThreadName=Thread-645;_RequestID=76e0b935-3439-43fb-b1e9-28ef1cb84069;|Exception

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>> occured in J2EEC Phasejava.lang.NullPointerException

>

> >

>

> > >>>>

>

> >

>

> > >>>> com.sun.enterprise.deployment.backend.IASDeploymentException: Error

>

> >

>

> > >>>>

>

> >

>

> > >>>> loading deployment descriptors for module [WUMT] -- null

>

> >

>

> > >>>>

>

> >

>

> > >>>> at

>

> >

>

> > >>>>

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:390)

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>> at

>

> >

>

> > >>>>

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358)

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>> Is this due to mapping error?

>

> >

>

> > >>>>

>

> >

>

> > >>>> If yes how do I need to mapping?

>

> >

>

> > >>>>

>

> >

>

> > >>>> Where do I need to write the code shown in the link under the

> heading

>

> >

>

> > >>>>

>

> >

>

> > >>>> "A sample of the lookup done for the Connection factories and

>

> > creating

>

> >

>

> > >>>>

>

> >

>

> > >>>> the session is given below." ?

>

> >

>

> > >>>>

>

> >

>

> > >>>> Thanks and Regards

>

> >

>

> > >>>>

>

> >

>

> > >>>> Deepu Janardhananachary

>

> >

>

> > >>>>

>

> >

>

> > >>>> -----Original Message-----

>

> >

>

> > >>>>

>

> >

>

> > >>>> From: Ramesh.Parthasarathy_at_Sun.COM

>

> >

>

> > >>>>

>

> >

>

> > >> [mailto:Ramesh.Parthasarathy_at_Sun.COM]

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>> Sent: Tuesday, November 10, 2009 9:29 PM

>

> >

>

> > >>>>

>

> >

>

> > >>>> To: users_at_genericjmsra.dev.java.net

>

> >

>

> > >>>>

>

> >

>

> > >>>> Cc: Seema Richard; Deepu Syamaladevi Janardhananachary

>

> >

>

> > >>>>

>

> >

>

> > >>>> Subject: Re: Issue in glassfish configuration with Tibco EMS

> and MDB

>

> >

>

> > >>>>

>

> >

>

> > >>>> 1. I dont see the ra config in the domain.xml, have u created it

>

> >

>

> > >>>>

>

> >

>

> > >> as per

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>> "Configuring the Resource Adapter"

>

> >

>

> > >>>>

>

> >

>

> > >>>> 2. I do not see the Tibco classes in the classpath prefix of

> server,

>

> >

>

> > >>>>

>

> >

>

> > >>>> without which your integration is not going to work

>

> >

>

> > >>>>

>

> >

>

> > >>>> has to be done as per 3rd bullet in "Initial Setup"

>

> >

>

> > >>>>

>

> >

>

> > >>>> Thanks

>

> >

>

> > >>>>

>

> >

>

> > >>>> -Ramesh

>

> >

>

> > >>>>

>

> >

>

> > >>>> Deepu Syamaladevi Janardhananachary wrote:

>

> >

>

> > >>>>

>

> >

>

> > >>>>> PFA

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> Thanks and Regards

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> Deepu Janardhananachary

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> -----Original Message-----

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> From: Ramesh.Parthasarathy_at_Sun.COM

>

> >

>

> > >>>>>

>

> >

>

> > >>>> [mailto:Ramesh.Parthasarathy_at_Sun.COM]

>

> >

>

> > >>>>

>

> >

>

> > >>>>> Sent: Tuesday, November 10, 2009 8:37 PM

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> To: users_at_genericjmsra.dev.java.net

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> Cc: Seema Richard

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> Subject: Re: Issue in glassfish configuration with Tibco EMS

> and MDB

>

> >

>

> > >>>>>

>

> >

>

> > >>>>>> Do I need to give my queue name in the place of Queue?

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>> Yes,

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> and I need to see your deployment descriptor and domain.xml to

>

> >

>

> > >>>>>

>

> >

>

> > >> comment

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>> on the exception

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> -Ramesh

>

> >

>

> > >>>>>

>

> >

>

> > >>>>> Deepu Syamaladevi Janardhananachary wrote:

>

> >

>

> > >>>>>

>

> >

>

> > >>>>>> Hi Ramesh,

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> I have done as in the document

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> I am using EJB3.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> I have done exactly like in the document.

>

> >

>

> > >>>>>>

>

> >

>

> > >>

>

> >

> https://genericjmsra.dev.java.net/docs/tibco-genericjmsra-integration-sample-doc/Integrating_Sun_Java_System_Application_Server_with_Tibco_JMS_using_the_Generic_Resource_Adapter_for_JMS.html

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> In the document in the sun-ejb-jar entry it is mentioned as

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> imqDestinationName=Queue

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> Do I need to give my queue name in the place of Queue?

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> When I tried to deploy the ear file I got the error like the

>

> >

>

> > >>>>>>

>

> >

>

> > >>> following

>

> >

>

> > >>>

>

> >

>

> > >>>>>> Could you please tell me where is the mapping miss match

> happened?

>

> >

>

> > >>>>>>

>

> >

>

> > >>

>

> >

> [#|2009-11-10T20:13:30.151+0530|WARNING|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=60;_ThreadName=Thread-5373;_RequestID=7d1bb0da-cfcf-4365-ad8d-35d0f43e627f;|This

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> bean [MDBTest1] has no resource reference by the name of

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> [jms/QCFactory]|#]

>

> >

>

> > >>>>>>

>

> >

>

> > >>

>

> >

> [#|2009-11-10T20:13:30.151+0530|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=60;_ThreadName=Thread-5373;jndi-name;jms/QCFactory;_RequestID=7d1bb0da-cfcf-4365-ad8d-35d0f43e627f;|"DPL8007:

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> Invalid Deployment Descriptors element jndi-name value

>

> >

>

> > >>>>>>

>

> >

>

> > >>>> jms/QCFactory"|#]

>

> >

>

> > >>>>

>

> >

>

> > >>

>

> >

> [#|2009-11-10T20:13:30.666+0530|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=60;_ThreadName=Thread-5373;_RequestID=7d1bb0da-cfcf-4365-ad8d-35d0f43e627f;|Exception

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> occured in J2EEC Phasejava.lang.NullPointerException

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> com.sun.enterprise.deployment.backend.IASDeploymentException:

> Error

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> loading deployment descriptors for module [WUMT] -- null

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> at

>

> >

>

> > >>>>>>

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:390)

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> at

>

> >

>

> > >>>>>>

>

> >

>

> > >>

>

> >

> com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358)

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> Thanks and Regards

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> Deepu Janardhananachary

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> -----Original Message-----

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> From: Ramesh.Parthasarathy_at_Sun.COM

>

> >

>

> > >>>>>>

>

> >

>

> > >>>> [mailto:Ramesh.Parthasarathy_at_Sun.COM]

>

> >

>

> > >>>>

>

> >

>

> > >>>>>> Sent: Tuesday, November 10, 2009 9:34 AM

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> To: Seema Richard

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> Cc: users_at_genericjmsra.dev.java.net; Deepu Syamaladevi

>

> >

>

> > >>>>>>

>

> >

>

> > >>>> Janardhananachary

>

> >

>

> > >>>>

>

> >

>

> > >>>>>> Subject: Re: Issue in glassfish configuration with Tibco EMS

>

> >

>

> > >>>>>>

>

> >

>

> > >> and MDB

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> Hi Seema,

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> The ra.xml cannot be edited through admin GUI, and it is not

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> supposed to be. The ra.xml is a bundled configuration of the

>

> >

>

> > >>>>>>

>

> >

>

> > >> resource

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> adapter. The values configured through ra-config (that is

>

> >

>

> > >>>>>>

>

> >

>

> > >>> persisted in

>

> >

>

> > >>>

>

> >

>

> > >>>>>> domain.xml and *not* ra.xml) will override the the ra.xml

>

> >

>

> > >>>>>>

>

> >

>

> > >> values. And

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> finally an MCF configuration (or activation spec) will override

>

> >

>

> > >>>>>>

>

> >

>

> > >>>> what is

>

> >

>

> > >>>>

>

> >

>

> > >>>>>> configured in the ra-config.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> 1. The ra.xml file in the deployed file didn't have the values

>

> >

>

> > >>>>>>>

>

> >

>

> > >> that

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> were entered.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> What is the requirement for this ? If you are expecting the

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> configuration in ra-config to be persisted in ra.xml, then the

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> understanding is not correct.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> 2. The error message in the logs were " Caused by:

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> java.lang.Exception: ResourceAdapterConfig already exists:

>

> >

>

> > >>>>>>

>

> >

>

> > >> cannot add

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> duplicate"

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> There is already an ra-config with the same name, and that is

>

> >

>

> > >>>>>>

>

> >

>

> > >> why you

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> get this error.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> If there is any step in the integration guide that requires

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> clarification, please point out.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> Thanks

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> -Ramesh

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>> Seema Richard wrote:

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> Ramesh,

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> The following steps were performed according to the tutorial

> link

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> that you sent.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> - The asadmin create-resource-adapter-config command

>

> >

>

> > >>>>>>>

>

> >

>

> > >> displayed a

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> success message after execution.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> - The genericra.rar available in

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> glassfish-v2ur2\lib\addons\resourceadapters\genericjmsra was

>

> >

>

> > >>>>>>

>

> >

>

> > >> deployed

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> Results were as follows.

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> 1. The ra.xml file in the deployed file didn't have the values

>

> >

>

> > >>>>>>>

>

> >

>

> > >> that

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> were entered.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> 2. The error message in the logs were " Caused by:

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> java.lang.Exception: ResourceAdapterConfig already exists:

>

> >

>

> > >>>>>>

>

> >

>

> > >> cannot add

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>> duplicate"

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> Please advise if we are missing something.

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> Thanks,

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> Seema

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> -----Original Message-----

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> From: Ramesh.Parthasarathy_at_Sun.COM

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> [mailto:Ramesh.Parthasarathy_at_Sun.COM]

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> Sent: Monday, November 09, 2009 9:50 PM

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> To: users_at_genericjmsra.dev.java.net

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> Cc: Seema Richard

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> Subject: Re: Issue in glassfish configuration with Tibco EMS

>

> >

>

> > >>>>>>>

>

> >

>

> > >> and MDB

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> Hi

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> Its not clear as to what you are trying to do

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> If you are looking for integration steps, please follow this

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>

>

> >

> https://genericjmsra.dev.java.net/docs/tibco-genericjmsra-integration-sample-doc/Integrating_Sun_Java_System_Application_Server_with_Tibco_JMS_using_the_Generic_Resource_Adapter_for_JMS.html

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> If you have an error , the server.log file would provide more

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>> information.

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>> Thanks

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> Ramesh

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>> Deepu Syamaladevi Janardhananachary wrote:

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>> Hi,

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> I would like to know how to get messages from a Tibco Queue to

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>> an MDB

>

> >

>

> > >>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> deployed in glassfish.

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> I am using glassfish server(Sun Java System Application Server

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>> 9.1_02

>

> >

>

> > >>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> (build b04-fcs)), EJB 3 and Tibco EMS version 5.0.0

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> I created the resource adapter genericra using the command

> prompt

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> C:\Program Files\glassfish-v2ur2\bin>asadmin

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> create-resource-adapter-config --user admin --property

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>

>

> >

> SupportsXA=false:ProviderIntegrationMode=jndi:UserName=xxx:Password=xxx:JndiProperties=java.naming.factory.url.pkgs\\=com.tibco.tibjms

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>

>

> >

> .naming,java.naming.factory.initial\\=com.tibco.tibjms.naming.TibjmsInitialContextFactory,java.naming.provider.url\\=xxx\://xxx.xxx.com\\:1234:LogLevel=

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>>> finest genericra

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> After this though it is showing executed successfully, I

> couldn't

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>> find

>

> >

>

> > >>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> the location of created file.

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> From the admin console ApplicationsàConnector Modules, I

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>> deployed the

>

> >

>

> > >>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> genericra.rar available in

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> glassfish-v2ur2\lib\addons\resourceadapters\genericjmsra.

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> Then two columns of Name and Value came. The ra.xml in the

>

> >

>

> > >>>>>>>>

>

> >

>

> > >> deployed

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> file didn't have any of the value that I entered. Its version

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>> is 1.7

>

> >

>

> > >>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> What do I need to do to change the values in resource adapter?

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> So I changed my approach

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> I created a connector project in eclipse(Ganymede) and

>

> >

>

> > >>>>>>>>

>

> >

>

> > >> entered the

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> values in the ra.xml within the tag resourceadapter. But when I

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>> deploy

>

> >

>

> > >>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> it in the connector Modules, it is saying as error resource

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>> adapter.

>

> >

>

> > >>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> Regards,

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>> Deepu Janardhananachary

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >>>>>>

>

> >

>

> > >> ---------------------------------------------------------------------

>

> >

>

> > >>

>

> >

>

> > >>

>

> >

>

> > >>>>> 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

>

> >

>

> > >>>>

>

> >

>

> > >>>

> ---------------------------------------------------------------------

>

> >

>

> > >>>

>

> >

>

> > >>> 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

>

 

 

---------------------------------------------------------------------

To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net

For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net