Weblogic 9.2 Error in poll for fd=60, revents=32

hello,
Glad to talk with you。
When my web application running on weblogic 9.2,it often happens a problem, as follows:
<2010-7-14 下午01时15分26秒 CST> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
weblogic.utils.NestedError: Error adding FD to epoll.
weblogic.utils.NestedError: Error adding FD to epoll
at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:86)
at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:211)
at weblogic.servlet.internal.VirtualConnection.requeue(VirtualConnection.java:323)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1267)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1353)
Truncated. see log file for complete stacktrace
java.io.IOException: epoll_ctl failed: Bad file descriptor
at jrockit.ext.epoll.EPoll.epollEnableOneshot(II)V(Unknown Source)
at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:72)
at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:211)
at weblogic.servlet.internal.VirtualConnection.requeue(VirtualConnection.java:323)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1267)
Truncated. see log file for complete stacktrace
and another problem:
<Error> <HTTP> <BEA-101083> <Connection failure.
java.net.SocketException: Error in poll for fd=60, revents=32
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:133)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
thanks
regards,
lijun

Hi,
For WLS version 9.2 there is a Fix Available for the same issue : CR309671 Please contact Oracle support to get the Patch (CR309671).
After BEA/Oracle integration the Patch Naming convention is changed so to get the TAR version of the Patch Number u need to contact Oracle Support.
Thanks
Jay SenSharma
http://weblogic-wonders.com/ (WebLogic Wonders Are Here)

Similar Messages

  • Getting SocketException: Error in poll for fd: 'nn', revents 'nn+n'

              I'm running WL 5.1 SP9 on a HP9000 HPUX 11.0 with JRE 1.2.2-06 and I get the following:
              java.net.SocketException: Error in poll for fd: '21', revents: '25'
                   at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:304)
                   at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              Any help appreciated.
              Please cc my email if possible
              Thanks
              Ricky
              

    Derrick,
    I believe that this is a spurious error caused by a HTTP client which
    doesn't close the socket cleanly. This exception should be squelched in
    newer versions of the product. Until you can upgrade I believe you can
    safely ignore this message.
    Regards,
    Adam
    "Derrick" <[email protected]> wrote in message
    news:3a7834ef$[email protected]..
    >
    I am running apps server 5.1 on LINUX kernal 2.2 and using the POSIXperformance pack
    that was listed in a thread on this newsgroup (libmuxer.so) and am gettingthe following
    error sporatically...
    Wed Jan 31 11:39:15 EST 2001:<E> <HTTP> Connection failure
    java.net.SocketException: Error in poll for fd: '30', revents: '24'
    atweblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Has anyone seen this error and if so, does this perofrmance pack have knowissues
    with lost FDs? Should I run the app server without a performance pack ?
    thanks in advance for you help.

  • RMAN-10011: synchronization error while polling for rpc 8, action=startdefa

    Could anybody explain what is this error message caused by?
    TIA
    The entire spool below:
    051107064744: NetBackup RMAN Backup Started
    ORACLE_SID=db02
    backup_type=cold
    number_of_channels=2
    Started by: Oracle
    051107064745: Checking database status
    051107064745: Database status: OPEN
    051107064745: Getting database password
    051107064746: Checking database password
    051107064746: Database password: Valid
    051107064746: Checking Database mode
    051107064746: Database mode: NOARCHIVELOG
    051107064746: Shutdown no archive
    051107064838: RMAN BACKUP STARTED
    Recovery Manager: Release 10.1.0.4.0 - 64bit Production
    Copyright (c) 1995, 2004, Oracle. All rights reserved.
    connected to target database: db02 (DBID=3504436532)
    RMAN> connect catalog *
    2> run
    3> {
    4> sql 'alter session set sort_area_size=12582912';
    5> sql 'alter session set sort_area_retained_size=1048576';
    6> allocate channel t1 type 'SBT_TAPE' parms="ENV=(NB_ORA_POLICY=ORA_solcdi02, NB_ORA_SERV=sun4)"
    7> format 'df_%d_%p_%u_%t';
    8> set limit channel t1 maxopenfiles=1;
    9> allocate channel t2 type 'SBT_TAPE' parms="ENV=(NB_ORA_POLICY=ORA_solcdi02, NB_ORA_SERV=sun4)"
    10> format 'df_%d_%p_%u_%t';
    11> set limit channel t2 maxopenfiles=1;
    12> backup database filesperset=64
    13> include current controlfile;
    14> sql 'alter database open';
    15> release channel t1;
    16> release channel t2;
    17> }
    18>
    connected to recovery catalog database
    starting full resync of recovery catalog
    full resync complete
    sql statement: alter session set sort_area_size=12582912
    sql statement: alter session set sort_area_retained_size=1048576
    allocated channel: t1
    channel t1: sid=160 devtype=SBT_TAPE
    channel t1: VERITAS NetBackup for Oracle - Release 5.1 (2004122521)
    allocated channel: t2
    channel t2: sid=159 devtype=SBT_TAPE
    channel t2: VERITAS NetBackup for Oracle - Release 5.1 (2004122521)
    Starting backup at 11-MAY-07
    channel t1: starting full datafile backupset
    channel t1: specifying datafile(s) in backupset
    input datafile fno=00005 name=/oradata/10gid/u01/grid102/grid102/mgmt.dbf
    input datafile fno=00006 name=/oradata/10gid/u01/grid102/grid102/mgmt_ecm_depot1.dbf
    input datafile fno=00007 name=/oradata/10gid/u01/grid102/grid102/system02.dbf
    input datafile fno=00004 name=/oradata/10grid/u01/grid102/grid102/users01.dbf
    channel t1: starting piece 1 at 11-MAY-07
    channel t2: starting full datafile backupset
    channel t2: specifying datafile(s) in backupset
    input datafile fno=00008 name=/oradata/10ggrid/u01/grid102/grid102/mngmecm02.dbf
    input datafile fno=00001 name=/oradata/10ggrid/u01/grid102/grid102/system01.dbf
    input datafile fno=00002 name=/oradata/10ggrid/u01/grid102/grid102/undotbs01.dbf
    input datafile fno=00003 name=/oradata/10ggrid/u01/grid102/grid102/sysaux01.dbf
    channel t2: starting piece 1 at 11-MAY-07
    channel t2: finished piece 1 at 11-MAY-07
    piece handle=df_GRID102_1_19ihecmm_622277334 comment=API Version 2.0,MMS Version 5.0.0.0
    channel t2: backup set complete, elapsed time: 00:06:05
    channel t2: starting full datafile backupset
    channel t2: specifying datafile(s) in backupset
    including current controlfile in backupset
    channel t2: starting piece 1 at 11-MAY-07
    channel t2: finished piece 1 at 11-MAY-07
    piece handle=df_GRID102_1_1aihed24_622277700 comment=API Version 2.0,MMS Version 5.0.0.0
    channel t2: backup set complete, elapsed time: 00:00:35
    channel t1: finished piece 1 at 11-MAY-07
    piece handle=df_GRID102_1_18ihecmm_622277334 comment=API Version 2.0,MMS Version 5.0.0.0
    channel t1: backup set complete, elapsed time: 00:06:48
    Finished backup at 11-MAY-07
    Starting Control File and SPFILE Autobackup at 11-MAY-07
    piece handle=c-3404436532-20070511-00 comment=API Version 2.0,MMS Version 5.0.0.0
    Finished Control File and SPFILE Autobackup at 11-MAY-07
    sql statement: alter database open
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-10010: error while checking for RPC completion
    RMAN-10011: synchronization error while polling for rpc 8, action=startdefault
    Recovery Manager complete.
    051107065708: RMAN BACKUP FAILED, RMAN exit status=1
    051107065708: Cleaning log file (removing passwords)
    051107065709: Error Log Check
    051107065837: Rman Stat Generator
    051107065956: Backup Html Generator
    051107065956: NetBackup RMAN Backup Finished
    ######################################################

    Check on metalink:
    RMAN-10011: synchronization error while polling for rpc 3, action=startdefault
    Note:429572.1
    Werner

  • Just noticed error in samples for "Spry Rating"

    Hello, everyone.
    Just a heads-up if you are using the Spry Rating Widget.
    According to the samples page at http://labs.adobe.com/technologies/spry/samples/rating/RatingSample.html if you want to disable multiple votes (at least until page refresh) you set the option "allowMultipleVoting:false".
    It should be "allowMultipleRating:false".
    Took me almost an hour to figure this one out.  Hope this saves a few people some trouble.
    ^_^

    disregard. sorry.
              Paul Rowe wrote in message <[email protected]>...
              >Howdy;
              >
              > I just installed SP9 on my Redhat Linux 6.2 WL Server. The following
              >errors started to appear (lots of them):
              >
              >Thu May 10 09:10:22 PDT 2001:<E> <HTTP> Connection failure
              >java.net.SocketException: Error in poll for fd: '73', revents: '59'
              >
              > I noticed the server doesn't respond to HTTP requests sometimes, and the
              >HTTP side was completely down this morning. As a result I am reverting
              back
              >to SP8.
              >
              > Anyone else seeing this problem?
              >
              >
              >
              

  • Weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for ServletContext

    Hi,
         We have Installed Weblogic Server 10.3.5, applied the ADF Runtime 11.1.1.6 and applied the patch 11.1.2.4.0.
         All the Deployment libraries are appearing in the server.
    When we try to deploy a simple application, we are getting below error.
    [05:07:29 PM] Deploying Application...
    [05:07:30 PM] [Deployer:149193]Operation 'deploy' on application 'JSFPageTest_Project1_JSFPageTest' has failed on 'AdminServer'
    [05:07:30 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application JSFPageTest_Project1_JSFPageTest on AdminServer.: Failed to load webapp: 'JSFPageTest-ViewController-context-root'.
    [05:07:30 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'JSFPageTest-ViewController-context-root'
    [05:07:30 PM] Caused by: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@68993675[app:JSFPageTest_Project1_JSFPageTest module:JSFPageTest-ViewController-context-root path:/JSFPageTest-ViewController-context-root spec-version:2.5]", defined in weblogic.xml [Extension-Name: jsf, Specification-Version: 2, exact-match: false]
    [05:07:30 PM]   See server logs or server console for more details.
    [05:07:30 PM] weblogic.application.ModuleException: Failed to load webapp: 'JSFPageTest-ViewController-context-root'
    [05:07:30 PM] Deployment cancelled.
    [05:07:30 PM] ----  Deployment incomplete  ----.
    [05:07:30 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    Regards,
    Lakshmi

    looks like you didn't install the application development runtime on WLS, or if you did, you either forgot to extend your domain with the JRF or installed the wrong version of the application development runtime.

  • Error  While Polling Database changes using Custom SQL

    Hi,
    I am using Oralce SOA Suite 11g DbAdapter for polling Database changes.
    My source database is DB2,I am using custom query for polling the changes in source database.
    I am using "Update an External Sequencing Table on a Different Database" polling Strategy
    Query section of the Mapping file is as follows.
    <querying xsi:type="query-policy">
    <queries>
    <query name="ReceiveF554102TXEDataSelect" xsi:type="read-all-query">
    <call xsi:type="sql-call">
    <sql><![CDATA[SELECT FILE_NAME, LIBRARY_NAME,
                   USER_NAME, SEQUENCE_NUM,
                   JOURNAL_CODE, ENTRY_TYPE, TIME_STAMP, JOB_NAME, JOB_USER,
                   JOB_NUMBER, PROGRAM_NAME, ARM_NUMBER, ADDRESS_FAMILY, RMT_ADDRESS,
                   REMOTE_PORT, SYSTEM_NAME, REL_RECORD, OTRCLN, IBMCU, IBITM, IBLITM,
                   IBAITM, IBY55ETAFR, IBY55ETATH, IBY55NUM01, IBY55NUM02, IBY55NUM03,
                   IBY55NUM04, IBY55NUM05, IBY55NUM06, IBY55NUM07, IBY55NUM08,
                   IBY55NUM09, IBY55NUM10, IBELM01, IBELM02, IBELM03, IBELM04, IBELM05, IBY55STR01,
                   IBY55STR02, IBY55STR03, IBY55STR04, IBY55STR05, IBY55CHA01,
                   IBY55CHA02, IBY55CHA03, IBY55CHA04, IBY55CHA05, IBY55DAT01, IBY55DAT02,
                   IBY55DAT03, IBY55DAT04, IBY55DAT05, IBUSER, IBPID, IBJOBN, IBUPMT,
                   IBUPMJ FROM PY_JRNMON.F554102T WHERE ((TIME_STAMP > (SELECT LAST_READ_DATE FROM SOALIB.SOASEQHDR WHERE (TABLE_NAME = 'F554102T'))) AND (TIME_STAMP < SYSDATE)) ORDER BY TIME_STAMP ASC]]> </sql>
    </call>
    <reference-class>ReceiveF554102TXEData.F554102T</reference-class>
    <lock-mode>none</lock-mode>
    <container xsi:type="list-container-policy">
    <collection-type>java.util.Vector</collection-type>
    </container>
    </query>
    </queries>
    <delete-query xsi:type="delete-object-query">
    <call xsi:type="sql-call">
    <sql>UPDATE SOALIB.SOASEQHDR SET LAST_READ_DATE = #LAST_READ_DATE WHERE (TABLE_NAME = 'F554102T')</sql>
    </call>
    </delete-query>
    </querying>
    I am getting following Error after defining the custom SQL in my mapping.xml file. (After executing the Created Process)
    Caused by: BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by BINDING.JCA-11626
    Query Not Found Exception.
    Could not find Named Query [ReceiveSampleCustomPollSelect] with ? arguments, belonging to Descriptor [ReceiveSampleCustomPoll.F554102T] for [oracle.tip.adapter.db.DBActivationSpec@2ec733b0] inside of mappings xml file: [ReceiveSampleCustomPoll-or-mappings.xml].
    You may have changed the queryName info in either the _db.jca or toplink-mappings.xml files so that they no longer match.
    Make sure that the queryName in the activation/interactionSpec and in the Mappings.xml file match. If an old version of the descriptor has been loaded by the database adapter, you may need to bounce the app server. If the same descriptor is described in two separate Mappings.xml files, make sure both versions include this named query.
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake. This polling process will shut down, unless the fault is related to processing a particular row, in which case polling will continue but the row will be rejected (faulted).
         at oracle.tip.adapter.db.exceptions.DBResourceException.createNonRetriableException(DBResourceException.java:653)
         at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:619)
         at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:291)
         at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:883)
         at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
         at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:266)
         at oracle.tip.adapter.db.InboundWork.init(InboundWork.java:322)
         at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:526)
         ... 4 more
    Caused by: BINDING.JCA-11626
    Query Not Found Exception.
    Could not find Named Query [ReceiveSampleCustomPollSelect] with ? arguments, belonging to Descriptor [ReceiveSampleCustomPoll.F554102T] for [oracle.tip.adapter.db.DBActivationSpec@2ec733b0] inside of mappings xml file: [ReceiveSampleCustomPoll-or-mappings.xml].
    You may have changed the queryName info in either the _db.jca or toplink-mappings.xml files so that they no longer match.
    Make sure that the queryName in the activation/interactionSpec and in the Mappings.xml file match. If an old version of the descriptor has been loaded by the database adapter, you may need to bounce the app server. If the same descriptor is described in two separate Mappings.xml files, make sure both versions include this named query.
         at oracle.tip.adapter.db.exceptions.DBResourceException.queryNotFoundException(DBResourceException.java:694)
         at oracle.tip.adapter.db.ox.TopLinkXMLProjectInitializer.initializeQuery(TopLinkXMLProjectInitializer.java:1238)
         at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:728)
         ... 8 more
    Help required to fit custom SQL in mapping.xml file for complex queries.
    Thanks,
    Arun Jadhav.

    "Execuite Custom SQL" in DB adapter and you'l get it.
    But in this case you'll have to implement your own polling strategy (if you need one).
    If you want to use one of the predefined polling strategy you should use "Poll for New or Changed records" and import all the tables you use and connect them in wizard.

  • Java.io.IOException: error in poll: Input/output error

    Hello,
    My server is running on Linux 7.1, IBM JDK 1.3 and WLS 6.1. When the
    following error is thrown in weblogic.log, the server is stopped by this
    error. This error keeps happening once it occurs for about every one second.
    ####<Dec 23, 2001 3:12:46 AM SGT> <Error> <Posix Performance Pack>
    <MyPC.1st-cube.com> <myserver> <ExecuteThread: '12' for queue:
    'default'><><><000000> <Uncaught Throwable in processSockets>
    java.io.IOException: error in poll: Input/output error
    at weblogic.socket.PosixSocketMuxer.poll(Native Method)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Can anyone help?
    Thanks.
    Regards,
    Mo

    I too am seeing a slight variation of this error with JM 1.3.1. Unfortunately, the message has since been deleted. Any ideas?
    java.io.IOException: Error in encoded stream, got 2
    at com.sun.mail.util.BASE64DecoderStream.decode(BASE64DecoderStream.java:148)
    at com.sun.mail.util.BASE64DecoderStream.read(BASE64DecoderStream.java:53)
    at com.sun.mail.util.BASE64DecoderStream.read(BASE64DecoderStream.java:78)
    at java.io.FilterInputStream.read(FilterInputStream.java:90)
    at javax.activation.DataHandler.writeTo(DataHandler.java:289)
    at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1147)
    at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:668)
    at javax.mail.internet.MimeMultipart.writeTo(MimeMultipart.java:233)
    at com.sun.mail.handlers.multipart_mixed.writeTo(multipart_mixed.java:67)
    at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:839)
    at javax.activation.DataHandler.writeTo(DataHandler.java:295)

  • How to get rid of the weblogic.kernel.Default errors and warning?

    Hi there,
    When i'm running my application deployed on WLS8.1 SP3 and the application is running fine, but the following error and warnings were thrown.
    2004-08-05 11:26:30,453 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] ERROR com.bea.wlw.runtime.core.util.Config - Failed to obtain connection to datasource=cgDataSource, using generic DB properties
    <Aug 5, 2004 11:26:30 AM SGT> <Error> <WLW> <000000> <Failed to obtain connection to datasource=cgDataSource, using generic DB properties>
    2004-08-05 11:27:12,281 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.default.elementattributes
    2004-08-05 11:27:12,282 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.default.elementattributes', using defaults.
    2004-08-05 11:27:12,308 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.system.groupIdCache.elementattributes
    2004-08-05 11:27:12,308 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.system.groupIdCache.elementattributes', using defaults.
    2004-08-05 11:27:12,386 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.region.CodeTableCache.elementattributes
    2004-08-05 11:27:12,386 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.region.CodeTableCache.elementattributes', using defaults.
    2004-08-05 11:27:13,527 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN com.bea.wlw.netui.script.el.NetUIReadVariableResolver - Could not create a ContextFactory for type "com.bea.netuix.servlets.script.PortalVariableResolver$PortalContextFactory" because the ContextFactory implementation class could not be found.
    May i know why this is so? How to get rid of these error and warnings?
    Thanks
    Derek
    Message was edited by derekchan at Aug 4, 2004 8:41 PM
    Message was edited by derekchan at Aug 4, 2004 8:42 PM

    you didnt seem to have configured the datasource / connection pool / database control with proper db properties
    you should check your configuration to see if you have done it right and then you should check your application and the properties settings in the controls to ensure they are right.

  • Error targeting server for the EJB module while deploying the sample banking application

    I am currently having a very difficult time attempting to deploy the
    example banking application that I downloaded from the BEA website. I
    have followed all of the steps in the "Hands On: Deploying the Sample
    Banking Application" document, and I do fine until I get to the next to
    last step. When I attempt to target the server for the EJB module, the
    deployment process generates the error that I have included at the end
    of this message.
    I can get to the login.html page under "http://localhost:7001/banking/",
    but after that I can't go further.
    Any suggestions. BTW, in case you haven't figured it out, I'm brand new
    to BEA WebLogic server.
    Thanks in advance for any help you can offer.
    Scott
    Error deploying application \ejb:
    Unable to deploy EJB: \ejb from \ejb:
    Compiler failed
    executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
    at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
    at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy11.addDeployment(Unknown Source)
    at
    weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy68.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
    at
    weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    The deployment process invokes javac internally to compile some generated classes.
    Do you have javac installed and in the path?
    Seth
    Scott Springer wrote:
    I am currently having a very difficult time attempting to deploy the
    example banking application that I downloaded from the BEA website. I
    have followed all of the steps in the "Hands On: Deploying the Sample
    Banking Application" document, and I do fine until I get to the next to
    last step. When I attempt to target the server for the EJB module, the
    deployment process generates the error that I have included at the end
    of this message.
    I can get to the login.html page under "http://localhost:7001/banking/",
    but after that I can't go further.
    Any suggestions. BTW, in case you haven't figured it out, I'm brand new
    to BEA WebLogic server.
    Thanks in advance for any help you can offer.
    Scott
    Error deploying application \ejb:
    Unable to deploy EJB: \ejb from \ejb:
    Compiler failed
    executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
    at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
    at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy11.addDeployment(Unknown Source)
    at
    weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy68.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
    at
    weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • Sender SFTP Adapter channel is not polling for files

    Hello All,
    Couple of SFTP sender adapter channel was failing in Developent system with u201Cdirectory listingu201D error.All SFTP sender channels stopped polling for the files in Developent system  . We were unable to find the reason for adapter failure, Hence we restarted the j2ee server and adapter started polling files. Later we are facing the same issue in Quality system. THe adapter cahnnel is not polling files in Quality system even.
    All lean tool adapters were showing the u201CHost key was not accepted erroru201D on 27th of Feb . As per the other channel trace, the time stamp of last successful polling and error time stamp of lean tool sender channels are exactly same
    Eventhough two communication channels access the same SFTP adapter, one communicationchannel is getting 'Host key was not accepted error' but in other communication channel, files are getting picked.
    Please let me know the solution if you have come accross this issue previously
    Regards,
    DilipKumar

    Hi Mike,
    Thanks for your reply.
    Its not a standard SFTP adapter rather its a C-BURGER SFTP adapter.
    Sorry I did not mention this in my previous post
    Regards,
    DilipKumar

  • File Adapter going into infinite mode while polling for the file

    Hi,
    I am facing an issue while the file adapter is reading the data from the file.
    If the file from which it is reading has been deleted it keeps on polling for it infinite number of times and also doesn't pops out with any error message. Is there any method that after polling for some time period we can pop out a message that the particular file is not available and then the file adapter should stop polling for the file.Anyone has some ideas about this. Any pointers will be of great help.
    Thanks
    Vinay
    Message was edited by:
    soachd

    Hi soachd,
    As far as I understand polling is infinite process. You need to adopt this strategy if you are expecting some thing to happen all the time or may be when you want to be ready when ever an expected event happens. This provides a real time solution but with the downside of infinite execution.
    Hope it helps.
    Kalyan.

  • ICal yields "Error during PUT for mailto:valid@email: iMIP request failed"

    Hello,
    I'm trying to bring up an iCal server (using Mac OS X Lion 10.7.3 Server on a Mac Mini). The basic configuration runs fine. But when I tried to enable eMail invitations, I got stuck with those messages in the error log:
    [twistedcaldav.scheduling.imip#error] Could not do server-to-imip request : <twistedcaldav.scheduling.imip.ScheduleViaIMip object at 0x10075e5d0> User timeout caused connection failure.
    [twistedcaldav.scheduling.scheduler.ScheduleResponseQueue#error] Error during PUT for mailto:valid@email: iMIP request failed
    My configuration settings:
    calendar:Scheduling:CalDAV:EmailDomain = ""
    calendar:Scheduling:CalDAV:HTTPDomain = ""
    calendar:Scheduling:CalDAV:AddressPatterns = _empty_array
    calendar:Scheduling:iMIP:Sending:Server = "valid.mail.server"
    calendar:Scheduling:iMIP:Sending:UseSSL = no
    calendar:Scheduling:iMIP:Sending:Username = "valid@email"
    calendar:Scheduling:iMIP:Sending:Address = "valid@email"
    calendar:Scheduling:iMIP:Sending:Password = "safe_password"
    calendar:Scheduling:iMIP:Sending:Port = 25
    calendar:Scheduling:iMIP:Enabled = yes
    calendar:Scheduling:iMIP:MailGatewayPort = 62310
    calendar:Scheduling:iMIP:Receiving:Server = "valid.mail.server"
    calendar:Scheduling:iMIP:Receiving:UseSSL = yes
    calendar:Scheduling:iMIP:Receiving:Username = "valid_email"
    calendar:Scheduling:iMIP:Receiving:PollingSeconds = 30
    calendar:Scheduling:iMIP:Receiving:Type = "imap"
    calendar:Scheduling:iMIP:Receiving:Password = "safe_password"
    calendar:Scheduling:iMIP:Receiving:Port = 993
    calendar:Scheduling:iMIP:AddressPatterns:_array_index:0 = "mailto:.*"
    calendar:Scheduling:iMIP:MailGatewayServer = "valid.mail.server"
    calendar:Scheduling:iSchedule:Enabled = no
    calendar:Scheduling:iSchedule:Servers = "servertoserver.xml"
    calendar:Scheduling:iSchedule:AddressPatterns = _empty_array
    It does not even try to connect to the given smtp server. How do I proceed?

    I dug into the sources, and am now smarter
    the above settings are invalid, because of the gateway (this has to be iCal itself):
    calendar:Scheduling:iMIP:MailGatewayServer = "localhost"
    Now the IMAP server is being asked, but now I have the next problem:
    [mailgateway] 2012-03-27 11:14:37+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadFactory#debug] Scheduling next IMAP4 poll
    [mailgateway] 2012-03-27 11:15:07+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] RECEIVED: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
    [mailgateway] 2012-03-27 11:15:07+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] IMAP servergreeting
    [mailgateway] 2012-03-27 11:15:07+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] SENDING: 0001 AUTHENTICATE PLAIN
    [mailgateway] 2012-03-27 11:15:07+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] RECEIVED: +
    [mailgateway] 2012-03-27 11:15:07+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] SENDING: 1GNhbEwhZHNwZXJ0LmRlAFlpZXE5YW==
    [mailgateway] 2012-03-27 11:15:09+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] RECEIVED: 0001 NO [AUTHENTICATIONFAILED] Authentication failed.
    [mailgateway] 2012-03-27 11:15:09+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] IMAP authenticate failed for valid@email, trying login
    [mailgateway] 2012-03-27 11:15:09+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] SENDING: 0002 LOGIN "valid@email" "valid_password"
    [mailgateway] 2012-03-27 11:15:16+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#debug] RECEIVED: 0002 NO [AUTHENTICATIONFAILED] Authentication failed.
    [mailgateway] 2012-03-27 11:15:16+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadProtocol#error] IMAP login failed for valid@email
    [mailgateway] 2012-03-27 11:15:16+0200 [IMAP4DownloadProtocol,client] [twistedcaldav.mail.IMAP4DownloadFactory#debug] IMAP factory connection lost

  • Polling for database updates fails to update sequence file/table

    I have a small system to poll for changes to a database table of student details. It consists of:
    Database adapter, which polls the database for changes, retreives a changed row, and passes the generated XML to -
    "receive" router service, which simply passes the retrieved database XML data to -
    "execute" router service, which transforms the XML and passes the new message to -
    File Adapter, which writes the transformed XML to a file.
    The problem is that the database polling is not updating the sequence recorder - I have tried using a sequence file which stores the personnumber, a sequence table which stores the personnumber and a sequence table which stores the last-updated timestamp. In all cases the database adapter successfully reads the sequence file/table and retreives the correct row, based on the sequence value ( I have tested this by manually changing the sequence value), the data is transformed and a correct xml file is created, but the system then fails to update the sequence file/table so that when the next polling time comes around the very same database row is extracted again and again and again.
    In the ESB control panel I have one error: "Response payload for operation "receive" is invalid!"
    The Trace is:
    oracle.tip.esb.server.common.exceptions.BusinessEventRejectionException: Response payload for operation "receive" is invalid! at oracle.tip.esb.server.service.EsbRouterSubscription.processEventResponse(Unknown Source) at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source) at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(Unknown Source) at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(Unknown Source) at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:281) at oracle.tip.adapter.db.InboundWork.onMessageImpl(InboundWork.java:1381) at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1291) at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1262) at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:501) at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:401) at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819) at java.lang.Thread.run(Thread.java:595)
    The payload is:
    <PersonCollection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/top/ISSSimIN">
    <Person>
    <name>Bob</name>
    <surname>Stupid</surname>
    <istatus>2</istatus>
    <active>Active</active>
    <personnumber>3001</personnumber>
    <role>Staff</role>
    <organization>TEX</organization>
    <updateTimestamp>2007-11-29T14:06:55.000+00:00</updateTimestamp>
    </Person>
    </PersonCollection>
    The payload above is the XML output from the Database adapter, the xsd for which was autogenerated by JDeveloper, so I don't understand how it can be invalid.
    I have only been working with ESB for 3 days, but half of that time has now been spent stuck on this issue. Anyone got any ideas??
    Richard

    You need to be careful. Submit and committing to the database are two different things.
    Submit on a page (and autoSubmit the property) are only posting the changes you typed into the field, back down to the application server. NOTHING is happening with the database at this point. So the applications's internal "cache" of records (using something like ADF BC) is holding the changes but the database doesn't know anything. So if you quit now, no changes will go to the database.
    These changes onlyget submitted down to the app server when you do some sort of action like press a button. Simply navigating fields will be doing nothing back to the app server. If you add autoSubmit then you will automatically submit the changes on that field down to the app server when you leave the field (but again, this is not touching the database)
    You have to explicitly add a COMMIT operation to save those changes to the database.
    Maybe if you try in a simple EMP example and send us your findings we can help direct you further.
    Regards
    Grant

  • DBAdapter polling for new or changed records not issuing callback?

    I have a process which includes a partner link with a database adapter.
    The database adapter is to poll a table for new records using an external database server.
    I have no relationships setup, it's a single-table query.
    The adapter is configured to delete rows after they are read.
    I have the receive process of that partner link tied to a receive activity and its own input variable assigned.
    My process compiles and deploys successfully. When I initiate the process through the BPEL console, the instance of the process waits at the receive activity and nothing happens, even after I manually add records to the table being polled. (which do get deleted, apparently by the partner link.)
    I have other dbadapter partner links in the same process using the same connection that work fine, specifically using procedure execution and custom sql queries.
    I can't find any errors or warnings about this, and the interactions manager in the BPEL Console allows me to manually send a message to the instance, allowing it to continue.
    The application server is 10.1.3.1.0 and I am using JDeveloper 10.1.3.2.0.4066
    Message was edited by:
    Paul.Dunbar
    Follow-up:
    When I set activation logging to debug, I get the following in domain.log
    <2007-04-03 08:15:28,591> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.TopLinkLogger log> client acquired
    <2007-04-03 08:15:28,591> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.TopLinkLogger log> SELECT SOME_ID, SOME_VALUE FROM PAULD.SOME_TABLE ORDER BY SOME_ID ASC
    <2007-04-03 08:15:28,592> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.TopLinkLogger log> client released
    From looking at this it may be that the callback to the receive activity is not occurring?
    Message was edited by:
    Paul.Dunbar
    Second follow-up:
    I'm still having this issue but must give up on troubleshooting.
    Documentation on polling adapter says nothing about handling callbacks, I've been trying to use correlations here with no luck. I'm also not seeing any documentation about setting up correlations for use with the database adapter.
    now the issue I'm having is that the inbound database adapter is still polling my table and deleting records, even though I've undeployed my process.

    I did not. Currently the manual recovery area is empty. I've tried re-deploying my process and am now getting the following in my logs (all debugging on):
    <2007-04-05 08:01:36,671> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::acquire> Acquired read lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,671> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::release> Released lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,672> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::acquire> Acquired read lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,672> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::release> Released lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,678> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::getConnection> GOT CONNECTION 1 Autocommit = false
    <2007-04-05 08:01:36,681> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::closeConnection> CLOSE CONNECTION 0
    <2007-04-05 08:01:36,681> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::getConnection> GOT CONNECTION 1 Autocommit = false
    <2007-04-05 08:01:36,682> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::closeConnection> CLOSE CONNECTION 0
    <2007-04-05 08:01:36,686> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::acquire> Acquired read lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,687> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::release> Released lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,688> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::acquire> Acquired read lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,688> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::release> Released lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,688> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::acquire> Acquired write lock for SendEventNotice-1.0
    <2007-04-05 08:01:36,688> <DEBUG> <default.collaxa.cube.engine.data> <BaseProcessPersistenceAdaptor::updateMetaData> Updating process metadata [ domain = default, process = SendEventNotice, revision = 1.0, state = 0, lifecycle = 0 ]
    <2007-04-05 08:01:36,688> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::getConnection> GOT TX CONNECTION 1 Autocommit = false
    <2007-04-05 08:01:36,691> <DEBUG> <default.collaxa.cube.engine.dispatch> <BaseDispatchSet::receive> Receiving message log process event message 61b55bd8c71ae1e3:-3d66bcb1:111c1b2d4aa:-7f9c for set system
    <2007-04-05 08:01:36,691> <DEBUG> <default.collaxa.cube.engine.dispatch> <Dispatcher::adjustThreadPool> Allocating 1 thread(s); pending threads: 1, active threads: 0, total: 84
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine.dispatch> <DispatcherBean::send> Sent message to queue
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine> <DomainObserverRegistry::notify> Notifying observer class oracle.bpel.services.rules.DeploymentListener with aspect class com.collaxa.cube.engine.observer.ProcessStateChangeAspect for domain default
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine> <DomainObserverRegistry::notify> Notifying observer class com.collaxa.cube.engine.test.driver.deployment.BPELTestDeployer with aspect class com.collaxa.cube.engine.observer.ProcessStateChangeAspect for domain default
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine> <DomainObserverRegistry::notify> Notifying observer class oracle.bpel.services.workflow.task.PurgeTask with aspect class com.collaxa.cube.engine.observer.ProcessStateChangeAspect for domain default
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.services> <oracle.bpel.services.workflow.task.PurgeTask::update(ICubeAspect> Called for aspect com.collaxa.cube.engine.observer.ProcessStateChangeAspect
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine> <DomainObserverRegistry::notify> Notifying observer class oracle.tip.esb.configuration.deployment.bpel.BPELSvcDeploymentManager with aspect class com.collaxa.cube.engine.observer.ProcessStateChangeAspect for domain default
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine.dispatch> <SystemDispatchSet::fetchScheduled> Fetched message log process event message 61b55bd8c71ae1e3:-3d66bcb1:111c1b2d4aa:-7f9c from system queue for processing
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine.dispatch> <LogProcessEventMessageHandler::handle> Processing log process event message 61b55bd8c71ae1e3:-3d66bcb1:111c1b2d4aa:-7f9c
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine> <DomainObserverRegistry::notify> Notifying observer class com.collaxa.cube.engine.data.CubeInstanceCache with aspect class com.collaxa.cube.engine.observer.ProcessStateChangeAspect for domain default
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine> <DomainObserverRegistry::notify> Notifying observer class oracle.bpel.services.workflow.DeploymentListener with aspect class com.collaxa.cube.engine.observer.ProcessStateChangeAspect for domain default
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.services> <oracle.bpel.services.workflow.DeploymentListener::update(ICubeAspect> Called for aspect com.collaxa.cube.engine.observer.ProcessStateChangeAspect
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.engine> <DomainObserverRegistry::notify> Notifying observer class com.collaxa.cube.engine.core.BaseCubeProcess$ActivationObserver with aspect class com.collaxa.cube.engine.observer.ProcessStateChangeAspect for domain default
    <2007-04-05 08:01:36,693> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::onStateChanged State is changed for process 'bpel://localhost/default/SendEventNotice~1.0/', state=ON
    <2007-04-05 08:01:36,693> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - endpointActivation for portType=initialCoordination_ptt, operation=receive
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Looking up jca:address...
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Looking up WSDL Service jca:address for portType=initialCoordination_ptt and operation=receive
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Locating Resource Adapter for jca:address.. {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address: location='eis/DB/TST2' ManagedConnectionFactory='oracle.tip.adapter.db.DBManagedConnectionFactory' (properties: {Password=E466676A7A458FA6EBCFF72E13C04843, PlatformClassName=oracle.toplink.platform.database.oracle.Oracle10Platform, ConnectionString=jdbc:oracle:thin:@//lxdb2:1521/TST2, DriverClassName=oracle.jdbc.OracleDriver, UserName=SONRIS_DBA})
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Setting up Input Header Message QName: null
    <2007-04-05 08:01:36,693> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Setting up Input Header Part Name: null
    <2007-04-05 08:01:36,694> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::getConnection> GOT TX CONNECTION 2 Autocommit = false
    <2007-04-05 08:01:36,694> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Setting Adapter Name: Database Adapter
    <2007-04-05 08:01:36,694> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Determining Input and Output WSDL Message elements
    <2007-04-05 08:01:36,695> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Creating ActivationSpec...
    <2007-04-05 08:01:36,695> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Instantiating ActivationSpec oracle.tip.adapter.db.DBActivationSpec
    <2007-04-05 08:01:36,695> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Populating ActivationSpec oracle.tip.adapter.db.DBActivationSpec with properties: {MaxRaiseSize=1, MarkReadFieldName=DONE_READING, UseBatchDestroy=false, MarkUnreadValue=UNREAD, ReturnSingleResultSet=false, QueryName=initialCoordination, MarkReadValue=READ, MarkReservedValue=RESERVED, DescriptorName=initialCoordination.AnotherTable, NumberOfThreads=1, MappingsMetaDataURL=initialCoordination_toplink_mappings.xml, PollingStrategyName=LogicalDeletePollingStrategy, PollingInterval=5, SequencingFieldName=AN_ID, MaxTransactionSize=unlimited}
    <2007-04-05 08:01:36,697> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::closeConnection> CLOSE TX CONNECTION 1
    <2007-04-05 08:01:36,700> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Preparing ActivationSpec for Translation Service
    <2007-04-05 08:01:36,701> <DEBUG> <default.collaxa.cube.engine.dispatch> <BaseDispatchSet::acknowledge> Acknowledged message log process event message 61b55bd8c71ae1e3:-3d66bcb1:111c1b2d4aa:-7f9c
    <2007-04-05 08:01:36,705> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Preparing ActivationSpec for Connection Factory and Properties
    <2007-04-05 08:01:36,705> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Invoking endpointActivation() on Resource Adapter
    <2007-04-05 08:01:36,708> <INFO> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.DBResourceAdapter endpointActivation> Activating: oracle.tip.adapter.db.DBActivationSpec@4e7ed
    <2007-04-05 08:01:36,710> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.TopLinkLogger log> client acquired
    <2007-04-05 08:01:36,713> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.TopLinkLogger log> client released
    <2007-04-05 08:01:36,715> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.DBEndpoint start> About to schedule the inbound polling thread with the work manager. ActivationSpec: oracle.tip.adapter.db.DBActivationSpec@4e7ed
    <2007-04-05 08:01:36,716> <INFO> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.DBEndpoint start> Kicked off 1 threads.
    <2007-04-05 08:01:36,717> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.TopLinkLogger log> client acquired
    <2007-04-05 08:01:36,719> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.TopLinkLogger log> begin transaction
    <2007-04-05 08:01:36,721> <DEBUG> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.TopLinkLogger log> rollback transaction
    <2007-04-05 08:01:36,722> <ERROR> <default.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.InboundWork handleException> Non retriable exception during polling of the database ORABPEL-11624
    DBActivationSpec Polling Exception.
    Query name: [initialCoordination], Descriptor name: [initialCoordination.AnotherTable]. Polling the database for events failed on this iteration.
    If the cause is something like a database being down successful polling will resume once conditions change. Caused by Exception [TOPLINK-6024] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.exceptions.QueryException
    Exception Description: Modify queries require an object to modify.
    Query: UpdateObjectQuery(null).
    <2007-04-05 08:01:36,722> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [initialCoordination_ptt::receive(AnotherTableCollection)]Resource Adapter requested Process shutdown!
    <2007-04-05 08:01:36,723> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound>
    ORABPEL-11624
    DBActivationSpec Polling Exception.
    Query name: [initialCoordination], Descriptor name: [initialCoordination.AnotherTable]. Polling the database for events failed on this iteration.
    If the cause is something like a database being down successful polling will resume once conditions change. Caused by Exception [TOPLINK-6024] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.exceptions.QueryException
    Exception Description: Modify queries require an object to modify.
    Query: UpdateObjectQuery(null).
    As reflected in the log messages, the process is automatically turned off. Turning it back on is ineffective, the server turns it back off with the same exception.
    This is a separate issue, but I'm not seeing much reason for this to be happening either. I've scrapped the process and started over, using my own BPEL process that simulates what I would expect that the dbadapter is supposed to do when it's configured to poll for records.

  • Error marking transaction for rollback: java.lang.IllegalStateException in WLI 6.1 SP3

    Hi,
    The following exception occurs, when the workflow was waiting after it has made
    a synchronous call to an external system through WTC Interface.
    I had read Rob's comments earlier for WLI 6.1 SP1 on this exception that there
    would be a fix available for it in the next minor release. For your information,
    I had got this exception in WLI 6.1 SP3. Is still EJB Container's timeout excels
    the JTA's timeout? Can anybody help me out to find a fix for this problem?
    Thanks in Advance,
    Regards
    Jegadeesan.
    The Stack Trace is given below :
    <Error marking transaction for rollback: java.lang.IllegalStateException: Cannot
    mark the transaction for rollback. xid=4362:5b4c62b47adcc632, status=Rolled back.
    [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
    after 31 seconds
    Xid=4362:5b4c62b47adcc632(6932052),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=31,seconds left=30,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[ecwli001+admin_ecwli001]=(state=active),properties=({weblogic.jdbc=t3://147.149.116.70:50101}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=admin_ecwli001+147.149.116.70:50101+ecwli001+,
    Resources={})],CoordinatorURL=admin_ecwli001+147.149.116.70:50101+ecwli001+)]>
    java.lang.IllegalStateException: Cannot mark the transaction for rollback. xid=4362:5b4c62b47adcc632,
    status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
    timed out after 31 seconds
    Xid=4362:5b4c62b47adcc632(6932052),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=31,seconds left=30,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[ecwli001+admin_ecwli001]=(state=active),properties=({weblogic.jdbc=t3://147.149.116.70:50101}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=admin_ecwli001+147.149.116.70:50101+ecwli001+,
    Resources={})],CoordinatorURL=admin_ecwli001+147.149.116.70:50101+ecwli001+)]
         at weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(TransactionImpl.java:1492)
         at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:466)
         at weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.java:255)
         at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:215)
         at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:153)
         at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
         at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
         at com.bea.wlpi.server.principal.WLPIPrincipalBean_u7lmf4_EOImpl.getOrganizationInfo(WLPIPrincipalBean_u7lmf4_EOImpl.java:463)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getBusinessCalendarProcessor(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Timer.dateAdd(Unknown Source)
         at com.bea.wlpi.server.workflow.action.ActionTimedEvent.getScheduleTimestamp(Unknown
    Source)
         at com.bea.wlpi.server.workflow.action.ActionTimedEvent.execute(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
         at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Decision.activate(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Decision.activate(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
         at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
         at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
         at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
         at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
         at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
         at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
         at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
         at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
    Source)
         at com.bea.wlpi.server.workflow.Start.activate(Unknown Source)
         at com.bea.wlpi.server.workflow.Workflow.start(Unknown Source)
         at com.bea.wlpi.server.workflow.Workflow.instantiate(Unknown Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean$1.invoke(Unknown
    Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.performWithErrorHandling(Unknown
    Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.instantiate(Unknown
    Source)
         at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.instantiate(WorkflowProcessorBean_h7kt4j_EOImpl.java:692)
         at com.bea.wlpi.server.eventprocessor.EventProcessor.checkTrigger(Unknown Source)
         at com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(Unknown Source)
         at com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(Unknown Source)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:262)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:214)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1865)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    You could change the transaction timeout value, but I'd re-examine the
    application and see if the transaction times could be reduced some.
    29 seconds seems like a long time.

Maybe you are looking for