Author |
Message
|
cvengatesan |
Posted: Tue Dec 09, 2014 4:57 pm Post subject: logon to MQWF failed - service startup |
|
|
Newbie
Joined: 13 Jul 2009 Posts: 7
|
Current Env: Windows server 2003
DB2 : 9.7
MQ : 6
MQ workflow 3.6
we have service to handle all the submission to create work item instance.
When we start the service it will use syscom framework to use logon to MQWF.
But right now we are moving to new tech servers Windows
New Env: Windows server 2008
DB2 : 9.7
MQ : 7
MQ workflow 3.6
when we start the service we are getting some different error..
com.syscom.msghndlr.MessageHandlerNodeInitializationException: Throwable exception while logging onto MQWF in init: com.ibm.msg.client.jms.JmsMessageProducer.send(Ljavax/jms/Message;IIJ)V
at com.wellsfargo.flo.mh.services.SetTransferInfo.init(SetTransferInfo.java:180)
at com.syscom.msghndlr.upes.service.UPESServiceAdapter.init(UPESServiceAdapter.java:126)
at com.syscom.msghndlr.service.DefaultMessageHandlerServiceContainer.loadNode(DefaultMessageHandlerServiceContainer.java:60)
at com.syscom.msghndlr.command.BootstrapCommandModule.loadMessageHandlerServices(BootstrapCommandModule.java:278)
at com.syscom.msghndlr.command.BootstrapCommandModule.init(BootstrapCommandModule.java:789)
at com.syscom.msghndlr.command.DefaultCommandModuleContainer.loadNode(DefaultCommandModuleContainer.java:89)
at com.syscom.msghndlr.command.DefaultCommandModuleContainer.init(DefaultCommandModuleContainer.java:29)
at com.syscom.msghndlr.loader.Main.init(Main.java:126)
at com.syscom.msghndlr.loader.Service.start(Service.java:81)
at com.syscom.msghndlr.loader.Service.start(Service.java:45)
Can you please some one help us with this.
Appreciate your help and time on this issue. I struggling with this issue for last 3 days
Thanks
Venkat |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
jmac |
Posted: Wed Dec 10, 2014 4:16 am Post subject: |
|
|
![](images/avatars/42012047429c7f2bc3b3e.gif) Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Venkat:
It has been a LONG time since I worked with the Message Handler, but I know there are some properties files, if you have upgraded the OS perhaps there is something in there that might need to be updated that would cause the problem.
John _________________ John McDonald
RETIRED |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
jmac |
Posted: Wed Dec 10, 2014 4:41 am Post subject: |
|
|
![](images/avatars/42012047429c7f2bc3b3e.gif) Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Taking another look at the stack trace, I now see that there is a wells module right at the top "SetTransferInfo". If you haven't already had a close look at that, I would start there.
Good Luck _________________ John McDonald
RETIRED |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
cvengatesan |
Posted: Wed Dec 10, 2014 10:34 am Post subject: |
|
|
Newbie
Joined: 13 Jul 2009 Posts: 7
|
Thanks for your reply. After debugging more we got this exception
java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsMessageProducer.send(Ljavax/jms/Message;IIJ)V
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:333)
at com.ibm.workflow.client.util.FmcFMLC.Put_to_Queue(FmcFMLC.java:2159)
at com.ibm.workflow.client.util.FmcFMLC.PutMsg(FmcFMLC.java:683)
at com.ibm.workflow.client.util.FmcFMLC.Converse(FmcFMLC.java:595)
at com.ibm.workflow.client.api.FmcSession.CallSync(FmcSession.java:460)
at com.ibm.workflow.client.api.FmcSession.Logon(FmcSession.java:1008)
at com.ibm.workflow.client.api.FmcExecutionService.logon2(FmcExecutionService.java:800)
at com.wellsfargo.flo.mh.services.SetTransferInfo._logonToMQWF(SetTransferInfo.java:357)
at com.wellsfargo.flo.mh.services.SetTransferInfo.init(SetTransferInfo.java:158)
at com.syscom.msghndlr.upes.service.UPESServiceAdapter.init(UPESServiceAdapter.java:126)
at com.syscom.msghndlr.service.DefaultMessageHandlerServiceContainer.loadNode(DefaultMessageHandlerServiceContainer.java:60)
at com.syscom.msghndlr.command.BootstrapCommandModule.loadMessageHandlerServices(BootstrapCommandModule.java:278)
at com.syscom.msghndlr.command.BootstrapCommandModule.init(BootstrapCommandModule.java:789)
at com.syscom.msghndlr.command.DefaultCommandModuleContainer.loadNode(DefaultCommandModuleContainer.java:89)
at com.syscom.msghndlr.command.DefaultCommandModuleContainer.init(DefaultCommandModuleContainer.java:29)
at com.syscom.msghndlr.loader.Main.init(Main.java:126)
at com.syscom.msghndlr.loader.Service.start(Service.java:81)
at com.syscom.msghndlr.loader.Service.start(Service.java:45)
com.syscom.msghndlr.MessageHandlerNodeInitializationException: Throwable exception while logging onto MQWF in init: com.ibm.msg.client.jms.JmsMessageProducer.send(Ljavax/jms/Message;IIJ)V
at com.wellsfargo.flo.mh.services.SetTransferInfo.init(SetTransferInfo.java:187)
at com.syscom.msghndlr.upes.service.UPESServiceAdapter.init(UPESServiceAdapter.java:126)
at com.syscom.msghndlr.service.DefaultMessageHandlerServiceContainer.loadNode(DefaultMessageHandlerServiceContainer.java:60)
at com.syscom.msghndlr.command.BootstrapCommandModule.loadMessageHandlerServices(BootstrapCommandModule.java:278)
at com.syscom.msghndlr.command.BootstrapCommandModule.init(BootstrapCommandModule.java:789)
at com.syscom.msghndlr.command.DefaultCommandModuleContainer.loadNode(DefaultCommandModuleContainer.java:89)
at com.syscom.msghndlr.command.DefaultCommandModuleContainer.init(DefaultCommandModuleContainer.java:29)
at com.syscom.msghndlr.loader.Main.init(Main.java:126)
at com.syscom.msghndlr.loader.Service.start(Service.java:81)
at com.syscom.msghndlr.loader.Service.start(Service.java:45)
But the jar is present.. can you please help me how we can get resolved. |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
jmac |
Posted: Wed Dec 10, 2014 12:49 pm Post subject: |
|
|
![](images/avatars/42012047429c7f2bc3b3e.gif) Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Like I said it's been a long time, and I really don't know what this is without digging in a bit.
You can contact EmeriCon, or maybe SysCom and see if they can provide you some support. _________________ John McDonald
RETIRED |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
cvengatesan |
Posted: Mon Dec 15, 2014 4:38 pm Post subject: |
|
|
Newbie
Joined: 13 Jul 2009 Posts: 7
|
Thanks Knight for your response, we are able to process but I am facing strange issue now, is that you can guide something here
We have our environment like this
Webserver (windows 2008) - IIS Server (Site minder and channel secure)
Application Server (windows 2008) – Web Sphere server
Workflow Server (windows 2008) – DB2, MQ Series and workflow 3.6
When we access directly through app url we are able to get our work list.
But when we try through channel secure we are getting the following issue. Can you please assist me why we are getting this issue?
Workflow Processing Error
FMC00119E Not authorized |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
|