| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ICS Error(goes down) |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeevan_p |
 Posted: Fri Apr 07, 2006 1:15 am Post subject: ICS Error(goes down) |
 |
|
Novice
Joined: 02 Mar 2006
Posts: 11
Location: India
|
Hi,
I am using teo jdbc connectors to connect 2 databases of 2 different departments. So that whenever I do some change in dept1 same change should take place in dept2.I have two jdbc connectors and db2 as database. whenver a Business Object is passed from connector1 to connector2 I am actually auditing the message in my collaboration and the database in dept2 is getting updated.
But the ICS server is goind down whenver a message is passed through it saying COLLABOARATION CANNOT DELETE EVENT FROM PERSISTENT STORAGE.
And everytime i have to delete entries from cxbusobjstate table from icsrepos database.
I want to know what is the persistent storage and why the collaboration cannot delete the event from there.
THE ERROR ON ICS LOG IS AS FOLLOWS
2006/04/07 14:25:45.016 Collaboration Error CGXPushbutton icsCo icsCo.thread1 (#1334234984) The server will be shut down because the collaboration cannot delete event ORDERTBL1.Create from persistent storage. Business object keys = ORDERNO=a62.Reason:Event {{1}, DEP1JDBCConnector, 2) could not be registered with the submission manager. Reason: An event state change could not be saved: state = icsCo, connector = DEP1JDBCConnector, eventId = 2. [info]::A JDBC error was encountered during an attempt to execute accessor PBOSWrite. [info]:: (SQLState [23505]:[IBM][CLI Driver][DB2/NT] SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "JIWAN.CXPBUSOBJSTATE" from having duplicate rows for those columns. SQLSTATE=23505 DB specific error:-803) |
|
| Back to top |
|
 |
| emiddleware |
| Posted: Mon Apr 10, 2006 6:14 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi,
if your problem is not solved , can you say what is the verb used in the event table .. is it Create verb mentioned in the event table ??
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| jeevan_p |
| Posted: Mon Apr 10, 2006 9:11 pm Post subject: |
|
|
Novice
Joined: 02 Mar 2006
Posts: 11
Location: India
|
Hi
Problem is not solved . It is failing for Create, Update aswell as delete verbs. Do u have any idea about this persistance storage in ICS.
Its event cannot be deleted from persistent storage. |
|
| Back to top |
|
|
| emiddleware |
| Posted: Tue Apr 11, 2006 10:59 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi Jeevan,
Have you used delivery transport as MQ in the connector config file . I just saw in pdf and pasting it . Let me know if it helps you.
WebSphere MQ and IDL Use WebSphere MQ rather than IDL for event delivery transport, unless you must have only one product. WebSphere MQ offers the following advantages over IDL: v Asynchronous communication: WebSphere MQ allows the application-specific component to poll and persistently store events even when the server is not available. v Server side performance: WebSphere MQ provides faster performance on the server side. In optimized mode, WebSphere MQ stores only the pointer to an event in the repository database, while the actual event remains in the WebSphere MQ queue. This prevents writing potentially large events to the repository database. v Agent side performance: WebSphere MQ provides faster performance on the application-specific component side. Using WebSphere MQ, the connector polling thread picks up an event, places it in the connector queue, then picks up the next event. This is faster than IDL, which requires the connector polling thread to pick up an event, go across the network into the server process, store the event persistently in the repository database, then pick up the next event.JMS The JMS transport mechanism enables communication between the connector and client connector framework using Java Messaging Service (JMS). If you select JMS as the delivery transport, additional JMS properties such as jms.MessageBrokerName, jms.FactoryClassName, jms.Password, and jms.UserName are listed in Connector Configurator. The properties jms.MessageBrokerName and jms.FactoryClassName are required for this transport. There may be a memory limitation if you use the JMS transport mechanism for a connector in the following environment: v AIX 5.0 v WebSphere MQ 5.3.0.1 v ICS is the integration brokerIn this environment, you may experience difficulty starting both the connector controller (on the server side) and the connector (on the client side) due to memory use within the WebSphere MQ client. If your installation uses less than 768MB of process heap size, set the following variable and property: v Set the LDR_CNTRL environment variable in the CWSharedEnv.sh script. 112
Adapter
for
JDBC
User
Guide
Hope it helps you ...
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| emiddleware |
| Posted: Tue Apr 11, 2006 11:53 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi Jeevan,
Have you used delivery transport as MQ in the connector config file . I just saw in pdf and pasting it . Let me know if it helps you.
WebSphere MQ and IDL Use WebSphere MQ rather than IDL for event delivery transport, unless you must have only one product. WebSphere MQ offers the following advantages over IDL: v Asynchronous communication: WebSphere MQ allows the application-specific component to poll and persistently store events even when the server is not available. v Server side performance: WebSphere MQ provides faster performance on the server side. In optimized mode, WebSphere MQ stores only the pointer to an event in the repository database, while the actual event remains in the WebSphere MQ queue. This prevents writing potentially large events to the repository database. v Agent side performance: WebSphere MQ provides faster performance on the application-specific component side. Using WebSphere MQ, the connector polling thread picks up an event, places it in the connector queue, then picks up the next event. This is faster than IDL, which requires the connector polling thread to pick up an event, go across the network into the server process, store the event persistently in the repository database, then pick up the next event.JMS The JMS transport mechanism enables communication between the connector and client connector framework using Java Messaging Service (JMS). If you select JMS as the delivery transport, additional JMS properties such as jms.MessageBrokerName, jms.FactoryClassName, jms.Password, and jms.UserName are listed in Connector Configurator. The properties jms.MessageBrokerName and jms.FactoryClassName are required for this transport. There may be a memory limitation if you use the JMS transport mechanism for a connector in the following environment: v AIX 5.0 v WebSphere MQ 5.3.0.1 v ICS is the integration brokerIn this environment, you may experience difficulty starting both the connector controller (on the server side) and the connector (on the client side) due to memory use within the WebSphere MQ client. If your installation uses less than 768MB of process heap size, set the following variable and property: v Set the LDR_CNTRL environment variable in the CWSharedEnv.sh script. 112
Adapter
for
JDBC
User
Guide
Hope it helps you ...
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| Curry |
| Posted: Thu Apr 13, 2006 6:55 am Post subject: |
|
|
Newbie
Joined: 22 Feb 2006
Posts: 7
|
I'd suggest you contact support in this case. It usually is a bug in the software. In our case, when we got the error, support indicated that there was a flaw in our collaboration design.. which was causing this error. Ended up redesigning the collabs. To give you a background, every event gets written to persistent storate (CxPBusobjstate) table. After succesful collab processing, it gets deleted.. But when the server encounters a problem issuing a delete (2 events with the same key, etc), then the server will crash.
Another idea would be to set the DB_Tracing to 5 and check the exact sql statement that gets issued when the server crashes. This might give you some more insight.
Problem is not solved . It is failing for Create, Update aswell as delete verbs. Do u have any idea about this persistance storage in ICS.
Its event cannot be deleted from persistent storage.[/quote] |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
