Topic
  • 4 replies
  • Latest Post - ‏2008-11-17T11:18:17Z by SystemAdmin
SystemAdmin
SystemAdmin
2340 Posts

Pinned topic MQ Workflow Trace files

‏2006-08-12T14:14:02Z |
Dear All
I'm having tracefiles generated in the home of the FMC user. These files have the following entries
So, what might be causing it?
and How can trace files be disabled?
14:36:46.298 com.ibm.rmi.corba.PluginRegistry loadPrereqPluginsGroupThree:269 P=5727:O=0:CT ORBRas[
default] org.omg.CORBA.INTERNAL: CONNECTIONINTERCEPTOR_INVALID_CLASSNAME vmcid: 0x49421000 minor
code: 5B completed: No org.omg.CORBA.INTERNAL: CONNECTIONINTERCEPTOR_INVALID_CLASSNAME vmcid: 0x4
9421000 minor code: 5B completed: No
at com.ibm.ws.orbimpl.transport.WSTransport.init(WSTransport.java:189)
at com.ibm.rmi.corba.PluginRegistry.loadPrereqPluginsGroupThree(PluginRegistry.java:240)
at com.ibm.rmi.corba.ORB.initializePrereqPlugins(ORB.java:442)
at com.ibm.CORBA.iiop.ORB.initializePrereqPlugins(ORB.java:959)
at com.ibm.rmi.corba.ORB.orbParameters(ORB.java:1333)
at com.ibm.CORBA.iiop.ORB.orbParameters(ORB.java:1251)
at com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1262)
at com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1839)
at org.omg.CORBA.ORB.init(ORB.java:368)
at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:77)
at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:174)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:98)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:74)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:386)
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:284)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.jav
a:368)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:112)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:422)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:143)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at om.gov.moci.oss.framework.util.EJBHomeFactory.getHomeInterface(EJBHomeFactory.java:208)
at om.gov.moci.oss.component.eapplication.common.EApplicationDispatcher.changeState(EApplic
ationDispatcher.java:296)
at om.gov.moci.oss.coreservice.workflowmanager.service.Evaluator.startProcessing(Evaluator.
java:144)
at om.gov.moci.oss.coreservice.workflowmanager.service.UpesImplementation.main(UpesImplemen
tation.java:312)
Updated on 2008-11-17T11:18:17Z at 2008-11-17T11:18:17Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    2340 Posts

    Re: MQ Workflow Trace files

    ‏2006-08-14T06:33:56Z  
    Yousef,

    what you see is the exception stack of a severe error.
    You can avoid this kind of 'tracing' if you avoid this exception.
    So the real question is: what kind of error are you seeing?
    Do you use RMI/IIOP? What JNDI lookup is failing?

    Volker Hoss
    IBM WebSphere MQ Workflow Development
  • SystemAdmin
    SystemAdmin
    2340 Posts

    Re: MQ Workflow Trace files

    ‏2006-08-15T17:27:00Z  
    Yousef,

    what you see is the exception stack of a severe error.
    You can avoid this kind of 'tracing' if you avoid this exception.
    So the real question is: what kind of error are you seeing?
    Do you use RMI/IIOP? What JNDI lookup is failing?

    Volker Hoss
    IBM WebSphere MQ Workflow Development
    Hi Volker
    From Application Prespective, we do not face any problems. Application is
    working properly.
    But it's when I see these errors, I think maybe more severe errors can
    happen later!!

    <hos@de.ibm.com> wrote in message
    news:ebp5gk$1o862$1@news.boulder.ibm.com...
    > Yousef,
    >
    > what you see is the exception stack of a severe error.
    > You can avoid this kind of 'tracing' if you avoid this exception.
    > So the real question is: what kind of error are you seeing?
    > Do you use RMI/IIOP? What JNDI lookup is failing?
    >
    > Volker Hoss
    > IBM WebSphere MQ Workflow Development

  • SystemAdmin
    SystemAdmin
    2340 Posts

    Re: MQ Workflow Trace files

    ‏2008-11-04T07:52:05Z  
    Hi Guys,

    Our application is running well, but when I try to run the Junits I am encountering the same problem.

    I am anewbie in WebSphere Apllication Server. It would be a big help if you could kindly give a clearer or broader explanation why this problem occurs.

    I am using the following JVM options and classpath listed bellow:

    JVM OPTION:
    -DINSTALL_DIR=<PROJECT_LOCATION>
    -Dtower.java.naming.provider.url=corbaloc:iiop://localhost:2809/NameService
    -Dtower.host.port=localhost:9080
    -Djava.naming.factory.url.pkgs=com.ibm.webspheres.naming.WsnInitialContextFactory
    -Ddesktopindicator.webserviceurl=http://localhost:9080/services/AlertService
    -Dcactus.contextURL=http://localhost:9080
    -Dvissys.appserver=WEBSPHERE
    -Dtower.db.vendor=oracle
    CLASS PATH:
    bootstrap.jar
    j2ee.jar
    urlprotocols.jar
    lmproxy.jar
    ras.jar
    naming.jar
    wsexception.jar
    namingclient.jar
    ecutils.jar
    iwsorb.jar
    ffdc.jar
    emf.jar
    idl.jar
    Hope to hear a favorable response from you guys.

    Thanks,
    Hoopwine
  • SystemAdmin
    SystemAdmin
    2340 Posts

    Re: MQ Workflow Trace files

    ‏2008-11-17T11:18:17Z  
    Hi Guys,

    Our application is running well, but when I try to run the Junits I am encountering the same problem.

    I am anewbie in WebSphere Apllication Server. It would be a big help if you could kindly give a clearer or broader explanation why this problem occurs.

    I am using the following JVM options and classpath listed bellow:

    JVM OPTION:
    -DINSTALL_DIR=<PROJECT_LOCATION>
    -Dtower.java.naming.provider.url=corbaloc:iiop://localhost:2809/NameService
    -Dtower.host.port=localhost:9080
    -Djava.naming.factory.url.pkgs=com.ibm.webspheres.naming.WsnInitialContextFactory
    -Ddesktopindicator.webserviceurl=http://localhost:9080/services/AlertService
    -Dcactus.contextURL=http://localhost:9080
    -Dvissys.appserver=WEBSPHERE
    -Dtower.db.vendor=oracle
    CLASS PATH:
    bootstrap.jar
    j2ee.jar
    urlprotocols.jar
    lmproxy.jar
    ras.jar
    naming.jar
    wsexception.jar
    namingclient.jar
    ecutils.jar
    iwsorb.jar
    ffdc.jar
    emf.jar
    idl.jar
    Hope to hear a favorable response from you guys.

    Thanks,
    Hoopwine
    For me it helped setting the following system property before instantiating the ORB:
    com.ibm.ws.orb.transport.ConnectionInterceptorName=com.ibm.ws.orb.transport.DefaultConnectionInterceptor
    /Morten