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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED] : FMC38002E at signin on Portal Client

Post new topic  Reply to topic Goto page 1, 2  Next
 [SOLVED] : FMC38002E at signin on Portal Client « View previous topic :: View next topic » 
Author Message
ggcaer
PostPosted: Mon May 30, 2005 11:38 pm    Post subject: [SOLVED] : FMC38002E at signin on Portal Client Reply with quote

Novice

Joined: 30 Jan 2004
Posts: 19
Location: France

I get the message erreur : java.beans.PropertyVetoException FMC38002E Locator LOC_LOCATOR is not supported
while signin on Portal Client.
My Workflow 3.5 SP3 system is on Win2k with MQseries 5.3 CSD 7.
My Portal system uses WPS 5 on AIX with MQseries 5.3 csd 8 and workflow components 3.5 SP3.
Can you please help me ?


Last edited by ggcaer on Wed Jun 29, 2005 6:24 am; edited 3 times in total
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
vennela
PostPosted: Tue May 31, 2005 9:29 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

From the portal server machine, can you logon to workflow using fmcautil
Back to top
View user's profile Send private message Send e-mail Visit poster's website
ggcaer
PostPosted: Tue May 31, 2005 11:58 pm    Post subject: Reply with quote

Novice

Joined: 30 Jan 2004
Posts: 19
Location: France

Hi Vennela,

Yes I can connect to workflow server from portal server using fmcautil.

RYS
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
hos
PostPosted: Wed Jun 01, 2005 1:04 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Hi,

this could be the weired error message that you get when your application tries to change the configurationID. Have you running other MQWF clients on WAS with a different configurationID? Try to make the portal client configuration to the default configuration.
Back to top
View user's profile Send private message
ggcaer
PostPosted: Wed Jun 01, 2005 1:19 am    Post subject: Reply with quote

Novice

Joined: 30 Jan 2004
Posts: 19
Location: France

Hi hos,
I do not understand what you mean.

on the workflow server, I have a config for workflow system, another one for web client.

on the portal server, I only have a config for the portalclient, using a local queue manager which is part of workflow cluster FMCGRP.

what do you want me to do ?
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
jmac
PostPosted: Wed Jun 01, 2005 5:06 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

I believe that Volker is referring to the following document:

http://www-128.ibm.com/developerworks/websphere/library/techarticles/0406_kulhanek/0406_kulhanek.html

There is an issue running under WAS of having two MQWF configurations running concurrently. This document indicates how to solve the problem

It might help you.

GOOD LUCK
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
ggcaer
PostPosted: Wed Jun 01, 2005 6:52 am    Post subject: Reply with quote

Novice

Joined: 30 Jan 2004
Posts: 19
Location: France

I do not have any other worflow client on the was running wps.
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
vennela
PostPosted: Wed Jun 01, 2005 7:13 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

There is a java program in the link below. Compile it and run it from the portal server machine and see if it works.

http://www.mqseries.net/phpBB2/viewtopic.php?t=10990&highlight=mqwflogin

Also see if you get any errors iwhen you run fmczchk

Also set the CLASSPATH right for the portal server (make sure you include the workflow jars)
Back to top
View user's profile Send private message Send e-mail Visit poster's website
ggcaer
PostPosted: Wed Jun 01, 2005 7:39 am    Post subject: Reply with quote

Novice

Joined: 30 Jan 2004
Posts: 19
Location: France

classpath is right in portal was server
no error in fmczchk

Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
ggcaer
PostPosted: Thu Jun 02, 2005 1:44 am    Post subject: Java Agent Reply with quote

Novice

Joined: 30 Jan 2004
Posts: 19
Location: France

How can I know if java agent is running ?
I cannot find the fmcagent-configid.sh file....
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
vennela
PostPosted: Thu Jun 02, 2005 5:57 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Compile the above program and see if that works.
AFAIK, a java agent is just configured. You don't have to start it. With very old versions of workflow there was something that needs to be started but there isn't anything that needs to be started for a web client to work.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
ggcaer
PostPosted: Thu Jun 02, 2005 6:23 am    Post subject: Reply with quote

Novice

Joined: 30 Jan 2004
Posts: 19
Location: France

Hi Vennala,
The java program returns bad news....

Loggingintoworkflow......
MQWF Error13 - FMC00013E Communication error - Failing Action: Connect_to_QM, Reason Code: 2102, Failing Object: WPSMQWF.

  StackTrace:
com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : /projects/fmc/drv2/lbld/v350/aix/src/fmcjcesv.cxx, line 2450
Error Message : FMC00013E Communication error - Failing Action: Connect_to_QM, Reason Code: 2102, Failing Object: WPSMQWF.
Nested Exception : None
at com.ibm.workflow.api.loc.ExecutionServiceImpl.logon2(ExecutionServiceImpl.java:262)
at MQWFLogin.main(MQWFLogin.java:37)
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
vennela
PostPosted: Thu Jun 02, 2005 6:28 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Code:
$ mqrc 2102

      2102  0x00000836  MQRC_RESOURCE_PROBLEM
$

What all are running on your machine
Looks like too many things and the box is overloaded.
See if there are any FDC's cut from MQ side.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
ggcaer
PostPosted: Thu Jun 02, 2005 8:12 am    Post subject: Reply with quote

Novice

Joined: 30 Jan 2004
Posts: 19
Location: France

everything seems ok with system ressources on portal box.
does the message relate to portal or workflow box ?


is it possible that the problem comes from java agent parameters (reaper cycle, threshold, ratio ) ?

Concerning the chltab file. Do I have or not to copy the file from workflow server to portal server ?

I tried values 4 and 11 for IPCCBaseAddress in mqs.ini file on portal box without more success...

While running vennela's java program, does it use chltab file ?
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
vennela
PostPosted: Thu Jun 02, 2005 8:27 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

That program will not use channel table.
These are the things I am assuming:
Workflow server and portal server are talking to each other using QMGR-QMGR communication.
It is MQ v5.3
Quote:
Concerning the chltab file. Do I have or not to copy the file from workflow server to portal server ?

If the first assumption above is true then NO.

You don't have to worry about IPCCBaseAddress in MQ v5.3

Quote:
is it possible that the problem comes from java agent parameters (reaper cycle, threshold, ratio ) ?

It is possible.

See if there are any hanging java processes on the box. See if there is any process that is eating up the memory/cpu
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED] : FMC38002E at signin on Portal Client
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.