Exception starting server on MICO - exception

I've made server and client using mico, but by trying to start server with
./server –ORBInitRef NameService=corbaloc::localhost:12456
I get this:
uncaught MICO exception: IDL:omg.org/CORBA/ORB/InvalidName:1.0
Problem seems to be with NameService.

Related

Moodle: Installation failed - Coding Error Detected

I have tried to install Moodle 3.5.1 on my development server (Apache 2.4.29 and MySQL v.5.7).
The installation process went smoothly: The MySQL database has been set up, all required PHP packages are installed, the system has been successfully installed, all file permissions are correct.
After the installation I only get the following error:
"Coding error detected, it must be fixed by a programmer: PHP catchable fatal error"
There are no further error messages. There are no error messages in Apache Error log or PHP log files. In the PHP ini file the display of error messages is activated.
So I can not figure out what did not work or how to fix it.
Put error_reporting(E_ALL); and ini_set('display_errors', 1); in the beggining of the script you see problem in for more debug info
Moodle 3.5 requires PHP 7
https://docs.moodle.org/35/en/PHP
Could that be your problem?

Class 'DebugBarFilter' not found in cakephp3 for server

My client project is working in localhost environment but in client server, it is giving the following fatal error:
Error: Class 'DebugBarFilter' not found
File /home/pantaid8/public_html/vendor/cakephp/debug_kit/config/bootstrap.php
Line: 2
yes code is in 21 line but message is coming same what I mentioned.

Error building server: An error occurred while resigning test.apk

Whenever i try to run the following command:
java -jar selendroid-standalone-0.15.0-with-dependencies.jar -app test.apk
I get the following error:
io.selendroid.standalone.SelendroidLauncher launchServer
SEVERE: Error building server: An error occurred while resigning the app 'test.apk'.
Exception in thread "main" io.selendroid.server.common.exceptions.SessionNotCreatedException: An error occurred while resigning the app 'test.apk'.
The same question has been posted earlier.
Kindly respond if anyone has the solution to it.
Thanks.
System requirements on the selenroid website:
Java SDK (minimum 1.6) must be installed and JAVA_HOME configured. IMPORTANT: If JAVA_HOME is pointing to a Java runtime environment, selendroid will produce errors because tools like the jarsigner are not available!

Calling createEntityManager in CORBA program causes exception: org.omg.CORBA.OBJECT_NOT_EXIST

I have a CORBA client-server program that is working perfectly. The client can get a servant and call methods remotely.
I would now like to make the server interact with a database using JPA. However everything goes wrong when I add this one line to the server code:
emf.createEntityManager();
The server builds, and it registers to the orbd without error. However when I run the client which tries to connect with the server I get the following exception:
Exception: org.omg.CORBA.OBJECT_NOT_EXIST:
Full exception and stack trace are:
Exception: org.omg.CORBA.OBJECT_NOT_EXIST: ----------BEGIN server-side stack trace----------
org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: SUN minor code: 401 completed: No
at com.sun.corba.se.impl.logging.ActivationSystemException.errorInBadServerIdHandler(ActivationSystemException.java:239)
at com.sun.corba.se.impl.logging.ActivationSystemException.errorInBadServerIdHandler(ActivationSystemException.java:257)
at com.sun.corba.se.impl.activation.ServerManagerImpl.handle(ServerManagerImpl.java:604)
at com.sun.corba.se.impl.orb.ORBImpl.handleBadServerId(ORBImpl.java:1602)
at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.checkServerId(CorbaServerRequestDispatcherImpl.java:407)
at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:182)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1700)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1558)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:940)
at com.sun.corba.se.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:198)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:712)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:471)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1230)
at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:490)
at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:519)
Caused by: com.sun.corba.se.spi.activation.ServerNotRegistered: IDL:activation/ServerNotRegistered:1.0
at com.sun.corba.se.impl.activation.RepositoryImpl.getDBServerDef(RepositoryImpl.java:221)
at com.sun.corba.se.impl.activation.RepositoryImpl.getServer(RepositoryImpl.java:228)
at com.sun.corba.se.impl.activation.ServerManagerImpl.getEntry(ServerManagerImpl.java:350)
at com.sun.corba.se.impl.activation.ServerManagerImpl.handle(ServerManagerImpl.java:566)
... 12 more
To my mind, a call to createEntityManager is logically completely separate from the CORBA networking functionality, so I can't see how this could possible have an impact on the client connecting to the server.
The exception was coming from my EntityManagerFactory. It had nothing to do with the networking, but because I never ran the server until a client connected, no exception occurred until that point.
The exception output was not particularly useful. I found it helpful to comment out all the networking code and just run the server as a stand-alone program from development (much more useful error messages when something goes wrong).

"File not found Exception" at runtime in Glassfish ESB 2.1

Good wishes of the day..!
In production we have Glassfish 2.1 server hosting ESB Applications in two instances each under two Linux Boxes. Functionality of the ESB app to takes client request and transform to destination, again receive the response and sent back to the client.
From past few days we are seeing "File not found Exception" in the logs throwing by WsdlQueryHelper of HTTP BC. We analyzed the logs and came to know that it is happening for only one instance (Instance 2 of Server 1), that to for few requests in that instance. We checked the service of that instance from SOAP tool and it is giving appropriate response, Understood that WsdlQueryHelper failed to process few requests at runtime. Below exception details for the same in logs,
*[#|2012-12-13T18:29:24.526+1100|FINE|sun-appserver2.1|com.sun.jbi.httpsoapbc.WsdlQueryHelper|_ThreadID=319;_ThreadName=httpWorkerThread-7092-0;ClassName=com.sun.jbi.httpsoapbc.WsdlQueryHelper;MethodName=;_RequestID=6fdd0535-24d4-4878-8c98-b48e2dea39eb;|init
query helper failed. javax.wsdl.WSDLException: WSDLException (at
/definitions/types/xsd:schema): faultCode=OTHER_ERROR: An error
occurred trying to resolve schema referenced at 'RouterSchema_v4.xsd',
relative to ''.: java.io.FileNotFoundException: This file was not
found:
file:/home/glassfish/GlassFishESBv21/glassfish/nodeagents/GLASSFISH-001-NA/GLASSFISH-001-instB/RouterSchema_v4.xsd
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:918)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:678)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(WSDLReaderImpl.java:639)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:339)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2324)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2288)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2341)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2362)
at com.sun.jbi.httpsoapbc.WsdlQueryHelper.(WsdlQueryHelper.java:105)
at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processSynchronousQueryResource(JAXWSGrizzlyRequestProcessor.java:293)
at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:217)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:647)
at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
Caused by: java.io.FileNotFoundException: This file was not found:
file:/home/glassfish/GlassFishESBv21/glassfish/nodeagents/GFESB_ASPAC_001-NA/GFESB_ASPAC_001-instB/RouterSchema_v4.xsd
at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(StringUtils.java:199)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:840)
... 17 more |#]*
Could you please help us to resolve the issue.
Regards,
Ram