| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQIv210; Java node errors |
« View previous topic :: View next topic » |
| Author |
Message
|
| Neinie |
 Posted: Fri Oct 07, 2005 9:03 am Post subject: WMQIv210; Java node errors |
 |
|
Newbie
Joined: 06 Aug 2003
Posts: 7
|
1) I am working on a java node that calls a business service using http protocol. At this point I am trying to implement SSL authentication and encoutnring problem in defining URL to connect to.
When I try to set the URL
URL SSL_URL = new URL("https://some.valid.url.com");
program throws malformed URL exception (unknown protocol:https).
2) Also, aside for error above, I am seeing lot of System generated errors on Application Log (WIN2K). Descritpion states "Failure to locate java class... Contact your IBM support". Does anyone know where should I define those missing java classes. I have tried to add those to CLASSPATH, to JSDK\lib dir, and to MQI21\jre\lib without any luck.
As always any help is greatly appreciated and TIA.
Neinie |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Oct 07, 2005 4:49 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I would recommend getting the "logic" portion of your java node to function fully *outside* broker first.
Then worry about patching it into a java node that will run in broker.
This will tell you exactly what classes and jars and such your code needs. Then you can go back to the documentation, and read about where to put those dependancies in the broker installation.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wbibrk |
| Posted: Mon Oct 10, 2005 5:42 am Post subject: |
|
|
Apprentice
Joined: 09 Jul 2005
Posts: 46
|
Hi,
Failure to locate java class errors are a result of broker unable to find the java classes from the CLASSPATH / loaded jar files from jplugin directory. Broker loads all the jar files from the jplugin directory and all user jar files from CLASSES directory.
If a java class A calls class B and class B calls class C etc, class B and class C should be found by the broker either by the jar file loading describe above via the CLASSPATH.
If they are not found then you would get the BIP4371S error. Also, remember to reboot your system after changing the CLASSPATH on Windows as Windows system variables do not take effect until a reboot (unless you use setx) |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
