11.5.9 concurrent progrmas are accessible in Oracle OA Adapter ?

Hi Friends,
I need to access concurent programs in 11.5.9 instance of Oracle Apps using OA Adapters in BPEL/ESB.
Can you pls tell me if we can do this ? Any reference link will be a great help.
i have only 11.5.10 instance and I could do that, but now the requirement is for 11.5.9 and I do not have any instance for that.
Thanks.

EP-3000: Internal error starting Oracle Toolkit. REP-3000: Internal error starting Oracle Toolkit. Report Builde
REP-3000 is a known error which is related to DISPLAY settings.
Please see previous threads for discussion and solution -- https://forums.oracle.com/community/developer/search.jspa?q=REP-3000
Thanks,
Hussein

Similar Messages

  • I am new to Mac and am having trouble with uploading images from my pictures folder to Facebook and other share sites- some of my images are accessible while others are seemingly locked....

    I am new to Mac and am having trouble up loafing images from my pictures folder to photography sites and Facebook. Some of the saved images are accessible, while others are not, ( they are light colored and cannot be uploaded) I am not saving them any differently.

    Hi Robodisko,
    Thanks for your prompt reply...... 
    I often proof my work in preview then edit images in photoshop and rename from there.  The dsc images are renamed to correlate the name of the class etc.  i.e. dcs_001 is saved as the file name required 7A.jpeg etc.
    The file names are required to correlate what is what and so on..........

  • MDB cannot loads enitities if more than 10 concurrent messages are sent tog

    Hello,
    I have seen a weird behavior of the MDB in Jboss or perhaps in transaction management.
    Here is a my scenario
    I have a session bean sb, an entity bean e and a message driven bean mb
    When a request comes to sb , it persists a new entity e and send a message (primary key) to mb
    mb then loads e from the database using one of the findByXX method and does something else.
    If 10 concurrent request comes to sb, 10 different entities are persisted and 10 different messages are sent to mb
    mb are able to load 10 different e from the database
    Everything works fine as long as there are 10 concurrent request. If there are 13 concurrent request, then one or two mb
    cannot load e from the database. It seems that the session bean has persisted the entities but some of them are still unload able from mb. They have been persisted , (I saw in the logs), but mb cannot load them.
    Initially I thought that a transaction mishap might be happening, so instead of persisting the entity and sending the message in one method in sb , I separated these two tasks in two methods a and b, in which both a and b uses RequiresNew transaction attribute. But the problem still remains. Please note if the number of parallel request are less than 10 then everything works fine. Is there something I am missing or is Jboss doing something buggy?
    The above situation is reproducible .
    Here is some more information about the problem along with some code snapshots. Note that the code is trimmed for clarity purposes.
    Request is a simple entity (e as mentioned in the problem before) that is persisted in session bean . Here is a trimmed snapshot
    Request.java
    package gov.fnal.ms.dm.entity;
    import java.io.Serializable;
    import javax.persistence.Column;
    import javax.persistence.Entity;
    @Entity
    @NamedQueries({@NamedQuery(name = "Request.findById", query = "SELECT r FROM Request r WHERE r.id = :id"),
    @NamedQuery(name = "Request.findAll", query = "SELECT r FROM Request r"),
    @Table(name = "cms_dbs_migration.Request")
    @SequenceGenerator(name="seq", sequenceName="cms_dbs_migration.SEQ_REQUEST")
    public class Request implements Serializable {
    private String detail;
    @Id
    @GeneratedValue(strategy = GenerationType.AUTO, generator="seq")
    @Column(nullable = false)
    private Long id;
    private String notify;
    .....The session bean is MSSessionEJBBean.
    MSSessionEJBBean.java
    @Stateless(name="MSSessionEJB")
    @WebService(endpointInterface = "gov.fnal.ms.dm.session.MSSessionEJBWS")
    public class MSSessionEJBBean implements MSSessionEJB, MSSessionEJBLocal, MSSessionEJBWS {
    @PersistenceContext(unitName="dm")
    private EntityManager em;
    .......    The methods that is called concurrently in this bean is
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    public Request addRequest(String srcUrl, String dstUrl, String path,
    String dn, String withParents, String withForce, String notify) throws
    Exception {
    Request r = addRequestUnit(srcUrl, dstUrl, path, dn, withParents, withForce, notify);
    if (r != null) sendToQueue(r.getId());
    return r;
    }    It first adds the request entity and then sends a message to the queue in separate methods each using TransactionAttributeType.REQUIRES_NEW (I don't think this TransactionAttributeType is needed . I was just playing to see if this resolves the problem)
    Here is the method that actually persist the entity
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    public Request addRequestUnit(String srcUrl, String dstUrl, String path,
    String dn, String withParents, String withForce, String notify) throws
    Exception {
    ....// Does something before persisting
    Request r = new Request();
    r.setNotify(notify);
    r.setPath(path);
    r.setPerson(p);
    r.setWithForce(withForce);
    r.setWithParents(withParents);
    r.setProgress(new Integer(0));
    r.setStatus("Queued");
    r.setDetail("Waiting to be Picked up");
    em.persist(r);
    System.out.println("Request Entity persisted");
    System.out.println("ID is " + r.getId());
    return r;
    }I can see that the log files has messages
    *{color:#800000}"Request Entity persisted" "ID is " 12 (or some other number){color}*
    . So it is safe to assume that the request entity is persisted properly before the message is sent to the queue. Here is how the message is sent to the queue
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    private void sendToQueue(long rId) throws Exception {
    QueueSession session = null;
    QueueConnection conn = null;
    try {
    conn = factory.createQueueConnection();
    session = conn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
    MapMessage mapMsg = session.createMapMessage();
    mapMsg.setLong("request", rId);
    session.createSender(queueRequest).send(mapMsg);
    } finally {
    if (session != null) session.close();
    if(conn != null) try {
    conn.close();
    }catch(Exception e) {e.printStackTrace();}
    System.out.println("Message sent to queue");
    }I can see the message
    {color:#800000}*"Message sent to queue"*{color}
    in the log file right after I see the
    *{color:#800000}
    "Request Entity persisted"{color}*
    message. So it correct to assume that the message is infact sent to the queue.
    Here is the md bean that gets the message from the queue and process it
    @MessageDriven(activationConfig =
    @ActivationConfigProperty(propertyName="destinationType",
    propertyValue="javax.jms.Queue"),
    @ActivationConfigProperty(propertyName="destination",
    propertyValue="queue/requestmdb")
    public class RequestMessageDrivenBean implements MessageListener {
    @EJB
    private MSSessionEJBLocal ejbObj;
    public void onMessage(Message message) {
    try{
    System.out.println("Message recived ");
    if(message instanceof MapMessage) {
    System.out.println("This is a instance of MapMessage");
    MapMessage mMsg = (MapMessage) message;
    long rId = mMsg.getLong("request");
    List<Request> rList = ejbObj.getRequestById(new Long(rId));
    System.out.println("rList size is " +  rList.size());
    for(Request r: rList) {
    //Does something and print something in logs
    System.out.println("Finsihed onMessage");
    }catch(Exception e) {
    System.out.println(e.getMessage());
    }    One thing to note here is that getRequestById is another method in the same session bean MSSessionEJB. Can that be the reason for not loading the request from the database when many concurrent request are present? Here is what it does
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    public List<Request> getRequestById(Long id) throws Exception {
    System.out.println("Inside getRequestById id is " + id);
    return em.createNamedQuery("Request.findById")
    .setParameter("id", id)
    .getResultList();
    }    In the logs I do see
    {color:#800000}*"This is a instance of MapMessage"*{color}
    and I do see the correct Rid that was persisted before in the log
    *{color:#800000}
    "inside getRequestById id is 12"{color}*
    . Finally I do see
    *{color:#800000}
    "Finsihed onMessage"{color}*
    for all the request no matter how many are sent concurrently.
    *{color:#ff0000}Here is where the problem is . rList size is 1 for most of the cases but it returns 0 when the number of concurrent message exceeds 10.*
    *{color}*
    So you see there is no exception per se, just that entity does not get loaded from the database. I would like to mention this again, it does work properly when the number of concurrent request are less than 10. All the invocation of onMessage in MB are able to load the entity properly in that case. Its only when the number of concurrent request increases more than 10, the onMessage is unable to load the entity and the rList is 0.
    FYI I am using jboss-4.2.2.GA on RedHat enterprise linux 4 with jdk1.6.0_04
    Please let me know if there is more information required on this.
    Thank you

    Hello,
    I have seen a weird behavior of the MDB in Jboss or perhaps in transaction management.
    Here is a my scenario
    I have a session bean sb, an entity bean e and a message driven bean mb
    When a request comes to sb , it persists a new entity e and send a message (primary key) to mb
    mb then loads e from the database using one of the findByXX method and does something else.
    If 10 concurrent request comes to sb, 10 different entities are persisted and 10 different messages are sent to mb
    mb are able to load 10 different e from the database
    Everything works fine as long as there are 10 concurrent request. If there are 13 concurrent request, then one or two mb
    cannot load e from the database. It seems that the session bean has persisted the entities but some of them are still unload able from mb. They have been persisted , (I saw in the logs), but mb cannot load them.
    Initially I thought that a transaction mishap might be happening, so instead of persisting the entity and sending the message in one method in sb , I separated these two tasks in two methods a and b, in which both a and b uses RequiresNew transaction attribute. But the problem still remains. Please note if the number of parallel request are less than 10 then everything works fine. Is there something I am missing or is Jboss doing something buggy?
    The above situation is reproducible .
    Here is some more information about the problem along with some code snapshots. Note that the code is trimmed for clarity purposes.
    Request is a simple entity (e as mentioned in the problem before) that is persisted in session bean . Here is a trimmed snapshot
    Request.java
    package gov.fnal.ms.dm.entity;
    import java.io.Serializable;
    import javax.persistence.Column;
    import javax.persistence.Entity;
    @Entity
    @NamedQueries({@NamedQuery(name = "Request.findById", query = "SELECT r FROM Request r WHERE r.id = :id"),
    @NamedQuery(name = "Request.findAll", query = "SELECT r FROM Request r"),
    @Table(name = "cms_dbs_migration.Request")
    @SequenceGenerator(name="seq", sequenceName="cms_dbs_migration.SEQ_REQUEST")
    public class Request implements Serializable {
    private String detail;
    @Id
    @GeneratedValue(strategy = GenerationType.AUTO, generator="seq")
    @Column(nullable = false)
    private Long id;
    private String notify;
    .....The session bean is MSSessionEJBBean.
    MSSessionEJBBean.java
    @Stateless(name="MSSessionEJB")
    @WebService(endpointInterface = "gov.fnal.ms.dm.session.MSSessionEJBWS")
    public class MSSessionEJBBean implements MSSessionEJB, MSSessionEJBLocal, MSSessionEJBWS {
    @PersistenceContext(unitName="dm")
    private EntityManager em;
    .......    The methods that is called concurrently in this bean is
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    public Request addRequest(String srcUrl, String dstUrl, String path,
    String dn, String withParents, String withForce, String notify) throws
    Exception {
    Request r = addRequestUnit(srcUrl, dstUrl, path, dn, withParents, withForce, notify);
    if (r != null) sendToQueue(r.getId());
    return r;
    }    It first adds the request entity and then sends a message to the queue in separate methods each using TransactionAttributeType.REQUIRES_NEW (I don't think this TransactionAttributeType is needed . I was just playing to see if this resolves the problem)
    Here is the method that actually persist the entity
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    public Request addRequestUnit(String srcUrl, String dstUrl, String path,
    String dn, String withParents, String withForce, String notify) throws
    Exception {
    ....// Does something before persisting
    Request r = new Request();
    r.setNotify(notify);
    r.setPath(path);
    r.setPerson(p);
    r.setWithForce(withForce);
    r.setWithParents(withParents);
    r.setProgress(new Integer(0));
    r.setStatus("Queued");
    r.setDetail("Waiting to be Picked up");
    em.persist(r);
    System.out.println("Request Entity persisted");
    System.out.println("ID is " + r.getId());
    return r;
    }I can see that the log files has messages
    *{color:#800000}"Request Entity persisted" "ID is " 12 (or some other number){color}*
    . So it is safe to assume that the request entity is persisted properly before the message is sent to the queue. Here is how the message is sent to the queue
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    private void sendToQueue(long rId) throws Exception {
    QueueSession session = null;
    QueueConnection conn = null;
    try {
    conn = factory.createQueueConnection();
    session = conn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
    MapMessage mapMsg = session.createMapMessage();
    mapMsg.setLong("request", rId);
    session.createSender(queueRequest).send(mapMsg);
    } finally {
    if (session != null) session.close();
    if(conn != null) try {
    conn.close();
    }catch(Exception e) {e.printStackTrace();}
    System.out.println("Message sent to queue");
    }I can see the message
    {color:#800000}*"Message sent to queue"*{color}
    in the log file right after I see the
    *{color:#800000}
    "Request Entity persisted"{color}*
    message. So it correct to assume that the message is infact sent to the queue.
    Here is the md bean that gets the message from the queue and process it
    @MessageDriven(activationConfig =
    @ActivationConfigProperty(propertyName="destinationType",
    propertyValue="javax.jms.Queue"),
    @ActivationConfigProperty(propertyName="destination",
    propertyValue="queue/requestmdb")
    public class RequestMessageDrivenBean implements MessageListener {
    @EJB
    private MSSessionEJBLocal ejbObj;
    public void onMessage(Message message) {
    try{
    System.out.println("Message recived ");
    if(message instanceof MapMessage) {
    System.out.println("This is a instance of MapMessage");
    MapMessage mMsg = (MapMessage) message;
    long rId = mMsg.getLong("request");
    List<Request> rList = ejbObj.getRequestById(new Long(rId));
    System.out.println("rList size is " +  rList.size());
    for(Request r: rList) {
    //Does something and print something in logs
    System.out.println("Finsihed onMessage");
    }catch(Exception e) {
    System.out.println(e.getMessage());
    }    One thing to note here is that getRequestById is another method in the same session bean MSSessionEJB. Can that be the reason for not loading the request from the database when many concurrent request are present? Here is what it does
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    public List<Request> getRequestById(Long id) throws Exception {
    System.out.println("Inside getRequestById id is " + id);
    return em.createNamedQuery("Request.findById")
    .setParameter("id", id)
    .getResultList();
    }    In the logs I do see
    {color:#800000}*"This is a instance of MapMessage"*{color}
    and I do see the correct Rid that was persisted before in the log
    *{color:#800000}
    "inside getRequestById id is 12"{color}*
    . Finally I do see
    *{color:#800000}
    "Finsihed onMessage"{color}*
    for all the request no matter how many are sent concurrently.
    *{color:#ff0000}Here is where the problem is . rList size is 1 for most of the cases but it returns 0 when the number of concurrent message exceeds 10.*
    *{color}*
    So you see there is no exception per se, just that entity does not get loaded from the database. I would like to mention this again, it does work properly when the number of concurrent request are less than 10. All the invocation of onMessage in MB are able to load the entity properly in that case. Its only when the number of concurrent request increases more than 10, the onMessage is unable to load the entity and the rList is 0.
    FYI I am using jboss-4.2.2.GA on RedHat enterprise linux 4 with jdk1.6.0_04
    Please let me know if there is more information required on this.
    Thank you

  • Since I get Adobe revel my photos in "Mobile albums" on my iMac disappeared. "Mobile albums" are accessible on mobile devices only. How to get back mobile albums on my iMac?

    Since I get Adobe revel my photos in "Mobile albums" on my iMac disappeared. "Mobile albums" are accessible on mobile devices only. How to get back mobile albums on my iMac?

    Which version of PSE? For PSE 12 you should be able to just log into revel in PSE and have them appear. If you were using an older version of PSE, there's a free mac app in the app store.

  • I have nine, 1-page PDF files that are accessible and need to combine into 1 PDF file.  I have tried appending, adding and the combine PDFs process. The file created is not keeping my changes. The created file is partially accessible but I have to re-fix

    I have nine, 1-page PDF files that are accessible and need to combine into 1 PDF file.  I have tried appending, adding and the combine PDFs process. The file created is not keeping my changes. The created file is partially accessible but I have to re-fix issues I had fixed in the single files. I need suggestions on what else can be done if any. Using Acrobat pro XI.

    Out of habit, I tend to combine PDF files in the Page Thumbnails pane by right-click then "Insert Pages" -> "From File". For me, this preserves the tags from both documents, although the tags may have to be moved into the right location (if I recall correctly the tags for the inserted pages get put at the end of the tag structure, regardless of where the pages are inserted), If I first put the tags for the document to be inserted inside a container tag like Section, it makes the process easier. Moving that set of tags to the right place is the only re-fixing that I recall having to do. What behavior are you experiencing?
    a 'C' student

  • My mail is stuck in yesterday's mail.  None of the icons are accessible.  Can't open delete or change mailboxes.  Still getting mail.  Any suggestions?

    My mail is stuck in yesterday's mail.  None of the icons are accessible.  Can't open delete or change mailboxes.  Still getting mail.  Any suggestions?

    This forum is for troubleshooting Mail under Mac OS 10.4 Tiger, not Leopard. You'll probably want to post your question in the Leopard Mail discussions:
    http://discussions.apple.com/forum.jspa?forumID=1223

  • Shutting down when the concurrent users are more

    Hi,
    We are working on EP 5.0 SP5, our problem is that if the concurrent users are more automatically our LDAP or Portal is shutting down (approximately 300 or above..).
              For this problem… where we have to check? help can be appreciated...
    Regards,
    Sudhir

    Hi,
    look at thread:
    SAP J2EE engine shuts down frequently
    Regards,
    Gerhard

  • Server Shutting down, when the Concurrent Users are more

    Hi,
    We are working on EP 5.0 SP5, our problem is that if the concurrent users are more automatically our LDAP or Portal is shutting down (approximately 300 or above..).
    For this problem… where we have to check? help can be appreciated...
    Regards,
    Sudhir

    Hi,
    If you portal is shutting down when it is getting a high load I would look at the memory settings defined in the configtool (if you are using a service or the startupframework) or the go.bats if you are running them manually. I would assume that the problems comes from the java process not being able to get enough memory, so try increasing the heapsize parameter Xmx (?)
    See notes
    597187
    696410 (for EP6 but content and related notes should be relevant)

  • Concurrent timers are not getting invoked for same timer inf

    Do weblogic has some parameter in weblogic deployment descriptor like numAlarmThreads="5" minThreads="1" maxThreads="10" etc
    becoz I am facing one problem relating to timer service in EJB
    Problem Scope: Concurrent timers are not getting invoked for same timer info (Serializable object containing the details of timer).
    Details : I am implementing EJB timer 2.1 and when ejbTimeOut execution of one timer exceeds the interval time, next timeout doesn’t happens till the execution of first ejbTimeOut completes . Ideally the timers should behave in the manner that on every interval the ejbTimeOut should occur no matter the previous timeout is completed or not
    for example : consider there is timer T whose timeout occurs every minute, and on every timeout it calls process P, so on every minute ideally container should give call to process P irrespective of the previous status of P (call is complete or not). In our case next call to process P is not happening after timeout also since it is waiting for previous call to P to get completed

    You should also cross-post this in the WebLogic EJB forum:
    WebLogic Server - EJB

  • Concurrent timers are not getting invoked for same timer info (Serializable

    Problem Scope: Concurrent timers are not getting invoked for same timer info (Serializable object containing the details of timer).
    Details : I am implementing EJB timer 2.1 and when ejbTimeOut execution of one timer exceeds the interval time, next timeout doesn’t happens till the execution of first ejbTimeOut completes . Ideally the timers should behave in the manner that on every interval the ejbTimeOut should occur no matter the previous timeout is completed or not
    for example : consider there is timer T whose timeout occurs every minute, and on every timeout it calls process P, so on every minute ideally container should give call to process P irrespective of the previous status of P (call is complete or not). In our case next call to process P is not happening after timeout also since it is waiting for previous call to P to get completed

    You should also cross-post this in the WebLogic EJB forum:
    WebLogic Server - EJB

  • Concurrent timers are not getting invoked for same timer info

    Problem Scope: Concurrent timers are not getting invoked for same timer info (Serializable object containing the details of timer).
    Details : I am implementing EJB timer 2.1 and when ejbTimeOut execution of one timer exceeds the interval time, next timeout doesn’t happens till the execution of first ejbTimeOut completes . Ideally the timers should behave in the manner that on every interval the ejbTimeOut should occur no matter the previous timeout is completed or not
    for example : consider there is timer T whose timeout occurs every minute, and on every timeout it calls process P, so on every minute ideally container should give call to process P irrespective of the previous status of P (call is complete or not). In our case next call to process P is not happening after timeout also since it is waiting for previous call to P to get completed

    You should also cross-post this in the WebLogic EJB forum:
    WebLogic Server - EJB

  • What Files are accessible on My comput

    What files are accessible on my pc through X-Fi? I have a external hard dri've with mp3's on it and want?to use it with X-fi.

    do you mean Zen X-Fi?
    just simply put your mp3 files into the player and enjoy.
    maybe i misunderstand your question.

  • I just purchased a new iMac, and can't get into my Wordpress blog. The username and password work on my old Macbook, iPhone4, etc, and all my other password-restricted sites are accessible...just not Wordpress. Ideas? New to all this...

    I just purchased a new iMac, and can't get into my Wordpress blog. The username and password work on my old Macbook, iPhone4, etc, and all my other password-restricted sites are accessible...just not Wordpress. Ideas? New to all this...Thanks! JP

    Try holding down the Shift key in Windows when opening iTunes. In the resulting dialogue you will get the option to create a new library or navigate to an existing one. The default location for your iTunes library is in C:\Documents and Settings\Username\My Documents\My Music\iTunes\ (or C:\Username\Music\iTunes\ in Vista). Look in there and see if you have more than one library file (they have the extension .itl) If you have more than one try opening them in turn, you may find your original library is still intact: How to open an alternate iTunes Library file

  • How many concurrent users are allowed for an Azure Virtual Machine?

    How many concurrent users are allowed for an Azure Virtual Machine?
    Please share the details with the Azure VM size. Currently I have Standard VM of size D13(4 cores, 28GB RAM)

    Hi SanPSK,
    Thanks for posting here.
    I suggest you to check this article for Azure VM size
    https://msdn.microsoft.com/en-us/library/azure/dn197896.aspx
    For the concurrent users on VM - A maximum of 2 concurrent connections are supported, unless the server is configured as a Remote Desktop Services session host.
    Girish Prajwal

  • (BUG?) Oracle Apps Adapter - Unable to setup Concurrent with no parameter

    Hi all.
    I'm facing a problem when using Oracle Apps Adapter 10.1.3.1
    In JDev Adapter Configuration Module Browser, when I want to configure it to execute a concurrent program that has no input parameter, the Module Browser does not work (the OK button does nothing)
    Examples of concurrent with no parameters are:
    1) Discrete Manufacturing->Inventory->Material Transaction->Open Interfaces->Inventory Transaction Open Interface->Concurrent Programs->Material Transactions Interface Manager (This one is the main issue I'm facing)
    2) Supply Chain Management->Shop Floor Management->Lot Based Job->Open Interfaces->Lot Based Job Open Interface->Concurrent Programs->Manager: Lot Move Transactions
    Other concurrents that have parameters all seems to pass in the configuration wizard.
    Does any one know about this issue?
    Thanks.
    Denis

    We've already been in conversation with the AppsAdapter developers about this.
    Part of the problem is that you have to have NLS_LANG set correctly on your PC. So if the NLS_LANG on your Apps install is US then the PC needs to be set like this also.
    I have some documentation which I can forward if you send me your contact details to [email protected]
    Not saying that this will solve all your problems, as we found a few with this adapter but hopefully will put you on the right track.

Maybe you are looking for