Frequently Asked Questions

Categories


X

java.lang.IllegalStateException: zip file closed using MapForce service

 

Question

I uploaded a new MapForce zip file. Now I see some java.lang.IllegalStateException: zip file closed messages in my logging.

Answer

This problem is a known issue and has to do with some class overloading in the system. There is probably nothing wrong with your mappings, just restart the ConnectAgent.

If the problem consists, please contact the ConnectPlaza servicedesk.

X

(S)FTP(S) troubleshoot checklist

 

Question

I'm having connection problems while trying to connect with a FTP server

Answer

This document describes a checklist to solve common FTP connectivity problems for the  following components:

Consumer:

FTP Pickup See more documentation

Service:

FTP Command Service See more documentation

FTP Sender See more documentation

Producer:

FTP Upload See more documentation

If any problems occur with your (s)FTP(s) sessions within any of these ConnectPlaza components please use this checklist for troubleshooting.

  1. Check if the server Hostname is correct
  2. Check if the server Port number is correct
  3. Check if the connection protocol (FTP Type) is correct.
    You can choose between FTP (insecure), SFTP (SSH) or FTPS (secure FTP)
  4. Check if you use the correct encryption when using FTPS. You can choose either explicit over TLS (default) or implicit over TLS. Note that this option is only available when using a secure FTP connection protocol (FTPS).
  5. Check whether the transfer mode to the server should be Active or Passive
  6. Check what Charset / Encoding the server expects (Default UTF-8)
  7. Check whether the File Type of the server is either ASCII, Binary or EBCDIC
X

ActiveMQ Memory limit is full

 

Question

When I check the log file of the connectAgent, i see the message:

activemq.broker.region.Queue - Usage Manager Memory Limit is full

Answer

Your internal memory reserved for an ActiveMQ queue not enough for the current amount of messages. This is a flooding mechanism of ActiveMQ, a kind of flow controle. 

Stop the connector (NOT THE AGENT!!) which is flooding the system and you will see that the messages will be consumed. 

 

If you encounter this problem again, check the ActiveMQ memory settings. 

X

Cannot login into Analyze. Password is correct

 

Question

Cannot login into Analyze. Password is correct

Answer

It is possible that the connection to the backend is not correctly defined in you configuration file. Check the connection parameters of the file analyze.properties in the conf.global.php file in the config directory of Analyze.

Check if the connection URL for the backend, is the same as the connnection URL as configured in the connectAgent configuration. Open the file connectagent.properties in the conf directory of you connectAgent:

connect.jetty.sslconnector.host=10.1.0.184
connect.jetty.connector.host=10.1.0.184
connect.jetty.sslconnector.port=8443
connect.jetty.connector.port=8088

The portnumber and IP address must be entered in the configuration file of analyze:

$configparam["jsonopdionconnector"]["analyze"]["url"] = "https://10.1.0.184:8443/analyze/";
$configparam["jsonopdionconnector"]["security"]["url"] = "http://10.1.0.184:8088/securitybackend/"; 

The most common mistake is to enter the localhost instead of the IP address of FQDN.

X

Cannot read from Windows share

 

Question

When I start my connectAgent as a service in my Windows environment, I cannot read from some of the shares I have created. I checked this with my administrator account and there seems to be no problems at all.

Answer

Your connectAgent service is default installed as a local system user. This user must have the rights to use the shared directories.

X

ConnectAgent 3.3.0 Installation issue

Valid after version 3.3.0-RELEASE

Question

Deploy does not install the latest version of my interface. Got the error message:

Atrribute 'description' is not allowd to appear in element 'myesb.adapter'.

Answer

This is a known issue. The easiest way to solve this is to upgrade to ConnectAgent 3.3.0 (or higher).

 

X

ConnectAgent crashed immediately

 

Question

I start the ConnectAgent via ./runAgent.sh (or .bat) and the agent immediately crashed and stopped working. There is only a wrapper-updater.log file. In this logfile we see the error:

java.lang.UnsupportedClassVersionError: com/opdion/myesb/connect/wrapper/MyESBUpdateWrapper : Unsupported major.minor version 52.0

The java version seems to be ok. 

Answer

The message of the java version is the message you get from the first wrapper. The problem is often a different java version for the other wrapper, which is of a lower version. Check this and restart the agent. 

For test purposes start the agent with the standAlone version, i.e. \bat\connect-standalone\connect-agent.bat (or for Linux /bin/connect-standalone/connect-agent.sh

X

Connectivity errors when starting the ConnectAgent

Valid after version 3.1.0-RELEASE

Question

When I start a connectAgent, the agent seems to start wel. But after 15 seconds I got a server 500 error message.

Answer

Check if you are running Java 1.8.0_66 or higher version on your machine. The prefered version at time of writing is java 1.8.0_121

X

Deploy returns strange view. Dynamic values are not changable anymore

Valid after version 3.4.0-RELEASE

Question

Deploy returns strange view. Dynamic values are not changable anymore.

Answer

This is due to an incompatability between the backend in 3.4.0 and higer and the connectAgents version 3.3.x. The only thing you can do is upgrade to ConnectAgent 3.4.0. Then this issue should be solved.

X

Error after deploying interface returns error

 

Question

After changing the interface name I deployed my interface, but I got errors like this:

.13:19:04.967 [AdapterContextStarter-demoscripting] WARN  c.opdion.myesb.agent.AdapterContext - AdapterContext start aborted.
.13:19:04.971 [AdapterContextStarter-demoscripting] ERROR c.opdion.myesb.agent.AdapterContext - Reason: Error creating bean with name 'org.springframework.integration.handler.MessageHandlerChain#1': 

Error creating bean with name 'org.springframework.integration.config.FilterFactoryBean#5469dff4': 
Cannot resolve reference to bean 'Script1.HTMLChannel' while setting bean property 'discardChannel'; No bean named 'Script1.HTMLChannel' is defined

 

Answer

The problem could be that the selected property is not changed after the change of the name of the interface. . 

X

Error message Caused by: org.springframework.messaging.MessagingException: nested exception is java.lang.Exception: OpenEdge Procedure did not return any value

Valid after version 3.5.0-RELEASE

Question

With the upgrade to version 3.5.6 we get the message OpenEdge Procedure did not return any value. We did not change this interface. What does this error mean?

Answer

This error is introduced in the version 3.5.6. In the previous versions the called procedure can return a Null as an anser to your request. This result in hanging threads in our agent, because an answer is expected. As of version 3.5.6, the client catches this problem and thows an exception.

The best way to solve this 'issue', is to always return an answer to the calling procedure.

X

Error message in Analyze screen: No connection to the backend. Please check the agent and try again.

Valid after version 3.3.0-RELEASE

Question

When I select the tab Analyze ik see the messae No connection to the backend. Please check the agent and try again. in my screen.

Answer

When you have a valid license for analyze, but the Back-end Adapter is not yet installed, you will get this error message. You can check this in your agents installation directory. Search in the adapters directory for the file ConnectPlaza Analyze Backend Adapter (of the Mongo variant). If this Interface is not yet installed, contact ConnectPlaza to correct this issue.

X

File Pattern with a wild card does not work

Valid after version 3.1.1-RELEASE

Question

A file with a name structured like: Weborder-1234567890.xml is not be picked up with a File Pattern structured like Weborder-* on Windows machines.

Answer

Windows does not recognize file extensions as part of a file name. And now we specifically pick up only files with the File Consumer, this becomes important when using a File Pattern in your File Consumer. Please make sure that you explicitly include both the file name and the file extension in the File Pattern when you are deploying the particular Interface to a Windows machine.

This example illustrates this issue:

The file Weborder-1234567890.xml will not be picked up with the File Pattern Weborder-* on Windows machines. Instead you should use one of the following options: Weborder-*.xml or Weborder-*.* 

Please note that this is only necesarry if you deploy your Interface to a Windows machine.

X

File pickup returns file not found exception after succesfull pickup

 

Question

I have a file pickup consumer which is picking up files to be processed. I use the Solid File Check Time at 10000. File is being picked up, but I see in the logfile the error:

 ERROR o.s.i.handler.LoggingHandler - org.springframework.integration.transformer.MessageTransformationException: Failed to transform Message; nested exception is org.springframework.messaging.MessagingException: failed to transform File Message; nested exception is java.io.FileNotFoundException: E:\data\connectplaza\input\notfound.log.xml (The system cannot find the file specified)
        at org.springframework.integration.transformer.MessageTransformingHandler.handleRequestMessage(MessageTransformingHandler.java:95)
        at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:99)
        at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:127)
        at org.springframework.integration.handler.MessageHandlerChain$1.send(MessageHandlerChain.java:123)
        at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:115)
        at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:45)
        at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:105)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.sendOutput(AbstractMessageProducingHandler.java:231)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.produceOutput(AbstractMessageProducingHandler.java:154)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.sendOutputs(AbstractMessageProducingHandler.java:102)
        at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:105)
        at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:127)
        at org.springframework.integration.handler.MessageHandlerChain$1.send(MessageHandlerChain.java:123)
        at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:115)
        at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:45)
        at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:105)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.sendOutput(AbstractMessageProducingHandler.java:231)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.produceOutput(AbstractMessageProducingHandler.java:154)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.sendOutputs(AbstractMessageProducingHandler.java:102)
        at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:105)
        at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:127)
        at org.springframework.integration.handler.MessageHandlerChain$1.send(MessageHandlerChain.java:123)
        at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:115)
        at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:45)
        at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:105)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.sendOutput(AbstractMessageProducingHandler.java:231)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.produceOutput(AbstractMessageProducingHandler.java:154)
        at org.springframework.integration.handler.AbstractMessageProducingHandler.sendOutputs(AbstractMessageProducingHandler.java:102)
        at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:105)
        at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:127)
        at org.springframework.integration.handler.MessageHandlerChain.handleMessageInternal(MessageHandlerChain.java:104)
        at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:127)
        at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:116)
        at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:147)
        at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:120)
        at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77)
        at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:442)
        at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:392)
        at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:115)
        at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:45)
        at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:105)
        at org.springframework.integration.endpoint.SourcePollingChannelAdapter.handleMessage(SourcePollingChannelAdapter.java:161)
        at org.springframework.integration.endpoint.AbstractPollingEndpoint.doPoll(AbstractPollingEndpoint.java:251)
        at org.springframework.integration.endpoint.AbstractPollingEndpoint.access$000(AbstractPollingEndpoint.java:57)
        at org.springframework.integration.endpoint.AbstractPollingEndpoint$1.call(AbstractPollingEndpoint.java:176)
        at org.springframework.integration.endpoint.AbstractPollingEndpoint$1.call(AbstractPollingEndpoint.java:173)
        at org.springframework.integration.endpoint.AbstractPollingEndpoint$Poller$1.run(AbstractPollingEndpoint.java:330)
        at org.springframework.integration.util.ErrorHandlingTaskExecutor$1.run(ErrorHandlingTaskExecutor.java:55)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: org.springframework.messaging.MessagingException: failed to transform File Message; nested exception is java.io.FileNotFoundException: E:\data\connectplaza\input\notfound.log.xml (The system cannot find the file specified)
        at org.springframework.integration.file.transformer.AbstractFilePayloadTransformer.transform(AbstractFilePayloadTransformer.java:100)
        at org.springframework.integration.transformer.MessageTransformingHandler.handleRequestMessage(MessageTransformingHandler.java:89)
        ... 50 more
Caused by: java.io.FileNotFoundException: E:\data\connectplaza\input\notfound.log.xml (The system cannot find the file specified)
        at java.io.FileInputStream.open0(Native Method)
        at java.io.FileInputStream.open(Unknown Source)
        at java.io.FileInputStream.<init>(Unknown Source)
        at com.opdion.myesb.connect.transformer.FileToConnectMessageTransformer.transformFile(FileToConnectMessageTransformer.java:57)
        at com.opdion.myesb.connect.transformer.FileToConnectMessageTransformer.transformFile(FileToConnectMessageTransformer.java:17)
        at org.springframework.integration.file.transformer.AbstractFilePayloadTransformer.transform(AbstractFilePayloadTransformer.java:87)
        ... 51 more

Answer

The problem is triggered by the high value of the Solid File Check Time. The file is beinig picked up correctly, but there are more than one trackers, checking the file growing in size. Because of this, the file can be removed while a tracker is checking the file.

You can ignore this message.

X

FileNotFound exception when map found in file pickup directory

 

Question

When you have a map in you file pickup directory and you collect all the files in the lower directory, you will get a java.io.FileNotFoundException because it will try to read the map as a file name.

Answer

When you have a map in you file pickup directory and you collect all the files in the lower directory, you will get a java.io.FileNotFoundException because it will try to read the map as a file name.

You can solve this to enter a *.txt instead of a * , or use a regex expression.

X

FileReader service does not read the XML file

 

Question

The FileReader service  does not read the XML file recieved from another service. There are no errors in the log files or in Analyze.

Answer

The problem is within the FileReader service. The file must be specified as an URI. file:/path/file.extention

You must also specify the output type as TEXT, because otherwise .CSV files will be parsed. 

X

FTP Connection problems

 

Question

I see in the logfile an exception when I try to use FTP to send a file to another server.

java.net.NoRouteToHostException: No route to host

Answer

Your FTP Server cannot be reached from the server the connectAgent is installed on. 

Check if you can connect to this FTP server by hand from the server the connectAgent is installed on. For instance, use a telnet connection to check if you can connect to this FTP server.

 

X

Heapsize continues to grow

 

Question

Heapsize continues to grow

Answer

You can have more memory set to your JVM proces than needed. Try to reduce your total heap size. The GC should now be running more frequently, resulting in a lesser heap size.

X

How do I deal with XML Documents in UTF-8 encoding containing Byte Order Markers?

 

Question

How do I deal with XML Documents in UTF-8 encoding containing Byte Order Markers?

Answer

You can avoid issues with Byte Order Markers on UTF-8 encoded XML Documents by adding an Encoding Converter Service to your flow and setting both the source encoding as well as the target encoding to UTF-8. This will result in the removal of the Byte Order Marker.

X

I can login into analyze, but I do not get any data

 

Question

I can login into analyze, but I do not get any data

Answer

After version 3.x the backend connector must be connected secure. In the configuration directory of analyze, check the file conf.global.php. Overwrite the selected paramter with the next rule:

$configparam["jsonopdionconnector"]["analyze"]["url"] =  "https://test.connectplaza.com:8443/analyze/";
X

I got errors on a message which looks the same as another message which returns no errors.

 

Question

I got errors on a message which looks the same as another message which returns no errors. If you check the files with Notepad the files look identical.

Answer

We see a lot of issues like this with UTF-8 encoding and bytes in messages that only appear in a HEX editor.

A simple solution to this problem is a message converter, which converts the message from UTF-8 to UTF-8. This removes all bytes which can interfere with the transaction.

You can also, if you use a pickup mechanism, but the type at DOCUMENT. If there are problems with the read document, you get an error instantly.

X

I see a lot of Out of Memory and Heap space errors in my logfiles

 

Question

I see a lot of Out of Memory and Heap space errors in my logfiles

Answer

OutOfMemroy means there is insufficient memory allocated for the running JVM to do its job. You need to allocate more memrory to the JVM.

Default the connectAgent has 1,2 GB maximum heapspace allocated. This is the part of memory where the java objects are stored. This should be sufficient for most systems. If there are OutOfMemory issues you can check with JConsole of VisualVM where the problems occur. A ConnectAgent system must have at least 4 GB of memeory on board.

Problem situations where processes parse large XML files can trigger this behaviour as well. Parsing (DOM) of XML documents in Java can lead to exceptional memory usage. We see this problem occur when XML files are bigger than 10 MB.

X

I want to read a file without an extention

Valid after version 3.2.0-RELEASE

Question

I want to read only files without an extention. How do I do that?

Answer

At the file pattern field you are allowed to use REGEX expressions.

Use for instance the expression:

^([^.]+)$
X

Interface does not seem to work anymore. Without reason or logging the messages are gone.

 

Question

It looks like the interface is consuming the data, but after that nothing is happening anymore. No logs are produced, no messages are produced, no analyze messages are written or logged.

Answer

One of the problems could be that the following settings could be to low:

connect.taskexecutor.poolsize=25
connect.taskscheduler.poolsize=50

The numbers could be different in your case.

Check this using the Jconsole tool, follow this link here

 

X

Interface is not removed after renaming interface

 

Question

After renaming my interface, the old interface is not removed.

Answer

When deploying the new interace, the connectAgent will remove the old interface with the same name. But because the name of the interface has changed, the connectAgent cannot find an interface with the same name.

You have to remove the old .jar yourself in the adapters directory of the connectAgent installation.

X

IP address is wrong in the License check file

 

Question

The licenselog returnes an IP address which is not the current running address.

Answer

Check in your conf directory the file connectplaza-agent.properties. In this file you will find an entry called: connect.network.interfacename.

Uncheck this value and enter the network adapter name. Restart the agent and all should be ok.

 

X

Java exception during startup of ConnectAgent

 

Question

When I start a connectAgent I see the following error in my logfile:

Exception in org.rzo.yajsw.controller.jvm.JVMController: testAgent.connectplaza.local: testAgent.connectplaza.local: unknown error
  java.net.InetAddress.getLocalHost(InetAddress.java:1484)
  org.rzo.yajsw.controller.jvm.ControllerPipelineFactory.initChannel(ControllerPipelineFactory.java:91)
  org.rzo.yajsw.controller.jvm.ControllerPipelineFactory.initChannel(ControllerPipelineFactory.java:36)
  io.netty.channel.ChannelInitializer.channelRegistered(ChannelInitializer.java:68)
  io.netty.channel.AbstractChannelHandlerContext.invokeChannelRegistered(AbstractChannelHandlerContext.java:143)
  io.netty.channel.AbstractChannelHandlerContext.fireChannelRegistered(AbstractChannelHandlerContext.java:129)
  io.netty.channel.DefaultChannelPipeline.fireChannelRegistered(DefaultChannelPipeline.java:733)
  io.netty.channel.AbstractChannel$AbstractUnsafe.register0(AbstractChannel.java:450)
  io.netty.channel.AbstractChannel$AbstractUnsafe.access$100(AbstractChannel.java:378)
  io.netty.channel.AbstractChannel$AbstractUnsafe$1.run(AbstractChannel.java:424)
  io.netty.channel.ThreadPerChannelEventLoop.run(ThreadPerChannelEventLoop.java:52)
  io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
  java.lang.Thread.run(Thread.java:745)
  Caused by: testAgent.connectplaza.local: unknown error

Answer

When you see this error check if your 'Hostname' is defined in you host file on your specific system.

If the hostname mentioned in the error is not defined in your host file, but another name is, just add the hostname to the host file and all will be fine.

X

JVM Binding error when starting ConnectAgent

 

Question

When starting my ConnectAgent, it stops with the error:

18-09-05 10:37:33|8668/1|INFO|Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.opdion.myesb.connect.handler.MyESBNotificationPublishingMessageHandler#0': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serverConnectorJMXRM' defined in class path resource [META-INF/spring/applicationContext.xml]: Invocation of init method failed; nested exception is java.net.BindException: Cannot assign requested address: JVM_Bind

The agent keeps restarting itself.

Answer

In your connectplaza-agent.properties file there is a setting like this:

connect.mbean.server.connector.url=service\:jmx\:jmxmp\://10.1.0.9\:9876

This setting is incorrect. Remove this line from your property file and start the agent again

The correct line should be:

connect.mbean.server.connector.url=service:jmx:jmxmp://localhost:9876

X

Mapforce with multiple inputfiles

 

Question

When working with Mapforce and multiple input files within the connectAgent, the outcome is different from the outcome via Mapforce itself.

Answer

If you read from multiple input files check within the generated software that the order of the files to read. This could differ from the way they are arranged on screen in Mapforce.

This issue could lead to a different outcome.

X

Message cannot be parsed or problems with parsing messages in mappings

 

Question

When processing messages it is possible that you get a parsing error. When looking into your XML file, nothing seems to be wrong.

Caused by: com.altova.SourceInstanceUnavailableException: cannot parse input stream.
                at com.altova.xml.XmlTreeOperations.loadDocument(XmlTreeOperations.java:71)
                at com.altova.xml.XmlTreeOperations.loadDocument(XmlTreeOperations.java:39)
                at com.mapforce.MappingMapToweborder.run(MappingMapToweborder.java:898)
                ... 81 common frames omitted
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
                at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
                at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
                at com.altova.xml.XmlTreeOperations.loadDocument(XmlTreeOperations.java:66)
                ... 83 common frames omitted

When saving the message in notepad, the message suddenly checks out and there are nor problems...

WHat is going on?

Answer

When you get inexplicable messages like this, your XML file probably has a BOM. A BOM or Byte Order Marker is a special marker added at the very beginning of an Unicode file encoded in UTF-8, UTF-16 or UTF-32.It is used to indicate whether the file uses the big-endian or little-endian byte order. The BOM is mandatory for UTF-16 and UTF-32, but it is optional for UTF-8.

The problem with a BOM is, that it is not visible in an ASCII editor, but you can detect it in a HEX editor.

The byte order mark is likely to be one of these byte sequences:

UTF-8 BOM   : ef bb bf 
UTF-16BE BOM: fe ff 
UTF-16LE BOM: ff fe 
UTF-32BE BOM: 00 00 fe ff 
UTF-32LE BOM: ff fe 00 00

ConnectPlaza does not like the BOM and you can get rid of it by using the Encoding Converter service, converting the message from, for instance, UTF-8 to UTF-8. This will remove the BOM from the file.

Keep in mind that some applications require a BOM.

X

New updates are not delivered on my ConnectAgent

Valid after version 3.5.0-RELEASE

Question

When using deploy on my system, it tells me that all is up to date, but in deploy I cannot update my interface due incompatability with the current running agent.

Answer

When updating you connect a server at ConnectPlaza to download the update files. Check in your conf/ directory the file connectplaza-agent.properties file. Check the entry: connect.cloudserver.uri. There must be the value https://backend.connectplaza.com.

Restart the agent afterwards. If all is wel the update file will be downloaded in the temp/update folder of your installation.

X

No connection to deploy. Agent is running.

 

Question

No connection to deploy. Agent is running.

Answer

Your connection is created with an RHTTP connection. The connection to this RHTTP connection fails. Normaly the RHTTP server reconnects automatically, but in some cases it fails.

The reason is unknown, and is still under investigation.

If you experience this problem, restart the connectAgent.

X

Reading an Excel (XLSX) file with MapForce

 

Question

When I try to read an Excel file, I'm getting the following error message:

Caused by: java.lang.Exception: XLSX can be read from the stream
	at com.altova.xml.XLSXFileReader.(XLSXFileReader.java:68)
	at com.mapforce.MappingMapToweborder.run(MappingMapToweborder.java:2122)
	... 81 more

Answer

If you want to perform a transformation of an Excel file (xlsx), that is possible, but the file should be read in as BYTES, not as TEXT. You can choose how to read in the file in your Consumer Component, for instance the File Consumer.

X

Rename interface does not remove bundle at Agent

 

Question

When uploading a bundle of a renamed interface, the old bundle is not removed.

Answer

When you rename an  interface it's name changes. The .jar file, which is created is not the same as before, so the Deploy application cannot know what it's previous name was, therefor cannot delete the old bundle.

If you encounter this problem, manually delete the old .jar file from the ./adapters directory in your ConnectAgent installation and restart your agent. The problem should be resolved.

X

Root certificate errors when accessing a SSL related site

 

Question

When accessing a SSL releated site I get certificate errors on the root CA certificate. The certificate chain is loaded, so the root certificate should be available.

Answer

As of version 8.0_131 Certificates using SHA1 or MD5 are not permitted anymore by JAVA . This certificates are ignored and therefore none existent, resulting in the Certificate Chain Error.

X

Special characters in MapForce

 

Question

A german account has a lot of special characters like  ß, ö, Ü etc. Those characters are replace by ? within the ESB output. The encoding in MapForce is set to UTF-8. Other mappings are ok, but they are not .csv files. 

Answer

Set the default encoding of ConnectPlaza to UTF-8. All strings will be interpreted by default as UTF-8.

Set the next parameter in the wrapper.conf of the wrapper from the connectAgent. 

wrapper.java.additional.9 = -Dfile.encoding=UTF-8 

!! the number 9 is a sequense number. Change accordingly to you environment. 

Restart the agent to activate this change.