Error Queue Problem

Hi,
          I have defined an error queue for a given queue. The problem is that
          the error queue doesn't get any messages when there is an error, etc.
          For example (WebLogic configuration for the queue1) -
          Error Destination: errorqueue8.
          Time To Live Override: 20000.
          I want the messages in the queue1 to be transferred to errorqueue8
          when the time-to-live expires. But this doesn't happen!
          Does anyone know whats wrong? Am I doing something wrong with the
          configurations?
          I am using WebLogic 7.
          Thanks in Advance.

Good timing!
          WebLogic 8.1, which is out in restricted beta at the moment, and
          will be out in public beta "soon", has this extension. You can
          configure a WebLogic 8.1 destination to redirect expired messages
          to an error destination. Prior versions of WebLogic do not
          have this extensions.
          Tom, BEA
          mal wrote:
          > Thanks for the answer!
          >
          > So what if I want to send the undilivered messages, for a given time,
          > to go to another queue (without them getting lost)? Is there a way
          > that I can do it within WebLogic 7? Or should I program for it in the
          > application?
          >
          > Thanks,
          >
          >
          > "Bart Simpson" <[email protected]> wrote in message news:<3e445c0c$[email protected]>...
          >
          >>Hi,
          >>
          >>How are you doing? If the TTL expires the messages are lost. So, WLS is behaving
          >>as expected.
          >>
          >>Error destination makes sense for redelivery of messages that have already been
          >>redelivered so many times...
          >>
          >>Best regards,
          >>-Bart Simpson
          >

Similar Messages

Problem Configuring JMS Error Queue

Domain configuration : one adminServer, One cluster, 2 managedservers in cluster
Two distibuted Queues: InboundQueue, Error Queue
I want to redirect any bad message from InboundQueue to ErrorQueue and discard it.
It worked fine for 4 yrs in Wls 8.1 ( did configured in 8.1)..
now i upgrde to wls 10.1 and i did same configuration but InboundQueue is not redirecting to Errorqueue..
Dont know where i am missing..
here is the config.xml entry and jms/JmModule.xml files..
config.xml entry_
<jms-system-resource>
<name>JmsModule</name>
<target>cluster1</target>
<sub-deployment>
<name>subdeployment1</name>
<target>JmsServer1,JmsServer2</target>
</sub-deployment>
<descriptor-file-name>jms/JmsModule-jms.xml</descriptor-file-name>
</jms-system-resource>
JmsModule.xml_
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<uniform-distributed-queue name="ErrorQueue">
<sub-deployment-name>subdeployment1</sub-deployment-name>
<delivery-params-overrides>
<delivery-mode>Non-Persistent</delivery-mode>
<time-to-deliver>-1</time-to-deliver>
<time-to-live>-1</time-to-live>
<priority>-1</priority>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>0</redelivery-limit>
</delivery-failure-params>
<jndi-name>ErrorQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
</uniform-distributed-queue>
<uniform-distributed-queue name="InboundQueue">
<sub-deployment-name>subdeployment1</sub-deployment-name>
<delivery-params-overrides>
<delivery-mode>Persistent</delivery-mode>
<time-to-deliver>10</time-to-deliver>
<time-to-live>10</time-to-live>
<priority>2</priority>
<redelivery-delay>10</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<error-destination>ErrorQueue</error-destination>
<redelivery-limit>1</redelivery-limit>
<expiration-policy>Redirect</expiration-policy>
</delivery-failure-params>
<jndi-name>InboundQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>10</forward-delay>
</uniform-distributed-queue>
</weblogic-jms>
Any help
Thanks
ksr

Are you still having a problem? If so, I recommend trying to simplify the reproducer by removing the "time-to-deliver", "redelivery-delay", and "time-to-live" settings.
<time-to-deliver>10</time-to-deliver>
<time-to-live>10</time-to-live>
<redelivery-delay>10</redelivery-delay>
Note that these are all set to a very small value (10 milliseconds), and that the message will expire before it can be delivered or redelivered. The delivery delay is 10 millis, so by the time the delivery delay completes, the time-to-live will have passed -- furthermore, if there was no delivery delay, the redelivery delay is at 10 millis -- so by the time the redel occurs the time-to-live expires).
Tom

Messages are not moving to Error Queue in OSB if Error is Raised

Hi All,
My OSB process is as below.
Queue1-->OSB-->Queue2.
OSB Proxy is listening to the Queue1.When messages comes to Queue1 Proxy will pick the message and after applying the business logic it will put the message to Queue2.
If OSB is not able to deliver the message succesfully to Queue2 then it should retry for 2 times.If retry exhausted then the message should move to the error Queue.
I have configured Queue 1 with delivery failure paramaters redelivery limit and redelivery delay.Also the Connection factory is XA enabled.Even if any error happens (i am not using reply activity in the error handler) its retrying infinitely and messages are not coming to the error Queue.If i use reply activity its not retrying its failing at first time and the message is moved out of the main Queue1.
Can any one please help me on this?
Thanks.
Edited by: 892479 on Dec 21, 2011 6:31 AM

Since the messages are getting retried, it means that messages are getting rolled back to Queue1 when any errors happen. So transactional behavior is configured correctly.
Now the problem yu face is that the messages are not moving to error queue.
Make sure that you have configured following in the delivery failure tab of the queue>
Redelivery Delay Override - delay in miliseconds between retries
Redelivery Limit - number of retries
Expiration Policy - Redirect
Error Destination - Choose the error queue here
After that make sure that the Server is restarted, even though a server restart sign is not mentioned on the config page, some of these settings might not take effect without a restart.

SAP HANA D3 Library errors - "queue" is not a function

Hello all,
i have a question regarding D3 Integration into SAP HANA and hope one can help me.
The last days i developed a D3 Choropleth (spatial data) with hover effects, tooltips and a legend. I have an existing SAPUI5 and HANA XS application running and now i wanted to integrate my D3 Choropleth.
1 ) First of all, i added the following tags into the head section of the index.html file of my SAPUI5 project as i need those libaries.
<script type="text/javascript" src="http://d3js.org/d3.v3.min.js"></script>
<script type="text/javascript" src="http://d3js.org/queue.v1.min.js"></script>
<script type="text/javascript" src="http://d3js.org/topojson.v1.min.js"></script>
2) Then, i added the program code of my D3 Choropleth into the view.js of my SAPUI5 project:
var html2 = new sap.ui.core.HTML("d3choropleth", {
                content: "<div class='D3Choropleth'>" + "</div>",
                preferDOM: false,
                afterRendering: function() {
                              .... here is my code ...
I have a SAPUI5 shell with different NavigationItems (tabs) and for this D3 Choropleth tab i am writing:
case "WI_choropleth":
oShell.setContent(html2);
break;
When i start my SAPUI5 project and klick on the tab where the D3 Choropleth should be rendered, i get the following errors:
d3.scale.threshold is not a function
d3.geo.albers center is not a function
queue is not a function
Moreover, i have to say that my D3 Choropleth works standalone outside HANA very well, that is why i assume it is a library integration issue.
In my browsers (firefox) developer console i can see that there is a D3 library loaded by default (as it is one of SAPUI5s components) with the path: sap/ui5/1/resources/sap/ui/thirdparty/D3.js.
BUT this is a really old version of D3 (2.9), the current release is D3 (3.4), so maybe the problem is that the D3 libary that is loaded by default overwrites my integration of D3 (script tag above)?
Does anyone have the same issues and knows how to solve that? Furthermore it seems that the d3 queue library is also not integrated as the error "queue is not a function" occurs and i also ask me how to solve that error.
We have SAP HANA Developer Edition Revision 80 (by AWS), HANA Studio and Client are on revision 73 (64bit).
It would be great if anyone could help me with my issue.
Further question: Is the current release of D3 going to be integrated into the next HANA revision?
Thanks a lot & regards,
Andreas

Hi Andreas,
You are right. The way you integrate the libraries in your code is not the way that will work for HANA XS projects. This is why it doesn't accept the queue function (library is not loaded) and also why the 3.x only D3JS funcitons are not accepted (only the internal D3JS library is loading and these functions were not a part of 2.9 yet).
To integrate third party libraries, you need to add XSJSLIB files to your project. These need to pass the server-side JSLint checks before accepted by the XS engine. (Client-side checks that fail might not count though).
Please see this post from David Brookler for more information.
http://scn.sap.com/community/developer-center/hana/blog/2013/12/23/db001-using-libraries-in-xs
Best regards,
Tobias

Move to error queue after certain redelivery limit

Hi,
          I am newbie to Weblogic. I am currently using Weblogic8.1.4.
          I have written an MDB say mdbx which listens on a specific queue say QA, once it receives a message it will send this message to another queue QB. I have configured the queue QA such that it will try to redeliver the message 3 times to QB, if it fails in its first attempt. I have also configured an error queue to which the message should finally be placed when all the 3 attempts fails.
          My problem is, i find the redelivery limit and error queue i have configured for queue QA doesn't take effect. Please help me to resolve this.
          More Info:
          I am trying to send message from mdbx on the onMessage() method.
          Thanks and Regards
          A.SathishKumar

Please refer : http://www.javaoracleblog.com/java/How_to_set_minimumDelayBetweenMessages_for_delay_between_messages_for_JCA_adapters.jsf

Distributed Destinations and Error Queues

          I have a distributed queue - distqueue which is configured with two queue members
          - srvr1q
          and srvr2q. srvr1q is a physical queue destination that is running on JMSServer1
          on one instance in a cluster. srvr2q is a physical queue destination that is running
          on JMSServer2 on another instance in the cluster. I have two errorqueues - srvr1errq
          and srvr2errq - deployed on JMSServer1 and JMSServer2 respectively. I have configured
          the srvr1q to the following:
          Redelivery Delay Override: 10000
          Redelivery Limit: 3
          Error Destination: srvr1errq
          Also the srvr2q is configured to the following:
          Redelivery Delay Override: 10000
          Redelivery Limit: 3
          Error Destination: srvr2errq
          There is an MDB listening to each one of these local queues. The MDB is programmed
          to throw a null pointer exception (to simulate business logic processing failures)
          My expectations are : the message goes to one of the local queues. Null Pointer
          exception is thrown. After 10 seconds the message is resent to the same queue
          with a similar fate. After the third attempt, the message is moved to the error
          queue of the corresponding local queue.
          What I see is the following:
          When I send a message I do see a Null Pointer Exception, but it occurs only once
          and I dont see the message going to the error queue. Since my Load Balancing policy
          is Round-Robin on the distqueue, the local queues receive the message every other
          time with the same result - Null Pointer Exception thrown only once.
          I also have JMSStores configured so the messages are persistent.
          Can someone explain to me what I am doing wrong?
          Thanks.


          "Prakash Muthukrishnan" <[email protected]> wrote:
          >
          >Hi Tom
          > Thanks again for the reply. I do use a tx MDB. I have set the transaction-type
          >to Container in the message-driven stanza in ejb-jar.xml. And also the
          >trans-attribute
          >for that EJB in the container-transaction stanza, I have used Required.
          >Do I need
          >to setup anything else ?
          I don't think so.
          > The transaction descriptor element in the weblogic-enterprise-bean
          >stanza in weblogic-ejb-jar.xml for that MDB is empty.
          Not sure what you mean?
          > Am I missing anything
          >else?
          Container & Required is all that is needed
          If you like, post your ejb descriptor xml file, and I'll take a quick
          look to double-check.
          >-Prakash
          >
          >Tom Barnes <[email protected]> wrote:
          >>Hi Prakash,
          >>
          >>A runtime exception should force a rollback for tx MDBs, and
          >>a recover for non-tx MDBs. If you are seeing different
          >>behavior there may be a bug in WL.
          >>
          >>Since MDBs do not log an exception when the app throws
          >>a Runtime exception, I often recommend wrapping the
          >>application code in a try catch anyhow
          >> try {
          >> } catch (Throwable t) {
          >> log
          >> force rollback
          >> }
          >>I think there are plans to provide a configurable that
          >>optionally does something similar in the next release (no guarantees).
          >>(The problem is that some apps throw a runtime on purpose, and
          >>could quickly flood the log if such runtimes were logged per message.)
          >>
          >>Tom
          >>
          >>Prakash Muthukrishnan wrote:
          >>> Tom
          >>> Thanks for the suggestion. Using the setRollbackOnly method did the
          >>trick. This
          >>> brings up
          >>> a related question: What if a run time exception was thrown during
          >>the processing
          >>> in an MDB?
          >>> Is it not retried and ultimately shoved into the error queue?
          >>> Thanks again.
          >>> -Prakash
          >>>
          >>>
          >>> Tom Barnes <[email protected]> wrote:
          >>>
          >>>>Hi Prakash,
          >>>>
          >>>>At first glance, it doesn't seem like your doing anything wrong.
          >>>>Could you post your release and SP level, as well as your config.xml?
          >>>>
          >>>>How many messages did you send through?
          >>>>
          >>>>Note that for transactional MDBs it is best to call "setRollbackOnly"
          >>>>on the EJB context rather than throwing an NPE. This is because
          >>>>throwing a runtime exception forces the MDB to destroy itself and
          >>>>get re-initialized (pretty high overhead). For non-transactional
          >>>>MDBs, throwing a runtime exception is your only option.
          >>>>
          >>>>Tom, BEA
          >>>>
          >>>>Prakash Muthukrishnan wrote:
          >>>>
          >>>>
          >>>>>I have a distributed queue - distqueue which is configured with two
          >>>>
          >>>>queue members
          >>>>
          >>>>>- srvr1q
          >>>>>and srvr2q. srvr1q is a physical queue destination that is running
          >>>>
          >>>>on JMSServer1
          >>>>
          >>>>>on one instance in a cluster. srvr2q is a physical queue destination
          >>>>
          >>>>that is running
          >>>>
          >>>>>on JMSServer2 on another instance in the cluster. I have two errorqueues
          >>>>
          >>>>- srvr1errq
          >>>>
          >>>>>and srvr2errq - deployed on JMSServer1 and JMSServer2 respectively.
          >>>>
          >>>>I have configured
          >>>>
          >>>>>the srvr1q to the following:
          >>>>>
          >>>>>Redelivery Delay Override: 10000
          >>>>>Redelivery Limit: 3
          >>>>>Error Destination: srvr1errq
          >>>>>
          >>>>>Also the srvr2q is configured to the following:
          >>>>>Redelivery Delay Override: 10000
          >>>>>Redelivery Limit: 3
          >>>>>Error Destination: srvr2errq
          >>>>>
          >>>>>There is an MDB listening to each one of these local queues. The
          >MDB
          >>>>
          >>>>is programmed
          >>>>
          >>>>>to throw a null pointer exception (to simulate business logic processing
          >>>>
          >>>>failures)
          >>>>
          >>>>>My expectations are : the message goes to one of the local queues.
          >>>>
          >>>>Null Pointer
          >>>>
          >>>>>exception is thrown. After 10 seconds the message is resent to the
          >>>>
          >>>>same queue
          >>>>
          >>>>>with a similar fate. After the third attempt, the message is moved
          >>>>
          >>>>to the error
          >>>>
          >>>>>queue of the corresponding local queue.
          >>>>>
          >>>>>What I see is the following:
          >>>>>When I send a message I do see a Null Pointer Exception, but it occurs
          >>>>
          >>>>only once
          >>>>
          >>>>>and I dont see the message going to the error queue. Since my Load
          >>>>
          >>>>Balancing policy
          >>>>
          >>>>>is Round-Robin on the distqueue, the local queues receive the message
          >>>>
          >>>>every other
          >>>>
          >>>>>time with the same result - Null Pointer Exception thrown only once.
          >>>>>
          >>>>>I also have JMSStores configured so the messages are persistent.
          >>>>>
          >>>>>Can someone explain to me what I am doing wrong?
          >>>>>Thanks.
          >>>>
          >>>
          >>
          >

OEM takes Lot of time to show Error Queue

I have configured Multi-Master Advanced Replication for 3 master sites (Using Oracle Enterprise Edition 9.2.0.1.0 on MS Windows2K). But I have observed a problem during this week that the size of SYSTEM tablespace has been growing rapidly. After further analysis it was observed that a major portion of the tablespace is covered by DEF$_AQCALL. It has nearly 21,763,626 rows on master definition site and increasing day by day while there are just less that 6650,400 rows in participating other master sites. Due to this larger size when I try to observe the Error Queue using OEM, It takes more than 45 minutes to just show the Errors transactions list. Please have a look on the following script, I have run:-
SQL> select count(*) from def$_aqcall;
COUNT(*)
21763626
SQL> select count(*) from deferror;
COUNT(*)
3
SQL> select count(*) from deftrandest;
COUNT(*)
1466
Transactions are being propagated normally. But If I have to see the Error Queue to check the error transactions for possible data conflicts, it takes a long time. I have moved this table to USERS tablespace and then move again to SYSTEM tablespace but alas its size doesn't vary. Can I truncate this table i.e. DEF$_AQCALL. As its size is going to be bigger and bigger due to increasing number of rows in it. what should I do ?
Thanks
Masood

You should read the documentation for multimaster replication because mulitimater replication between two databases is easy but the replication between more then two databases required complete knowledge and strong understanding of oracle server working as well as replication concept. If you not create replication between more then two database with proper considration then it will create a very big overhead on the server and situation which you already mention.
Moreover create Replication with API rather then GUI tools. it will includes more option to create replication environment.

Getting the error " [java] Problem invoking WLST - java.lang.RuntimeException: Could not find the OffLine WLST class " while building the O2A 2.1.0 PIP

Getting the error " [java] Problem invoking WLST - java.lang.RuntimeException: Could not find the OffLine WLST class " while building the O2A 2.1.0 PIP. I am using the Design Studio 4.3.2 for building the O2A 2.1.0 PIP. Please let me know how to resolve this issue. Here I am enclosing the log file .

We have basically the same issue when we try to create the interpreter using the embedded method..
I was able to use the interpreter embedded in a java client as long as the weblogic jars were located in a weblogic install if I tried to use them from a maven repository no luck at all...
All of this worked easily in 9.2 now in 10.3 it seems more error prone and less documented.
I have seen close to a 100 posts on issues related to this so is there a document which outlines specifics....
We / I have used weblogic now for almost 10 years and moving from 8.1 to 9.2 was painful and we expected the move from 9.2 to 10.3 not to be soo bad but its proving to be as painful if not more painful than moving to 9.2. We seem to spend a good bit of our time working around issues in the next new release that were not in the previous one..
Any help would be appreciated I think we will open a support case but even that is more painful...
Any help would be greatly appreciated..
PS: We confirmed that all jars in the startweblogic classpath were in the startup. The server we have the embedded wlst instance is a managed server and we are using the component in a war... Are there any restrictions which we are unaware of.
Error we get is
1 [ERROR] com.tfn.autex.order.weblogic.QueueMaintenanceUtility.addQueue():217 Error Adding Queue wowsers JNDI Name wowsers Exception: Invocation Target exception while getting the WLSTOffLineScript path

WebLogic JMS error queue

Hello. I have problem after sending message to JMS queue. Message by log file sending is success. But Message don't put to queue and put to error queue.
Message don't put to queue in 25 % cases.
Speak please, what can be reasons what message put to error queue ?

give me please need section link.
I closing the sender, session and connection in method destroy();
That class, That is EJB:
@Stateless(name = "BeanName", mappedName = "ejb.un.BeanName")
@Local(BeanLocal.class)
public class BeanName implements ReleaserLocal {
@PreDestroy
public void destroy() {
try {
jmsSender.close();
} catch (Exception ex) {
try {
jmsSession.close();
} catch (Exception ex) {
try {
jmsConnection.close();
} catch (Exception ex) {
private void sendMessage(String payload, String channel, long qId){
try {
jmsSender.send(message);
if (log.isDebugEnabled()) {
log.debug("message SEND");
I running this app from depployed in weblogic.

Datasynchronisation: Error Queue message conflict detected.

Any idea what the cause of error queue message "conflict detected" could mean?
It happens with a dml operation update, version 207 for one date field.
If i go to record details there seems to be no records and there is the message:
* Field names inside <> are primary key fileds.
Any one got this problem before?

press HELP at error queue page :)
Synchronization conflicts are resolved by the MGP using the relevant conflict rules. All modifications are applied to the server tables and the transaction is committed. If the conflict rule is "Server Wins", then an error queue record with the message CONFLICT DETECTED is also generated to let you know that a conflict occurred and this rule was applied. A conflict that is resolved by the conflict rules is not rolled back. You can choose to override the conflict resolution performed by modifying the error queue record for a conflict and re-executing the transaction.
A Mobile Server synchronization conflict occurs if:
The client and the server update the same row. This error is resolved by the Mobile Server by the conflict rules, but is logged in the error queue for you to see the result. You can choose to modify the result.
The client and server create rows with the same primary key values. This error is resolved by the Mobile Server, but is logged in the error queue for you to see the result. You can choose to modify the result.
The client deletes the same row that the server updates. This error is resolved by the Mobile Server, but is logged in the error queue for you to see the result. You can choose to modify the result.

Error queues

I am looking to build an error handling service that will process the contents of an error queue. At present, TMQFORWARD is configured to forward the messages into the 'Read from Queue' service. I would assume that the TMQFORWARD can be re-configured to also forward messages from the error queue to the error handling service. From my understanding of it, the '-q' command line option in the 'CLOPT' can be used to specify the names of one or more queues/services for the forwarding of messages. I understand that messages are then sent to a server providing a service whose name matches the queue name from which the message is read. Is it the case that by adding both service names to the '-q' option and ensuring that the relevant service and queue names match, that the TMQFORWARD will be able to forward messages from the correct queue to the correct service? Thanks, dsmith78

Seems reasonable because errorQ is also one common queue. However, the
potential problem is if the error handling service has any problem, it will
make TMQFORWARD redequeue to the error Q which may lead loop which should be
handled correctly.
/Bruce
<Derek Smith> wrote in message news:[email protected]..
I am looking to build an error handling service that will process thecontents of an error queue. At present, TMQFORWARD is configured to forward
the messages into the 'Read from Queue' service. I would assume that the
TMQFORWARD can be re-configured to also forward messages from the error
queue to the error handling service. From my understanding of it, the '-q'
command line option in the 'CLOPT' can be used to specify the names of one
or more queues/services for the forwarding of messages. I understan
d that messages are then sent to a server providing a service whose namematches the queue name from which the message is read. Is it the case that
by adding both service names to the '-q' option and ensuring that the
relevant service and queue names match, that the TMQFORWARD will be able to
forward messages from the correct queue to the correct service? Thanks,
dsmith78

OWA error: A problem occurred while you were trying to use your mailbox (Exchannge 2010 SP3)

Hi!
I have several mailboxes that are was moved from Exchange 2007 to Exchange 2010.
Sometimes occurs a problem: in OWA may appears error "A problem occurred while you were trying to use your mailbox" when selecting interface elements (such as "Options", "Public Folders",
"Reminders"). After this error user cannot access to mailbox through OWA during 10 minutes. The error "A problem occurred while you were trying to use your mailbox" appears in top of browser window on any computers. This behavior is manifested
in any browser, but it can not be associated with any particular event.
Access to mailbox through Outlook or through mobile devices (ActiveSync) continues to work fine in this time.
The errors in Application log on Client Access Server is absent (including error with EventID 9646). ExBPA is not showing anything specific to that error message. Test of OWA connectivity working successfully.
In the logs of IIS finded records:
2014-08-26 09:23:01 172.16.0.31 GET /owa/ &ex=UE:Microsoft.Exchange.Data.Storage.TooManyObjectsOpenedException 443 DOMAIN\username 172.16.4.218 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.1;+WOW64;+Trident/5.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0;+InfoPath.3;+.NET4.0C;+.NET4.0E;+.NET+CLR+1.1.4322;+MS-RTC+LM+8)
200 0 0 31
Someone faced with such issue?
Have ideas to solve the issue?

Hi,
Event 9646 occurs if a MAPI client opens more than the default value. You can follow the steps below for troubleshooting:
1. Run regedit, and then click OK.
2. Expand the following registry subkey:
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
3. Right-click ParametersSystem, point to New, and then click Key.
4. Type MaxObjsPerMapiSession, and then press ENTER to name the new subkey.
5. Right-click MaxObjsPerMapiSession, click New, and then click DWORD Value.
6. Type Object_type, and then press ENTER to name the object.
Note: Object_type is the name of the object type in the error message that is mentioned in the "Symptoms" section.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

How to configure a error queue for weblogic jms topic

Hi guys.
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration Policy: Redirect
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
Any suggestions for this topic? Can anyone provide some helps or any useful links.
Thanks in advance.
Mingzhuang

Mingzhuang
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
Let me know if we are not on same page.
Cheers
Manoj

I am not able to open iCloud from pc, error is "problem with the server". what should I do?

I am not able to open iCloud from pc, error is "problem with the server". what should I do?

Go to Settings>General>Restrictions>Accounts (near the bottom) and set this to Allow Changes. You will then be able to access Settings>iCloud again.

Error logging problem:

error logging problem:
I would like to implement an error logger that will do the following tasks when a error/exception arrises:
- surpress the DacfErrorPopupLogger
- alert the user that an error has occured with a simplified popup (create a global listener then use the ErrorAttributes to create the text of the popup)
- log the error in a file with a timestamp and all error information
- later if the above works....i would like to add the error attributes (time stamp, error type) to a oracle object/ Jdev domain.
Questions:
What is the best technique to use....errorManager, error logger ...?? combination
How do i use the error manager to register listners for the errors?.
In the following code i am not sure how to access the ErrorsAttributes[] array that is returned by loggerReader.getErrors();
Any general tips places to find sample code on errorManager or associated interfaces, will be appreciated
I used the OutPutStreamLogger to write error information to a FileOutputStream then a loggerReader to get the error attributes from the file. The reason i went in this direction is because i found some smple code on the outputStream logger.
package DACVideo;
import oracle.dacf.util.errorloggers.*;
import oracle.dacf.util.errormanager.*;
import oracle.dacf.util.errorloggers.InputStreamLoggerReader.ErrorAttributes;
import java.io.*;
* A Class class.
* <P>
* @author Adam Maddox
public class ErrorLogger extends Object {
static OutputStreamLogger logger = null;
static InputStreamLoggerReader loggerReader = null;
public ErrorLogger() {
System.out.println("==============ErrorLogger Created==============");
//remove default error logger (popup logger)
ErrorManager.removeErrorLogger(ErrorManager.findLoggerByName(DacfErrorPopupLogger.NAME));
try
logger = new OutputStreamLogger(new FileOutputStream("out.dat"));
loggerReader = new InputStreamLoggerReader(new FileInputStream("out.dat"));
catch(java.io.IOException e)
System.err.println("Error!");
try
ErrorManager.addErrorLogger(logger);
catch(NameAlreadyRegisteredException e)
System.err.println("A Logger with this name is already registered.");
private void closeErrorLog()
//close the OutputStream, to force flushing
logger.closeOutputStream();
ErrorManager.removeErrorLogger(logger);
public static void showErrorLog()
ErrorAttributes[] errorArray = loggerReader.getErrors(); <<<<CANNOT GET ERROR ATTRIBUTES ??
null

JDev could you help??

Error Queue Problem

Similar Messages

Maybe you are looking for