IBM Worklight server not working after update 6.3. The error states Server MobileFirst Development Server failed to start.
Any thoughts about this error? Added a image for reference.
On console, i am getting the error
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
Transport already in use: could you have an old copy of the server still running. Unless I can spot the process and kill it I'd restart my machine.
Related
I am new to rabbitmq and would appreciate help in the issue I am facing.
I have deployed rabbitmq using the rabbitmq cluster k8s operator on openshift which is hosted on Azure. (This is the guide I referred to deploy the operator).
The operator and cluster is up and running, also able to access the management UI on localhost:15672.
But when I describe the pod, it shows the warning of readiness probe failed:
dial tcp <IP>:5672 connect: connection refused
Due to this, when I try to run the rabbitmq hello world tutorial, it fails with the error:
connect ETIMEDOUT 172.30.69.51:5672
errno: -4039
code: 'ETIMEDOUT'
syscall:'connect'
address: 172.30.69.51
port:5672
(172.30.69.51 is the clusterIP)
From the management UI, I am able to create new exchange, queue and binding and send & publish msgs.
PS. apologies if the conversation format is incorrect, pls feel free to correct me and I'll take care from next time. Thank you.
I want to delpoy the Execution Server in follwing environment:
Wildfly17.0.0.Final
JVM memory, min:64m, max:1024m
Execution Server WAR package: kie-server-7.22.0.Final-ee7.war
A message shows in deployment page of Wildfly's HAL Management Console:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"kie-server-7.22.0.Final-ee7.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"kie-server-7.22.0.Final-ee7.war\"
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
can someone help? thanks in advance!
It seems that you started WildFly with default standalone profile. However Kie server requires standalone-full profile as it uses JMS queues.
Please try to start WildFly with standalone-full profile. For linux based system you can achieve that using command:
./standalone.sh -c standalone-full.xml
After starting one server in a cluster we are getting below error while other node is working fine
Runtime synchronization failed (No constructor has a #ConstructorProperties for this set of items: [action, createdTime, downloadLink, message, multiLanguageMessagesJSON])
Server MobileFirst 7.1
Please advice ?
Such an error may happen because the faulty server may be missing the correct level of an iFix, unlike the rest of the servers in the cluster, or an iFix that was "partially" installed, i.e. it is missing the correct JEE .jar or the admin .war files.
I'm GlassFish 3.1.2, ActiveMQ 5.1.1 and ActiveMQ 5.8 resource adapter (activemq-rar-5.1.1) I have created a GlassFish cluster with 2 instances. I reference http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/ to assist with the initial deployment/configuration of activemq resource adapter After configuring the Connector Connection Pool via GlassFish Admin Console and enable Ping. When Ping is executed an error occurs: Ping Connection Pool for jms/ActiveMQConnectionFactory is Failed. Ping failed Exception - This pool is not registered with the runtime environment : jms/ActiveMQConnectionFactory Please check the server.log for more details. Ping failed Exception - This pool is not registered with the runtime environment : jms/ActiveMQConnectionFactory Please check the server.log for more details.
appreciate for your replay
by any chance is your glassfish instance in a cluster?. In our case it was failing with the same error message, and we figured out that if the instance is in a cluster, it doesn´t work. Though it works if it is not in a cluster.
We verified this also by checking in the activemq admin console the the consumers were active and receiving message, even if the ping command was failing.
I am getting the following error trying to communicate from WCF -> WCF across the internet with a SSL certificate. I have 'No authentication required' checked in the WS-AT configuration on the server.
After a few seconds I'm getting the following message on my client, and trying to figure out what is wrong in my configuration (or understanding of WS-AT).
The flowed transaction could not be
unmarshaled. The following exception
occurred: The WS-AtomicTransaction
protocol service could not unmarshal
the flowed transaction. The following
exception occured: A fault reply with
code CoordinatorRegistrationFailed was
received. The fault reason follows:
The WS-AT protocol service failed to
register with its coordinator. A
connection could not be established.
Looking at the log file on the server I find a link to http://msdn.microsoft.com/en-us/library/aa702582(VS.90).aspx and the following trace message
Microsoft.Transactions.TransactionBridge.RegistrationCoordinatorFailed
Traced if the local TransactionManager is not able to
Register with its superior
TransactionManager due to the
inability to send a message.
So I'm wondering... is the server attempting to communicate with the client through a different channel to the SSL connection originally established by the client. I'm pretty sure thats what it's trying to do for me to end up with this message. The client is my laptop (currently in Starbucks) so there's no chance of any incoming connections.
So is it possible to use WS-AT transactions where only the server has an open firewall? Assuming it is possible - what do i have to do to allow for it? I'm finding very little information about necessary configuration - even in my massive Programming WCF book .
Bonus: Here's a few small tips for anyone trying to get WS-AT working :
If when trying to install the WS-AT tab you can't get it to appear - and you're running an x64 operating system - make sure you're using the x64 version of RegAsm.exe:
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe /codebase wsatui.dll
If once installing WS-AT, configuring it for incoming connections and restarting MCAT you still get errors about the protocol being disabled you may have forgotton to restart IIS(!)