Menu

Problem uploading CPA

John
2014-03-26
2014-04-06
  • John

    John - 2014-03-26

    Hello,
    we have a problem importing a CPA using the EBMS 3.2 upload utility.

    The CPA is used in a Biztalk environment and configured with the Covast adapter and is working ok in that environment.

    We want to migrate Biztalk/Covast to Websphere Message Broker (IBM Integration Bus 9) in combination with the EBMS adapter.

    Mule info:

    Mule ESB and Integration Platform *
    * Version: 3.4.0 Build: c8afb471 *
    * MuleSoft, Inc. *
    * For more information go to http://www.mulesoft.org *
    * *
    * Server started: 4-3-14 9:47 *
    * JDK: 1.7.0_25 (mixed mode) *
    * OS: Windows 2003 - Service Pack 2 (5.2, x86) *

    EBMS Info:

    ebms-adapter-mule3-2.0.0'

    I have setup an environment to test the EBMS Adapter so I can try to load the extisting CPA, but when starting the EBMS adapter it tries to load the CPA file and it gives an error.

    "nl.clockwork.ebms.validation.ValidationException: CPA Conversation Constraints not supported!"

    My question is if this is version related or something else, the cpa was created by "EBV/JustID CPA Creatie Toolkit (SMF 2.0). Website http://www.justid.nl"
    Regards,
    John.

     
  • Edwin Luinstra

    Edwin Luinstra - 2014-03-26

    hello John,

    I just looked at the CPP specs and came to the conclusion that not supporting Conversation Constraints is not an issue for the ebms adapter. So I will remove the check in the next version, which I will probably release this week.

    Till then you can remove the ConversationConstraints Element from the CPA before importing it.

    kind regards,
    Edwin

     
  • John

    John - 2014-03-27

    Hello Edwin,
    ok, thanks for the response.

    I removed the ConversationConstraints but ran in another problem.

    I will post the problem tommorow.

    Regards,
    John.

     
  • John

    John - 2014-03-28

    Hello Edwin,
    I removed the line:
    " <tns:conversationconstraints tns:concurrentconversations="0" tns:invocationlimit="0"> " </tns:conversationconstraints>

    but then there is an other error saying

    Exception stack is:
    1. Data truncation: Data too long for column 'cpa' at row 1 (com.mysql.jdbc.MysqlDataTruncation)
    com.mysql.jdbc.MysqlIO:3607 (null)
    2. PreparedStatementCallback; SQL [insert into cpa (cpa_id,cpa) values (?,?)]; Data truncation: Data too long for column 'cpa' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'cpa' at row 1 (org.springframework.dao.DataIntegrityViolationException)
    org.springframework.jdbc.support.SQLStateSQLExceptionTranslator:101 (null)
    3. org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [insert into cpa (cpa_id,cpa) values (?,?)]; Data truncation: Data too long for column 'cpa' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'cpa' at row 1 (nl.clockwork.ebms.dao.DAOException)
    nl.clockwork.ebms.dao.spring.AbstractEbMSDAO:162 (null)
    4. nl.clockwork.ebms.dao.DAOException: org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [insert into cpa (cpa_id,cpa) values (?,?)]; Data truncation: Data too long for column 'cpa' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'cpa' at row 1 (nl.clockwork.ebms.service.CPAServiceException)
    nl.clockwork.ebms.service.CPAServiceImpl:81 (null)
    5. Component that caused exception is: DefaultJavaComponent{file.cpa.upload.component.29366817}. Message payload is of type: String (org.mule.component.ComponentException)
    org.mule.component.DefaultComponentLifecycleAdapter:352 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html)

    The cpa was used in a MS SQL database and I use a MYSQL database.

    Is there a difference in the table definition?

    Regards,
    John.

     
  • Edwin Luinstra

    Edwin Luinstra - 2014-04-04

    hello John,

    sorry for the late response.

    I just found out that a TEXT field in MySQL only holds 64kb and this will be too less in some (or even most) cases. You can better change all TEXT fields to MEDIUMTEXT or LONGTEXT, as they can hold 16MB and 4GB respectively.

    I will update the MySQL scripts in the next release.

    If you like, you can contact me through Clockwork/Ordina.

    Kind regards,
    Edwin

     
  • John

    John - 2014-04-06

    Hello Edwin,
    ok thanks I will change that and try again.

    If I find any other problem I will do that.

    Kind regards,
    John

     

Log in to post a comment.