After adding a destination(Queue) to Destination Resources from Admin Console at Resources/JMS Resources/Destination Resources, no physical destinations are displayed at server(Admin Server)/JMS Physical Destinations .Instead, the following error message is displayed below the heading:
An error has occured
Unable to list JMS Destinations
Also, on trying to add a new Physical Destination at server(Admin Server)/JMS Physical Destinations, of type 'Queue', following error message is displayed:
An error has occured
Unable to create JMS Destination
On trying to add a Physical Destination using asadmin in command-line as:
asadmin> create-jmsdest -T queue DemoQueue
the following error is displayed:
remote failure: Unable to create JMS Destination.
Command create-jmsdest failed.
Here, GlassFish Server Open Source Edition 3.1-b24 is run on Ubuntu with kernel 2.6.28-11-server.
Any help is appreciated.
I don't think that you should create physical destinations manually. All you need to do to set up JMS resources in GlassFish is defining a connection factory and destinations - all under Resources - JMS resources branch in admin interface. When your destinations are used physical destinations will be created automatically.
confused me to no end first time so I sympathise
For GFv2.1.1 (and I suspect for v3) a physical destination - mq.sys.dmq - is already created and configured and queues are created here. The messaging server is SunMQ and if it is your intention to use this out-of-the-box then you don't need to create another physical destination.
if you do indeed need to create another physical destination launch [path-to-glassfish]/imq/bin/imqadmin.exe (or ubuntu equiv) and do it there.
Related
While creating destination to my hana system. I face the error 'Backend is not available in the list of defined system mappings in Cloud connector' in the connection test.
The connection in cloud connector is reachable. I read through blogs, the virtual and internal address doesn't mismatch. the url doesn't have any '_', but still I face the error. Any leads to this kind of issue?
Thanks
Issue is resolved by deleting the location id in the destination settings
From Linux server with MQ client installed we are trying to set up connection to secured channel. I am ETL person and our MQ admin is struggling. Anyways I will explain what I tried (which obviously hasn't worked yet ) and anyone please let me know what else needs to be done to set up the connectivity.. Thanks :)
tmp/mqmutility/keyrepmodmq> ls
AMQCLCHL.TAB key.kdb key.rdb key.sth MODE_MODELTAP_DEV_keyStLst.txt
export MQSSLKEYR=/tmp/mqmutility/keyrepmodmq/key
export MQCHLLIB=/tmp/mqmutility/keyrepmodmq
export MQCHLTAB=AMQCLCHL.TAB
/opt/mqm/samp/bin> amqsputc <queue_name> <queue_manager_name>
Sample AMQSPUT0 start
MQCONN ended with reason code 2058
Note: I can connect to the same queue manager for a non-SSL channel.
Any help will be great and other approaches you follow for SSL channel connectivity from client machine will also be helpful.
When using a Client Channel Definition Table (CCDT) file - your AMQCLCHL.TAB file, a return code of 2058 usually means that the queue manager name the application tried to use - your 'queue_manager_name' - was not found in any of the channel entries in the CCDT file.
If you're using. MQ V8 you can very easily display the entries in your CCDT file and the queue manager names they are configured for using the following command:
runmqsc -n
DISPLAY CHANNEL(*) QMNAME
If none of the channels in your file have the queue manager name you are using when running the amqsputc sample then this is the cause of your 2058 reason code.
Hopefully it will be clear when you see the entries in the file listed out which queue manager name you should be using, but if not, update your question with some more details (like the contents of said file and the queue manager details) and we can help further.
You must ensure that you have a CLNTCONN channel defined which has the queue manager name you want to use in the QMNAME field, and that you have a matching named SVRCONN channel defined on the queue manager. Since you are using SSL, you must also ensure that these two channels are using the same SSLCIPH.
Please read Creating server-connection and client-connection definitions on the server and it's child topics.
I am trying OO on a RHEL Atomic Host. I spun up OO master as a container following this guide https://docs.openshift.org/latest/getting_started/administrators.html
After attaching a shell to the Master Container, I cannot deploy an app.
# oc new-app openshift/deployment-example
error: can't look up Docker image "openshift/deployment-example": Internal error occurred: Get https://registry-1.docker.io/v2/: net/htt p: request canceled while waiting for connection error: no match for "openshift/deployment-example"
The 'oc new-app' command will match arguments to the following types:
1. Images tagged into image streams in the current project or the 'openshift' project
- if you don't specify a tag, we'll add ':latest'
2. Images in the Docker Hub, on remote registries, or on the local Docker engine
3. Templates in the current project or the 'openshift' project
4. Git repository URLs or local paths that point to Git repositories
--allow-missing-images can be used to point to an image that does not exist yet.
See 'oc new-app -h' for examples.
The host needs proxy to access Internet. I have configured proxy in /etc/sysconfig/docker and that is how I could pull the origin image in the same place.
I have tried setting proxy for master and node with luck
https://docs.openshift.org/latest/install_config/http_proxies.html
It is possible that your proxy is terminating the connection. you can test by creating an internal registry, push image to that and then use
"oc new-app your.internal.registry/openshift/deployment-example"
We are continuously getting this error:
2014-11-06 07:05:34,460 [main ] INFO SharedFileLocker - Database activemq-data/localhost/KahaDB/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: Failed to create directory 'activemq-data/localhost/KahaDB'
We have verified that activemq is running as activemq, we have verified that the owner of the directories are activemq. It will not create the directories automatically, and if we create them ourselves, it still gives the same error. The service starts fine, but it will just continuously spit out the same error. There is no lock file as it will not generate any files or directories.
Another way to fix this problem, in one step, is to create the missing symbolic link in /usr/share/activemq/. The permissions are already set properly on /var/cache/activemq/data/, but it seems the activemq RPM is not creating the symbolic link to that location as it should. The symbolic link should be as follows: /usr/share/activemq/activemq-data -> /var/cache/activemq/data/. After creating the symbolic link, restart the activemq service and the issue will be resolved.
I was able to resolve this by the following:
ensure activemq is owner and has access to /var/log/activemq and all sub dirs.
ensure /etc/init.d/activemq has: ACTIVEMQ_CONFIGS="/etc/sysconfig/activemq"
create file activemq in /etc/sysconfig if it doesnt exist.
add this line: ACTIVEMQ_DATA="/var/log/activemq/activemq-data/localhost/KahaDB"
The problem was that activeMQ 5.9.x was using /usr/share/activemq as its KahaDB location.
I'm attempting to call a Stored proc, get some data back, map that to the desired schema, output the result.
However, I'm getting the following error:
The Messaging engine failed to process a message submitted by
adapter:WCF-SQL Source
URL:mssql://master-biztalk//ReportServer?InboundId=batman. Details:The
published message could not be routed because no subscribers were
found. This error occurs if the subscribing orchestration or send port
has not been enlisted, or if some of the message properties necessary
for subscription evaluation have not been promoted. Please use the
Biztalk Administration console to troubleshoot this failure.
I'm not quite certain why I'm getting this error. Searching the web hasn't enlightened me any further. Following are some of the steps I've undertaken
Consume adapter = generated schema.
Map this schema to desired output.
Receive port in the Orchestration which connects to a receive message which has the Schema generated by the consume adapter as the type.
Added a receive port in Biztalk, configured WCF-SQL and setup bindings. (Typed polling)
Linked this receive port to the logical receive port in orchestration.
I haven't promoted any elements in messages.
Thanks for the help
EDIT: I updated the pipeline to XML, and now I'm getting the following error:
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: "DatabaseReceiveport" URI:
"mssql://master-biztalk//ReportServer?InboundId=batman" Reason:
Finding the document specification by message type
"http://schemas.microsoft.com/Sql/2008/05/TypedPolling/batman#TypedPolling"
failed. Verify the schema deployed properly.
I'm not quite sure what it's trying to do above.
This means that either:
The Project/Assembly with the specified Schema has not been deployed.
The WCF SQL configuration is off somehow, frequently the InBoundId parameter. That's where "batman" would come from.
In the All Artifacts Application, check the Schemas folder for that Schema by Root Node and Namespace.