Unable to register Enterprise Messaging Service(EMS) agent in TIBCO Enterprise Administrator(TEA)
Article ID: KB0084340
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Administrator (TEA) | 2.2 |
Description
===================
java.lang.NullPointerException
at com.tibco.tea.agent.ems.Agent.addEMSServer(Agent.java:290)
at com.tibco.tea.agent.ems.Agent.registerEMSServerUI(Agent.java:216)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.tibco.tea.agent.internal.RequestTargetForTopLevelTeaObject.doInvoke(RequestTargetForTopLevelTeaObject.java:35)
at com.tibco.tea.agent.internal.RequestTarget.invoke(RequestTarget.java:104)
at com.tibco.tea.agent.internal.task.TaskManager.executeTask(TaskManager.java:102)
at com.tibco.tea.agent.internal.RequestTargetForTaskManager.invoke(RequestTargetForTaskManager.java:46)
at com.tibco.tea.agent.internal.RequestTarget.getResult(RequestTarget.java:472)
at com.tibco.tea.agent.internal.server.BaseTeaAgentServer.processRequest(BaseTeaAgentServer.java:305)
at com.tibco.tea.agent.internal.server.BaseTeaAgentServer.processRequest(BaseTeaAgentServer.java:219)
at com.tibco.tea.agent.server.TeaAgentServer$AgentHandler.handle(TeaAgentServer.java:621)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.websocket.server.WebSocketHandler.handle(WebSocketHandler.java:112)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
====================
Issue/Introduction
Environment
Resolution
The following are a number of scenarios where this issue can happen.
Scenario 1:
When registering an Enterprise Messaging Service (EMS) Fault tolerance pair in the TIBCO Enterprise Administrator(TEA) UI, make sure the Active Server URL is provided in the Primary is given in the primary URL field and the Standby Server URL in the secondary URL field. If this is done incorrectly, then the registration fails with a NullPointerException.
Scenario 2:
When the EMS user used for registering the EMS server has insufficient permissions to access all the EMS objects, registration fails with a "NullPointerException". Make sure that proper permissions are assigned to the user.
Scenario 3:
When the EMS server URL is used while registering in TIBCO Enterprise Administrator (TEA) UI is different from the listening URL in the tibemsd.conf file used to start the EMS server, registration fails with a NullPointerException. Make sure the URL matches the URL set in the tibemsd.conf file in the EMS server. The IP address or hostname of the server must explicitly appear in the listening URL in the tibemsd.conf file used to start the EMS server.
In the event that the above scenarios/steps are not helpful, open a Case with TIBCO Support.
Feedback
