Problem Starting a custom built portal service

Question

Hi,
When I try to start my custom build portal service I get the following error message:
"Server 4128450:Error in the listener class com.sap.ip.portal.admin.portalanywhere.QueryHandler during the process of handleTopic."
Does anyone have a solution on this problem?
Here is my portalapp.xml file:
<?xml version="1.0" encoding="utf-8"?>
<application>
  <application-config>
    <property name="releasable" value="false"/>
    <property name="startup" value="true"/>
  </application-config>
  <components/>
  <services>
    <service name="TestService" alias="Test">
      <service-config>
        <property name="className" value="se.xxx.mdm.TestService"/>
      </service-config>
      <service-profile>
        <property name="ServerName" value="ABC"/>
      </service-profile>
    </service>
  </services>
</application>
Kind Regars
Michael

Answer 1

Hi Jasmin
Yes TemplateCC is my class. I originally used RSA (Rational) to export the JAR, but have since also done it with Vanilla Eclipse (Using the same export options that you use). Eventually I've come to the conclusion that there's nothing wrong with the jar, but rather something wrong with my App server. Here's why:
If I install and start the component on another ES2 server (running on JBoss) it installs perfectly and works correctly in a LC application. The problem only occurs when I try to install the component to my ES2 server on Websphere. I was wondering if it might have something to do with the IBM JVM, but haven't been able to confirm that suspicion yet.
In pursuit of a solution, can you confirm whether the following statement is valid: "If a component installs and starts on one LC server, it must be able to deploy and start on another,  even on different platforms"
Thanks for the help thus far.