ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Class should inherit from Java Compute Node

Post new topic  Reply to topic
 Class should inherit from Java Compute Node « View previous topic :: View next topic » 
Author Message
ninjahatodi
PostPosted: Sat Feb 20, 2010 10:41 pm    Post subject: Class should inherit from Java Compute Node Reply with quote

Novice

Joined: 02 Apr 2009
Posts: 12

Has any one faced any problem similar to this?
I have encountered many times in our project problem of "Class should inherit from Java Compute Node".

The problem is JavaComputeNode is supposed to hold reference to class which extends from MbJava Compute Node.
However for some unknown reasons Mb can not uniquely locate this particular class.
Manually if you try to reload this class it gives the error unable to uniquely map type name to type.

I have tried
1) Cleaning up workspace.
2) Delete all class files and clean the project having "should inherit problem" and recompile entire work space.
3) Removed and added the java project refereces to message flow project

This still does not solve the problem.

Problems seem to be related with eclipse unable to locate unique class type which container is trying to refer.

If any onbe has experience similar problem ; can you pleas share your valuable findings? It would be of great help if some one can point out
root cause of problem
Back to top
View user's profile Send private message
ninjahatodi
PostPosted: Sat Feb 20, 2010 10:49 pm    Post subject: Reply with quote

Novice

Joined: 02 Apr 2009
Posts: 12

Forgot to mention javacompte.jar file is already added to java project in its library path
Back to top
View user's profile Send private message
ninjahatodi
PostPosted: Wed Mar 24, 2010 11:29 am    Post subject: Reply with quote

Novice

Joined: 02 Apr 2009
Posts: 12

I was not able to find out the root cause of the issue.
However i found work around which is working well on my system.
Hope this may help some one facing similar problem cause when it
occurs it block all your deployment plans.

Hers is what i did to resolve the issue:

In the java code extends MbJavaComputeNode was replaced by com.ibm.broker.javacompute.MbJavaComputeNode and the problem got resolved.

I am not sure though why this problem is intermittent in nature.

Why MB toolkit class loader can not identify the MbJavaComputeNode
class ; imported from package com.ibm.broker.javacompute when it is specified without full package name and package is imported in class file.

The most important question is why this does not happen consistently?
Some times it is okay for toolkit to do even without package name and some time it doesn't.

It would be great help some one can explain this toolkit behavior.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Mar 24, 2010 8:02 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

ninjahatodi wrote:
I was not able to find out the root cause of the issue.
However i found work around which is working well on my system.
Hope this may help some one facing similar problem cause when it
occurs it block all your deployment plans.

Hers is what i did to resolve the issue:

In the java code extends MbJavaComputeNode was replaced by com.ibm.broker.javacompute.MbJavaComputeNode and the problem got resolved.

I am not sure though why this problem is intermittent in nature.

Why MB toolkit class loader can not identify the MbJavaComputeNode
class ; imported from package com.ibm.broker.javacompute when it is specified without full package name and package is imported in class file.

The most important question is why this does not happen consistently?
Some times it is okay for toolkit to do even without package name and some time it doesn't.

It would be great help some one can explain this toolkit behavior.


The class (iface) being extended must be imported and unique enough not to lead to confusion with a class with same name in a different package.... only then can you drop the fully qualified name for the short name...

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
rekarm01
PostPosted: Thu Mar 25, 2010 12:43 am    Post subject: Re: Class should inherit from Java Compute Node Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415

ninjahatodi wrote:
Forgot to mention javacompute.jar file is already added to java project in its library path

How exactly does the java project library path refer to javacompute.jar? Check the documentation for more detailed instructions.
Back to top
View user's profile Send private message
ninjahatodi
PostPosted: Tue Dec 30, 2014 2:39 am    Post subject: Reply with quote

Novice

Joined: 02 Apr 2009
Posts: 12

The link points to dragon infomration. I set the classpath the way you would do in eclipse. Although it has been many years since this was last faced. After going through log i belive it should have been error related to not setting class paths properly.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Class should inherit from Java Compute Node
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.