JMS persistence problem

          Hi,
          I have persistence half working on WLS6.1 Messages are being written to the database
          ok. When I crash the server, the message is still there. When I bring the server
          back up the message appears in the destination but is removed from the database.
          Therefore if the server crashes before the message is consumed it is lost.
          Any help appreciated.
          Fraser

The message appears in the destination but is removed
          from the database? That is strange behavior, and I
          have no explanation. I highly recommend contacting
          customer support. I also
          recommend trying the latest SP, just to see if that makes
          a difference.
          Tom, BEA
          Fraser wrote:
          > Hi,
          >
          > I have persistence half working on WLS6.1 Messages are being written to the database
          > ok. When I crash the server, the message is still there. When I bring the server
          > back up the message appears in the destination but is removed from the database.
          > Therefore if the server crashes before the message is consumed it is lost.
          >
          > Any help appreciated.
          > Fraser

Similar Messages

JMS Persistence with WLS 8.1SP3 in a cluster

I have been following the BEA recommendations. I have configured my JMS to write to an Oracle DB for JMS persistence. This is in a clustered environment. I have had one server go down and then come back. During the outage or right before the outage there were request in the JMS queue. I would assume when the server that failed came back up it would then receive and process the JMS request that were waiting in the DB. That doesn't seem to be happening. My setup is one JMS topic for out bound. The JMS queue is set up for internal traffic. It uses Message Beans. We are also using XADrivers.
The setup is WLS8.1SP3 on Solaris hitting an Oracle 9 db. Please forward me any questions or suggestions. Thank you in advance.

WebLogic JMS won't automatically recover messages that enter an "in-doubt" state due to persistence errors that occur while they are being sent or received. To recover such messages, JMS needs to be restarted. You can contact customer support for an 8.1 sample program that automatically restarts JMS (without restarting all of WebLogic) when this problem occurs.
Tom

My iMac 27" Late 2012 has Image Persistence Problem

I'm wondering what to do about an annoying image persistence problem on my 27" late 2012 iMac. I got the iMac just a few days ago. Monday actually, so 4 days ago.
It's the 3.4GHz i7, 8GB, NVIDIA 680MX 1TB fusion drive model.
Overall it has become the love of my life, but the image persistence thing is getting harder to ignore. This happens after only a few minutes of use. If I follow Apple's instruction on dealing with LCD image persistence, I can make it go away for a while, but it comes back very quickly.
It is extremely noticeable on a plan dark background. It looks as thought he screen has been left on for a very long time with the same windows open, but it occurrs in less than 5 minutes of use with nothing more intense than a bit of web surfing.
I've read that this is happening a great deal on these new iMacs, particularly teh 27" machines.
While the problem seems to be known to those of us afflicted I don't know if Apple has acknowledged an issue or not.
Here is a sample of the complaints: http://forums.macrumors.com/showthread.php?t=1509571
I can make the ghost image vanish by bringing up an all white scree for a minute or so or using LCD Scrub.
I'm wondering if anyone else has foun a solution other than asking for a replacement computer, which Apple seems to be granting on this issue?

Avoiding image persistence on Apple (IPS) displays
Avoiding image persistence on Apple LCD displays
If you cannot resolve the issue yourself, then return the computer for a replacement. You may do this freely within 14 days from date of purchase, so don't delay.

OSB 10.3 JMS queue problem: JMSCorrelationID is null

Hi everybody,
I am new to OSB/ALSB, and need some help regarding JMS message handling. I am trying to put some input data into a JMS queue( say, reqQueue) and to get the response from another JMS queue(say resQueue). My architecture is:
OSB proxy service->OSB business service->JMS queue(reqQueue)->BPEL process(through JMS adapter) ->JMS queue(resQueue)->OSB business service->OSB proxy service.
I have used JMSCorrelationID for response correlation. but my problem is that when I am trying to test the service from proxy service, I am getting the JMSCorrelationId as null in BPEL process as well as in the weblogic server JMS log, and as I am getting the CorrelationId as null, I am unable to correlate the response, so I am not getting any response.
This is urgent, please help me as soon as possible as possible.
Thanks in advance.
Joy

Sovled it..
OSB 10.3 JMS queue problem: JMSCorrelationID is null

Migrating JMS Persistence from WLS 4.5.2 to WLS 6.1

Hi,
we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
to change persistence mode to FIles. Therefore during migration process we have to
move the messages stored in the database to a file. The messages stored in the file
will be recovered for WLS 6.1.
My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
file?
Thanks

Hi.
I'm not sure that there is an automatic process to accomplish this, but you might get a
better answer by posting this on the JMS newsgroup.
Regards,
Michael
Manuel Villalta wrote:
Hi,
we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
to change persistence mode to FIles. Therefore during migration process we have to
move the messages stored in the database to a file. The messages stored in the file
will be recovered for WLS 6.1.
My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
file?
Thanks--
Michael Young
Developer Relations Engineer
BEA Support

Weblogic jms connection problem

Hi All,
My jms bpel process listening on jms Queue. If I deploy bpel process first time I am not getting any jms connection problem with weblogic , but if redploy I am getting jms conneciton problem. saying
Adapter_start: Jms Adapter started
<2005-12-07 10:19:20,044> <ERROR> <default.collaxa.cube.activation> <JMSAdapter::Inbound> Error whil
e creating managed connection:
<2005-12-07 10:19:20,044> <ERROR> <default.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor BP
ELJMS neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnection
FactoryFactory.java:156)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConne
ctionFactoryFactory.java:95)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:143)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:102)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionF
actory.java:355)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConn
ectionFactory.java:346)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionF
actory.java:309)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConn
ectionFactory.java:99)
at com.evermind.server.connector.ApplicationConnectionManager.createManagedConnection(Applic
ationConnectionManager.java:564)
at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnection(ConnectionPoolImpl.java:
Work around is I need to restart the BPEL server.
Is there any permanant solution for this, Please suggest.
Thanks,
Srini

srini,
see this thread
JMS Connection
thanks,
-Ng.

Server boot takes a lot of time due to JMS persistence file store

Hi,
We're using WebLogic 9.2 on a windows machine.
Recently, we enhanced our application to work with JMS.
We're using 2 JMS servers on 2 different servers in a cluster, and working with distributed destinations.
We're using file store as our persistence store.
Lately, we found that server boot takes a lot of time due to actions which are performed on the file-store.
Analyzing this problem, we saw that the file size is ~2GB.
We understand that the file size does not shrink (unless manually compacted), and its size is matching the highest number ever of pending messages in the queues (like a high water-mark).
We also turned store debug on, using weblogic.Debug.DebugStoreIOPhysical, and we saw a lot of recovery logs after the file-store is opened.
We've checked and verified that our JMS transactions are completed successfully. We also verified that the number of pending and current messages is 0.
We've stopped the server gracefully, verifying there are no pending messages.
However, server boot repeatedly takes ~30 minutes due to heavy work done on the persistence store.
Compacting or removing the file store eliminates the delay.
However, we want to avoid manual operations every time we want to boot the server.
Please share your ideas.
Thanks,
Itsik

The only suggestions I have off the top of my head are:
* Ensure (1) the host system has at least 2GB (file store size) of free physical memory in addition to the memory used by current processes, and (2) the host system is not rebooted between each WebLogic restart. If you make sure of these two items, then the operating system will implicitly cache the store's file contents in memory even between boots -- when WebLogic subsequently boots the file store, the O/S should serve the file contents up much more quickly.
* Consider moving to a JDBC store. JDBC store runtime performance is lower, but since you have a typically only have a small amount of records to recover, boot performance should be higher in this case.
* Not that it helps your particular case, but it happens that we have boot performance enhancements in process for a future release (hopefully a near future release).
Tom

JMS configuration problem log file

Hello,
My purpose is to send xml data from MQSeries to BW using XI. MQSereies is installed in XI server. For thah I am trying to configure JMS adpter for MQSeries in XI. I have successfully deployed the necessary external drivers using SDM. I have configured the sender channel with the following parameters.
Adapter type: JMS
Transport Protocol :WEBsphereMQ(non-JMS)
Message protocol :JMS1.x
Queue connection factory java class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class: com.ibm.mq.jms.MQQueue
IP address: IP address of XI system.
Port: 1414
Queue manager name : MQ-manager-name_XI-system-name
Channel Name : reciever-channel-name_XI-system-name
JMS queue: postcard
Charecter set ID:
Transport/networkprotocol: TCP/IP
JMS-Compliant : WebsphereMQ(non-JMS)
But when I check it in adapter monitor JMS is shown as red.
<b>In default trace file I am getting the following error</b>
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'SYSTEMNAME:QUEUEMANAGERNAME_SYSTEMNAME'
            at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
            at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
            at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:960)
            at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:159)
            at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:215)
            at com.sap.aii.af.service.jms.WorkerJMSReceiver.init(WorkerJMSReceiver.java:283)
            at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:325)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
<b>I also get the following warning</b>
Warning   : Catching java.lang.NullPointerException
            at com.sap.aii.af.service.jms.WorkerJMSReceiver.start(WorkerJMSReceiver.java:584)
            at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:335)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Can any one tell what could be the problem.
Regards,
Amith

Try the following :
1. Check if by any chance more than 1 Queue manager listeners have port number as 1414. Make sure all run on unique ports.
2. Instead of IP addreess in the adapter config., try using hostname.
3. Also check the website www.mqseries.net for this error

JMS Delievery Problem

Hi,
After having deployed SP7 we have problems with the delievery of JMS
Messages in a scenario that uses the Sync/Async Bridge with Adapter
Modules.Our receiver ist xy, that offers an Request/Reply
Service with Queues, our Sender is a synchronous Web Service Client via
SOAP Adapter.
The Problem is, the JMS Messages never get delievered to the Request
Queue, so the client receives a Message expired Exception.
On the channel monitoring we see a confusing message that says that the
message was processed but ignored.
Here s the orginal message in German Language:
"XI-Message d5ed86c0-6fb9-11de-8041-00144f805f2a wurde erfolgreich als
JMS-Message mit ID d5ed86c06fb911de804100144f805f2a beim Empfänger
verarbeitet und aus diesem Grund ignoriert."
We set up a trace in receiver system and we can see the message never appears
there.
In the Audit Log of the failed request messages we see the error
message "Unable to read payload from the message object" with the SAP
Category XIServer and the SAP:Code area="MAPPING", which doesn t makes
sense to us, as the message gets transformed succesfully.
The secanrio worked before deploying the Service Pack and we didn t
change anything about the configuration.
Can you anyone give uns infos?
Thanks in advance,
Frank

Hm - I am not very familiar with Tibco, but had also problems after SP upgrades on PI 7.0 and MQ series 6.
I can only suggest to contact Tibco and / or SAP for some support on this issue.
Ours had been solved by a OSS note which had been released.
Regads,
Kai

JMS queue problem integrating with TIBCO

Hi all!
We have several communication channels between XI 3.0 (SP21) and TIBCO via JMS queues. All of them are working fine except one. This problem only happens in development and quality systems with SP21, production has SP17 and doesn't have this error on the same communication channel.
We are getting the following error in communication channel details...
27-03-2008 16:32:21   XI message ID corresponding to the JMS message ID 'ID:EMS-QUALITY.14C46ECF3303EC:61' has the value 'null', with the ID: prefix removed+
27-03-2008 16:32:21   XI message ID corresponding to JMS message with ID 'ID:EMS-QUALITY.14C46ECF3303EC:61' will be created with same value as JMSCorrelationID with value 'null'+
27-03-2008 16:32:20   Error while processing message 'null'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in converting Binary message <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_PedCarga_GE xmlns:ns0="http://pt.galp.is-oil.ec">    <Partner>        <ZIDIF>62</ZIDIF>    </Partner>    <Controle>        <Nr_Envio>29183049</Nr_Envio>        <Dt_envio>20080229</Dt_envio>        <Tipo_Carga>CPAT</Tipo_Carga>        <Operador>230</Operador>    </Controle>    <PedCarga>        <FRETE>            <Tipo_Registo>N</Tipo_Registo>            <Inst_Carreg>ES41</Inst_Carreg>            <Data_Execucao>20080228</Data_Execucao>            <Resp_Transporte>13</Resp_Transporte>            <Transporte>          </Transporte>            <Transportador>1700</Transportador>            <Ref_Externa_head>2008022931859</Ref_Externa_head>            <Gera_Docs>X</Gera_Docs>            <Imprim_Docs>X</Imprim_Docs>            <Imprim_Ordem_Carreg>X</Imprim_Ordem_Carreg>            <Confirm_Autom>X</Confirm_Autom>            <Operador>230</Operador>        </FRETE>        <ENTREGA>            <Tipo_Destinatario>1</Tipo_Destinatario>            <Local_Entrega>14018</Local_Entrega>            <Cod_Produto>GOA []</Cod_Produto>            <Quantidade>05100</Quantidade>            <Ref_Externa_Item>01737307470601</Ref_Externa_Item>            <Regime_Fiscal>N</Regime_Fiscal>        </ENTREGA>        <ENTREGA>            <Tipo_Destinatario>1</Tipo_Destinatario>            <Local_Entrega>14018</Local_Entrega>            <Cod_Produto>GOC []</Cod_Produto>            <Quantidade>13300</Quantidade>            <Ref_Externa_Item>02737307470602</Ref_Externa_Item>            <Regime_Fiscal>R</Regime_Fiscal>        </ENTREGA>    </PedCarga> </ns0:MT_PedCarga_GE> to XI message for message: null: InvalidParamException: Invalid message id: com.sap.guid.GUIDFormatException+
Any clues?
Regards,
Fernando Figueiredo

We changed the conversation ID from Message ID to Correlation ID.

Recent batches 30" with shadow imprint/persistence problems

Recently changed 2!!! displays, and both 30" had the same shadow imprints or what some would call persistence. You do not need to leave the display on for a long time, just on it for about a minute, and set any coloured image on a dark bg, eg dark blue, and later switch to the complete bg which had the same dark blue background, u'll definetly be able to see the imprint or shadow coloured image which u viewed previously, its so obvious u wouldnt miss it.

from wat i understand, it is the vendor thats supplying apple with the "problematic" panels..so the recent batches of the 30" all have the shadow imprint problem, thats why apple is saying that its within specification as they cant reject all the panels from the vendor. Right now i am being in a difficult position as i know i will get back a recent batch with the same problem even if i changed another display.

Persistence problems wit seam/hibernate and EntityHome

This is the scenario(using JBoss Seam 2.2 and JBoss Application Server 5.1.0.):
I've got TestCases and TestSteps. One TestCase has multiple TestSteps. I have a table that displays the steps and actions like "addStep" and "deleteStep".
I use rich:inplaceInput to edit existing steps. This works perfectly.
Adding or deleting a step however does not. When adding, I create an "empty" step which is displayed in the table and the user can then edit it.
I can't explain how it persists changes to existing steps, but doesn't cooperate when list TestCaseHome.testSteps changes in size.
Entity TestStep:
@Entity
@Table(name = "teststeps")
public class TestStep implements java.io.Serializable {
     private static final long serialVersionUID = 6534546556882292702L;
     private long id;
     private TestCase testCase;
     private String test;
     private String expectedResult;
     private long ordering;
     @ManyToOne(fetch = FetchType.LAZY)
     @JoinColumn(name = "tc_id")
     public TestCase getTestCase() {
          return this.testCase;
     public void setTestCase(TestCase testCase) {
          this.testCase = testCase;
}Entity TestCase: Entity CoreTestObject isn't really relevant, TestCase just inherits it's id from it.
@Entity
@Table(name = "testcases")
@PrimaryKeyJoinColumn(name="id")
public class TestCase extends CoreTestObject implements java.io.Serializable{
     private Set<TestStep> testSteps = new HashSet<TestStep>(0);
     public TestCase(Set<TestStep> testSteps, ...) {
          this.testSteps = testSteps;
     @OneToMany(fetch = FetchType.LAZY, mappedBy = "testCase")
     @OrderBy("test")
     public Set<TestStep> getTestSteps() {
          return this.testSteps;
     public void setTestSteps(Set<TestStep> testSteps) {
          this.testSteps = testSteps;
}TestCaseHome:
@Name("testCaseHome")
@Scope(ScopeType.CONVERSATION)
public class TestCaseHome extends EntityHome<TestCase> {
     @DataModel
     private List<TestStep> testSteps;
     /*@param step The Step after which the new Step is to be inserted*/
     public void addStep(TestStep step){
          testSteps = new ArrayList<TestStep>(this.getInstance().getTestSteps());
          long id, ordering;
          [...] // here I find the id and ordering of step
          testSteps.add(new TestStep(id+1, this.getInstance(), "", "", ordering+1));
          this.getInstance().setTestSteps(new HashSet<TestStep>(testSteps));
     /*@param step The Step to be deleted*/
     public void deleteStep(TestStep step){
          int index = testSteps.indexOf(step);
          testSteps.remove(index);
          this.getInstance().setTestSteps(new HashSet<TestStep>(testSteps));
}EntityHome:
public class EntityHome<E> extends Home<EntityManager, E>
   @Transactional
   public String update()
      joinTransaction();
      getEntityManager().flush();
      updatedMessage();
      raiseAfterTransactionSuccessEvent();
      return "updated";
   @Transactional
   public String persist()
      getEntityManager().persist( getInstance() );
      getEntityManager().flush();
      assignId( PersistenceProvider.instance().getId( getInstance(), getEntityManager() ) );
      createdMessage();
      raiseAfterTransactionSuccessEvent();
      return "persisted";
}View:
<rich:dataTable value="#{testCaseHome.testSteps}" var="_testStep"
          id="testStepsTable" rowKeyVar="row" autoresize="true">
     <rich:column sortBy="#{_testStep.ordering}"
          sortOrder="ASCENDING" style=" width : 20px;">
          <f:facet name="header">Order</f:facet>
          <rich:inplaceInput layout="block" value="#{_testStep.ordering}"
               selectOnEdit="true" editEvent="onclick">
               <a:support event="onviewactivated" ajaxSingle="true"
                    reRender="testStepsTable" />
          </rich:inplaceInput>
     </rich:column>
     <rich:column sortBy="#{_testStep.expectedResult}" [...] </rich:column>
     <rich:column sortBy="#{_testStep.test}"> [...] </rich:column>
     <rich:column style=" width : 80px;">
          <f:facet name="header">
               Action
                    </f:facet>
          <a:commandLink ajaxSingle="true" id="deletelink"
               reRender="testStepsTable"
               action="#{testCaseHome.deleteStep(_testStep)}">
               <h:graphicImage value="/img/delete.gif" />
               <f:param name="testCaseId" value="#{testCaseHome.instance.id}" />
               <f:param name="testStepFrom" value="TestCase" />
          </a:commandLink>
          <a:commandLink ajaxSingle="true" id="addlink"
               reRender="testStepsTable"
               action="#{testCaseHome.addStep(_testStep)}">
               <h:graphicImage value="/img/plus_icon.gif" style=" width : 16px; height : 16px;"/>
               <f:param name="testCaseId" value="#{testCaseHome.instance.id}" />
               <f:param name="testStepFrom" value="TestCase" />
               <s:conversationId />     
          </a:commandLink>
     </rich:column>
</rich:dataTable>
<div class="actionButtons">
     <h:commandButton id="save"
          value="Save" action="#{testCaseHome.persist}"
          disabled="#{!testCaseHome.wired}"
          rendered="#{!testCaseHome.managed}" />
     <h:commandButton id="update"
          value="Save" action="#{testCaseHome.update}"
          rendered="#{testCaseHome.managed}" />
</div>I cut a lot from the code, I hope I didn't leave anything relevant out. I also hope this is the right place for this question, excuse me if not (noob here).
I would very much appreciate your help since I'm trying to fix this for weeks. Thank you!

Hello gimbal2,
yes, I initialized the collection by myself now and it works better.
But I think there is a general Problem in the order-Example. The Example isn't implemented as described in the written part of the tutorial and has several other
bugs with persistence in this example.
I've installed the turorial with Update Tool. Is it possible that the samples in the update contain a newer/older version than the code that is described in the PDF?
Thanks,
Johann

Persistence problems

Hello. I have made myself a web app using Java Server Faces which I am running on Glass Fish V2.
The problem that I am having is that while the program complies and runs without throwing any exceptions. My entities are not beeing saved to the database when I call the persist() method on them. The primary key of the entity objects (which is set to auto generate) is updated after the call to persist(), and the sequence database table is also updated. But no data is entered in to the database table for the entity object.
My app reads data from the database that I have inserted via SQL commands by running Queries made in the Java persistencve query lanuage and returns entity objects as you would expect.
Here is the entity object I am trying to save.
@Entity
@NamedQueries({
@NamedQuery(name="getTimeSheetsBetween",
            query="Select ts From TimeSheet ts Where ts.startDate >= :startDate AND ts.endDate <= :endDate"),
@NamedQuery(name="getTimeSheetsFor",
            query="Select ts From TimeSheet ts Where ts.timeSheetUser = :user")})
public class TimeSheet implements Serializable {
    private static final long serialVersionUID = 1L;
    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Long id;
    @ManyToOne
    private TimeSheetUser timeSheetUser;
    @Temporal(TemporalType.DATE)
    private Date startDate;
    @Temporal(TemporalType.DATE)
    private Date endDate;
    private boolean signedOff;
    @OneToMany(cascade=CascadeType.ALL)
    private List<TimeSheetDay> timeSheetDays;
    public TimeSheet(){
    public TimeSheet(TimeSheetUser pUser, Calendar pStartDate, Calendar pSettingsStartDate, int pLength){
        Calendar testEndDate = (GregorianCalendar) pSettingsStartDate.clone();//modifications to objects passed as method parameters are not reverted after the method is finished
        Calendar testStartDate = (GregorianCalendar) pSettingsStartDate.clone();//so we create new date values to change which will not effect the pSettingsStartDate object
        testEndDate.add(Calendar.DAY_OF_MONTH, pLength);
        while(!(pStartDate.after(testStartDate) && pStartDate.before(testEndDate))){
            testStartDate.add(Calendar.DAY_OF_MONTH, pLength);
            testEndDate.add(Calendar.DAY_OF_MONTH, pLength);
        }//not sure if this is the best way to work this out. Refacter later
        startDate = testStartDate.getTime();
        endDate = testEndDate.getTime();
        signedOff = false;
        timeSheetUser = pUser;
        timeSheetDays = new ArrayList(pLength);
        for(int counter = 1; counter <= pLength; counter++){
            TimeSheetDay day = new TimeSheetDay(testStartDate.getTime());
            timeSheetDays.add(day);
            testStartDate.add(Calendar.DATE, 1);
    Here is the method that saves data
package timesheet2;
import java.io.Serializable;
import java.util.Calendar;
import java.util.Date;
import java.util.GregorianCalendar;
import java.util.List;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.persistence.EntityExistsException;
import javax.persistence.EntityManager;
import javax.persistence.Query;
import javax.persistence.EntityManagerFactory;
import javax.persistence.Persistence;
import javax.persistence.PersistenceUnit;
import javax.persistence.TransactionRequiredException;
import timesheet2.entities.PayPeriodSettings;
import timesheet2.entities.TimeSheet;
import timesheet2.entities.TimeSheetUser;
import timesheet2.exceptions.*;
public class DataBaseAccess implements Serializable{
    private static final Logger logger = Logger.getLogger("timeSheet.DataBaseAccess");
    private List<PayPeriodSettings> periodSettings;
    private TimeSheetUser currentUser;
    @PersistenceUnit
    private EntityManagerFactory emf;
    public DataBaseAccess() throws Exception{
        logger.log(Level.INFO, "DBAO being created, timeSheet.DataBaseAccess");
            try{
                emf = Persistence.createEntityManagerFactory("TimeSheet2PU"); //emf is not injected into the object, don't know why.
            catch(Exception e){
                System.out.println("there was a problem with making the em " + e.getMessage());
    public TimeSheet getTimeSheet(TimeSheetUser pUser, Date pDate)throws NoPeriodSettingsFound, UserNotFound{
        EntityManager em;
        List<TimeSheet> userTimeSheets = pUser.getTimeSheets();
        for(TimeSheet ts : userTimeSheets){
            if(pDate.after(ts.getStartDate()) && pDate.before(ts.getEndDate())) return ts;
        //if we get this far the user does not have a time sheet that covers the given date
        Calendar date = new GregorianCalendar();
        date.setTime(pDate);
        PayPeriodSettings settings = getPayPeriodSettings(date);
        TimeSheet timeSheet = new TimeSheet(pUser, date, settings.getSettingsStartDate(), settings.getPeriodLength());
        try{
            em = emf.createEntityManager();
            System.out.println("Time sheet id = " + timeSheet.getId());
            em.persist(timeSheet);
            System.out.println("Time sheet id = " + timeSheet.getId()); //id is updated at this time.
        catch(EntityExistsException e){
            System.out.println("EntityExistsException with persist method call. " + e.getMessage());
        catch(IllegalStateException ise){
            System.out.println("IllegalStateException with persist method call. " + ise.getMessage());
        catch(IllegalArgumentException iae){
            System.out.println("IllegalArgumentException with persist method call. " + iae.getMessage());
        catch(TransactionRequiredException tre){
            System.out.println("TransactionRequiredException with persist method call. " + tre.getMessage());
        catch(Exception e){
            logger.log(Level.INFO,"Exception: DateBaseAccess.getTimeSheet", e);
        pUser.addTimeSheet(timeSheet);
        return timeSheet;
    }

Hi,
We are using JDeveloper 11.1.1.6. We have enabled the MDS on this setup.
Though its working fine with all the defined components , its not working for af:panelsplitter.
Can you please update if MDS is working fine with af:panelsplitter in JDeveloper 11.1.1.6?

Integration Sap PI - JCAPS through JMS queue problem

Hi to all,
we have to send data through Sap PI 7.1 to an application server Sun Seebeyond JCAPS via JNDI JMS.
We created a Simple Java Test Class that sends data to Jcaps Queues using stcms libraries suggested from Sun.
I already tested this code on Eclipse, and it works fine. (Jcaps receive correctly messages sent from Java Class)
Using JMS Communication Channel on Sap PI with same settings used on Java Class (Queue Connection Factory, Initial Context Factory, URL, Queue Name) and deployed the same stcms libraries on PI,
Jcaps doesn't receive any message. In ABAP Monitor and Communication Channel Monitor we don't check any error: infact in CC Monitor a "Succesfully Connected to Queue" is displayed.
During our tests on Java Class, we tried to change CreateQueueSession istruction ( qsession = qcon.createQueueSession( false, javax.jms.Session.CLIENT_ACKNOWLEDGE ));
we checked that any other setting (changing parameters required from Java Method), different from setting just exposed,
messages are not received from Jcaps and we don't have any error during sending operation (like happens in Sap PI).
So correct setting to send message to JCAPS are:
Transacted = False;
acknowledgeMode = CLIENT_ACKNOWLEDGE;
How we can set this parameter in JMS Communication Channel on Sap PI?
If the CC configuration is correct, where we can find the problem and what kind of issue could be? On client side (Sap PI) or on Server side (JCAPS)?
Thanks

In order to set Transacted = false, uncheck "Transactional JMS Session" in the Processing Tab of JMS adapter. Keep in mind that the message delivery is NOT guaranteed in such a scenario. It is recommended to use transactional sessions in JMS scenarios.
The JMS sessions created by JMS adapter are of type "AUTO_ACKNOWLEDGE".
Regards,
TK
Edited by: Sameej T.K. on Oct 20, 2010 10:47 PM

Jms queue problem in 11g

exception trace is comming, while running the project in weblogic, in the project iam using jms queue, i configured the jms server and jms module and connection factory but it is showing these exception
[The selected operation process could not be invoked.
An exception occured while invoking the webservice operation. Please see logs for more details.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: InvalidSecurity : error in processing the WS-Security security header]
can any one please, provide the suggestions

i got the solution for my problem, i just need to add owsm policies to my processs

JMS persistence problem

Similar Messages

Maybe you are looking for