| Author |
Message
|
| vsc |
 Posted: Thu Sep 05, 2013 3:20 am Post subject: Seibel Adaptor configuration error : OutofMemoryError |
 |
|
Newbie
Joined: 15 Jul 2013
Posts: 7
|
Hi All,
Iam trying to configure Seibel Adaptor in toolkit
Version : 7.0.0.4 Windows
When iam configuring Adaptor connection-->Seibel Inbound Adaptor-->Configure Settings Discovery Agent--> and provided the creditinals and after proceeding further iam getting
com.ibm.adapter.framework.BaseException
Reason :
java.lang.OutOfMemoryError
I was able to do telnet and ping the url and it is successfull.
and done the configuration as documented
mqsichangeproperties Local_Brk -c EISProviders -o Siebel -n jarsURL -v C:\siebel
mqsichangeproperties Local_Brk -c EISProviders -o Siebel -n nativeLibs -v C:\siebel
tried to increase the JVM Heap Size but no use.
Need your  |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Sep 05, 2013 4:21 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Why do people think about monkeying around with jvm heap size? This has nothing to do with your problem
AND THE DOCUMENTATION SPECIFICALLY SAYS DO NOT MODIFY JVM HEAP SIZE UNLESS TOLD TO DO SO BY SUPPORT.
{Rhetorical} What leads you to believe this issue has anything to do with JVM heapsize?
It does not.
Update your toolkit and runtime to 7.0.0.6. Then try again.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu Sep 05, 2013 8:22 am Post subject: Re: Seibel Adaptor configuration error : OutofMemoryError |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| lancelotlinc wrote: |
| AND THE DOCUMENTATION SPECIFICALLY SAYS DO NOT MODIFY JVM HEAP SIZE UNLESS TOLD TO DO SO BY SUPPORT. |
Not to suggest that this is related to the OP's issue, but where does the documentation specifically say that? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 05, 2013 9:11 am Post subject: Re: Seibel Adaptor configuration error : OutofMemoryError |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rekarm01 wrote: |
| lancelotlinc wrote: |
| AND THE DOCUMENTATION SPECIFICALLY SAYS DO NOT MODIFY JVM HEAP SIZE UNLESS TOLD TO DO SO BY SUPPORT. |
Not to suggest that this is related to the OP's issue, but where does the documentation specifically say that? |
The closest I can find is here which says:
| Quote: |
| Increase the maximum heap size only if you use Java intensively with, for example, user-defined nodes |
and leaves the definition of "intensively" to the reader.
I also found (and all should bear in mind my extensive knowledge of Java & the JVM here!) this entry, which says:
| Quote: |
| The maximum size of the storage available to the JVM, specified in bytes. If you have configured a publish/subscribe domain, when execution groups retain publications, you might need to increase this value. If you have included the XSLTransform node in one or more message flows, and the node is processing very large XML messages, you might also have to change this parameter |
which seems to give 2 use cases where IBM expect the value to be increased without reference to Support. Now again, "very large" is left as an exercise for the reader as are the circumstances under which retained publications cause a problem, but it does seem to indicate that
| lancelotlinc wrote: |
| monkeying around with jvm heap size |
is something IBM expect people to do without asking first.
Moving to the OP's problem:
| lancelotlinc wrote: |
| What leads you to believe this issue has anything to do with JVM heapsize |
The Seibel Adaptor in WMB being Java based? That the error message indicates a Java OutOfMemory condition? Either of those might have started me looking for a Java person to advise me. If the memory it's out of is Heap memory or some other Java construct I leave to more knowledgeable Java people, and I'll defer to the assertion that this is categorically not a heap problem.
Being on the latest FP is always a good idea. Especially when there's a fix in 7.0.0.5 for what sounds like this problem.
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Thu Sep 05, 2013 9:26 am; edited 1 time in total |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Sep 05, 2013 9:20 am Post subject: Re: Seibel Adaptor configuration error : OutofMemoryError |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 05, 2013 9:27 am Post subject: Re: Seibel Adaptor configuration error : OutofMemoryError |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| rekarm01 wrote: |
| lancelotlinc wrote: |
| AND THE DOCUMENTATION SPECIFICALLY SAYS DO NOT MODIFY JVM HEAP SIZE UNLESS TOLD TO DO SO BY SUPPORT. |
Not to suggest that this is related to the OP's issue, but where does the documentation specifically say that? |
http://www-01.ibm.com/support/docview.wss?uid=swg21202971 |
- that is the heap size for the Toolkit, not the run time
- it also says:
| Quote: |
| Note that this should only be performed in case of Toolkit reporting Out of memory issues |
i.e. you don't need to call support first
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
