Nabble - Generic Resource Adapter for JMS

Re: Type 2 driver while connecting Generic JMS RA 2.0 with Oracle AQ

2008-10-02T22:41:37Z

Hi Sri,
What is the error/exception you are seeing ?

Thanks
-Ramesh

Sri Sri wrote:

> Hi Ramesh,
>
> We are facing a problem using Generic JMS RA 2.0 with Type 2 driver..
>
> SJAS Oracle AQ integration issue
>
>
>
> I am unable to setup type 2 driver setting for Oracle AQ. With type 4
> driver everything is working fine.
>
>
>
> Following is my environment configuration.
>
> Application Server - SJAS 8.1_02
>
> GenericJMSRA - 2.0
>
> Oracle ( client & server) - 10g
>
>
>
> Is it possible to configure type 2 driver?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Users of Generic Resource Adapter for JMS

Type 2 driver while connecting Generic JMS RA 2.0 with Oracle AQ

2008-10-02T20:36:43Z

Hi Ramesh,

We are facing a problem using Generic JMS RA 2.0 with Type 2 driver..

SJAS Oracle AQ integration issue

I am unable to setup type 2 driver setting for Oracle AQ. With type 4
driver everything is working fine.

Following is my environment configuration.

Application Server - SJAS 8.1_02

GenericJMSRA - 2.0

Oracle ( client & server) - 10g

Is it possible to configure type 2 driver?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Users of Generic Resource Adapter for JMS

Type 2 driver while connecting Generic JMS RA 2.0 with Oracle AQ

2008-10-02T20:36:43Z

Hi Ramesh,

We are facing a problem using Generic JMS RA 2.0 with Type 2 driver..

SJAS Oracle AQ integration issue

I am unable to setup type 2 driver setting for Oracle AQ. With type 4
driver everything is working fine.

Following is my environment configuration.

Application Server - SJAS 8.1_02

GenericJMSRA - 2.0

Oracle ( client & server) - 10g

Is it possible to configure type 2 driver?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Development of Generic Resource Adapter for JMS

Re: GenericJMSRA and MQS: JNDI-Lookup in FSContext fails

2008-09-30T07:20:54Z

Hi Chris,
I just responded to your query in the GlassFish forum.

Thanks
-Ramesh
huberc@... wrote:

> Hello everyone,
>
> I have some trouble configuren MQS as JMS Provider in my GlassFish
> using the genericJMSra and was hoping that someone on this list might
> be able to give me a hint what I have done wrong.
>
> I am trying to include all desired information so my apologies for the
> lengthy post (i also posted it in the GlassFish forum, the log
> messages might be more readable over there
> http://forums.java.net/jive/thread.jspa?threadID=47592):
>
> I followed the tutorial at
> https://genericjmsra.dev.java.net/docs/websphere-mq-integration-guide/webspheremq_integration_guide.html
> and got beyond the first problems.
>
> But now I am kinda stuck because when I try to deploy my MDB it can't
> lookup the ConnectionFactory that I specified in the sun-ejb-jar.xml
> under activation-config. Here is the relevant snippet:
>
> <mdb-resource-adapter>
> 
> <resource-adapter-mid>genericra</resource-adapter-mid>
> <activation-config>
> <activation-config-property>
> <activation-config-property-name>DestinationType</activation-config-property-name>
>
> <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
>
> </activation-config-property>
> <!activation-config-property>
> <activation-config-property-name>ConnectionFactoryJndiName</activation-config-property-name>
>
> <activation-config-property-value>BEA10TEST.JNDI.QCF</activation-config-property-value>
>
> </activation-config-property>
> <activation-config-property>
> <activation-config-property-name>DestinationJndiName</activation-config-property-name>
>
> <activation-config-property-value>BEA10TEST.JNDI.QUEUE</activation-config-property-value>
>
> </activation-config-property>
>
> Now the lookup for BEA10TEST.JNDI.QCF fails (it says bea here because
> I am reusing a binding that has been initially created for a bea test
> scenario but the output of the JMSAdmin tool is not dependent on the
> appserver). I set the initial context factory to
> com.sun.jndi.fscontext.RefFSContextFactory and referenced the
> directory containing the .bindings file as provider url. But still the
> lookup fails. There are some log messages that look a bit suspicious
> to me:
>
> [#|2008-09-24T14:37:26.817+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
> Properties;MethodName=setResourceAdapter;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|setResourceAdapter
> com.sun.genericra.GenericJMSRA@403e9a1b{ConnectionFactory ClassName =
> null},{QueueConnectionFactoryClassName =
> null},{TopicConnectionFactoryClassName =
> null},{XAConnectionFactoryClassName =
> null},{XAQueueConnectionFactoryCla ssName =
> null},{XATopicConnectionFactoryClassName = null},{QueueClassName =
> null},{TopicClassName = null},{UnifiedDestinationClassName =
> null},{ConnectionFactoryPrope rties = null},{JndiProperties =
> java.naming.factory.url.pkgs=com.ibm.mq.jms.naming,java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.
> provider=file://www/sungf/mqm},{ProviderIntegrationMode =
> jndi},{CommonSetterMethodName = null},{SupportsXA =
> true},{UseFirstXAForRedelivery = false},|#]
>
> [#|2008-09-24T14:37:26.862+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
>
> Properties;MethodName=getProviderIntegrationMode;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|ProviderIntegrationMode
> null|#]
>
> [#|2008-09-24T14:37:26.865+0200|FINE|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.inbound.Activa
>
> tionSpec;MethodName=validate;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|com.sun.genericra.inbound.ActivationSpec@7ca58b69{ConnectionFactoryClassName
> = null},{Qu
> eueConnectionFactoryClassName = null},{TopicConnectionFactoryClassName
> = null},{XAConnectionFactoryClassName =
> null},{XAQueueConnectionFactoryClassName = null},{XATop
> icConnectionFactoryClassName = null},{QueueClassName =
> null},{TopicClassName = null},{UnifiedDestinationClassName =
> null},{ConnectionFactoryProperties = null},{JndiPr
> operties =
> java.naming.factory.url.pkgs=com.ibm.mq.jms.naming,java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider=file://www/s
>
> ungf/mqm},{ProviderIntegrationMode = jndi},{CommonSetterMethodName =
> null},{SupportsXA = true},{UseFirstXAForRedelivery =
> false},{RedeliveryInterval = 1},{RedeliveryA
> ttempts = 0},{ClientID = null},{MessageSelector =
> null},{SubscriptionDurability =
> Non-Durable},{ConnectionFactoryJNDIName =
> BEA10TEST.JNDI.QCF},{SubscriptionName = nu
> ll},{DestinationJNDIName = BEA10TEST.JNDI.QUEUE},{DestinationType =
> javax.jms.Queue},{DeadMessageDestinationType =
> javax.jms.Destination},{MaxPoolSize = 32},{Destinat
> ionProperties = null},{DeadMessageDestinationJndiName =
> null},{DeadMessageConnectionFactoryJndiName =
> null},{DeadMessageConnectionFactoryProperties = null},{DeadMessa
> geDestinationClassName = null},{DeadMessageDestinationProperties =
> null},{SendBadMessagesToDMD = false},{EndpointReleaseTimeOut =
> 180},{InstanceCount = 1},{LoadBalanc
> ingRequired = true},{Instance ID =
> 0},{CustomLoadBalancingMessageSelector = },{ShareClientID = false}|#]
>
> [#|2008-09-24T14:37:26.867+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
>
> Properties;MethodName=getProviderIntegrationMode;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|ProviderIntegrationMode
> jndi|#]
>
> [#|2008-09-24T14:37:26.868+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
>
> ;MethodName=getInstance;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|GenericJMSRA
> - getInstance() orig
> com.sun.genericra.GenericJMSRA@403e9a1b{ConnectionFactoryCl
> assName = null},{QueueConnectionFactoryClassName =
> null},{TopicConnectionFactoryClassName =
> null},{XAConnectionFactoryClassName =
> null},{XAQueueConnectionFactoryClass
> Name = null},{XATopicConnectionFactoryClassName =
> null},{QueueClassName = null},{TopicClassName =
> null},{UnifiedDestinationClassName = null},{ConnectionFactoryPropert
> ies = null},{JndiProperties =
> java.naming.factory.url.pkgs=com.ibm.mq.jms.naming,java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.pr
>
> ovider=file://www/sungf/mqm},{ProviderIntegrationMode =
> jndi},{CommonSetterMethodName = null},{SupportsXA =
> true},{UseFirstXAForRedelivery = false},|#]
>
> [#|2008-09-24T14:37:26.870+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
>
> Properties;MethodName=getProviderIntegrationMode;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|ProviderIntegrationMode
> null|#]
>
> As you see the ProviderIntegrationMode property is sometimes printed
> as jndi and sometimes as null even though it is defined as jndi in the
> domain.xml which is logged correctly too. But everytime before the
> failing lookup takes place the last log states that it is null. So I
> assume this is why the lookup fails, but I cannot figure out what I am
> doing wrong here.
>
> Just in case it matters, the domain is set up as a cluster but I am
> only using one instance and the corresponding DAS on the same machine,
> the other instance is shut down.
>
> Does anyone have a clue what's wrong here?
>
> Thanks,
> Chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Users of Generic Resource Adapter for JMS

GenericJMSRA and MQS: JNDI-Lookup in FSContext fails

2008-09-30T07:00:01Z

Hello everyone,

I have some trouble configuren MQS as JMS Provider in my GlassFish using
the genericJMSra and was hoping that someone on this list might be able to
give me a hint what I have done wrong.

I am trying to include all desired information so my apologies for the
lengthy post (i also posted it in the GlassFish forum, the log messages
might be more readable over there
http://forums.java.net/jive/thread.jspa?threadID=47592):

I followed the tutorial at https://genericjmsra.dev.java.net/docs/websphere-mq-integration-guide/webspheremq_integration_guide.html
and got beyond the first problems.

But now I am kinda stuck because when I try to deploy my MDB it can't
lookup the ConnectionFactory that I specified in the sun-ejb-jar.xml under
activation-config. Here is the relevant snippet:

<mdb-resource-adapter>

<resource-adapter-mid>genericra</resource-adapter-mid>
<activation-config>
<activation-config-property>
<activation-config-property-name>DestinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
<!activation-config-property>
<activation-config-property-name>ConnectionFactoryJndiName</activation-config-property-name>
<activation-config-property-value>BEA10TEST.JNDI.QCF</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>DestinationJndiName</activation-config-property-name>
<activation-config-property-value>BEA10TEST.JNDI.QUEUE</activation-config-property-value>
</activation-config-property>

Now the lookup for BEA10TEST.JNDI.QCF fails (it says bea here because I am
reusing a binding that has been initially created for a bea test scenario
but the output of the JMSAdmin tool is not dependent on the appserver). I
set the initial context factory to
com.sun.jndi.fscontext.RefFSContextFactory and referenced the directory
containing the .bindings file as provider url. But still the lookup fails.
There are some log messages that look a bit suspicious to me:

[#|2008-09-24T14:37:26.817+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
Properties;MethodName=setResourceAdapter;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|setResourceAdapter
com.sun.genericra.GenericJMSRA@403e9a1b{ConnectionFactory ClassName =
null},{QueueConnectionFactoryClassName =
null},{TopicConnectionFactoryClassName =
null},{XAConnectionFactoryClassName = null},{XAQueueConnectionFactoryCla
ssName = null},{XATopicConnectionFactoryClassName = null},{QueueClassName
= null},{TopicClassName = null},{UnifiedDestinationClassName =
null},{ConnectionFactoryPrope rties = null},{JndiProperties =
java.naming.factory.url.pkgs=com.ibm.mq.jms.naming,java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.
provider=file://www/sungf/mqm},{ProviderIntegrationMode =
jndi},{CommonSetterMethodName = null},{SupportsXA =
true},{UseFirstXAForRedelivery = false},|#]

[#|2008-09-24T14:37:26.862+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
Properties;MethodName=getProviderIntegrationMode;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|ProviderIntegrationMode
null|#]

[#|2008-09-24T14:37:26.865+0200|FINE|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.inbound.Activa
tionSpec;MethodName=validate;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|com.sun.genericra.inbound.ActivationSpec@7ca58b69{ConnectionFactoryClassName
= null},{Qu
eueConnectionFactoryClassName = null},{TopicConnectionFactoryClassName =
null},{XAConnectionFactoryClassName =
null},{XAQueueConnectionFactoryClassName = null},{XATop
icConnectionFactoryClassName = null},{QueueClassName =
null},{TopicClassName = null},{UnifiedDestinationClassName =
null},{ConnectionFactoryProperties = null},{JndiPr
operties =
java.naming.factory.url.pkgs=com.ibm.mq.jms.naming,java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider=file://www/s
ungf/mqm},{ProviderIntegrationMode = jndi},{CommonSetterMethodName =
null},{SupportsXA = true},{UseFirstXAForRedelivery =
false},{RedeliveryInterval = 1},{RedeliveryA
ttempts = 0},{ClientID = null},{MessageSelector =
null},{SubscriptionDurability = Non-Durable},{ConnectionFactoryJNDIName =
BEA10TEST.JNDI.QCF},{SubscriptionName = nu
ll},{DestinationJNDIName = BEA10TEST.JNDI.QUEUE},{DestinationType =
javax.jms.Queue},{DeadMessageDestinationType =
javax.jms.Destination},{MaxPoolSize = 32},{Destinat
ionProperties = null},{DeadMessageDestinationJndiName =
null},{DeadMessageConnectionFactoryJndiName =
null},{DeadMessageConnectionFactoryProperties = null},{DeadMessa
geDestinationClassName = null},{DeadMessageDestinationProperties =
null},{SendBadMessagesToDMD = false},{EndpointReleaseTimeOut =
180},{InstanceCount = 1},{LoadBalanc
ingRequired = true},{Instance ID = 0},{CustomLoadBalancingMessageSelector
= },{ShareClientID = false}|#]

[#|2008-09-24T14:37:26.867+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
Properties;MethodName=getProviderIntegrationMode;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|ProviderIntegrationMode
jndi|#]

[#|2008-09-24T14:37:26.868+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
;MethodName=getInstance;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|GenericJMSRA
- getInstance() orig
com.sun.genericra.GenericJMSRA@403e9a1b{ConnectionFactoryCl
assName = null},{QueueConnectionFactoryClassName =
null},{TopicConnectionFactoryClassName =
null},{XAConnectionFactoryClassName = null},{XAQueueConnectionFactoryClass
Name = null},{XATopicConnectionFactoryClassName = null},{QueueClassName =
null},{TopicClassName = null},{UnifiedDestinationClassName =
null},{ConnectionFactoryPropert
ies = null},{JndiProperties =
java.naming.factory.url.pkgs=com.ibm.mq.jms.naming,java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.pr
ovider=file://www/sungf/mqm},{ProviderIntegrationMode =
jndi},{CommonSetterMethodName = null},{SupportsXA =
true},{UseFirstXAForRedelivery = false},|#]

[#|2008-09-24T14:37:26.870+0200|FINEST|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=22;_ThreadName=httpWorkerThread-1648-0;ClassName=com.sun.genericra.GenericJMSRA
Properties;MethodName=getProviderIntegrationMode;_RequestID=7b48e375-620b-4c9c-b8de-c77f60ee74af;|ProviderIntegrationMode
null|#]

As you see the ProviderIntegrationMode property is sometimes printed as
jndi and sometimes as null even though it is defined as jndi in the
domain.xml which is logged correctly too. But everytime before the failing
lookup takes place the last log states that it is null. So I assume this
is why the lookup fails, but I cannot figure out what I am doing wrong
here.

Just in case it matters, the domain is set up as a cluster but I am only
using one instance and the corresponding DAS on the same machine, the
other instance is shut down.

Does anyone have a clue what's wrong here?

Thanks,
Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Users of Generic Resource Adapter for JMS

Training & jobs

2008-09-29T23:41:20Z

“Join us to make future”
FOR OPT/F-1 STUDENTS
FREE TRAINING
FOOD ACCOMODATION
H1B PROCESSING FOR L1/ L2/ H1/ H4/ EAD/ GC
EXCELLENT OPPRTUNITIES
TRAINING
PLACEMENT
Highly Competitive offers for New H1b Transfers
About Us:
V2 technology inc is serving NJ since 2005, for us our employees are of utmost importance. Our highly skilled and dedicated instructors train you explicitly in market-related technologies for today and tomorrow. We will work with you in developing marketing strategies and finding the assignments of your choice.
We not only help you get a job but we build your long lasting careers!!!
What are we Looking for:
Excellent communication skills.
Valid F1/ OPT/ CPT/ H1/ H4/ L1 or valid work status (EAD, GC).
Bachelors’ degree in CS/ IT or previous IT experience.
Preferably (not mandatory) Master's Degree in Computers/ Electronics or previous IT experience.
Willing to relocate anywhere in USA.
What’s The Deal:
H1-B sponsorship to F1/ OPT/ H4/ L1/ L2/ E3/ EAD
Transfer of H1 & L1 visas.
Green Card sponsorship through PERM
Job focused professional training in
Java/ J2EE
.NET
Documentum
Share point
Oracle
Data Modeling
Relocation assistance- airfare, hotel accommodation, car rental etc
Guarantee lowest bench period.
Employee referral program.
Effective Resume writing help, Marketing and Placement.
Technical mock interviews. Preparation of In Person Interviews
100% Guaranteed placement
Get in Touch:
Contact immediately to know more about the opportunities with us at:609-843-0312
or
write mail at jobs@v2techinc.com
Contact person : John

From forum: Users of Generic Resource Adapter for JMS

THIS IS OKAY.

2008-09-24T05:53:45Z

THIS IS OKAY.
I am Mrs. Tatiana Georgieva. I am 52 years old from Bulgaria,based in Japan; I am deaf and suffering from a long time cancer of the Lungs which also affected my brain. From all indication, my condition is really deteriorating and it is quite obvious that, according to my doctors they have advised me that I will live for the next few months, this is because the cancer has eating up my lungs.
Below is the contact info of my attorney whom you will contact with your detailed information and will brief you more on this transaction.

ATTORNEY INFO:-
Name:Mr.Lius Coker
Email:luislobic08@...
Email;luislobic@...

Yours truly,
Mrs. Tatiana Georgieva

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Users of Generic Resource Adapter for JMS

Re: [Fwd: Re: XAException while connecting Generic JMS RA 2.0 with Oracle AQ]

2008-08-20T22:51:06Z

Hi Ramesh,

Thanks a lot for all your help. As advised by you, I have raised Issue 33 in java.net

https://genericjmsra.dev.java.net/issues/show_bug.cgi?id=33

Thanks again.

Cheers

Sri

On 8/20/08, Ramesh Parthasarathy <Ramesh.Parthasarathy@...> wrote:

Hi Sri,
Thanks for confirming that recovery is working

Are these exceptions causing any issues, it does not appear to be.

Could be because of the way we clean up when the pool is destroyed, please create an issue, we will investigate this

Thanks
-Ramesh

On 08/20/08 11:11, Sri Sri wrote:

Hi Ramesh,
There are no exceptions on transaction recovery now.. It is working . Thanks to you.
One last issue for today :-).. While the server shuts down I get host of exceptions while committing transactiosn
[#|2008-08-20T16:31:01.972+0530|FINE|sun-appserver-ee8.1_02|com.sun.genericjmsra|_ThreadID=47;|could not use local transactio
n rollback in a global transaction
oracle.jms.AQjmsException: could not use local transaction rollback in a global transaction
at oracle.jms.AQjmsSession.preClose(AQjmsSession.java:971)
at oracle.jms.AQjmsObject.close(AQjmsObject.java:409)
at oracle.jms.AQjmsSession.close(AQjmsSession.java:1011)
at com.sun.genericra.inbound.sync.SyncJmsResource.destroy(SyncJmsResource.java:112)
at com.sun.genericra.inbound.sync.SyncJmsResourcePool.releaseAllResources(SyncJmsResourcePool.java:183)
at com.sun.genericra.inbound.sync.SyncJmsResourcePool.stop(SyncJmsResourcePool.java:198)
at com.sun.genericra.inbound.sync.SyncJmsResourcePool.destroy(SyncJmsResourcePool.java:206)
at com.sun.genericra.inbound.sync.SyncConsumer.stop(
I have attached the server logs... Can you suggest anything ..
Thanks a lot .. Cheers Sri
On 8/20/08, *Sri Sri* <mesri09@... <mailto:mesri09@...>> wrote:

Hi Ramesh,
Thanks a lot.. Let me try the below and will let you know. The
previous issue did get sorted out with the RMPolicy.:-)
Cheers
Srikala

On 8/20/08, *Ramesh Parthasarathy* <Ramesh.Parthasarathy@...
<mailto:Ramesh.Parthasarathy@...>> wrote:

Hi Sri,
You mean, it works after setting the RMPolicy, correct !

For the resource recovery to work, i guess you might have to do
the following, please try this and let me know

You might need special permissions set on the transaction tables.
I have not tried this myself, and not an Oracle expert either,
you might want to check this with a DBA.

As user SYS, run the following commands on your Oracle server:

grant select on pending_trans$ to public;
grant select on dba_2pc_pending to public;
grant select on dba_pending_transactions to public;
grant execute on dbms_system to <user>;

User would be the user id that is used in the connection pool
for connecting to AQ.

On the other hand if you do not want automatic transaction
recovery in the application , you could simply turn it off in
the transaction service.

BTW: If your transactions go through without any issues, there
should not be any PENDING XA resources left to recover, i see 2
XAs in your case for recovery

Thanks
-Ramesh

On 08/20/08 07:36, Sri Sri wrote:

Hi Ramesh,
Also attached is the domain.xml
Cheers and Thanks
Sri

On 8/20/08, *Sri Sri* <mesri09@...
<mailto:mesri09@...> <mailto:mesri09@...

<mailto:mesri09@...>>> wrote:

Hi,
Thanks a lot. The flow seems to work. It is
publishing to the
DeadLetter Queue. I am facing one more issue while
recovering XA
transactions on server startup. I have attached the
server.log and
the MDB code which I am working on.
Recover exception
[#|2008-08-20T12:33:21.715+0530|WARNING|sun-appserver-ee8.1_02|javax.enterprise.system.core.transaction|_ThreadID=11;|JTS5028
: XAException occured during recovery of XAResource objects.
javax.transaction.xa.XAException
at
oracle.jdbc.xa.OracleXAResource.recover(OracleXAResource.java:613)
at
oracle.jms.AQjmsXAResource.recover(AQjmsXAResource.java:318)
at
com.sun.genericra.outbound.XAResourceProxy.recover(XAResourceProxy.java:188)
at
com.sun.jts.CosTransactions.RecoveryManager.proceedWithXARecovery(RecoveryManager.java:880)
at
com.sun.jts.CosTransactions.RecoveryManager.recover(RecoveryManager.java:431)
at
com.sun.jts.CosTransactions.ResyncThread.run(RecoveryManager.java:1556)
Any more info please let me know
Thanks again

On 8/19/08, *Ramesh Parthasarathy*
<Ramesh.Parthasarathy@...
<mailto:Ramesh.Parthasarathy@...>
<mailto:Ramesh.Parthasarathy@...
<mailto:Ramesh.Parthasarathy@...>>> wrote:

-------- Original Message --------
Subject: Re: XAException while connecting Generic JMS
RA 2.0
with Oracle AQ
Date: Tue, 19 Aug 2008 12:19:38 +0000
From: Ramesh Parthasarathy <Ramesh.Parthasarathy@...>
Reply-To: users@...
<mailto:users@...>
<mailto:users@...
<mailto:users@...>>
To: dev@...
<mailto:dev@...>
<mailto:dev@...
<mailto:dev@...>>
CC: users@...
<mailto:users@...>
<mailto:users@...

<mailto:users@...>>
References:
<6e63bb0c0808182341u7081d265r2161cda55773c326@...
<mailto:6e63bb0c0808182341u7081d265r2161cda55773c326@...>
<mailto:6e63bb0c0808182341u7081d265r2161cda55773c326@...
<mailto:6e63bb0c0808182341u7081d265r2161cda55773c326@...>>>

Hi,
Would it be possible to share your code and the
domain.xml.
Have you configured the rm policy when you created
the ra config ?
"RMPolicy=OnePerPhysicalConnection"

Thanks
-Ramesh

On 08/19/08 06:41, Sri Sri wrote:

Hi,

Following is my scenario:-

I have configured Generic JMS RA 2.0 with Oracle
AQ (on 10G
Database) as the JMS provider. I have a container
managed
MDB with "Required" transaction consuming from queue
OutboundQueue and from within the MDB looks up Queue
DeadLetterQueue and publishes to DeadLetterQueue.
When it is
publishing to Queue DeadLetterQueue, I am getting the
following exception and the message is getting
rolled back
to Queue OutboundQueue. There are 2 Connector
pools for both
the queues (I have tried using a single pool also
as both
the queues are on the same schema in the database)

[#|2008-08-19T11:27:21.632+0530|WARNING|sun-appserver-ee8.1_02|javax.enterprise.system.core.transaction|_ThreadID=14;|JTS5041
: The resource manager is doing work outside a global
transaction
oracle.jdbc.xa.OracleXAException
at
oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1223)
at
oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:318)
at
oracle.jms.AQjmsXAResource.start(AQjmsXAResource.java:440)
at
com.sun.genericra.outbound.XAResourceProxy.start(XAResourceProxy.java:244)
at
com.sun.enterprise.resource.XAResourceWrapper.start(XAResourceWrapper.java:98)
at
com.sun.jts.jta.TransactionState.startAssociation(TransactionState.java:265)
at
com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:181)
at
com.sun.enterprise.distributedtx.J2EETransaction.enlistResource(J2EETransaction.java:397)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.enlistResource(J2EETransactionManagerImpl.java:317)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.enlistResource(J2EETransactionManagerOpt.java:114)
at
com.sun.enterprise.resource.ResourceManagerImpl.registerResource(ResourceManagerImpl.java:117)

I have attached the server.log, the screenshots of
configuration on SUN Application server 8.1_02.
Has anyone
faced a similar problem, please help me solve the
above issue.

Any more information required, please let me know.

Cheers

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

---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
<mailto:dev-unsubscribe@...>
<mailto:dev-unsubscribe@...
<mailto:dev-unsubscribe@...>>
For additional commands, e-mail:
dev-help@...
<mailto:dev-help@...>
<mailto:dev-help@...
<mailto:dev-help@...>>

---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
<mailto:users-unsubscribe@...>
<mailto:users-unsubscribe@...
<mailto:users-unsubscribe@...>>
For additional commands, e-mail:
users-help@...
<mailto:users-help@...>
<mailto:users-help@...
<mailto:users-help@...>>

From forum: Users of Generic Resource Adapter for JMS

Re: [Fwd: Re: XAException while connecting Generic JMS RA 2.0 with Oracle AQ]

2008-08-20T22:51:06Z

Hi Ramesh,

Thanks a lot for all your help. As advised by you, I have raised Issue 33 in java.net

https://genericjmsra.dev.java.net/issues/show_bug.cgi?id=33

Thanks again.

Cheers

Sri

On 8/20/08, Ramesh Parthasarathy <Ramesh.Parthasarathy@...> wrote:

Hi Sri,
Thanks for confirming that recovery is working

Are these exceptions causing any issues, it does not appear to be.

Could be because of the way we clean up when the pool is destroyed, please create an issue, we will investigate this

Thanks
-Ramesh

On 08/20/08 11:11, Sri Sri wrote:

Hi Ramesh,
There are no exceptions on transaction recovery now.. It is working . Thanks to you.
One last issue for today :-).. While the server shuts down I get host of exceptions while committing transactiosn
[#|2008-08-20T16:31:01.972+0530|FINE|sun-appserver-ee8.1_02|com.sun.genericjmsra|_ThreadID=47;|could not use local transactio
n rollback in a global transaction
oracle.jms.AQjmsException: could not use local transaction rollback in a global transaction
at oracle.jms.AQjmsSession.preClose(AQjmsSession.java:971)
at oracle.jms.AQjmsObject.close(AQjmsObject.java:409)
at oracle.jms.AQjmsSession.close(AQjmsSession.java:1011)
at com.sun.genericra.inbound.sync.SyncJmsResource.destroy(SyncJmsResource.java:112)
at com.sun.genericra.inbound.sync.SyncJmsResourcePool.releaseAllResources(SyncJmsResourcePool.java:183)
at com.sun.genericra.inbound.sync.SyncJmsResourcePool.stop(SyncJmsResourcePool.java:198)
at com.sun.genericra.inbound.sync.SyncJmsResourcePool.destroy(SyncJmsResourcePool.java:206)
at com.sun.genericra.inbound.sync.SyncConsumer.stop(
I have attached the server logs... Can you suggest anything ..
Thanks a lot .. Cheers Sri
On 8/20/08, *Sri Sri* <mesri09@... <mailto:mesri09@...>> wrote:

Hi Ramesh,
Thanks a lot.. Let me try the below and will let you know. The
previous issue did get sorted out with the RMPolicy.:-)
Cheers
Srikala

On 8/20/08, *Ramesh Parthasarathy* <Ramesh.Parthasarathy@...
<mailto:Ramesh.Parthasarathy@...>> wrote:

Hi Sri,
You mean, it works after setting the RMPolicy, correct !

For the resource recovery to work, i guess you might have to do
the following, please try this and let me know

You might need special permissions set on the transaction tables.
I have not tried this myself, and not an Oracle expert either,
you might want to check this with a DBA.

As user SYS, run the following commands on your Oracle server:

grant select on pending_trans$ to public;
grant select on dba_2pc_pending to public;
grant select on dba_pending_transactions to public;
grant execute on dbms_system to <user>;

User would be the user id that is used in the connection pool
for connecting to AQ.

On the other hand if you do not want automatic transaction
recovery in the application , you could simply turn it off in
the transaction service.

BTW: If your transactions go through without any issues, there
should not be any PENDING XA resources left to recover, i see 2
XAs in your case for recovery

Thanks
-Ramesh

On 08/20/08 07:36, Sri Sri wrote:

Hi Ramesh,
Also attached is the domain.xml
Cheers and Thanks
Sri

On 8/20/08, *Sri Sri* <mesri09@...
<mailto:mesri09@...> <mailto:mesri09@...

<mailto:mesri09@...>>> wrote:

Hi,
Thanks a lot. The flow seems to work. It is
publishing to the
DeadLetter Queue. I am facing one more issue while
recovering XA
transactions on server startup. I have attached the
server.log and
the MDB code which I am working on.
Recover exception
[#|2008-08-20T12:33:21.715+0530|WARNING|sun-appserver-ee8.1_02|javax.enterprise.system.core.transaction|_ThreadID=11;|JTS5028
: XAException occured during recovery of XAResource objects.
javax.transaction.xa.XAException
at
oracle.jdbc.xa.OracleXAResource.recover(OracleXAResource.java:613)
at
oracle.jms.AQjmsXAResource.recover(AQjmsXAResource.java:318)
at
com.sun.genericra.outbound.XAResourceProxy.recover(XAResourceProxy.java:188)
at
com.sun.jts.CosTransactions.RecoveryManager.proceedWithXARecovery(RecoveryManager.java:880)
at
com.sun.jts.CosTransactions.RecoveryManager.recover(RecoveryManager.java:431)
at
com.sun.jts.CosTransactions.ResyncThread.run(RecoveryManager.java:1556)
Any more info please let me know
Thanks again

On 8/19/08, *Ramesh Parthasarathy*
<Ramesh.Parthasarathy@...
<mailto:Ramesh.Parthasarathy@...>
<mailto:Ramesh.Parthasarathy@...
<mailto:Ramesh.Parthasarathy@...>>> wrote:

-------- Original Message --------
Subject: Re: XAException while connecting Generic JMS
RA 2.0
with Oracle AQ
Date: Tue, 19 Aug 2008 12:19:38 +0000
From: Ramesh Parthasarathy <Ramesh.Parthasarathy@...>
Reply-To: users@...
<mailto:users@...>
<mailto:users@...
<mailto:users@...>>
To: dev@...
<mailto:dev@...>
<mailto:dev@...
<mailto:dev@...>>
CC: users@...
<mailto:users@...>
<mailto:users@...

<mailto:users@...>>
References:
<6e63bb0c0808182341u7081d265r2161cda55773c326@...
<mailto:6e63bb0c0808182341u7081d265r2161cda55773c326@...>
<mailto:6e63bb0c0808182341u7081d265r2161cda55773c326@...
<mailto:6e63bb0c0808182341u7081d265r2161cda55773c326@...>>>

Hi,
Would it be possible to share your code and the
domain.xml.
Have you configured the rm policy when you created
the ra config ?
"RMPolicy=OnePerPhysicalConnection"

Thanks
-Ramesh

On 08/19/08 06:41, Sri Sri wrote:

Hi,

Following is my scenario:-

I have configured Generic JMS RA 2.0 with Oracle
AQ (on 10G
Database) as the JMS provider. I have a container
managed
MDB with "Required" transaction consuming from queue
OutboundQueue and from within the MDB looks up Queue
DeadLetterQueue and publishes to DeadLetterQueue.
When it is
publishing to Queue DeadLetterQueue, I am getting the
following exception and the message is getting
rolled back
to Queue OutboundQueue. There are 2 Connector
pools for both
the queues (I have tried using a single pool also
as both
the queues are on the same schema in the database)

[#|2008-08-19T11:27:21.632+0530|WARNING|sun-appserver-ee8.1_02|javax.enterprise.system.core.transaction|_ThreadID=14;|JTS5041
: The resource manager is doing work outside a global
transaction
oracle.jdbc.xa.OracleXAException
at
oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1223)
at
oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:318)
at
oracle.jms.AQjmsXAResource.start(AQjmsXAResource.java:440)
at
com.sun.genericra.outbound.XAResourceProxy.start(XAResourceProxy.java:244)
at
com.sun.enterprise.resource.XAResourceWrapper.start(XAResourceWrapper.java:98)
at
com.sun.jts.jta.TransactionState.startAssociation(TransactionState.java:265)
at
com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:181)
at
com.sun.enterprise.distributedtx.J2EETransaction.enlistResource(J2EETransaction.java:397)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.enlistResource(J2EETransactionManagerImpl.java:317)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.enlistResource(J2EETransactionManagerOpt.java:114)
at
com.sun.enterprise.resource.ResourceManagerImpl.registerResource(ResourceManagerImpl.java:117)

I have attached the server.log, the screenshots of
configuration on SUN Application server 8.1_02.
Has anyone
faced a similar problem, please help me solve the
above issue.

Any more information required, please let me know.

Cheers

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

---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
<mailto:dev-unsubscribe@...>
<mailto:dev-unsubscribe@...
<mailto:dev-unsubscribe@...>>
For additional commands, e-mail:
dev-help@...
<mailto:dev-help@...>
<mailto:dev-help@...
<mailto:dev-help@...>>

---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
<mailto:users-unsubscribe@...>
<mailto:users-unsubscribe@...
<mailto:users-unsubscribe@...>>
For additional commands, e-mail:
users-help@...
<mailto:users-help@...>
<mailto:users-help@...
<mailto:users-help@...>>

From forum: Development of Generic Resource Adapter for JMS