| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Configurable property "Reply-to queue" on node &qu |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Tue Mar 28, 2006 8:42 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| sstubble wrote: |
| You're right, I'm exporting/importing using the eclipse tool. I'm old school and call it the config manager, regardless of the tooling I'm using to access it. |
Well. I guess I'm not sure that we are actually understanding each other yet. Again, probably we are, but since it has bearing on your problem I want to be extra clear.
In broker 2.1 versions, the Configuration Manager was not only used to control brokers, it was also used as a source control management repository.
In broker v5 and later, the Configuration Manager no longer stores much of anything, other than broker configuration information. It no longer stores code at all.
The 2.1 Control Center had functions for checking projects in and out of the source control sections of the configuration manager.
The v5 and later Eclipse tooling can use plugins to access source control tools of all kinds - CVS is one.
The v5 (and later) Configuration Manager is represented in the >v5 Broker Toolkit as a "domain connection" in the Broker Administration Perspective. You are not in anyway trying to import or export objects from this Domain Connection, correct? Or any objects underneath it?
Instead, you are for example exporting Message Flow and Message Set Projects from the Broker Development perspective, and Importing them that way as well. Or you are checking them into CVS or some other Source Control tool from one Toolkit workspace and checking them back out into another Toolkit workspace.
Yes?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| Tibor |
| Posted: Wed Mar 29, 2006 7:31 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Jeff,
It is a very interesting warning  . I've just made a new attempt, my steps was:
- creating a brand new toolkit session with command-line argument -data
- define a new msgflow project and a msgflow with 2 nodes: mqinput - mqoutput
...and getting the known message in the 'Task List' 
That's why I think this is not related to any earlier projects rather CSD07. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 29, 2006 8:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Tibor -
I agree absolutely with your findings, and your analysis of this as an "interesting warning".
I'm running v6, so I can't quickly recreate the problem.
Did you try a -clean option? It may be a plugin registry issue...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Mar 29, 2006 1:22 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| jefflowrey wrote: |
| Did you try a -clean option? It may be a plugin registry issue... |
Yes I did, moreover I try some other options: -debug -consoleLog -noRegistryCache and I got this:
| Code: |
Startup: using configuration file:D:\tbors\toolkit\dev\.\.metadata\.config\platform.cfg
Boot URL: file:C:/mqsi/eclipse/plugins/org.eclipse.core.boot_2.1.2/boot.jar
Startup: splash path = C:\mqsi\ibtoolkit\eclipse\plugins\com.ibm.etools.wbimsgbroker_5.1.7\splash.bmp
Workspace location:
.
Debug-Options:
file:D:/tbors/toolkit/dev/.options
Install URL:
file:C:/mqsi/eclipse/
!ENTRY org.eclipse.core.runtime 2 1 marc. 29, 2006 22:49:16.422
!MESSAGE Problems encountered loading the plug-in registry.
!SUBENTRY 1 org.eclipse.core.runtime 2 1 marc. 29, 2006 22:49:16.422
!MESSAGE Unknown extension point "com.ibm.etools.ctc.binding.eis.ui.Customized" specified in plug-in "com.ibm.etools.ctc.ui".
!SUBENTRY 1 org.eclipse.core.runtime 2 1 marc. 29, 2006 22:49:16.422
!MESSAGE Unknown extension point "com.ibm.etools.ctc.binding.eis.ui.Customized" specified in plug-in "com.ibm.etools.ctc.ui".
!SUBENTRY 1 org.eclipse.core.runtime 2 1 marc. 29, 2006 22:49:16.422
!MESSAGE Unknown extension point "com.ibm.sed.library.LibraryContributions" specified in plug-in "com.ibm.sed.editor".
!ENTRY org.eclipse.core.runtime 4 2 marc. 29, 2006 22:44:15.453
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.runtime".
!STACK 0
java.lang.NullPointerException
at org.eclipse.jdt.internal.launching.LaunchingPlugin.startup(LaunchingPlugin.java:382)
at org.eclipse.core.internal.plugins.PluginDescriptor$1.run(PluginDescriptor.java:736)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java(Compiled Code))
at org.eclipse.core.internal.plugins.PluginDescriptor.internalDoPluginActivation(PluginDescriptor.java:748)
at org.eclipse.core.internal.plugins.PluginDescriptor.doPluginActivation(PluginDescriptor.java:188)
at org.eclipse.core.internal.plugins.PluginClassLoader.activatePlugin(PluginClassLoader.java:112)
at org.eclipse.core.internal.plugins.PluginClassLoader.internalFindClassParentsSelf(PluginClassLoader.java(Compiled Code))
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.findClassParentsSelf(DelegatingURLClassLoader.java(Compiled Code))
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java(Compiled Code))
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java(Compiled Code))
at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java(Compiled Code))
at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java(Compiled Code))
at org.eclipse.core.internal.plugins.ConfigurationElement.createExecutableExtension(ConfigurationElement.java(Compiled Code))
at org.eclipse.jdt.core.JavaCore.getClasspathContainerInitializer(JavaCore.java:961)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:881)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1531)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1463)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1439)
at org.eclipse.jdt.internal.core.search.JavaSearchScope.add(JavaSearchScope.java:75)
at org.eclipse.jdt.internal.core.search.JavaWorkspaceScope.initialize(JavaWorkspaceScope.java:78)
at org.eclipse.jdt.internal.core.search.JavaSearchScope.<init>(JavaSearchScope.java:49)
at org.eclipse.jdt.internal.core.search.JavaWorkspaceScope.<init>(JavaWorkspaceScope.java:30)
at org.eclipse.jdt.internal.core.search.indexing.IndexManager.shutdown(IndexManager.java:507)
at org.eclipse.jdt.internal.core.JavaModelManager.shutdown(JavaModelManager.java:1550)
at org.eclipse.jdt.core.JavaCore.shutdown(JavaCore.java:3017)
at org.eclipse.core.internal.plugins.PluginRegistry$2.run(PluginRegistry.java:295)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java(Compiled Code))
at org.eclipse.core.internal.plugins.PluginRegistry$1.visit(PluginRegistry.java:308)
at org.eclipse.core.internal.plugins.PluginRegistry.accept(PluginRegistry.java:58)
at org.eclipse.core.internal.plugins.PluginRegistry.shutdownPlugins(PluginRegistry.java:311)
at org.eclipse.core.internal.plugins.PluginRegistry.shutdown(PluginRegistry.java:277)
at org.eclipse.core.internal.runtime.InternalPlatform.loaderShutdown(InternalPlatform.java:630)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.internal.boot.InternalBootLoader.shutdown(InternalBootLoader.java:1008)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:863)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)
Start VM: c:\mqsi\eclipse\jre\bin\java.exe
-cp c:\mqsi\eclipse\startup.jar org.eclipse.core.launcher.Main
-os win32
-ws win32
-arch x86
-showsplash c:\mqsi\eclipse\mqsistudio.exe -showsplash 600
-data .
-debug
-consoleLog
|
However, we plan to upgrade the toolkits to v6 and I hope this helps. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
