Query WLI Timer Event Generator's status

Hi guys,
I am using WLI 10.3. Does anyone know how to query the status of Timer Event Generator programatically?
I am able to create and start the timer programatically through JMX and WebLogicDeploymentManager but not getting the status
of timer. It doesn't even look like this is possible through TimerEventGenRuntimeMBean or am I missing something?
Thanks
Sam

Ok, you can basically leave the messageType as XML
and for the Timer EG configuration, for the optional message you can add <dummy/> this will fire the request and start a workflow or whatever is bound to the channel.

Similar Messages

  • Using WLST: Unable to create WLI Timer Event Generator

    Hello,
    I'm trying to create a WLST script, whcih will create Timer Event Generator on WLI 9.2 MP2.
    Though to some extent script runs perfect, but it gives error when calling MBean egCfgMBean = getTarget("TimerEventGeneratorss/TimerEventGenerators")
    Here is my script:-
    import weblogic.Deployer
    import com.bea.wli.mbconnector.timer as timereggen
    import com.bea.wli.mbconnector.file as fileeggen
    import com.bea.wli.management.configuration as wlicfg #Must have wli.jar in classpath
    import java.lang.Boolean as bool
    import jarray
    import sys
    print 'Starting the Timer Event Generation Configuration script .... '
    if connected != 'true':
    print 'Connecting to weblogic server .... '
    connect(userName,passWord,URL)
    else:
    print 'Connected'
    try:
    print "Creating Timer EG ", timerEgName
    timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir + "/" + "WLITimerEG_" + timerEgName + ".jar"])
    #timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir,"-destJNDIName",jndiName])
    #timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir])
    #wlst.config()
    custom()
    #egCfgMBean = wlst.getTarget("TimerEventGenerators/TimerEventGenerators")
    egCfgMBean = getTarget("TimerEventGeneratorss/TimerEventGenerators")
    egMBean = egCfgMBean.newTimerEventGenConfigurationMBean(timerEgName)
    #egMBean = cmo.getTimerEventGenConfigurationMBeans()
    cData = jarray.zeros(1, wlicfg.TimerEventGenChannelConfiguration)
    print 'pass one'
    cData[0] = wlicfg.TimerEventGenChannelConfiguration()
    cData[0].setChannel(channel)
    cData[0].setEffective(effectiveTime)
    #cData[0].setExpiry(expiryTime)
    cData[0].setFrequency(frequency)
    cData[0].setMessageContent(message)
    cData[0].setCalendarName(calendar)
    cData[0].setPublishAsUser(publishAsUser)
    egMBean.setChannels(cData);
    appName = "WLITimerEG_" + timerEgName
    deploy( appName, domaindir + "/" + appName + ".jar", adminServerName, "nostage" )
    cd("Applications/" + appName)
    set("LoadOrder", 1500)
    cd("../..")
    print "script returns SUCCESS"
    except:
    print "ERROR: configuration"
    #dumpStack()
    # Finished
    print 'Disconnecting from server...'
    disconnect('y')
    print 'Finished.'
    exit()
    I really need some help to fix this issue.
    Thanks
    dig

    Hi,
    RDBMS Event Generator Channel Rule Definition
    When you are creating channel rule definitions in the WebLogic Integration Administration Console, it is recommended that you do not use the Back button if you want to resubmit the details on a page.
    You should always use the navigation links provided and create a new channel rule definition.
    http://download.oracle.com/docs/cd/E13214_01/wli/docs85/deploy/cluster.html
    http://download.oracle.com/docs/cd/E13214_01/wli/docs81/relnotes/relnotesLimit.html
    http://otndnld.oracle.co.jp/document/products/owli/docs10gr3/pdf/deploy.pdf
    This problem has been seen in the past when defining the channel rule for an RDBMS Event Generator if schema name was specified with the incorrect case (i.e. lowercase when it should have been uppercase or vice versa). To that end, it is suggested to change the case of the schema when creating the channel rule
    Regards,
    Kal

  • Timer Event Generator.

    Hi there
    I'm running WL Platform 8.1 SP4. I am using the timer event generator to fire requests to a channel/process. The timer is simply used to start a given process, there is no notion of message sent to it.
    Issues
    1) When defining a channel,
    e.g
    <channel name ="XToY" messageType="xml"
    qualifiedMetadataType="eg:TimerEventGenerator" />
    It seems I must define messageType="xml", if i define it as 'none' then it does not appear in the channel list when defining the timer event generator, therefore i cannot bind to it. So if I leave the messageType as xml, it appears. For the configuration of the timer, the message element is optional. Problem is when the timer now fires it throws the following error:
    <08-May-2006 10:25:25 o'clock BST> <Error> <WLI-Core> <BEA-489030> <Error publishing Timer Event message for XToYTimerEG : com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't create proc
    ess variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't read XML (no root element)>
    Any ideas?
    2) Can someone direct me to any wlst scripts that allow the creation of a timer event generator in a cluster? ?I cannot find anything on dev2dev ?
    TIA
    Arvinder

    Ok, you can basically leave the messageType as XML
    and for the Timer EG configuration, for the optional message you can add <dummy/> this will fire the request and start a workflow or whatever is bound to the channel.

  • Weblogic Timer Event Generator - How it works?

    Hello everyone!
    I have wrote simple wli-application, that subscribes to the message broker channel.
    I have deployed it to the cluster (managed servers 1 (ms1) and 2(ms2)). (I use Weblogic Server 10.3, cluster contains 1 admin server and 2 managed servers.)
    Than I have created the timer event generator (EG) via wliconsole and rule for this EG - to send message to the MB-channel every 30 seconds.
    Then I redeploy EG application via console (WLS Admin Console) from managed server 1 to cluster (m.servers 1 and 2) and start it.
    Everything started ok - I got messages to both instatnces of my application in the following way:
    15:30:00 - to instance on ms1
    15:30:30 - to instance on ms2
    15:31:00 - to instance on ms1
    15:31:30 - to instance on ms2
    ...and so on
    when I shut down ms2 - I started to receive messages to instance of my application on ms1 every 30 secodns. Here Everything is OK.
    Then I start ms 2 and got the picture like:
    15:30:00 - to instance on ms1
    15:30:30 - to instance on ms2
    15:31:00 - to instance on ms1
    15:31:30 - to instance on ms2
    ...and so on
    Then I shutdown ms1... And that's all - no messages to instance on ms2 :(
    I started ms1 and no messages on both instances - on ms1 and ms2..
    Can you explain me how Timer Event Generator works? What resources it uses? And how can I setup it to get load-balancing while both instances running and failover - when one of the instances shutdowned?
    Thanks in advance,
    Vladimir.

    Hi Vladimir, it seems like we must have different environments. I don't know if you used the latest version of wli or not...
    So, not exactly for you, but for someone who happens to read this post, and has the same problems we did...
    -- I've configured the cluster address using the IP i've assigned to the servers.
    --- it means that it is like: 192.168.70.120:8013,192.168.70.120:8113 - ip's & PORT, yes?
    Yes, that's the format we are using (http://download.oracle.com/docs/cd/E13222_01/wls/docs92/cluster/setup.html#wp751583)
    -- Configured the FrontEndHost and FrontEndPort with that same values as the AdminServer.
    --- and you have the http-proxy deployed on your admin server? 'cause front-end host and port - must be the host and port of http-proxy that performs load-balancing for requests to your processes on your managed servers.
    Actually we don't need the HTTP load balance, we only start the process via EG events, so we only benifit from load balancing on the JMS queues, but i had to configure this to be able to start the process. We had errors if we didn't configure this. We used the AdminServer address and port.
    -- Relocated the Persistent Stores and JMS Servers since some were incorrectly pointing to the AdminServer.
    ---I didn't understand about what p.stores you are talking about.. I meant that you must create new JDBC p.store with table in cgDataSource and targeted to migratable target. And than you must create a new jms-server, which hosted to this p.store.
    ...But I didn't retarget any existing p.stores......
    Once the domain was created (didn't do anything but to follow the wizard) we had the persistent stores (and underlying JMS servers) targeted to the AdminServer (obviously incorrect). So we retargeted them to the Managed Server.
    -- Created the JSP_<PROCESS> table in the database.
    --- and what is this? :)
    We had to create a table to persist the wli process state, because it is a statefull process (http://download.oracle.com/docs/cd/E13214_01/wli/docs102/dbtuning/wliTuning.html)
    The matter of fact is everything works fine, despite the exceptions i mentioned in the AdminServer, once it gets started... But it seems to have no negative impact on the application, and migration is done successfully
    I will continue to work on figuring out what the origin of those exceptions is, and if i manage to find a solution i, most surely, will post it here... One thing i find to be strange is that the exceptions start even before i have anything deployed to the Migratable Target... Once i create it and restart the server i get those messages, and we tried the Concensus configuration with NodeManager, as well as the Database configuration.
    I guess that what's really important for us now is that we do have fail over and load balancing working... :D
    I don't know if it would be abusive to ask you for that document of yours, maybe it has some clue on what's wrong in our config, but again, i understand if you can't share that =)
    By the way, i'm portuguese, but since google made the translator available, i guess i can manage russian documentation as well ;)
    I can't tell you how gratefull i am for your help, and for sharing your previous experience with the rest of us. If it wasn't for your altruism i guess i would be stuck with this for much longer... you sure saved my day... BIG BIG thank you..
    Once again, thank you and i wish you all the best !!! I just wished i could be helpfull to you sometime =)

  • WLI MQ Event Generator Tuning

    Greetings:
    I have a MQ Event generator that subscribes to a qlocal and publishes messages onto a channel read by a business process.
    I need to process around 10 messages a second syncronously through this process (fifo), judging by the process instance monitoring I am able to process most transactions in <.1 seconds. However, it doesn't seem like the event generator is polling/publishing fast enough to fully utilize the efficiency of the process. I routinely have thousands of messages backing up on the queue awaiting processing. I have tried different configurable params on the event generator (500 messages every 10 seconds, 1 msg every 100 msecs etc) to no avail... i still only seem to be pulling one message in just under a second.
    I'm wondering where I can tune this piece of the application. All my threads seem pretty free etc...
    Any help would be greatly appreciated. Thanks!

    Suspending / resuming event generators is nothing else then undeploying /redeploying the component, which is building up the event generator (either a MDB or a servlet). That can be done via the JMX Api.
    If you are using Timer events , you have to do that inside a workflow. A cron job calling a script could do that less resource intensive (or use whatever scheduling system which is available like Control-M ...)
    Be also aware that WLI timers are JMS based, so an event is only guaranteed to be raised not before the scheduled time, but maybe not exactly at the scheduled time.
    -Kai

  • Edit Timer Event Generator MBean-Weblogic 9.2

    As of new 9.0 api ,MBeanHome interface is deprecated & I have to use standard javax.management classes to connect to mbean servers.
    I am been able to manage the mbean under weblogic server.
    By using MBeanHome.getMBeansByType(TimerEventGeneratorsMBean.TYPE) in old API I can easily manipulate the properties.
    But how can I get the Event Generator MBeans & manage their properties in new 9.0 api?
    I am really worried & could not get any proper documentation of manipulating WLI Mbeans in new API.
    Thanks in advance.

    As of new 9.0 api ,MBeanHome interface is deprecated & I have to use standard javax.management classes to connect to mbean servers.
    I am been able to manage the mbean under weblogic server.
    By using MBeanHome.getMBeansByType(TimerEventGeneratorsMBean.TYPE) in old API I can easily manipulate the properties.
    But how can I get the Event Generator MBeans & manage their properties in new 9.0 api?
    I am really worried & could not get any proper documentation of manipulating WLI Mbeans in new API.
    Thanks in advance.

  • Weblogic Integration - Timer Event

    (Sorry about my english, but it isn't my native language)
    Hi, I'm working with weblogic integration 8.1 sp6 and I didn't found enough documentation about Timer Event. When I'm creating a new Timer Event Generator, Weblogic Integration Administrative Console required 2 parameters (Generator Name and JMS Connection Factory JNDI Name), and JMS Connection Factory JNDI Name show three options (weblogic.jws.jms.QueueConnectionFactory, wli.internal.egrdms.XAQueueConnectionFactory and com.bea.wli.b2b.server.TopicConnectionFactory). My question is: What is the best "JMS Connection Factory JNDI Name" option?.
    Thanks in advance.

    (Sorry about my english, but it isn't my native language)
    Hi, I'm working with weblogic integration 8.1 sp6 and I didn't found enough documentation about Timer Event. When I'm creating a new Timer Event Generator, Weblogic Integration Administrative Console required 2 parameters (Generator Name and JMS Connection Factory JNDI Name), and JMS Connection Factory JNDI Name show three options (weblogic.jws.jms.QueueConnectionFactory, wli.internal.egrdms.XAQueueConnectionFactory and com.bea.wli.b2b.server.TopicConnectionFactory). My question is: What is the best "JMS Connection Factory JNDI Name" option?.
    Thanks in advance.

  • Delete event generator using wlst

    Hi guys,
    Does someone know if it is possible to find timer event generator by its name and delete it in Weblogic(version 9.2.3) using wlst?
    Thanks

    You could see this informantion here:
    http://docs.oracle.com/cd/E14981_01/wli/docs1031/deploy/cluster.html#wp1519038

  • MapMessage and JMS Event Generator

    Hello
    I need to set up a WLI JMS event generator that will consume a JMS MapMessage. It appears that the only message types supported by a JMS event generator are xml, rawData, string and none.
    I've already tried each of these and for each I get a message saying "Cannot publish non-TextMessage to channel of type String" or "Cannot publish non-ByteMessage to channel of type ...".
    I have sent MapMessage types using WLI's JMS controls. Is there a way to consume a MapMessage type via an event generator?
    Thanks
    Tom

    Bishu thanks, Channel type is defined as String, Message on JMS queue are of type String. Also can you elaborate on "JMS event generator check the type of message you want to process." that you mentioned. I have not found this option while configuring JMS EG. (We are using ver. 8.1 sp 5)
    This was working fine in local env. But when we configured message bridge between MQ queue and JMS queue, we startted getting error messages. I am trying to find out how does MQ stores messages. Doing integrations with MQ has been real headache for us.

  • WLI 8.1 RDBMS Event Generator Problem

    Hi,
    I am using WLI 8.1 SP4. I have created a Trigger type RDBMSEventGenerator which publishes events in xml format.
    It is supposed to poll every 8 seconds.
    This event generator works fine if it is created after the server is started.
    However, if the server is restarted, the same event generator stops polling completely. No events are published irrespective of the number of inserts made in the specified table.
    Could anyone shed some light on why this is happening. I have tried to suspend and resume the event generator several times as well, to no effect.

    I would ask in the WebLogic Server - JMS forum.

  • Config event generator to log when file didn't arrive at certain time?

    hi everyone
    is it possible to configure a file event generator to write a log if certain files did not arrive at pre-defined time? or any event generator to log if certain events did not happen at specified time? thanks in advance.
    Message was edited by chendongtom at Sep 13, 2004 10:23 AM

    Hi,
    I don't think, it is possible.
    What you can do is:
    Don't use file EG, but a timer EG, which kicks off a workflow, using a file control to look for/read in/.. the file and do some reporting afterwards.
    You do not have to kick-off the workflow at the exact time, but also can do it 2 hours (for example) before and use a timer inside the workflow for watching a time period for the arrival of the file.
    Keep in mind that WLI timers are not 100% exact because they are JMS based, so it is guranteed not to be started before, but can start a little bit later than start-time.
    If you are using already a scheduling system like Control-
    M, you can also leverage this to start the workflow.
    -Kai

  • Cannot Deploy JPD with Timer Event Subscription in WLI 9.2 MP1 cluster

    Has anyone had any luck deploying a JPD with a timer event subscription to a 9.2 MP1 WLI cluster? I am able to deploy Synchronous Client Request JPDs without any trouble but the ones that rely on internal WLI queues for invocation will not deploy in production. I am able to deploy the problematic JPDs to a non-clustered development environment without any issues but when I try to deploy the same artifact to a 9.2 MP1 cluster I see the following error:
    Throwable: java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: tosipDomain_phase2:Name=cgJMSServer,Type=JMSServer
    Stack Trace:
    java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: tosipDomain_phase2:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.deployWorkshopQueues(EJBGenerator.java:178)
         at com.bea.wli.knex.runtime.core.dispatcher.DispResources.deployQueues(DispResources.java:727)
         at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:667)
         at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:1025)
         at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:946)
         at com.bea.wli.management.adminhelper.AdminHelperBean.getDispFile(AdminHelperBean.java:348)
         at com.bea.wli.management.adminhelper.AdminHelperBean.getProcessMetadata(AdminHelperBean.java:94)
         at com.bea.wli.management.adminhelper.AdminHelperSSB_wivmoo_EOImpl.getProcessMetadata(AdminHelperSSB_wivmoo_EOImpl.java:70)
         at com.bea.wli.management.adminhelper.AdminHelperSSB_wivmoo_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:548)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:438)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:434)
         at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:57)
         at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:965)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    I am suprised about this error, b/c we are running out of a vanilla WLI domain created with the Configuration Wizard and the error message has to do with an internal JMS server that we have left with the default configuration. Has anyone else had success with this?
    On a side note, I have to complain about the lack of 9.2 WLI documentation about deploying applications to production. The links on e-docs.bea.com actually redirect you to 8.5 documentation?!? I can't believe that this is the documentation we are left to use for 9.2 because there are so many changes between WLS 8 and 9.

    Hey buddies,
    I have a very similar error on WLI 9.2 MP2 on development mode with a cluster of managed servers on the same machine. I'm afraid that the automatic resource creation feature of dev mode is creating the error.
    The ...processes.UnlockService is jpd called by a JMS Broker thru a channel, and I considering it as the first suspect point.
    Any help is welcome.
    LOG CONTENT:
    <May 15, 2008 8:04:57 PM GMT-03:00> <Notice> <Stdout> <000000> <2008-05-15 20:04:57,575 [PERFO] localServer 10.10.10.10 xMDA  [iid=15899 prd=TC DATA act=INSTALL otp=I onb=00011552111 cid=12345189 mrt=]  END Designar_TCDATA OK>
    <May 15, 2008 8:04:57 PM GMT-03:00> <Error> <WLI> <000000> <Exception processing com.oi.integra.provisioning.lockManager.processes.UnlockService
    java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.deployWorkshopQueues(EJBGenerator.java:178)
         at com.bea.wli.knex.runtime.core.dispatcher.DispResources.deployQueues(DispResources.java:727)
         at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:671)
         Truncated. see log file for complete stacktrace
    java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.ensureQueue(EJBGenerator.java:442)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.ensureWorkshopQueues(EJBGenerator.java:412)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator$3.run(EJBGenerator.java:194)
         Truncated. see log file for complete stacktrace
    java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator.doesQueueExist(EJBGenerator.java:359)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator$6.run(EJBGenerator.java:449)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         Truncated. see log file for complete stacktrace
    javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getProxy(MBeanHomeImpl.java:68)
         at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:88)
         at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getAdminMBean(MBeanHomeImpl.java:265)
         at com.bea.wli.knex.runtime.core.bean.WLSUtil.getWorkshopJMSServer(WLSUtil.java:713)
         at com.bea.wli.knex.runtime.core.bean.EJBGenerator$5.run(EJBGenerator.java:372)
         Truncated. see log file for complete stacktrace
    >
    java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)

  • How to use single Timer to generate PWM PULSE, Pulse ON time measuremen​t, Event time measuremen​t1,Event time measuremen​t2

    Hi,
    I am planning to use a single Timer to generate PWM PULSE, Pulse ON time  measurement, Event time measurement1,Event time measurement2 some one please suggest me how can I achive this.
    Thanks in advance..
    Michael

    Hi Michael,
    It would be really good to understand your application a little more so that any specific needs that you have may be met. In the meantime, I would also suggest searching on ni.com for "pwm" or other keywords that relate to your application. You will see a faceted navigation on the left side that allows you to narrow your search for example code, tutorials, etc.
    Please post back with more information and the community will be able to help out with suggestions.
    ni.com search for "pwm"
    Mark E.
    Precision DC Product Support Engineer
    National Instruments
    Digital Multimeters (DMMs) and LCR Meters
    Programmable Power Supplies and Source Measure Units

  • WLI FTP File Event Generator

    Hi,
    I'm using a FTP file event Generator from my local machine (Windows) to an AIX machine and I've got this java exception:
    2007-05-29 15:28:06,781 ERROR (InternalLogger.java:65) - Unexpected error when parsing file
    Throwable: java.util.NoSuchElementException: Unix-List: Invalid Number Format
    Stack Trace:
    java.util.NoSuchElementException: Unix-List: Invalid Number Format
    at com.bea.control.FtpFile.parseUnixListLine(FtpFile.java:189)
    at com.bea.control.FtpFile.<init>(FtpFile.java:35)
    at com.bea.control.FtpClient.parseFileNames(FtpClient.java:379)
    at com.bea.control.FtpClient.getFiles(FtpClient.java:328)
    at com.bea.control.FileResource.ftpGetFiles(FileResource.java:1393)
    - My Event configuration:
    FTP Local Directory: /dir/local/
    Directory: /dir/fileDir/{myFile}
    Archive Directory: /dir/archive/
    Error Directory: /dir/error/
    FYI It works fine when I'm using disk file event generator with the same test file.
    Some ideas ?
    Thx,
    Vincent
    Edited by VincentLacaes at 05/29/2007 9:14 AM

    Hi
    This is a problem in WLI 8.1 SP4, and is fixed with a patch.
    Please talk to any BEA Customer support Engineer, and ask for patch from CR213993.
    Thanks
    Ashok

  • WLI 10g3 JMS Event Generator for Foreign Queues

    Hi,
    Our requirement is to listen to messages on a remote destination on another weblogic instance (8.1).
    One option we are trying is create a foreign JMS Module on local server (10g3) to connect to the remote destination
    and use JMS Event Generator to poll for messages on the local Foreign JMS Module and fetch the message and publish this
    message into a message channel.
    This works fine when I have a local JMS Queue and JMS Event Generator tries to listen to it.
    But while trying to use JMS Event Generator against foreign JMS module we are getting stuck with error failed to establish JMS Session :
    <Jul 8, 2009 12:26:29 PM IST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: foreignGenEventName is unable to connect to the JMS destination or bind to JCA resource adapter: test.mydestination. Connection failed after 64 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
    <Jul 8, 2009 12:26:29 PM IST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: foreignGenEventName is unable to connect to the JMS destination: test.mydestination. The Error was:
    weblogic.jms.common.JMSException: Error creating session
    Nested exception: weblogic.jms.common.JMSException: Error creating session
    Nested exception: weblogic.jms.common.JMSException: Error creating session
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server AdminServer
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:AdminServer'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:AdminServer'>
    Any pointers to a possible issue will eb really helpful.
    Thanks,
    CA

    Varun,
    Thanks for your inputs. Regarding the possibility of misconfiguring the ForeignJMSServer , we are able to view the remote destinationname (also the jndi binding name) in the jndi tree of the local server console, which in my opinion translates to a valid configuration.
    Can anyone let me know if this issue is fixed in 10.3 as there is a CR raised in the 10.0 version as well for this?
    CR332983
    CR326377  It was not possible to deploy an MDB while connecting to a foreign JMS provider through WLS foreign server resources configured in a JMS module.
    Thanks,
    CA
    Edited by: user1549937 on Jul 9, 2009 4:26 AM

Maybe you are looking for