I am using schemas generated with WCF-SQL adapter for TypedPolling to get items from database. Multiple items are returned and debatching is performed in the standard XMLReceive pipeline.
I use following configuration to get detaching to work:
Schema root node: Envelope = Yes
TypedPolling node: Body XPath = TypedPolling-TypedPollingResultSet0
TypedPolling-TypedPollingResultSet0 node: Min = 0, Max = 1
TypedPolling-TypedPollingResultSet0-TypedPollingResultSet0 node: Min = 0, Max = unbounded
Inbound map targets TypedPolling-TypedPollingResultSet0-TypedPollingResultSet0 node.
However, I get following warnings during build:
warning BEC1008: Node "TypedPollingResultSet0" - Body XPath property is invalid or references a node that may not exist in the schema.
warning BEC1008: Node "ArrayOfTypedPollingResultSet0" - Body XPath property is invalid or references a node that may not exist in the schema.
Resolution of the warnings above is to set schema root node Root Reference property to TypedPolling:
Schema root node: Root Reference = TypedPolling
However, I get following error message when running:
There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "" URI: "" Reason: The document specification by message type "http://schemas.microsoft.com/sql/2008/05/TypedPolling/SchemaName#TypedPollingResultSet0" failed. Verify the schema deployed properly.
Is it possible to do this scenario right, or do I have to live with warnings during build?
What you saw is essentially normal and expected. It's just a Warning and it technically correct in that TypedPolling and it's ancestors are min=0. You can safely ignore it. You will get many simiar warnings from the Mapper as well.
Because the Schema defines multiple messages, you will have to undo Schema root node.
Again, provided everything otherwise works, ignore the Warnings.
Related
We have tried to evacuate the instance with the "on-shared-storage" option but that parameter is not recognized. Please help me with this issue.
nova evacuate --on-shared-storage <<Instance_UUID>> <<host_name>>
Error:
error: unrecognized arguments: --on-shared-storage
Try 'nova help ' for more information.
According to the Nova release notes, the onSharedStorage option is no longer necessary:
https://github.com/openstack/nova/blob/master/releasenotes/notes/remove-on-shared-storage-flag-from-evacuate-api-76a3d58616479fe9.yaml
#gibizer
gibizer Remove onSharedStorage from evacuate API
Latest commit c01d16e on Nov 10, 2015
History
1 contributor
7 lines (7 sloc) 353 Bytes
---
features:
- Remove ``onSharedStorage`` parameter from server's evacuate action in
microversion 2.14. Nova will automatically detect if the instance is on
shared storage. Also adminPass is removed from the response body which
makes the response body empty. The user can get the password with the
server's os-server-password action.
The fact that your nova client doesn't recognize the option implies that your Nova service's default microversion is later than 2.14.
You could try forcing the microversion, but there doesn't seem to be much point ... based on what the release note says.
(According to the current python-novaclient source code, the --on-shared-storage option is recognized for microversions 2.0 through 2.13. See https://github.com/openstack/python-novaclient/blob/master/novaclient/v2/shell.py)
In the Airflow admin site
When I update the http_default connection the http sensor gives the following error:
ERROR - Could not create Fernet object: Incorrect padding
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/airflow/models.py", line 173, in get_fernet
_fernet = Fernet(fernet_key.encode('utf-8'))
File "/usr/local/lib/python3.6/site-packages/cryptography/fernet.py", line 35, in init
key = base64.urlsafe_b64decode(key)
File "/usr/local/lib/python3.6/base64.py", line 133, in urlsafe_b64decode
return b64decode(s)
File "/usr/local/lib/python3.6/base64.py", line 87, in b64decode
return binascii.a2b_base64(s)
binascii.Error: Incorrect padding
It seems your $FERNET_KEY is not set.
Can you check the output of echo $FERNET_KEY?
Can you also check the fernet_key = entry in your airflow.cfg?
If those are empty, you can generate a new one with some Python code:
from cryptography.fernet import Fernet
print(Fernet.generate_key().decode())
Then set this value in your airflow.cfg under fernet_key =.
Alternatively you can also set it via export AIRFLOW__CORE__FERNET_KEY=your_fernet_key (this gives you more flexibility if you are building your environment dynamically).
Important to keep in mind
The Fernet Key is used to encrypt your connections' credentials, so you need to keep it safe it you want to be able to decrypt them later. If you had created some connections before with another fernet key, and you generated a new one as described above, your old connections won't work and will have to be recreated once you set the new key in place.
We have 2 remote NPM registries inside of a virtual repository. One of them is the NPM Registry, the other one is from a software provider. When I add the second repository to the virtual repository, I am getting HTTP 400 messages at random.
For example: if I want to install a package from the npm-registry, I see through the logs that Artifactory is trying to get the package from the other repository (which does not have the package) and tries to parse the response as json. The response from the other repository gives back a html file though which results in the following error message:
2017-02-23 09:39:05,424 [http-nio-8080-exec-7112] [ERROR]
(o.a.a.n.r.NpmRemoteRepoHandler:362) - Error while parsing the response of a remote npm
JSON query on 'https://repository.domain.com/api/npm/public/file-loader':
Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object,
'true', 'false' or 'null')
at [Source:org.artifactory.storage.db.binstore.service.UsageTrackingBinaryProvider$ReaderTrackingStream#7360bc6c; line: 1, column: 2]
As you can see, Artifactory is trying to get the package from the other repository. The JSON response of our artifactory, when I try to get the package manually is :
{
"errors" : [ {
"status" : 400,
"message" : "Unable to parse remote repository npm metadata."
} ]
}
Any help would be greatly appreciated, since this makes the NPM Registry completely useless as some requests are returning this HTTP 400 error.
fyi: We are using Artifactory Pro 4.5.1
There are 2 things you should do to avoid this behavior
Configure the virtual repository resolution order so the NPM registry is approached before the software provider registry. The resolution order is controlled by the order they are presented in the Selected Repositories list.
Use include/exclude patterns to control which packages are resolved from the software provider registry. Assuming there is a way to identify the packages which should be resolved from software provider you can define patterns which will limit this registry only for the resolution of certain packages.
Another thing to check is whether the software provider remote repository configured properly. Normally it should not return an HTML response for an API call.
When I open NetSim's Config.txt file after Simulation I get the following error:
Error in config file ---
1) Unknown xml tag "UPDATE_TIMER" in line number 166.
Tag path: TETCOS_NETSIM/NETWORK_CONFIGURATION/DEVICE_CONFIGURATION/DEVICE
[3] /LAYER [2]/ROUTING_PROTOCOL/PROTOCOL_PROPERTY
However, Simulation runs Successfully. What does this mean?
You need to specify the missing parameters in the Configuration file which are mentioned in the "ConfigLog.txt". Since, NetSim will crash if all the required parameters are not configured, NetSim addresses this issue by enabling default values where ever required. Error produced in the "ConfigLog.txt" because the value for the "UPDATE_TIMER" for "ROUTING_PROTOCOL" is not specified in the Configuration file. In order to obtain accurate metrics for the desired scenario you need to update your Configuration.xml file.
I am trying to get symfony cmf up and running. After encountering a few problems during install, i'm stuck at this error message:
Catchable fatal error: Argument 1 passed to Symfony\Cmf\Component\Routing\ContentAwareGenerator::getBestLocaleRoute() must be an instance of Symfony\Component\Routing\Route, instance of Doctrine\ODM\PHPCR\Document\Generic given, called in D:\wamp\www\QHCMF\vendor\symfony-cmf\routing\Symfony\Cmf\Component\Routing\ContentAwareGenerator.php on line 86 and defined in D:\wamp\www\QHCMF\vendor\symfony-cmf\routing\Symfony\Cmf\Component\Routing\ContentAwareGenerator.php on line 98
I'm a novice and I have no clue what to make of this. I have looked at the ContentAwareGenerator.php but it was of no help to me.
You get a Generic document when no specific document is at that position in the content repository. PHPCR being a tree, there sometimes are nodes added in between so that a child node can have a parent. Those nodes do not map to any document, in which case the Generic document is used.
If you simply installed the sandbox from git and followed all the steps in order, this should not happen. You first set up the repository, then load the fixtures. If this is what you did, please open an issue at https://github.com/symfony-cmf/cmf-sandbox