GlassFish2 JMS (OpenMQ) Transaction Support options in Admin Console

Anyone knows where can I find a more detailed explanation regarding the various JMS Connection Factory Transaction Support configuration options that can be seen in the GlassFish2 Admin Console? Thanks in advance.

Please see GlassFish documentation on connector connection pool
http://docs.sun.com/app/docs/doc/820-7701/create-connector-connection-pool-1?l=en&n=1&a=view
and GlassFish Administration Guide on relationship between JMS connection factory and connector connection pool
http://docs.sun.com/app/docs/doc/821-1751/giotd?l=en&a=view
and JEE Connector specification on Transaction Management Contract. For GlassFish connector question, please post to [email protected]

Similar Messages

XA & JMS javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+' not available

Hi, I'm doing a "proof of concept" on XA transaction spanning two servers.
          In order to get it as simple as possible I have configured two servers and
          deployed the same MDB on both. I'm also only using JMS resources to simplify
          the test.
          The goal is to send a message to two different JMS servers (each deployed in
          a Weblogic server) both coordinated by an XA UserTransaction started in the
          client.
          The deployed MDB of each server just listens to a topic and prints out the
          received TextMessage.
          The configuration is as follows:
          * Server 1
          Domain name: a
          Server name: a00
          config.xml (extract):
          <JMSServer Name="a.a00.JMSServer" PagingStore="a.a00.JMSFileStore"
          Store="a.a00.JMSFileStore" Targets="a00">
          <JMSTopic JNDIName="xajms.test.Topic" Name="XA JMS Proof of Concept"
          StoreEnabled="true"/>
          </JMSServer>
          <JMSFileStore Directory="config/a/a00.jmsfilestore"
          Name="a.a00.JMSFileStore"/>
          <JMSConnectionFactory JNDIName="a.a00.JMSConnectionFactory"
          Name="a.a00.JMS Connection Factory" Targets="a00"
          UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
          * Server 2
          Domain name: b
          Server name: b00
          config.xml (extract):
          <JMSServer Name="b.b00.JMSServer" PagingStore="b.b00.JMSFileStore"
          Store="b.b00.JMSFileStore" Targets="b00">
          <JMSTopic JNDIName="xajms.test.Topic" Name="XA JMS Proof of Concept"
          StoreEnabled="true"/>
          </JMSServer>
          <JMSFileStore Directory="config/b/b00.jmsfilestore"
          Name="b.b00.JMSFileStore"/>
          <JMSConnectionFactory JNDIName="b.b00.JMSConnectionFactory"
          Name="b.b00.JMS Connection Factory" Targets="b00"
          UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
          and here is an extract of client code:
          068 UserTransaction utx;
          069
          070 InitialContext ctx1,ctx2;
          071
          072 System.out.println("Retrieving initial context for server 1");
          073 ctx1 = (InitialContext) getInitialContext(SERVER_1,PORT_1);
          074
          075 System.out.println("Retrieving initial context for server 2");
          076 ctx2 = (InitialContext) getInitialContext(SERVER_2,PORT_2);
          077
          078 utx = (UserTransaction)
          ctx1.lookup("javax.transaction.UserTransaction");
          079 utx.setTransactionTimeout(30);
          080
          081 System.out.println("Begining transaction");
          082 utx.begin();
          083
          084 System.out.println("Sending message to server 1");
          085 ref.send(ctx1, JMS_FACTORY_1, args[0]);
          086
          087 System.out.println("Sending message to server 2");
          088 ref.send(ctx2, JMS_FACTORY_2, args[0]);
          089
          090 System.out.println("Ending transaction...");
          091 if (args[1].equals("commit"))
          092 utx.commit();
          093 else
          094 utx.rollback();
          end the result of executing it from a third machine:
          CASE I:
          Retrieving initial context for server 1
          Retrieving initial context for server 2
          Begining transaction
          Sending message to server 1
          Sending message to server 2
          Ending transaction...
          javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
          not available
          Start server side stack trace:
          javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
          not available
          at
          weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
          at
          weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
          0)
          at
          weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
          sactionImpl.java:1619)
          at
          weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
          nsactionImpl.java:217)
          at
          weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
          Impl.java:189)
          at
          weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
          at
          weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
          at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
          at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
          End server side stack trace
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.transaction.RollbackException: SubCoordinator
          'b00+127.0.0.1:7001+b+' not available
          Start server side stack trace:
          javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
          not available
          at
          weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
          at
          weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
          0)
          at
          weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
          sactionImpl.java:1619)
          at
          weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
          nsactionImpl.java:217)
          at
          weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
          Impl.java:189)
          at
          weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
          at
          weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
          at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
          at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
          --------------- nested within: ------------------
          weblogic.transaction.RollbackException: SubCoordinator
          'b00+127.0.0.1:7001+b+' not available - with nested exception:
          [javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
          not available]
          at
          weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
          tionImpl.java:1524)
          at
          weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
          nsactionImpl.java:265)
          at
          weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
          Impl.java:189)
          at
          weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
          at
          weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
          at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
          at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
          End server side stack trace
          - with nested exception:
          [javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
          not available
          Start server side stack trace:
          javax.transaction.SystemException: SubCoordinator 'b00+127.0.0.1:7001+b+'
          not available
                  at
          weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:965
                  at
          weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:20
          0)
                  at
          weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
          sactionImpl.java:1619)
                  at
          weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
          nsactionImpl.java:217)
                  at
          weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
          Impl.java:189)
                  at
          weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
                  at
          weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
                  at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
                  at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
                  at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
          End server side stack trace
          at
          weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
          java:85)
          at
          weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy3.commit(Unknown Source)
          at
          weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:29
          4)
          at
          weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
          erImpl.java:247)
          at
          weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
          erImpl.java:240)
          at xajms.client.Send2BothTopics.main(Send2BothTopics.java:110)
          real 1m6.530s
          user 0m1.380s
          sys 0m0.050s
          If I swap message sending order the output changes to:
          CASE II:
          Retrieving initial context for server 1
          Retrieving initial context for server 2
          Begining transaction
          Sending message to server 2
          Sending message to server 1
          Ending transaction...
          weblogic.transaction.internal.TimedOutException: Timed out
          tx=0:8c9a9deee02fe21e after 30 seconds
          Start server side stack trace:
          weblogic.transaction.internal.TimedOutException: Timed out
          tx=0:8c9a9deee02fe21e after 30 seconds
          at
          weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
          Impl.java:1228)
          at
          weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
          ansactions(ServerTransactionManagerImpl.java:488)
          at
          weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
          erImpl.java:1629)
          at
          weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
          sactionManagerImpl.java:451)
          at
          weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
          rImpl.java:1595)
          at java.lang.Thread.run(Thread.java:479)
          End server side stack trace
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.transaction.RollbackException: Timed out tx=0:8c9a9deee02fe21e
          after 30 seconds
          Start server side stack trace:
          weblogic.transaction.internal.TimedOutException: Timed out
          tx=0:8c9a9deee02fe21e after 30 seconds
          at
          weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
          Impl.java:1228)
          at
          weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
          ansactions(ServerTransactionManagerImpl.java:488)
          at
          weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
          erImpl.java:1629)
          at
          weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
          sactionManagerImpl.java:451)
          at
          weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
          rImpl.java:1595)
          at java.lang.Thread.run(Thread.java:479)
          --------------- nested within: ------------------
          weblogic.transaction.RollbackException: Timed out tx=0:8c9a9deee02fe21e
          after 30 seconds - with nested exception:
          [weblogic.transaction.internal.TimedOutException: Timed out
          tx=0:8c9a9deee02fe21e after 30 seconds]
          at
          weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
          tionImpl.java:1524)
          at
          weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
          nsactionImpl.java:265)
          at
          weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
          Impl.java:189)
          at
          weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
          at
          weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
          at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
          at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
          End server side stack trace
          - with nested exception:
          [weblogic.transaction.internal.TimedOutException: Timed out
          tx=0:8c9a9deee02fe21e after 30 seconds
          Start server side stack trace:
          weblogic.transaction.internal.TimedOutException: Timed out
          tx=0:8c9a9deee02fe21e after 30 seconds
                  at
          weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
          Impl.java:1228)
                  at
          weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
          ansactions(ServerTransactionManagerImpl.java:488)
                  at
          weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
          erImpl.java:1629)
                  at
          weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
          sactionManagerImpl.java:451)
                  at
          weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
          rImpl.java:1595)
                  at java.lang.Thread.run(Thread.java:479)
          End server side stack trace
          at
          weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
          java:85)
          at
          weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy3.commit(Unknown Source)
          at
          weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:29
          4)
          at
          weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
          erImpl.java:247)
          at
          weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
          erImpl.java:240)
          at xajms.client.Send2BothTopics.main(Send2BothTopics.java:110)
          real 1m32.231s
          user 0m1.390s
          sys 0m0.030s
          not to be said that I have "some" questions about it:
          1. Why it doesn't work?
          2. Why order of message sending brings two different results?
          3. In CASE I:
          What is the meaning of the exception "javax.transaction.SystemException:
          SubCoordinator 'b00+127.0.0.1:7001+b+' not available"
          Why is it using the loopback (127.0.0.1) ip? Is that code being runned
          inside the server with the SERVER_2 (192.168.1.3) ip?
          4. In case II:
          How is that the message of the exception is
          "weblogic.transaction.internal.TimedOutException: Timed out
          tx=0:8c9a9deee02fe21e after 30 seconds" when it's clear the program took
          more than one and a half minutes to execute?
          Most of the time is spent after printing the "Ending transaction..." line.
          The first part of the program is executed in a few seconds (about 2 or 3 it
          depends of the time to get initial context against both servers)
          I'm really puzzled with this. I don't know what to think about it. Is this
          so weird nobody have tried something like this?
          I have done some other test for which the results are:
          a) Commenting lines related to UserTransaction (82,91-94)
          It works OK. Both servers receive the message.
          b) Commenting lines 85 or 88 (related to sending messages to each server)
          It works OK. Both servers receive the message. I pressume there is no
          "real" XA transaction as there is only one resource involved on it.
          c) In CASE I launching the client with "rollback" as second parameter I
          neither get any exception nor messages are delivered which would be OK
          d) In CASE II launching the client with "rollback" as second parameter I get
          a "javax.transaction.SystemException: Timeout during rollback processing"
          and messages are not delivered.
          Any idea?. I really need this to work in order to free our server for heavy
          asyncronous loads and deploy new stuff on it.
          PS.
          I attach both servers config.xml files and both MDB and client full code. If
          you are going to test it you must add a new user and group to weblogic
          default file realm:
          New user: subscriber
          New group: xajms
          of course you must add the new user to the new group in order to make it
          work.
          Here are the lines extracted from server's domain "fileRealm.properties"
          file reflecting the new user and group (defined on ejb-jar.xml and
          weblogic-ejb-jar.xml files on the "role" section):
          group.xajms=subscriber
          user.subscriber=0x6b9a704bebc709dd083edd61ed000236eb23987f
          The client receives two parameters. The first one is a string to be sent as
          message body, the second one is either "commit" or "rollback" just to test
          XA transaction doing it's work as expected.
          Thanks in advance.
          Regards.
          Ignacio.
          [xajmspoc.zip]


do you connect to 10g database inside onBusinessEvent using Non-XA/XA connection??. I guess it could be bcoz of Non-XA connection (or) XA Without Global Transaction support, and this connection is listed with the transaction manager and it is trying to commit it after onMessage.
For Global Transactions options, go to your weblogic console and check the following path.
(Datasource -> Advanced Options -> Global Transactions -> Honor Global Transactions should be true)
Let me know if you need any help
Rao Kotha.

Javax.jms.JMSException: Not supported in XA-backed session outside globaltx

I am trying to setup OracleOJMS provider and tries to access queue and post to queue from a normal jsp for testing.
I am getting the following
code:
javax.jms.JMSException: Not supported in XA-backed session outside global transaction
     at oracle.j2ee.ra.jms.generic.RAUtils.make(RAUtils.java:525)
     at oracle.j2ee.ra.jms.generic.RAUtils.toJMSException(RAUtils.java:199)
     at oracle.j2ee.ra.jms.generic.RAUtils.toJMSException(RAUtils.java:210)
     at oracle.j2ee.ra.jms.generic.CommonProducerWrapper.prepareForSend(CommonProducerWrapper.java:350)
     at oracle.j2ee.ra.jms.generic.CommonProducerWrapper.send(CommonProducerWrapper.java:159)
     at ResourceProvider.jspService(_ResourceProvider.java:112)
     at com.orionserver[Oracle Containers for J2EE 10g (10.1.3.1.0) ].http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Steps i have done
ResourceProvider.jsp
code:

<%@ page import="javax.jms.QueueConnectionFactory "%>
<%@ page import="javax.jms.XAQueueConnectionFactory "%>
<%@ page import="javax.jms.QueueConnection "%>
<%@ page import="javax.jms.QueueSession "%>
<%@ page import="javax.jms.Queue "%>
<%@ page import="javax.jms.QueueSender "%>
<%@ page import="javax.jms.Message "%>
<%@ page import="javax.jms.Session "%>
<%@ page import="javax.naming.Context "%>
<%@ page import="javax.naming.InitialContext "%>
<html>
<head>
<title>
Configuration of ResourceProvider for Advanced Queueing
</title>
</head>
<body>
<form name="TestResourceProvider" method="GET">
<%
// Check if the message has to be enqueued
if (request.getParameter("Message") != null){
Context jndiContext = new InitialContext();
XAQueueConnectionFactory queueCF = (XAQueueConnectionFactory)jndiContext.lookup
("java:comp/env/jms/InQueueCF");
Queue queue = (Queue)jndiContext.lookup("java:comp/env/jms/InQueue");
QueueConnection queueConnection = queueCF.createQueueConnection();
// Start the Connection
queueConnection.start();
QueueSender sender = queueSession.createSender(queue);
Message msg = queueSession.createTextMessage(request.getParameter("Message"));
sender.send(msg);
queueSession.commit();
sender.close();
queueSession.close();
queueConnection.close();
%>
<%
}else{
// User can enter the message to be enqueued through here
%>
Enter the message to be enqueued
<INPUT type="text" name="Message">
<br><br>
<input type="Submit" value="Enqueue Message">
<%
%>
</form>
</body>
</html>
My Steps for OJMS PRovider
1. Creating AQ queue in DB
2. configuration of resource adapter and provider
3. configuration of connection factories for resourceadapter[jmsconnector]
code:
1. Created the Queue table in DB using the sql
DROP USER jmsuser CASCADE;
GRANT connect, resource,AQ_ADMINISTRATOR_ROLE TO jmsuser IDENTIFIED BY jmsuser;
GRANT execute ON sys.dbms_aqadm TO jmsuser;
GRANT execute ON sys.dbms_aq TO jmsuser;
GRANT execute ON sys.dbms_aqin TO jmsuser;
GRANT execute ON sys.dbms_aqjms TO jmsuser;
connect jmsuser/jmsuser;
-- Create table to hold the queue, then create queue.
-- For topics multiple_consumers must be true
BEGIN
DBMS_AQADM.CREATE_QUEUE_TABLE( Queue_table => 'SMSCP_INQTBL', Queue_payload_type => 'SYS.AQ$_JMS_MESSAGE',
sort_list => 'PRIORITY,ENQ_TIME', multiple_consumers => false, compatible => '8.1.5');
DBMS_AQADM.CREATE_QUEUE( Queue_name => 'SMSCP_INQ', Queue_table => 'SMSCP_INQTBL');
DBMS_AQADM.START_QUEUE(queue_name => 'SMSCP_INQ');
END;
quit;
Now our queue Name is queue Name : SMSCP_INQ table Name: SMSCP_INQTBL
2. Creating the Cp and datasource for the db [jmsuser] to make java to access queue
Creating ConnectionPool jmsDBPool
Creating DataSource jmsDBDataSource
Jndi jdbc jdbc/JMSDBDS
After creating, i got the following data-sources.xml
DATASOURCES.XML
<?xml version = '1.0' encoding = 'UTF-8'?>
<data-sources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/data-sources-10_1.xsd" schema-major-version="10" schema-minor-version="1">

<managed-data-source connection-pool-name="Example Connection Pool" jndi-name="jdbc/OracleDS" name="OracleDS"/>

     <managed-data-source connection-pool-name="jmsDBPool" jndi-name="jdbc/JMSDBDS" name="jmsDBDataSource"/>

<connection-pool name="Example Connection Pool">
<connection-factory factory-class="oracle.jdbc.pool.OracleDataSource" user="scott" password="tiger" url="jdbc racle:thin:@//localhost:1521/ORCL"/>
</connection-pool>

<connection-pool name="jmsDBPool">
<connection-factory factory-class="oracle.jdbc.pool.OracleDataSource" user="jmsuser" password="jmsuser" url="jdbc racle:thin:@//localhost:1521/xe"/>
</connection-pool>
</data-sources>
3. JMS Connector Task. Customising the ra.xml
ra.xml

<resourceadapter>
<resourceadapter-class>oracle.j2ee.ra.jms.generic.JMSResourceAdapter</resourceadapter-class>
<config-property>
<config-property-name>lookupMethod</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>resourceProvider</config-property-value>
</config-property>
<config-property>
<config-property-name>resourceProviderName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>testResourceProvider</config-property-value>
</config-property>

          <adminobject>
<adminobject-interface>javax.jms.Queue</adminobject-interface>
<adminobject-class>oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl</adminobject-class>
<config-property>
<config-property-name>jndiName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>Queues/MY_QUEUE</config-property-value>
</config-property>
<config-property>
<config-property-name>resourceProviderName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>testResourceProvider</config-property-value>
</config-property>
</adminobject>

<adminobject>
<adminobject-interface>javax.jms.Queue</adminobject-interface>
<adminobject-class>oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl</adminobject-class>
<config-property>
<config-property-name>resourceProviderName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>testResourceProvider</config-property-value>
</config-property>
</adminobject>
<adminobject>
<adminobject-interface>javax.jms.Topic</adminobject-interface>
<adminobject-class>oracle.j2ee.ra.jms.generic.AdminObjectTopicImpl</adminobject-class>
<config-property>
<config-property-name>resourceProviderName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>testResourceProvider</config-property-value>
</config-property>
</adminobject>
</resourceadapter>
4. Create a JMS Connector INstance
oc4j-connectors.xml
     <connector name="testResourceAdapter" path="testResourceAdapter.rar">
          <config-property name="lookupMethod" value="resourceProvider"/>
          <config-property name="resourceProviderName" value="testResourceProvider"/>
          
          
     </connector>
5. RA Connection Factories
<?xml version="1.0" encoding="UTF-8"?>
<oc4j-connector-factories xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/oc4j-connector-factories-10_0.xsd"
schema-major-version="10"
schema-minor-version="0">
<connector-factory location="resourceAdapterXAQCF/MYXAQCF" connector-name="testResourceAdapter">
<config-property name="jndiLocation" value="XAQueueConnectionFactories/XAQCF"/>
<connection-pooling use="private">
<property name="waitTimeout" value="300" />
<property name="scheme" value="fixed_wait" />
<property name="maxConnections" value="50" />
<property name="minConnections" value="0" />
</connection-pooling>
<connectionfactory-interface>javax.jms.XAQueueConnectionFactory</connectionfactory-interface>
</connector-factory>
</oc4j-connector-factories>
orion-web.xml
<?xml version="1.0"?>
<orion-web-app
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-web-10_0.xsd"      deployment-version="10.1.3.1.0"
     deployment-time="1218369811921"
     jsp-cache-directory="./persistence"
     jsp-cache-tlds="standard"
     temporary-directory="./temp"
     context-root="/smscpReceiver"
schema-major-version="10" schema-minor-version="0" >
     
     <resource-ref-mapping name="jms/InQueueCF" location="resourceAdapterXAQCF/MYXAQCF" />
     <message-destination-ref-mapping location="resourceAdapterInQ/MYINQ" name="jms/InQueue">
          </message-destination-ref-mapping>
     <web-app>
     </web-app>
</orion-web-app>
web.xml
<resource-ref>
     <res-ref-name>jms/InQueueCF</res-ref-name>
     <res-type>javax.jms.XAQueueConnectionFactory</res-type>
     <res-auth>Container</res-auth>
</resource-ref>
<message-destination-ref>
     <message-destination-ref-name>jms/InQueue</message-destination-ref-name>
     <message-destination-type>javax.jms.Queue</message-destination-type>
     <message-destination-usage>Produces</message-destination-usage>
     <message-destination-link>jms/InQueue</message-destination-link>
</message-destination-ref>
<message-destination>
<message-destination-name>jms/InQueue</message-destination-name>
</message-destination>

Sorry for the jammed one
Neat one.
am trying to setup OracleOJMS provider and tries to access queue and post to queue from a normal jsp for testing.
I am getting the following
javax.jms.JMSException: Not supported in XA-backed session outside global transaction
at oracle.j2ee.ra.jms.generic.RAUtils.make(RAUtils.java:525)
at oracle.j2ee.ra.jms.generic.RAUtils.toJMSException(RAUtils.java:199)
at oracle.j2ee.ra.jms.generic.RAUtils.toJMSException(RAUtils.java:210)
at oracle.j2ee.ra.jms.generic.CommonProducerWrapper.prepareForS
INVOCATION
<form name="TestResourceProvider" method="GET">
<%
// Check if the message has to be enqueued
if (request.getParameter("Message") != null){
Context jndiContext = new InitialContext();
XAQueueConnectionFactory queueCF = (XAQueueConnectionFactory)jndiContext.lookup
("java:comp/env/jms/InQueueCF");
Queue queue = (Queue)jndiContext.lookup("java:comp/env/jms/InQueue");
QueueConnection queueConnection = queueCF.createQueueConnection();
// Start the Connection
queueConnection.start();
QueueSender sender = queueSession.createSender(queue);
Message msg = queueSession.createTextMessage(request.getParameter("Message"));
sender.send(msg);
queueSession.commit();
sender.close();
queueSession.close();
queueConnection.close();
%>
<%
}else{
// User can enter the message to be enqueued through here
%>
Enter the message to be enqueued
<INPUT type="text" name="Message">
<br><br>
<input type="Submit" value="Enqueue Message">
<%
%>
</form>
</body>
</html>
---------------------

JMS adapter transaction. Rollback message to queue.

Hi all !
A have question about jms adapter transaction. My composite application has 3 steps : JMS adapter (listener), mediator, WS adapter. JMS adapter listen queue push message to mediator, mediator invoke web service. If ws not available (server down), mediator try recovery 5 times. After 5 times, reject message from queue. I wont rollback message to queue. I saw examples with JMS + BPEL, but it not help me. Anybody can help me.

Hi,
You don’t need to catch a mediator fault – you can let it rollback to the JMS Queue and let the Queue do the retries.
To get the retries working, log in to the weblogic console and navigate to JMS Modules -> Your Module -> Your Queue -> Configuration -> Delivery Failure
Here you will find options for Redelivery Limit. Set this to the number of retries you need.
Then navigate to the connection factory you want and set the redelivery delay.
This should get your desired behaviour, but once the message has failed it will be discarded. If you prefer to put it on an error queue you can create an error queue, and in the original queue’s, goto Delivery Failure, change the expireation policy and set the Error Destination to be your error queue.
Hope that helps!
Robert

Javax.jms.JMSException: Not supported in XA-backed sessionoutside global tx

I am trying to setup OracleOJMS provider and tries to access queue and post to queue from a normal jsp for testing.
I am getting the following
javax.jms.JMSException: Not supported in XA-backed session outside global transaction
     at oracle.j2ee.ra.jms.generic.RAUtils.make(RAUtils.java:525)
     at oracle.j2ee.ra.jms.generic.RAUtils.toJMSException(RAUtils.java:199)
     at oracle.j2ee.ra.jms.generic.RAUtils.toJMSException(RAUtils.java:210)
     at oracle.j2ee.ra.jms.generic.CommonProducerWrapper.prepareForSend(CommonProducerWrapper.java:350)
     at oracle.j2ee.ra.jms.generic.CommonProducerWrapper.send(CommonProducerWrapper.java:159)
     at _ResourceProvider._jspService(_ResourceProvider.java:112)
     at com.orionserver[Oracle Containers for J2EE 10g (10.1.3.1.0) ].http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)I have posted query in this link.
http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=14&t=001837
Can you please help me out?

Sorry for the jammed one
Neat one.
am trying to setup OracleOJMS provider and tries to access queue and post to queue from a normal jsp for testing.
I am getting the following
javax.jms.JMSException: Not supported in XA-backed session outside global transaction
at oracle.j2ee.ra.jms.generic.RAUtils.make(RAUtils.java:525)
at oracle.j2ee.ra.jms.generic.RAUtils.toJMSException(RAUtils.java:199)
at oracle.j2ee.ra.jms.generic.RAUtils.toJMSException(RAUtils.java:210)
at oracle.j2ee.ra.jms.generic.CommonProducerWrapper.prepareForS
INVOCATION
<form name="TestResourceProvider" method="GET">
<%
// Check if the message has to be enqueued
if (request.getParameter("Message") != null){
Context jndiContext = new InitialContext();
XAQueueConnectionFactory queueCF = (XAQueueConnectionFactory)jndiContext.lookup
("java:comp/env/jms/InQueueCF");
Queue queue = (Queue)jndiContext.lookup("java:comp/env/jms/InQueue");
QueueConnection queueConnection = queueCF.createQueueConnection();
// Start the Connection
queueConnection.start();
QueueSender sender = queueSession.createSender(queue);
Message msg = queueSession.createTextMessage(request.getParameter("Message"));
sender.send(msg);
queueSession.commit();
sender.close();
queueSession.close();
queueConnection.close();
%>
<%
}else{
// User can enter the message to be enqueued through here
%>
Enter the message to be enqueued
<INPUT type="text" name="Message">
<br><br>
<input type="Submit" value="Enqueue Message">
<%
%>
</form>
</body>
</html>
---------------------

Is XA transactions supported for the SOA Suite 10.1.3.4 on weblogic platfor

There are 2 weblogic domains 1 & 2. Domain 1 hosts the JMS queue and domain 2 hosts the BPEL process. The BPEL process in domain 2 uses JMS adapter to get messages from domain 1. With queues on Weblogic domain 1, is XA transactions supported for the SOA suite 10.1.3.4 BPEL process JMS Adapter on weblogic domain 2?

There are 2 weblogic domains 1 & 2. Domain 1 hosts the JMS queue and domain 2 hosts the BPEL process. The BPEL process in domain 2 uses JMS adapter to get messages from domain 1. With queues on Weblogic domain 1, is XA transactions supported for the SOA suite 10.1.3.4 BPEL process JMS Adapter on weblogic domain 2?

Enable Oracle XA Transaction Support

Hi everybody. First of all, sorry for my terrible English.
I've been some problems using COM+ with Personal Oracle 8i (8.1.7.0.0) and SQL Server 2000 and Windows 2000 for development only.
I have one method that inserts the same data both SQL Server and Oracle (the tables and procedures definitions are identical) and I'm utilizing GetObjectContext method to commit or abort the transactions (the COM component were made in VB). Out of COM+ environment the method works 5x5. The error message is: "-2147168229 - Cannot connect to the transaction manager or the transaction manager is unavailable."
Checking Microsoft documentation I found an article (http://support.microsoft.com/support/complus/mtsandoracle.asp) telling me to "Enable Oracle XA Transaction Support" so I could have transactional work with Oracle and COM+. OK, just fine.
Does anyone knows how could I manage it? I am not a DBA nor I know one (an Oracle DBA), but I shall explain to my team how program 2 phase commit between Oracle and SQL Server.
Thanks in advance, and forgive me the size of this "book". I should be shorter next time...
null

Vivek, thanks for the help.
I am utilizing these versions of Oracle Products:
Personal Oracle8i Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Net8 Client 8.1.7.0.0
Oracle Services for MTS 8.1.7.0.0
Oracle Provider for OLE DB 8.1.7.2.0
The provider I first tried was MSDAORA with no success and then ORAOLEDB with no success too.
But those entries in registry that you sent me were all with Microsoft dll`s. I will try again tomorrow and send you the results
Thank you again
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Vivek Raja:
Renato, firstly what is the interface you use to access Oracle from your COM+ components? If it is OLEDB which provider is in use - MSDAORA or ORAOLEDB? What are the versions in use 8.1.6 or 8.1.7? If you are using MSDAORA as the provider then you will need to add the following key to your registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI.
Under this key add the following registry string values:
OracleOCILib - oraclient8.dll
OracleXALib - oraclient8.dll
OracleSQLLib - orasql8.dll
If you are using ORAOLEDB as the provider install Oracle Services For MTS 8.1.7. The error you receive seems to point to the fact that the "Distributed Transaction Coordinator" Windows2000 Service is not running.<HR></BLOCKQUOTE>
null

How do I download Adobe Acrobat using the Agreement Number provided by my employer. Having difficulty connecting to Adobe Chat with Support option.

How do I download Adobe Acrobat using the Agreement Number provided by my employer? Having difficulty connecting to Adobe Chat with Support option.

Hi,
If you already have the serial number then I would request you to download the software from the below link and install it.
http://www.adobe.com/downloads/other-downloads.html
Regards,
Anand

Local transaction support when BPEL invokes JCA adapter

Hi all,
I've implemented a BPEL process consisting of multiple invoke activities to my (custom) JCA Resource Adapter which connects to an EIS.
My concern is to support local transactions. Here are some code snippets describing what I've done so far.
Declare the transaction support at deployment time (ra.xml)
<transaction-support>LocalTransaction</transaction-support>Implementer class of ManagedConnection interface
public class MyManagedConnection implements ManagedConnection {
     public XAResource getXAResource() throws ResourceException {
         throw new NotSupportedException("XA Transactions not supported");
     public LocalTransaction getLocalTransaction() throws ResourceException {
         return new MyLocalTransaction(this);
        public void sendTheEvent(int eventType, Object connectionHandle) {
             ConnectionEvent event = new ConnectionEvent(this, eventType);
             if (connectionHandle != null) {
                event.setConnectionHandle(connectionHandle);
            ConnectionEventListener listener = getEventListener();
         switch (eventType) {
          case ConnectionEvent.CONNECTION_CLOSED:
               listener.connectionClosed(event); break;
          case ConnectionEvent.LOCAL_TRANSACTION_STARTED:
               listener.localTransactionStarted(event); break;
          case ConnectionEvent.LOCAL_TRANSACTION_COMMITTED:
               listener.localTransactionCommitted(event); break;
          case ConnectionEvent.LOCAL_TRANSACTION_ROLLEDBACK:
               listener.localTransactionRolledback(event); break;
          case ConnectionEvent.CONNECTION_ERROR_OCCURRED:
               listener.connectionErrorOccurred(event); break;
          default: break;
}Implementer class of LocalTransaction interface
public class MyLocalTransaction implements javax.resource.spi.LocalTransaction {
     private MyManagedConnection mc = null;
     public MyLocalTransaction(MyManagedConnection mc) {
         this.mc = mc;
     @Overide
     public void begin() throws ResourceException {
         mc.sendTheEvent(ConnectionEvent.LOCAL_TRANSACTION_STARTED, mc);
     @Override
     public void commit() throws ResourceException {
         eis.commit(); //eis specific method
         mc.sendTheEvent(ConnectionEvent.LOCAL_TRANSACTION_COMMITTED, mc);
     @Override
     public void rollback() throws ResourceException {
         eis.rollback(); //eis specific method
         mc.sendTheEvent(ConnectionEvent.LOCAL_TRANSACTION_ROLLEDBACK, mc);
}Uppon BPEL process completion, MyLocalTransaction.commit() is called. However, localTransactionCommitted(event) fails and I get the following error:
Error committing transaction:; nested exception is: weblogic.transaction.nonxa.NonXAException: java.lang.IllegalStateException:
[Connector:199175]This ManagedConnection is managed by container for its transactional behavior and has been enlisted to JTA transaction by container;
application/adapter must not call the local transaction begin/commit/rollback API. Reject event LOCAL_TRANSACTION_COMMITTED from adapter.Could someone give me some directions to proceed ?
My current installation consists of:
1. Oracle SOA Suite / JDeveoper 11g (11.1.1.4.0),
2. WebLogic Server 10.3.4
Thank you for your time,
George

Hi Vlad, thank you again for your immediate response.
With regards to your first comment. I already have been using logs, so I confirm that neither javax.resource.spi.LocalTransaction#begin() nor javax.resource.spi.LocalTransaction#commit()
is called in the 2nd run.
I think it might be helpful for our discussion if I give you the call trace for a successful (the first one) run.
After I deploy my custom JCA Resource Adapter, I create a javax.resource.cci.ConnectionFactory through Oracle EM web application and the following methods are called:
-- MyManagedConnectionFactory()
(Constructor of the implementer class of the javax.resource.spi.ManagedConnectionFactory interface)
-- javax.resource.spi.ManagedConnectionFactory#createManagedConnection(javax.security.auth.Subject, javax.resource.spi.ConnectionRequestInfo)
-- MyManagedConnection()
(Constructor of the implementer class of the javax.resource.spi.ManagedConnection interface)
-- javax.resource.spi.ManagedConnection#addConnectionEventListener(javax.resource.spi.ConnectionEventListener)
-- javax.resource.spi.ManagedConnection#getLocalTransaction()
-- MySpiLocalTransaction(MyManagedConnection)
(Constructor of the implementer class of the javax.resource.spi.LocalTransaction interface)
-- javax.resource.spi.ManagedConnectionFactory#createConnectionFactory(javax.resource.spi.ConnectionManager)
-- MyConnectionFactory(javax.resource.spi.ManagedConnectionFactory, javax.resource.spi.ConnectionManager)
(Constructor of the implementer class of the javax.resource.cci.ConnectionFactory interface)BPEL process consists of multiple invoke activities to my (custom) JCA Resource Adapter which connects to an EIS. Client tester invokes BPEL process, and execution starts.
Here is the method call trace for the last invoke (after which, commit is executed). The logs for all the rest invocations are identical:
-- javax.resource.cci.ConnectionFactory#getConnection()
-- javax.resource.spi.ManagedConnection#getConnection(javax.security.auth.Subject, javax.resource.spi.ConnectionRequestInfo)
-- MyConnection(MyManagedConnection)
(Constructor of the implementer class of the javax.resource.cci.Connection interface)
-- javax.resource.cci.Connection#close()
(I don't understand why close() is called here, any idea ?)
-- javax.resource.cci.ConnectionFactory#getConnection()
-- javax.resource.spi.ManagedConnection#getConnection(javax.security.auth.Subject, javax.resource.spi.ConnectionRequestInfo)
-- MyConnection(MyManagedConnection)
(Constructor of the implementer class of the javax.resource.cci.Connection interface)
-- javax.resource.cci.Connection#createInteraction()
-- MyInteraction(javax.resource.cci.Connection)
(Constructor of the implementer class of the javax.resource.cci.Interaction interface)
-- javax.resource.cci.Interaction#execute(javax.resource.cci.InteractionSpec, javax.resource.cci.Record, javax.resource.cci.Record)
-- javax.resource.spi.LocalTransaction#commit()I would expect that after the last commit() - meaning that BPEL process is done, and its state is "Completed" - Weblogic server would call the following:
javax.resource.cci.Connection#close()However it doesn't. Do I miss something ?

No Language and Input Support option in my OS 6 Applications list - need to add second language

I have a Curve 9300 bought a few weeks ago in the Caribbean (Digicel carrier). I'm now in Germany and was able to switch between english and german languages for the past few weeks; however this evening I synced the device with my Macbook for the first time, which prompted an upgrade in software.
Now I have OS version 6, but my language selection is only English and portuguese. When I select Applications on the desktop software, it does not give me the Language and Input Support option to re-add german.
I tried uninstalling and reinstalling from the offiste RIM link,(where people can choose their international carriers), but the download is an unreadable Text Edit format. I've tried un- and re-installing on my mac, but that doesn't do anything, and i don't know how to uninstall from the device itself (plus am scared i'll lose all my info).
Can anyone help? I've exhausted every option and I need to write in both languages for work...
Thanks in advance!

sariadina23 wrote :
I wanna add korean..
Downloading OS pack? I haven't.. How could i? The link please..
And,fyi.. I downloaded the bb desktop software from official blackberry website malaysia..
And it's successfully installed,no prob at all..
Hi sariadina23
Please remember as this section of forums is for Mac so the below mentioned steps can only be performed on a PC only not Mac. If you want to install Korean language support on your device you can try this :
1.Download and Install on your PC an OS pack having All Language from here Indosat or Device Software Download Sites for BlackBerry
( Make sure you are downloading for the same device model )
2.. Download and install the latest BlackBerry desktop software for Windows from here BlackBerry desktop software
3.Search your C: drive for Vendor.xml and delete them, there may be one or two vendor.xml ( On your Pc change your folders option to show hidden files/folders ) :
C:\Program Files (x86)\Common Files\Research In Motion\AppLoader
C:\Users\Windows UserName\AppData\Roaming\Research In Motion\BlackBerry\Loader XML
Once completed Open BlackBerry Desktop Software for Windows > Select Applications. > In the Language and Input Support section, select the language to be added to the BlackBerry smartphone (a + will appear next to the language to install) > Click Apply.
KB13067 : How to obtain language packs for BlackBerry smartphone.
KB05305 : Localization support for BlackBerry Smartphones.
So try it and let us know.
Prince
Click " Like " if you want to Thank someone.
If Problem Resolves mark the post(s) as " Solution ", so that other can make use of it.
Click " Like " if you want to Thank someone.
If Problem Resolves mark the post(s) as " Solution ", so that other can make use of it.

CAF entity proxies provide Transactional support???

Hi All,
We have created entity services, generated proxies so that we can use them in our webdynpro component's. Question here is, does the Generated Proxies of entity services provide Transaction support? or do we need to move all the business logic from webdynpro to CAF Application service?
Appreciate your time
Som

Hi Aliksei,
Thank you for the reply back.
Here is the situation:
We are generating proxy classes for CAF entity objects and using them in WebDynpro for all our custom CRUD operations.
Is this a good design or move all the CRUD operations to App Service and call it in the webdynpro. What is the exact difference in Updating the CAF Database from WebDynpro (Component controller) and from App Service.
In what scenario's you use App Service and WebDynpro Component controller with respect to Updating CAF Database.
Thank you for your time.
Thanks
Som

JMS receiver adapter supports SSL??

Hi
We have a interface in our project which uses JMS adapter and to make it secured communication , we are requested to use SSL.
Can anyone please suggest if JMS receiver adapter supports SSL.
If no possible, coould you please let us know any other alternative approach to this.
Regards
Jagruth

Look into below discussions
JMS To MQSeries with SSL.
Regards
Aashish Sinha

Edit of Foreign JMS module in admin console causes redeployment error

A JMS module (-jms.xml) for a foreign JMSServer specifies the url of the real JMS server. I am trying to use a deployment plan to make this url a deployment property.
Following the instructions in "Configuring and Managing Weblogic JMS" and "Deploying Applications to Weblogic Server", I have deployed the module with a fixed URL, and then attempt to edit the url in the admin console. The admin console correctly creates a deployment plan to hold modified value, but then can't redeploy the module due to errors during deployment.
I experience these errors with the module deployed stand-alone, or when bundled with my enterprise application. I also get the same error if I produce the deployment plan using the PlanGenerator.
The error seems to be a bug in the deployment plan machinery, since the xpath it produces for the variable-application does not match the xml schema for <weblogic-jms>. The plan.xml refers to "/weblogic-jms/foreign-server[name="IQN_OLTP_FOREIGN_JMS_Server"]/connectionurl" while the schema defines "/weblogic-jms/foreign-server/connection-url".
Any advice would be welcome.
We are running 9.2 SP3.
The messages in the admin console logs are:
####<Jan 22, 2009 12:07:02 PM MST> <Info> <J2EE> <truman> <IQN_ADMIN_SERVER> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (
self-tuning)'> <system> <> <> <1232651222010> <BEA-160166> <References were found in deployment plan for module 'IQN_JMS_OLTP_FOREIGN-jms.xml'
with uri, '.'. The plan was merged.>
####<Jan 22, 2009 12:07:02 PM MST> <Error> <J2EE> <truman> <IQN_ADMIN_SERVER> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default
(self-tuning)'> <system> <> <> <1232651222024> <BEA-160197> <Unable to load descriptor weblogic.deploy.api.spi.config.DescriptorParser$1@1c7654
8 finder: weblogic.utils.classloaders.CodeGenClassFinder@1ca6109 annotation: /. of module IQN_JMS_OLTP_FOREIGN-jms.xml. The error is weblogic.d
escriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
//www.bea.com/ns/weblogic/90' instead of 'default-targeting-enabled@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://ww
w.bea.com/ns/weblogic/90:<null>
problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
//www.bea.com/ns/weblogic/90' instead of 'foreign-destination@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://www.bea.
com/ns/weblogic/90:<null>
problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
//www.bea.com/ns/weblogic/90' instead of 'foreign-destination@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://www.bea.
com/ns/weblogic/90:<null>
problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
//www.bea.com/ns/weblogic/90' instead of 'foreign-connection-factory@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://w
ww.bea.com/ns/weblogic/90:<null>
problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
//www.bea.com/ns/weblogic/90' instead of 'foreign-connection-factory@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://w
ww.bea.com/ns/weblogic/90:<null>
/home/jbullock/development/patch841/domains/IQN/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential
-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http://www.bea.com/ns/weblogic/90' instead of 'connectionurl@http://www.bea.com/ns/w
eblogic/90' here in element foreign-server@http://www.bea.com/ns/weblogic/90:<nullplan.xml>

I also tried this, without success. Changing the deployment plan to use the element name "connection-url" leads to a different error during deployment:
<Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, IQN_JMS_OLTP_FOREIGN [archive: ../../package/jms/IQN_JMS_OLTP_FOREIGN-jms.xml], to IQN_BATCH IQN_OLTP1 .>
plan xpath defines an element [connection-url] that is not valid!(There is also a subtle variation in the xpath used in the deployment plan: It isn't clear whether the deployer expects /weblogic-jms/foreign-server/[name="IQN_OLTP_FOREIGN_JMS_Server"]/connection-url or /weblogic-jms/foreign-server[name="IQN_OLTP_FOREIGN_JMS_Server"]/connectionurl. The former, although not really correct XPath syntax, seems to be required for other elements, but in this case, the PlanGenerator emits latter, which is correct XPath, but has the wrong element name.)
Edited by: John Bullock on Jan 26, 2009 11:59 AM

Yesterday I purchased a new ipod classic to replace one that had worn out. The price was $179. I wonder if I am eligible for the extended warranty for $59. Can't seem to navigate through the apple support option to get answer. Anyone know?

yesterday I purchased a new ipod classic to replace one that had worn out. The price was $179. I wonder if I am eligible for the extended warranty for $59. Can't seem to navigate through the apple support option to get answer. Anyone know?

Put in the serial number but was not offered an extended apple care plan. I guess if you purchase a new one because your old one is out of warranty you get a deal for $179 but you don't get a chance for an extended warranty. You don't get a new box or earbuds, just a brand new iPod. Good deal but since my first died under warranty, got a new one for free, second one I smashed the screen and got a new one for (I don't remember) and now the hard drive went and I paid $179 for a new one, I was hoping to get an extended warranty. But I guess not...
Thank you!

Best support option for failing Bluetooth?

In the past few weeks or so, my Macbook has been losing bluetooth connectivity intermittently. I was hoping that somehow the 10.4.8 update would help, but if anything it's only gotten worse. Now it doesn't just happen when the laptop is hot, but also right after a cold boot.
Anyway, I'm fed up and was wondering what would be the best support option. Should I call Applecare or take it to my local genius bar?

So the problem was fixed at the Apple Store. They replaced my logic board and the bluetooth board + cable.
I have to say that I'm impressed with the support I got this time. They ordered the parts and let me keep my laptop until they came in. I called to check in with them after several days when I hadn't heard back from them and was told they were still waiting on a few parts. The guy called me right back after he checked in the days shipment to tell me that the rest of the parts were in. I brought the laptop in that evening and the repair was complete the next morning. Very nice.
I just wanted to throw that out there as I have posted my share of complaints about my MacBook here.

GlassFish2 JMS (OpenMQ) Transaction Support options in Admin Console

Similar Messages

Maybe you are looking for