WLS 8.1SP2 and "already released" warning

We have tests where our EIS is down and the connection is denied, the RA
          sends a CONNECTION_ERROR_OCCURRED event, which causes the MC.destroy() call
          as it is supposed to, but we always see the following type of message:
          [java] <Apr 22, 2004 5:57:47 PM GMT-07:00> <Warning> <Connector>
          <BEA-190098> <Trying to release a resource that has already been released
          for HooXG8 Line NoTxn Adapter_eis/generic-full-lineJNDINAME.>
          This is a different behavior than our experiences on WLS6 or WLS7 and isn't
          correct. Any ideas why this is occurring?
          Eric

Similar Messages

WLS 8.1SP2 and AIX 5.1.0.0

After installing WLS 8.1 and the AIX supplement patch plus fixes to java1.4
I am still unable to bring up my server. The following error occurs:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<May 5, 2004 1:29:26 PM MDT> <Info> <WebLogicServer> <BEA-000377> <Starting
WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<May 5, 2004 1:29:28 PM MDT> <Info> <Configuration Management> <BEA-150016>
<This server is being started as the administration server.>
<May 5, 2004 1:29:28 PM MDT> <Info> <Management> <BEA-141107> <Version:
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284WebLogic XMLX
Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<May 5, 2004 1:29:30 PM MDT> <Notice> <Management> <BEA-140005> <Loading
domainconfiguration from configuration repository at
/users/interop8/bea/user_projects/domain/hooxsgb/./config.xml.>
<May 5, 2004 1:29:49 PM MDT> <Notice> <Log Management> <BEA-170019> <The
serverlog file
/users/interop8/bea/user_projects/domain/hooxsgb/myserver/myserver.logis
opened. All server side log events will be written to this file.>
<May 5, 2004 1:30:08 PM MDT> <Notice> <Security> <BEA-090082> <Security
initializing using security realm myrealm.>
<May 5, 2004 1:30:09 PM MDT> <Notice> <WebLogicServer> <BEA-000327>
<Starting WebLogic Admin Server "myserver" for domain "hooxsgb">
JVMDG217: Dump Handler is Processing a Signal - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to
/users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.tx
t
JVMDG215: Dump Handler has Processed Exception Signal 11.
System Information for dixie
MODEL Bull ESCALA T (e8ED)
CPU 4 x K45, 32 bits (360.0 MH) ** 4 enabled **
MEM 2304 MB real memory
FIRM 03.03.09
OS AIX 5.1.0.0 [Fix level 58] [Maintenance level 05]
KERN System currently booted on 32 bits kernel
Attached is the Java core file
Any ideas?
Eric
[javacore37624.1083785465.txt]

BEA currently supports AIX 5.1 ML-4. Your configuration is ML-5.
Eric Hardesty wrote:
After installing WLS 8.1 and the AIX supplement patch plus fixes to java1.4
I am still unable to bring up my server. The following error occurs:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<May 5, 2004 1:29:26 PM MDT> <Info> <WebLogicServer> <BEA-000377> <Starting
WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<May 5, 2004 1:29:28 PM MDT> <Info> <Configuration Management> <BEA-150016>
<This server is being started as the administration server.>
<May 5, 2004 1:29:28 PM MDT> <Info> <Management> <BEA-141107> <Version:
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284WebLogic XMLX
Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<May 5, 2004 1:29:30 PM MDT> <Notice> <Management> <BEA-140005> <Loading
domainconfiguration from configuration repository at
/users/interop8/bea/user_projects/domain/hooxsgb/./config.xml.>
<May 5, 2004 1:29:49 PM MDT> <Notice> <Log Management> <BEA-170019> <The
serverlog file
/users/interop8/bea/user_projects/domain/hooxsgb/myserver/myserver.logis
opened. All server side log events will be written to this file.>
<May 5, 2004 1:30:08 PM MDT> <Notice> <Security> <BEA-090082> <Security
initializing using security realm myrealm.>
<May 5, 2004 1:30:09 PM MDT> <Notice> <WebLogicServer> <BEA-000327>
<Starting WebLogic Admin Server "myserver" for domain "hooxsgb">
JVMDG217: Dump Handler is Processing a Signal - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to
/users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.tx
t
JVMDG215: Dump Handler has Processed Exception Signal 11.
System Information for dixie
MODEL Bull ESCALA T (e8ED)
CPU 4 x K45, 32 bits (360.0 MH) ** 4 enabled **
MEM 2304 MB real memory
FIRM 03.03.09
OS AIX 5.1.0.0 [Fix level 58] [Maintenance level 05]
KERN System currently booted on 32 bits kernel
Attached is the Java core file
Any ideas?
Eric
NULL ------------------------------------------------------------------------
0SECTION TITLE subcomponent dump routine
NULL ===============================
1TISIGINFO signal 11 received
1TIDATETIME Date: 2004/05/05 at 12:31:05
1TIFILENAME Javacore filename: /users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.txt
NULL ------------------------------------------------------------------------
0SECTION XHPI subcomponent dump routine
NULL ==============================
1XHTIME Wed May 5 12:31:05 2004
1XHSIGRECV SIGSEGV received at 0xd3a96f54 in /usr/java14/jre/bin/classic/libjvm.a. Processing terminated.
1XHFULLVERSION J2RE 1.4.1 IBM AIX build ca1411-20030930
NULL
1XHCURRENTTHD Current Thread Details
NULL ----------------------
2XHCURRSYSTHD "ListenThread.Default" sys_thread_t:0x41C0F228
3XHNATIVESTACK Native Stack
NULL ------------
3XHSTACKLINE at 0xD46194CC in Java_weblogic_socket_PosixSocketMuxer_initNative
3XHSTACKLINE at 0xD3A96F54 in mmipInvoke_V_V
3XHSTACKLINE at 0xD3A909B0 in mmipInvokeLazyJniMethod
3XHSTACKLINE at 0xD3A5CBD8 in mmipExecuteJava
3XHSTACKLINE at 0xD3A54BBC in xeRunJvmMethod
3XHSTACKLINE at 0xD3A47628 in JVM_NewInstanceFromConstructor
3XHSTACKLINE at 0xD3C5658C in Java_sun_reflect_NativeConstructorAccessorImpl_newInstance0
3XHSTACKLINE at 0xD3A9641C in mmipInvoke_OO_O
3XHSTACKLINE at 0xD3A5CBD8 in mmipExecuteJava
3XHSTACKLINE at 0xD3BBCDF8 in mmijExecuteJavaFromJIT
3XHSTACKLINE at 0xD3C8AC90 in jit_init_memory_locks_md
NULL
1XHOPENV Operating Environment
NULL ---------------------
2XHHOSTNAME Host : dixie.gpv.az05.bull.com:141.112.17.150
2XHOSLEVEL OS Level : AIX 5.1.0.0
2XHCPUS Processors -
3XHCPUARCH Architecture : POWER_PC (impl: POWER_604, ver: PV_604)
3XHNUMCPUS How Many : 4
3XHCPUSENABLED Enabled : 4
NULL
1XHUSERLIMITS User Limits (in bytes except for NOFILE and NPROC) -
NULL -----------
2XHUSERLIMIT RLIMIT_FSIZE : infinity
2XHUSERLIMIT RLIMIT_DATA : 2147483645
2XHUSERLIMIT RLIMIT_STACK : 33554432
2XHUSERLIMIT RLIMIT_CORE : 1073741312
2XHUSERLIMIT RLIMIT_NOFILE : infinity
2XHLIMIT NPROC(max) : 4000
NULL
1XHPAGESPACES Page Space (in blocks) -
NULL ----------
2XHPAGESPACE /dev/hd6: size=200704, free=199709
2XHPAGESPACE /dev/paging00: size=196608, free=196495
2XHPAGESPACE /dev/paging01: size=196608, free=196495
NULL
1XHSIGHANDLERS JVM Signal Handlers
NULL -------------------
2XHSIGHANDLER SIGHUP : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGINT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGQUIT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGILL : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGTRAP : JITSigTrapHandler (libjitc.a)
2XHSIGHANDLER SIGABRT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGEMT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGFPE : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGBUS : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGSEGV : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGSYS : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGPIPE : ignored
2XHSIGHANDLER SIGTERM : intrDispatchMD (libhpi.a)
NULL
1XHSIGHANDLERS Chained Signal Handlers
NULL -----------------------
2XHSIGHANDLER SIGHUP : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGINT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGQUIT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGILL : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGTRAP : JITSigTrapHandler (libjitc.a)
2XHSIGHANDLER SIGABRT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGEMT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGFPE : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGBUS : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGSEGV : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGSYS : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGPIPE : ignored
2XHSIGHANDLER SIGTERM : intrDispatchMD (libhpi.a)
NULL
1XHENVVARS Environment Variables
NULL ---------------------
2XHENVVAR _=/usr/java14/bin/java
2XHENVVAR JAVA_VENDOR=IBM
2XHENVVAR LANG=en_US
2XHENVVAR TMOUT2=43200
2XHENVVAR PRODUCTION_MODE=
2XHENVVAR LOGIN=interop8
2XHENVVAR CLASSPATHSEP=:
2XHENVVAR PAGER=more
2XHENVVAR POINTBASE_HOME=/users/interop8/bea/weblogic81/common/eval/pointbase
2XHENVVAR PATH=/users/interop8/bea/weblogic81/server/bin:/usr/java14/jre/bin:/usr/java14/bin:/users/interop8/GCOSInterop/dsad/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin::/app/oracle/product/8.1.7/bin:/usr/local/bin:/usr/lbin:/users/interop8/jte/bin
2XHENVVAR RES_RETRY=1
2XHENVVAR JTE_BASE=/users/interop8/jte
2XHENVVAR JAVA_VM=
2XHENVVAR LC__FASTMSG=true
2XHENVVAR POINTBASE_CLASSPATH=:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar
2XHENVVAR CGI_DIRECTORY=/var/docsearch/cgi-bin
2XHENVVAR EDITOR=vi
2XHENVVAR EXINIT=set tabstop=4
2XHENVVAR HISTFILE=/users/interop8/.sh_history
2XHENVVAR CLASSPATH=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar::/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/usr/java14/jre/lib/rt.jar:/users/interop8/bea/weblogic81/server/lib/webservices.jar:
2XHENVVAR LOGNAME=interop8
2XHENVVAR RES_TIMEOUT=2
2XHENVVAR MAIL=/usr/spool/mail/interop8
2XHENVVAR ETC_PROFILE=1
2XHENVVAR POINTBASE_TOOLS=/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbtools44.jar
2XHENVVAR LOCPATH=/usr/lib/nls/loc
2XHENVVAR ORACLE_SID=demo
2XHENVVAR PS1=[dixie] (interop8).${PWD#${HOME}}>
2XHENVVAR PATHSEP=:
2XHENVVAR USER=interop8
2XHENVVAR DOCUMENT_SERVER_MACHINE_NAME=localhost
2XHENVVAR AUTHSTATE=compat
2XHENVVAR BEA_HOME=/users/interop8/bea
2XHENVVAR DEFAULT_BROWSER=netscape
2XHENVVAR DISPLAY=harp.gpv.az05.bull.com:0
2XHENVVAR SHELL=/bin/ksh
2XHENVVAR ODMDIR=/etc/objrepos
2XHENVVAR JAVA_HOME=/usr/java14
2XHENVVAR DOCUMENT_SERVER_PORT=49213
2XHENVVAR TMOUT=43200
2XHENVVAR HOME=/users/interop8
2XHENVVAR MEM_ARGS=-Xms32m -Xmx200m
2XHENVVAR WEBLOGIC_CLASSPATH=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar
2XHENVVAR TERM=vt220
2XHENVVAR MAILMSG=[YOU HAVE NEW MAIL]
2XHENVVAR ORACLE_HOME=/app/oracle/product/8.1.7
2XHENVVAR ITECONFIGSRV=/etc/IMNSearch
2XHENVVAR PWD=/users/interop8/bea/user_projects/domain/hooxsgb
2XHENVVAR DOCUMENT_DIRECTORY=/usr/docsearch/html
2XHENVVAR TZ=MST7
2XHENVVAR ITECONFIGCL=/etc/IMNSearch/clients
2XHENVVAR WL_HOME=/users/interop8/bea/weblogic81
2XHENVVAR ITE_DOC_SEARCH_INSTANCE=search
2XHENVVAR A__z=! TMOUT2=! LOGNAME=! ETC_PROFILE="*TMOUT
2XHENVVAR _IBM_JAVA_PIPE_37624=
2XHENVVAR IBM_JVM_AIXTHREAD_SCOPE_OLD_VALUE=
2XHENVVAR IBM_JVM_AIXTHREAD_SCOPE_NEW_VALUE=S
2XHENVVAR AIXTHREAD_SCOPE=S
2XHENVVAR IBM_JVM_CHANGED_ENVVARS_37624=AIXTHREAD_SCOPE,LDR_CNTRL
2XHENVVAR IBM_JVM_LDR_CNTRL_OLD_VALUE=
2XHENVVAR IBM_JVM_LDR_CNTRL_NEW_VALUE=MAXDATA=0x80000000
2XHENVVAR LDR_CNTRL=MAXDATA=0x80000000
2XHENVVAR LIBPATH=/usr/java14/jre/bin:/usr/java14/jre/bin/classic:/usr/java14/jre/bin:/app/oracle/product/8.1.7}/lib:/users/interop8/bea/weblogic81/server/lib/aix
2XHENVVAR NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat:/opt/Xprint/MSG/%l/%N:/opt/Xprint/mercator/MSG/%l/%N:/var/spool/Xprint/config/MSG/%l/%N:/var/spool/Xprint/config/mercator/MSG/%l/%N
2XHENVVAR _IBM_ENV_INITIAL_37624=807444056
2XHENVVAR IBM_JAVA_COMMAND_LINE=/usr/java14/bin/java -Xms32m -Xmx200m -Dweblogic.Name=myserver -Dweblogic.ProductionModeEnabled= -Djava..security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
NULL
1XHLOADEDLIBS Loaded Libraries (sizes in bytes)
NULL ---------------------------------
2XHLIBNAME /users/interop8/bea/weblogic81/server/lib/aix/libmuxer.so
3XHLIBSIZE filesize : 20757
3XHLIBSTART text start : 0xD4618000
3XHLIBLDSIZE text size : 0x282E
3XHLIBLDORG data start : 0x41E97CF4
3XHLIBLDDATASZ data size : 0x2AC
2XHLIBNAME /usr/java14/jre/bin/libnio.a
3XHLIBSIZE filesize : 61140
3XHLIBSTART text start : 0xD460F000
3XHLIBLDSIZE text size : 0x8925
3XHLIBLDORG data start : 0x408A5598
3XHLIBLDDATASZ data size : 0x50C
2XHLIBNAME /usr/java14/jre/bin/libnet.a
3XHLIBSIZE filesize : 122155
3XHLIBSTART text start : 0xD45F9000
3XHLIBLDSIZE text size : 0x1437A
3XHLIBLDORG data start : 0x3F592990
3XHLIBLDDATASZ data size : 0x820
2XHLIBNAME /usr/java14/jre/bin/libjitc.a
3XHLIBSIZE filesize : 2760315
3XHLIBSTART text start : 0xD3C7D000
3XHLIBLDSIZE text size : 0x2330F6
3XHLIBLDORG data start : 0x3E055F40
3XHLIBLDDATASZ data size : 0x1A8A4
2XHLIBNAME /usr/lib/libi18n.a
3XHLIBSIZE filesize : 148825
3XHLIBSTART text start : 0xD007A100
3XHLIBLDSIZE text size : 0xA1AE
3XHLIBLDORG data start : 0x3DFF2A18
3XHLIBLDDATASZ data size : 0x1290
2XHLIBNAME /usr/lib/nls/loc/en_US
3XHLIBSIZE filesize : 14342
3XHLIBSTART text start : 0xD0074000
3XHLIBLDSIZE text size : 0x2D71
3XHLIBLDORG data start : 0xD0077130
3XHLIBLDDATASZ data size : 0x2324
2XHLIBNAME /usr/java14/jre/bin/libzip.a
3XHLIBSIZE filesize : 109272
3XHLIBSTART text start : 0xD3C69000
3XHLIBLDSIZE text size : 0x1349A
3XHLIBLDORG data start : 0x3D80F398
3XHLIBLDDATASZ data size : 0x1908
2XHLIBNAME /usr/java14/jre/bin/classic/libcore.a
3XHLIBSIZE filesize : 172361
3XHLIBSTART text start : 0xD3C4E000
3XHLIBLDSIZE text size : 0x1AE66
3XHLIBLDORG data start : 0x3D801610
3XHLIBLDDATASZ data size : 0xD934
2XHLIBNAME /usr/java14/jre/bin/libhpi.a
3XHLIBSIZE filesize : 159668
3XHLIBSTART text start : 0xD3C36000
3XHLIBLDSIZE text size : 0x17708
3XHLIBLDORG data start : 0x3025DCC8
3XHLIBLDDATASZ data size : 0x1420
2XHLIBNAME /usr/java14/jre/bin/libxhpi.a
3XHLIBSIZE filesize : 44366
3XHLIBSTART text start : 0xD3C2F000
3XHLIBLDSIZE text size : 0x6578
3XHLIBLDORG data start : 0x3024E058
3XHLIBLDDATASZ data size : 0xE51C
2XHLIBNAME /usr/lib/libdl.a
3XHLIBSIZE filesize : 5248
3XHLIBSTART text start : 0xD070D0F8
3XHLIBLDSIZE text size : 0x1E0
3XHLIBLDORG data start : 0x3024D0F8
3XHLIBLDDATASZ data size : 0x0
2XHLIBNAME /usr/java14/jre/bin/libjsig.a
3XHLIBSIZE filesize : 13751
3XHLIBSTART text start : 0xD3C2D000
3XHLIBLDSIZE text size : 0x1B6E
3XHLIBLDORG data start : 0x3024C2F8
3XHLIBLDDATASZ data size : 0x1D0
2XHLIBNAME /usr/java14/jre/bin/libjava.a
3XHLIBSIZE filesize : 197639
3XHLIBSTART text start : 0xD3C10000
3XHLIBLDSIZE text size : 0x1CE78
3XHLIBLDORG data start : 0x30239690
3XHLIBLDDATASZ data size : 0x132C
2XHLIBNAME /usr/java14/jre/bin/classic/libjvm.a
3XHLIBSIZE filesize : 2698157
3XHLIBSTART text start : 0xD3A28000
3XHLIBLDSIZE text size : 0x1E71F8
3XHLIBLDORG data start : 0x302111E0
3XHLIBLDDATASZ data size : 0x27BE4
2XHLIBNAME /usr/lib/libiconv.a
3XHLIBSIZE filesize : 377974
3XHLIBSTART text start : 0xD0085100
3XHLIBLDSIZE text size : 0x1403A
3XHLIBLDORG data start : 0xF0317ED0
3XHLIBLDDATASZ data size : 0xA544
2XHLIBNAME /usr/lib/libbsd.a
3XHLIBSIZE filesize : 63178
3XHLIBSTART text start : 0xD01504C0
3XHLIBLDSIZE text size : 0x8183
3XHLIBLDORG data start : 0xF0169FB0
3XHLIBLDDATASZ data size : 0x1350
2XHLIBNAME /usr/lib/libpthreads.a
3XHLIBSIZE filesize : 912571
3XHLIBSTART text start : 0xD0047000
3XHLIBLDSIZE text size : 0x2B5BD
3XHLIBLDORG data start : 0xF0139000
3XHLIBLDDATASZ data size : 0x5020
2XHLIBNAME /usr/lib/libpthreads.a
3XHLIBSIZE filesize : 912571
3XHLIBSTART text start : 0xD0043000
3XHLIBLDSIZE text size : 0x38B1
3XHLIBLDORG data start : 0xF00D6000
3XHLIBLDDATASZ data size : 0x62318
2XHLIBNAME /usr/lib/libC.a
3XHLIBSIZE filesize : 6961880
3XHLIBSTART text start : 0xD0521560
3XHLIBLDSIZE text size : 0x1F983
3XHLIBLDORG data start : 0xF01E9560
3XHLIBLDDATASZ data size : 0x6578
2XHLIBNAME /usr/lib/libC.a
3XHLIBSIZE filesize : 6961880
3XHLIBSTART text start : 0xD0507E20
3XHLIBLDSIZE text size : 0x1846B
3XHLIBLDORG data start : 0xF01DFE20
3XHLIBLDDATASZ data size : 0x8511
2XHLIBNAME /usr/lib/libC.a
3XHLIBSIZE filesize : 6961880
3XHLIBSTART text start : 0xD04E7100
3XHLIBLDSIZE text size : 0x1F75A
3XHLIBLDORG data start : 0xF01DB700
3XHLIBLDDATASZ data size : 0x3019
2XHLIBNAME /usr/lib/libcrypt.a
3XHLIBSIZE filesize : 11059
3XHLIBSTART text start : 0xD00730F8
3XHLIBLDSIZE text size : 0x86E
3XHLIBLDORG data start : 0xF00D5530
3XHLIBLDDATASZ data size : 0x128
2XHLIBNAME /usr/lib/libc.a
3XHLIBSIZE filesize : 6806102
3XHLIBSTART text start : 0xD01D5640
3XHLIBLDSIZE text size : 0x1FDB9F
3XHLIBLDORG data start : 0xF0042520
3XHLIBLDDATASZ data size : 0x91B58
NULL
NULL ------------------------------------------------------------------------
0SECTION CI subcomponent dump routine
NULL ============================
1CIJAVAVERSION J2RE 1.4.1 IBM AIX build ca1411-20030930
1CIRUNNINGAS Running as a standalone JVM
1CICMDLINE /usr/java14/bin/java -Xms32m -Xmx200m -Dweblogic.Name=myserver -Dweblogic.ProductionModeEnabled= -Djava.security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
1CIJAVAHOMEDIR Java Home Dir: /usr/java14/jre
1CIJAVADLLDIR Java DLL Dir: /usr/java14/jre/bin
1CISYSCP Sys Classpath: /usr/java14/jre/lib/core.jar:/usr/java14/jre/lib/graphics.jar:/usr/java14/jre/lib/security.jar:/usr/java14/jre/lib/server.jar:/usr/java14/jre/lib/xml.jar:/usr/java14/jre/lib/charsets.jar:/usr/java14/jre/classes
1CIUSERARGS UserArgs:
2CIUSERARG vfprintf 0x30000B94
2CIUSERARG -Xms32m
2CIUSERARG -Xmx200m
2CIUSERARG -Dweblogic.Name=myserver
2CIUSERARG -Dweblogic.ProductionModeEnabled=
2CIUSERARG -Djava.security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy
2CIUSERARG -Dinvokedviajava
2CIUSERARG -Djava.class.path=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar::/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/usr/java14/jre/lib/rt.jar:/users/interop8/bea/weblogic81/server/lib/webservices.jar:
2CIUSERARG vfprintf
NULL
1CIJVMMI JVM Monitoring Interface (JVMMI)
NULL ------------------------
2CIJVMMIOFF No events are enabled.
NULL
NULL ------------------------------------------------------------------------
0SECTION DC subcomponent dump routine
NULL ============================
1DCHEADEREYE Header eye catcher DCST
1DCHEADERLEN Header length 24
1DCHEADERVER Header version 1
1DCHEADERMOD Header modification 0
1DCINTERFACE DC Interface at 0x3022270C with 15 entries
2DCINTERFACE 1 - dcCString2JavaString 0x3021EA7C
2DCINTERFACE 2 - dcInt642CString 0x3021EA88
2DCINTERFACE 3 - dcJavaString2NewCString 0x3021EA94
2DCINTERFACE 4 - dcJavaString2CString 0x3021EAA0
2DCINTERFACE 5 - dcJavaString2NewPlatformString 0x3021EAAC
2DCINTERFACE 6 - dcJavaString2UTF 0x3021EAB8
2DCINTERFACE 7 - dcPlatformString2JavaString 0x3021EAD0
2DCINTERFACE 8 - dcUnicode2UTF 0x3021EADC
2DCINTERFACE 9 - dcUnicode2UTFLength 0x3021EAE8
2DCINTERFACE 10 - dcUTF2JavaString 0x3021EAF4
2DCINTERFACE 11 - dcUTFClassName2JavaString 0x3021EB00
2DCINTERFACE 12 - dcJavaString2ClassName 0x3021EAC4
2DCINTERFACE 13 - dcUTF2UnicodeNext 0x3021EB0C
2DCINTERFACE 14 - dcVerifyUTF8 0x3021EB18
2DCINTERFACE 15 - dcDumpRoutine 0x3021EB24
1DCARRAYINFO Array info at 0x302131B8 with 16 entries
2DCARRAYINFO 1 - index 0 signature 0 name N/A factor 0
2DCARRAYINFO 2 - index 0 signature 0 name N/A factor 0
2DCARRAYINFO 3 - index 2 signature L name class[] factor 4
2DCARRAYINFO 4 - index 0 signature 0 name N/A factor 0
2DCARRAYINFO 5 - index 4 signature Z name bool[] factor 1
2DCARRAYINFO 6 - index 5 signature C name char[] factor 2
2DCARRAYINFO 7 - index 6 signature F name float[] factor 4
2DCARRAYINFO 8 - index 7 signature D name double[] factor 8
2DCARRAYINFO 9 - index 8 signature B name byte[] factor 1
2DCARRAYINFO 10 - index 9 signature S name short[] factor 2
2DCARRAYINFO 11 - index 10 signature I name int[] factor 4
2DCARRAYINFO 12 - index 11 signature J name long[] factor 8
2DCARRAYINFO 13 - index 0 signature 0 name uint[] factor 0
2DCARRAYINFO 14 - index 0 signature 0 name uint1[] factor 0
2DCARRAYINFO 15 - index 0 signature 0 name uint2[] factor 0
2DCARRAYINFO 16 - index 0 signature 0 name uint3[] factor 0
NULL ------------------------------------------------------------------------
0SECTION DG subcomponent dump routine
NULL ============================
1DGTRCENABLED Trace enabled: No
1DGJDUMPBUFF Javadump buffer size (allocated): 2621440
NULL ------------------------------------------------------------------------
0SECTION ST subcomponent dump routine
NULL ============================
1STGCMODES Resettable GC: No
1STGCMODES Concurrent GC: No
1STCURHBASE Current Heap Base: 302801fc
1STCURHLIM Current Heap Limit: 3281fbfc
1STMWHBASE Middleware Heap Base: 302801fc
1STMWHLIM Middleware Heap Limit: 3281fbfc
1STGCHELPERS Number of GC Helper Threads: 3
1STJVMOPTS -Xconcurrentlevel: 0
1STJVMOPTS -Xconcurrentbackground: 0
1STGCCTR GC Counter: 7
1STAFCTR AF Counter: 7
1STHEAPFREE Bytes of Heap Space Free: 80db00
1STHEAPALLOC Bytes of Heap Space Allocated: 259fa00
1STSMBASE SM Base: 0
1STSMEND SM End: 0
1STPAMSTART PAM Start: 0
1STPAMEND PAM End: 0
1STCOMACTION Compact Action: 0
NULL ------------------------------------------------------------------------
0SECTION XE subcomponent dump routine
NULL ============================
1XETHRESHOLD MMI threshold for java methods is set to 1250
1XEJITINIT JIT is initialized
1XEJVMPIOFF JVMPI is not activated
1XEJNITHRESH MMI threshold for JNI methods is set to 0
1XETRCHIS Trace history length is set to 4
1XEJITDUMP JIT dump routine is not yet implemented.
NULL ------------------------------------------------------------------------
0SECTION LK subcomponent dump routine
NULL ============================
NULL
1LKPOOLINFO Monitor pool info:
2LKPOOLINIT Initial monitor count: 32
2LKPOOLEXPNUM Minimum number of free monitors before expansion: 5
2LKPOOLEXPBY Pool will next be expanded by: 24
2LKPOOLTOTAL Current total number of monitors: 48
2LKPOOLFREE Current number of free monitors: 9
NULL
1LKMONPOOLDUMP Monitor Pool Dump (flat & inflated object-monitors):
2LKMONINUSE sys_mon_t:0x3020EE28 infl_mon_t: 0x3020E918:
3LKMONOBJECT java.lang.ref.Reference$Lock@303017F0/303017F8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "Reference Handler" (0x3D9C6A28)
2LKMONINUSE sys_mon_t:0x3020EED8 infl_mon_t: 0x3020E940:
3LKMONOBJECT java.lang.ref.ReferenceQueue$Lock@30301528/30301530: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "Finalizer" (0x3DA50CA8)
2LKMONINUSE sys_mon_t:0x3020EF88 infl_mon_t: 0x3020E968:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9830/302E9838: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '0' for queue: 'weblogic.kernel.Default'" (0x3EDB86A8)
2LKMONINUSE sys_mon_t:0x3020F038 infl_mon_t: 0x3020E990:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9798/302E97A0: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '1' for queue: 'weblogic.kernel.Default'" (0x3EDB8D28)
2LKMONINUSE sys_mon_t:0x3020F0E8 infl_mon_t: 0x3020E9B8:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9700/302E9708: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '2' for queue: 'weblogic.kernel.Default'" (0x3EDC2528)
2LKMONINUSE sys_mon_t:0x3020F198 infl_mon_t: 0x3020E9E0:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9668/302E9670: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '3' for queue: 'weblogic.kernel.Default'" (0x3EDD1EA8)
2LKMONINUSE sys_mon_t:0x3020F248 infl_mon_t: 0x3020EA08:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E95D0/302E95D8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '4' for queue: 'weblogic.kernel.Default'" (0x3EDD4528)
2LKMONINUSE sys_mon_t:0x3020F2F8 infl_mon_t: 0x3020EA30:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9538/302E9540: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '5' for queue: 'weblogic.kernel.Default'" (0x3EDD98A8)
2LKMONINUSE sys_mon_t:0x3020F3A8 infl_mon_t: 0x3020EA58:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E94A0/302E94A8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '6' for queue: 'weblogic.kernel.Default'" (0x3EDDCF28)
2LKMONINUSE sys_mon_t:0x3020F458 infl_mon_t: 0x3020EA80:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9408/302E9410: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '7' for queue: 'weblogic.kernel.Default'" (0x3EDE0528)
2LKMONINUSE sys_mon_t:0x3020F508 infl_mon_t: 0x3020EAA8:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9370/302E9378: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '8' for queue: 'weblogic.kernel.Default'" (0x3EDE2BA8)
2LKMONINUSE sys_mon_t:0x3020F5B8 infl_mon_t: 0x3020EAD0:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E92D8/302E92E0: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '9' for queue: 'weblogic.kernel.Default'" (0x3EDE8428)
2LKMONINUSE sys_mon_t:0x3020F668 infl_mon_t: 0x3020EAF8:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9240/302E9248: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '10' for queue: 'weblogic.kernel.Default'" (0x3EDE8A28)
2LKMONINUSE sys_mon_t:0x3020F718 infl_mon_t: 0x3020EB20:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E91A8/302E91B0: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '11' for queue: 'weblogic.kernel.Default'" (0x3EDF5E28)
2LKMONINUSE sys_mon_t:0x3020F7C8 infl_mon_t: 0x3020EB48:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9110/302E9118: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '12' for queue: 'weblogic.kernel.Default'" (0x3EDF94A8)
2LKMONINUSE sys_mon_t:0x3020F878 infl_mon_t: 0x3020EB70:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9078/302E9080: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '13' for queue: 'weblogic.kernel.Default'" (0x3EDFCAA8)
2LKMONINUSE sys_mon_t:0x3020F928 infl_mon_t: 0x3020EB98:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8FE0/302E8FE8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '14' for queue: 'weblogic.kernel.Default'" (0x3EE000A8)
2LKMONINUSE sys_mon_t:0x3020F9D8 infl_mon_t: 0x3020EBC0:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8F48/302E8F50: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '0' for queue: 'weblogic.kernel.System'" (0x3EE03728)
2LKMONINUSE sys_mon_t:0x3020FA88 infl_mon_t: 0x3020EBE8:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8EB0/302E8EB8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '1' for queue: 'weblogic.kernel.System'" (0x3EE06D28)
2LKMONINUSE sys_mon_t:0x3020FB38 infl_mon_t: 0x3020EC10:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8E18/302E8E20: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '2' for queue: 'weblogic.kernel.System'" (0x3EE0A328)
2LKMONINUSE sys_mon_t:0x3020FBE8 infl_mon_t: 0x3020EC38:
3LKMON

Pre-Ordering and album with already-released single

I'm wondering if I pre-order an album, do I get the already released single right away?
I've noticed times where I've downloaded the single, then purchased the album after release without the "complete my album" option. It seems sometimes the singles are flagged as their own album, or can't complete a deluxe edition, etc.
I'd hate to have to pay for a single song twice. Any insight from regular iTunes users?
Thanks!

Maybe:
Pre purchased song wont download

ConnectionPool problems with WLS 7.0 and Oracle 9.2

Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
application on the productive system (and only there) we constantly encounter
a whole set of SQLExceptions which have all in common that the Connection from
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSet
- Connection has already been closed
- Closed Statement
- Transaction is no longer active - status committing
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()
There are no special Statements which create these errors. They are spread at
random across practically every query the application creates, and the same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSets are
closed immediately after use. As an example, I attached a code snippet and a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrent usern,
since in the approval tests on an almost identical test system these errors never
occurred.
I also followed the advice from Oracle and installed the latest Oracle JDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in the application
classpath (via a reference in the Manifest file of the application jar), not in
the system classpath? There has never been a problem with that, but in a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script creates for the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath? If
it is possible, why is it necessary?
Best regards,
Andreas Zehrt
[CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

Andreas Zehrt wrote:
Hi Joe,
Your hint that there is a threading problem was right:
On further investigation of the code I found out that the class that passes the
Connection to the DAO not only stores it as a member at some point (which is not
a good idea anyway) but is also a singleton - then, of course, it's no surprise
that the Connection gets invalid in a incalculable way when concurrent threads
share it.
The singleton instantiation was not so obvious because the way of instantiation
is controlled by a configuration parameter that can be overridden at different
levels.
I changed it and the productive logfiles indicate that the SQLExceptions related
to that class have disappeared.I am happy to have helped.
So, thanks a lot for the advice.
But I am still wondering why this code has worked for so long a time with WLS
5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
it was multi-user environment.Mo idea.
I still believe that there is a difference between WLS 5.1 and 7.0 in the way
it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
a little more explicit about those changes and possible version incompatabilities
beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
effect in this case, I will certainly do what I can to see that our documentation
is explicit about changes.
Joe
Best regards, Andreas
Joe Weinstein <[email protected]> wrote:
Hi Andreas.
Andreas Zehrt wrote:
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
application on the productive system (and only there) we constantlyencounter
a whole set of SQLExceptions which have all in common that the Connectionfrom
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSetThat is typically if the statement that created it is either re-executed
or closed.
- Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
would show
where it was originally closed.
- Closed Statementsame as above.
- Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
datasource,
and then later trying to use it after the transaction which it was associated
with,
is finished.
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
There are no special Statements which create these errors. They arespread at
random across practically every query the application creates, andthe same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSetsare
closed immediately after use. As an example, I attached a code snippetand a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrentusern,
since in the approval tests on an almost identical test system theseerrors never
occurred.
I also followed the advice from Oracle and installed the latest OracleJDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in theapplication
classpath (via a reference in the Manifest file of the applicationjar), not in
the system classpath? There has never been a problem with that, butin a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script createsfor the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath?If
it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
We also ship
an oracle thin driver, which becomes obsolete soon...
I am concerned that your code creates pool connections to be used later.
The problems
can arise if more than one thread ever gets the same connection, or if
the connection
is used in the same thread, spanning transactions. It does also seem
that there may
be a threading issue, because if two threads each call the code to create
a connection,
and two connections are made, but one over-writes the other, the two
threads can
end up using the same connection, and closing it. The over-written one
never gets closed,
resulting in that leak message you got...
Joe
The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
several classes in the business layer, but not used, until the DAOtakes it to make the query.
So, the Connection is closed where it was opened, not in the DAO class.
public class ConcernDAOImpl extends BaseDAO {
     public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
throws DataAccessException, ConstraintException, ComaParseException{>
sqlMessage.append(")");
String sqlStmt = sqlMessage.toString();
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
pstmt = conn.prepareStatement(sqlStmt);
rs = pstmt.executeQuery();
while (rs != null && rs.next()) {
final Concern concern =
new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
return concerns;
} catch (SQLException sqle) {
// Wrapps real SQL exception
String[] message = new String[]{sqle.getMessage(), sqlStmt};
throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
sqle);
} finally {
closeAll(rs, pstmt);
_logger.exitDebug(method);
Here, the Connection is acquired and finally closed
public class ComaServiceProviderClassicImpl {
     public void updateComplaint(
final Request updateRequest,
final ResponseSingleElement response,
final Principal principal)
throws SystemException {
try {
logger.info("updateComplaint", "store incident");
// store the incident in the database
incidentManager.storeIncident(getConnection(), updateIncident);
// reload the incident from Cache and / or the databaseto get the ContactReferences.
Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
getConnection(), updateIncident.getOID());
} catch (RemoteException rex) {
// remote exceptions
rollbackIfNecessary();
CoreUtils.unwrapRemoteException(rex, logger);
} catch (SystemException e) {
// all other exceptions --> rollback if necessary and rethrow
rollbackIfNecessary();
throw e;
} finally {
removeConnection();
logger.exitDebug("updateComplaint");
This is the resulting StackTrace:
sql exception: [Closed Statement: next] - sql statement: [select *
     at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
     at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
     at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
was detected. A Connection leak occurs when a connection obtained from
the pool was not closed explicitly by calling close() and then was disposed
by the garbage collector and returned to the connection pool. The following
stack trace at create shows where the leaked connection was created.
Stack trace at connection create:
     at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
     at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
     at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
     at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
     at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
     at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

This method should not be called anymore. The client was already released i

Hi,
while configuring Business Packager for Projects 50.3 fo, we made few changes in R/3 side as per the documentation. after that we are getting following error in portal
"This method should not be called anymore. The client was already released into the pool or the pool entry was deleted"
all the chages were reverted in R/3 system still we are getting the same error.
Can any one help on this issue....
Thanks in advance and for early responce higher marks would be awarded!!!..
Regards
Ravi Sankar Karri

Hi,
Well there were errors in how stop works:
"Stopping a thread with Thread.stop causes it to
unlock all of the monitors that it has locked (as a
natural consequence of the unchecked ThreadDeath
exception propagating up the stack). If any of the
objects previously protected by these monitors were in
an inconsistent state, the damaged objects become
visible to other threads, potentially resulting in
arbitrary behavior. "
I do understand that you want to have something like
killTheTreadIDontCareAboutConcequences-method, but
it's better to let all your methods that you want to
be able to terminate take a timeout argument, and deal
with the termination in the method. (Close the
sockets/streams etc that you are blocking on).
/KajThe point is, it is not always possible to make those blocking methods stop, via some magic "timeout" thingamabob. The bottom line is still that the blocking methods were written incorrectly to begin with (to possibly block indefinitely), so one cannot come up with an across-the-board solution, other than getting the root cause fixed in the first place. However, one is not always in control of fixing the root cause.

Close Wait also with WLS 6.1SP2

Hi,
we encounter the same situation with the NES (predecessor of iPlanet) and WLS 6.1SP2.
Con      TWait      CWait      Files      Sockets
706     0     422     980     815
749     0     554     1022     857
749     0     597     1022     857
Any suggestions?
Regards
Andi

"Shirley" <[email protected]> wrote:
>
"Khalid" <[email protected]> wrote:
We seem to have close wait problem in extreme load where apache/weblogic
hold the
tread so the socket cannot be closed. Does anyone know how to fix this
problem.
It seems like after in runs out of thread the server crashes.
Have you fixed this problem you were facing ,because we are facing exactly
the
same problem.Did you find any solution .If so please do let us know
Cheers
Shirley RemediosWe had the same problem and reduced the number of sockets in this state by reducing
the time to wait before closing the sockets. On Solaris we set 'tcp_time_wait_interval'
to 30000 (30 seconds) on the web and app servers.

AdfFacesContext was already released or had never been attached JSP v. JSPX

This error is occuring on JSPX pages but not on JSP pages and only when I deploy the application to Oracle 10gAS 10.1.2. The problem does not normally present itself in JDeveloper (10.1.3). I had tried moving all my pages to the JSP form but found that some ADF components did not behave well < af: table > being a major problem. So I now have some pages in the JSP and some in JSPX. JSP (to avoid this problem) when the page does not include a table and otherwise a JSPX page.
This message appears at the foot of the page and does not otherwise seem to prevent the page from operating. Okay for now but hardly client deliverable. The page contains two < af: table > elements nexted in < af: showDetail > elements of an outer < af: showOneTab > element
java.lang.IllegalStateException: AdfFacesContext was already released or had never been attached.
at oracle.adf.view.faces.context.AdfFacesContext.release(AdfFacesContext.java: 320)
at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java: 240)
at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java: 8
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java: 645)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java: 322)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java: 790)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java: 208)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java: 125)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java: 192)
at java.lang.Thread.run(Thread.java: 534)
The page (greatly simplified) is as follows:
< ?xml version="1.0" encoding="iso-8859-1"? >
< jsp: root >
< jsp: directive.page contentType="text/html;charset=utf-8"/ >
< f: loadBundle / >
< f: view >
< af: document >
< af: form >
< af: panelPage >
< f: facet name="messages" >
< af: messages/ >
< /f: facet >
< jsp: directive.include file="GlobalFacet.jspf"/ >
< f: facet name="menu1" >
< af: menuTabs >
< af: commandMenuItem / >
< /af: menuTabs >
< /f: facet >
< jsp: directive.include file="BrandingFacet.jspf"/ >
< af: showOneTab position="both" >
< af: showDetailItem >
< af: panelGroup >
< af: table >
< af: column width="50" sortable="true" sortProperty="groupName" >
< f: facet name="header" >
< af: outputText value="Group name"/ >
< /f: facet >
< af: outputText value="#{groupRow.groupName}" / >
< /af: column >
< f: facet name="detailStamp" >
< afh: tableLayout >
< afh: rowLayout >
< afh: cellFormat >
< af: outputLabel / >
< /afh: cellFormat >
< afh: cellFormat >
< af: inputText / >/ >
< /afh: cellFormat >
... many more cells and rows
< /afh: rowLayout >
< afh: rowLayout halign="center" >
< afh: cellFormat halign="center" >
< af: commandButton rendered="#{bean.condition} / >
< af: commandButton rendered="#{!bean.condition} / >
< /afh: cellFormat >
< /afh: rowLayout >
< /afh: tableLayout >
< /f: facet >
< /af: table >
< /af: panelGroup >
< /af: showDetailItem >
< af: showDetailItem >
... Something almost identical to the first DetailItem but for a different table
< /af: showDetailItem >
< /af: showOneTab >
< /af: panelPage >
< /af: form >
< /af: document >
< /f: view >
< /jsp: root >
Note: I'm posting a separate item about the fact that when I deploy this application to 10g AS (10.1.2) the < jsp: directive.include > tag does not work.

Same probleme here but with both jsp and jspx
I'm using jdev 10.1.3 with jdk1.4.2_08, in a war file deployed to a weblogic 8.1 sp 5 application server.
It happens everytime (on every jsp) in the weblogic console and sometimes the jsp crashes and give me this error:
java.lang.IllegalStateException: AdfFacesContext was already released or had never been attached.
     at oracle.adf.view.faces.context.AdfFacesContext.release()V(AdfFacesContext.java:342)
     at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V(AdfFacesFilterImpl.java:253)
     at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V(AdfFacesFilter.java:87)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V(FilterChainImpl.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava/lang/Object;(WebAppServletContext.java:6987)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic/servlet/internal/ServletRequestImpl;Lweblogic/servlet/internal/ServletResponseImpl;)V(WebAppServletContext.java:3892)
     at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic/kernel/ExecuteThread;)V(ServletRequestImpl.java:2766)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
     at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
any suggestion is welcome
thanks
Message was edited by:
xavier.l

Proforma Invoice and Invoice Released to account

Hi All,
I have typical scenario. My client is asking for this scenario. below is the scenario:
In SAP we will create proforma invoice. That proforma invoice should release to account. Only educational cess to be released to account. No other condition type should released to account during proforma invoice.
Secondly while creating the normal invoice, basic price and excise duty should released account. But education cess (Which is already released to account during proforma Invoice) should not released to account during invoice.
How to resolve this issue?
Regards
Ashis

Hi
In my view , you must make your client about Proforma Invoice.
Possibly, your client is meaning some thing else but using the terminology 'proforma invoice" only.
Make him understand that, Proforma Invoice is a dummy invoice against which no account posting is possible. It does not update the status in reference document. You can create hundreds of Proforma Invoice with reference to Sales order and Delivery document.
For, Delivery related Proforma Invoice,even PGI is also not required.
In the copy control the "Positive/negative quantity" field mustbe remain disabled for Proforma Invoice.
Even if you are trying to do with some enhancement, it will not be logical and lot of problem will be encountered .
Make the client understand the concept of Proforma Invoice and try to understand his actual requirement.

Already released pr, again comng for pr release in sap inbox

dear friends,
our client is having work flw for PR release.
my user already release PR. but in his sap inbox, again same PR is displaying( in the list of PR's to be release).already released one , again coming in the list of new PR list to be released today.why old, already release PR, again coming for PR release.
kindly advice me in this regard.
your advice are considered valuable.
regards,
flemmings

For PR release we need to export and import from both side.
I want to say that if PR is release from your user id then it has exported from that client.
But if it is not get updated in target place then import has to be done in target place to see changes.
you can check code in both places and find out wether updated code is there or not.
If not then ask the basis person to check and import code in target client.
Rewards if helpful.....................
Minal

Delete an already released transport request

Hello together,
I have a problem in SE09/SE10 with a transport request.
The request is as follows:
Modifiable
D01K939667 100 Username /Description
D01K939668 Username Customizing Task
The requests itself has the status "Modifiable". The task D01K939668 within the request is already released. I have to delete the whole request now, but when trying to delete it, it says "Request D01K939668 already released". How can I delete a task within a request, that is already released?
Thank you for any help!
Best regards
Klaus Hirschegger

Of course, you can
But you have to chnage status of the request:
Use transaction SE38 or SA38 and run program: RDDIT076
Set your request number and run the program
After request is shown double click on it
You should be able to change status from R to D
And now, you can delete the transport for example in transaction: SE10...
Help on ABAP: Few Tips for Transport Request Manipulation

Intermittent java.lang.NoClassDefFoundError WLS 8.1SP2 Solaris 5.8

Hello.
I have experienced an intermittent java.lang.NoClassDefFoundError following deployment as follows:
java.lang.NoClassDefFoundError: /net/sf/hibernate/cfg/Configuration
on Solaris 5.8 WLS 8.1SP2 for a web application whose WAR contains all of the required .jar files for Hibernate. The code involved uses a static initializer (following the thread local pattern shown in many Hibernate documentation sources) and has shown no issues to date in a Win2K environment.
The issue persisted between several re-deployments and fresh server instances on a given day. Two days later the same WAR deployment was used and the error did not appear again.
Has anyone experienced a similar behaviour in their deployment experiences ? Does anyone have any suggestions on avoiding the issue (e.g. something related to ClassLoaders) ?
Regards,
James.

Hello.
I have experienced an intermittent java.lang.NoClassDefFoundError following deployment as follows:
java.lang.NoClassDefFoundError: /net/sf/hibernate/cfg/Configuration
on Solaris 5.8 WLS 8.1SP2 for a web application whose WAR contains all of the required .jar files for Hibernate. The code involved uses a static initializer (following the thread local pattern shown in many Hibernate documentation sources) and has shown no issues to date in a Win2K environment.
The issue persisted between several re-deployments and fresh server instances on a given day. Two days later the same WAR deployment was used and the error did not appear again.
Has anyone experienced a similar behaviour in their deployment experiences ? Does anyone have any suggestions on avoiding the issue (e.g. something related to ClassLoaders) ?
Regards,
James.

[svn:cairngorm3:] 21115: updating the md5 and metadata and swc release ( just in case, we missed anything in our last commit)

Revision: 21115
Revision: 21115
Author:   [email protected]
Date:     2011-04-21 09:13:29 -0700 (Thu, 21 Apr 2011)
Log Message:
updating the md5 and metadata and swc release (just in case, we missed anything in our last commit)
Modified Paths:
    cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/3.0.18/cairngorm3-3.0.18.pom
    cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/3.0.18/cairngorm3-3.0.18.pom.m d5
    cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/3.0.18/cairngorm3-3.0.18.pom.s ha1
    cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/contract/1.4/contract-1.4.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/contract/1.4/contract-1.4.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/contract/1.4/contract-1.4.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/contract/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/contract/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/contract/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/integration/0.16/integration-0.16.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/integration/0.16/integration-0.16.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/integration/0.16/integration-0.16.swc.sha 1
    cairngorm3/maven-repository/com/adobe/cairngorm/integration/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/integration/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/integration/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/0.16/integrationParsle y-0.16.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/0.16/integrationParsle y-0.16.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/0.16/integrationParsle y-0.16.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/maven-metadata.xml.sha 1
    cairngorm3/maven-repository/com/adobe/cairngorm/libraries/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/libraries/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/libraries/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/module/0.15/module-0.15.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/module/0.15/module-0.15.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/module/0.15/module-0.15.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/module/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/module/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/module/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/navigation/1.4/navigation-1.4.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/navigation/1.4/navigation-1.4.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/navigation/1.4/navigation-1.4.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/navigation/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/navigation/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/navigation/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/1.4/navigationParsley-1 .4.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/1.4/navigationParsley-1 .4.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/1.4/navigationParsley-1 .4.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/1.4/navigationSpringAS -1.4.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/1.4/navigationSpringAS -1.4.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/1.4/navigationSpringAS -1.4.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/maven-metadata.xml.sha 1
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/1.4/navigationSwiz-1.4.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/1.4/navigationSwiz-1.4.swc .md5
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/1.4/navigationSwiz-1.4.swc .sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/observer/1.14/observer-1.14.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/observer/1.14/observer-1.14.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/observer/1.14/observer-1.14.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/observer/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/observer/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/observer/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/1.14/observerParsley-1.14 .swc
    cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/1.14/observerParsley-1.14 .swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/1.14/observerParsley-1.14 .swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/popup/1.13/popup-1.13.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/popup/1.13/popup-1.13.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/popup/1.13/popup-1.13.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/popup/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/popup/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/popup/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/1.13/popupParsley-1.13.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/1.13/popupParsley-1.13.swc.m d5
    cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/1.13/popupParsley-1.13.swc.s ha1
    cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/task/1.10/task-1.10.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/task/1.10/task-1.10.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/task/1.10/task-1.10.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/task/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/task/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/task/maven-metadata.xml.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/validation/1.13/validation-1.13.swc
    cairngorm3/maven-repository/com/adobe/cairngorm/validation/1.13/validation-1.13.swc.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/validation/1.13/validation-1.13.swc.sha1
    cairngorm3/maven-repository/com/adobe/cairngorm/validation/maven-metadata.xml
    cairngorm3/maven-repository/com/adobe/cairngorm/validation/maven-metadata.xml.md5
    cairngorm3/maven-repository/com/adobe/cairngorm/validation/maven-metadata.xml.sha1

word!
second that.
This is really hard to follow, even for us who keep an eye on every update and read every single post and have an imagination of update problems out there.
You tried to make digitalpublishing.acrobat.com (the "dashboard") the one-stop place for downloading and updating all necessary tools. good idea to make this the central point, because adobe.com download sections is a pain in the arse when trying to find updates for secondary tools like the DPS.
also, make it super-duper clear what version is the current and what versio are currently available. I already wrote about lining up version numbers months ago and you seem to get this working — but it is still a mess. 1.7 vs 1.1.7 vs. 2.0 vs. drop17 vs. 11.4.2.201111104_m_670635 7.5.5.16 (you can imagine where I took the latter from)
Peter: The bold line in the sticky forum message was added later, as I recall.
—Johannes

MIR7 doesn't get PO and PO release strategy

I can see PO item 10, 10000 MYR in ME23N, and it is already released.
In MIR7, PO reference tab, I put PO number and item number, but mesages says no item number. and it didn't populate item from PO.
what's the reason?
also I create PR and released PR, but when I run ME59N and input PR number, it says No suitable purchase requisitions found
Message no. ME261? I can't generate PO automatically. I have to use ME21N, what's the wrong with my system?
I tried one purchase group and PO can't be released, but when I change purchase group, it is ok, may i know the SPRO configuration to define certain purchase group for release strategy?
also how can we set certain PO document type with release strategy and some PO document type without release strategy ?

Hello
For first question, Please check in the PO line item level Invoice tab, whether GR based invoice verification is checked. If yes, then system will allow you perform MIR7 after Goods receipt.
Second question:
ME59N should display the open PRs for PO creation. Please cross check once agian the input selection parameters.
Third Question
Yes, you can configure the Release procedure based on Purchasing document type/Pur group. You need to define the paramter as Charactetristic and assign to the Release class.
warm regards
Ramakrishna

OAS: Is there a version already released to support Servlets

Is there a version of OAS already released to support Java
Servlets? And if such a version is not yet released, when it
will be available?
We prefer to believe Oracle and do not want to use the Sun Java
Web Server.
I liked a lot the ready DBServlet classes which provide a lot of
functionality to build master-detail forms but I cannot use
them. What about the JWeb cartridge it does not provide any
serious advantage caompared to the old-fasioned PL/SQL cartridge
which I have to use before. Why use JWeb if it gives me just the
same like the PL/SQL cartridge?
null

Preslav,
OAS 4.0.8 supports servlets.
It is already available..
Preslav Nakov (guest) wrote:
: Is there a version of OAS already released to support Java
: Servlets? And if such a version is not yet released, when it
: will be available?
: We prefer to believe Oracle and do not want to use the Sun Java
: Web Server.
: I liked a lot the ready DBServlet classes which provide a lot
of
: functionality to build master-detail forms but I cannot use
: them. What about the JWeb cartridge it does not provide any
: serious advantage caompared to the old-fasioned PL/SQL
cartridge
: which I have to use before. Why use JWeb if it gives me just
the
: same like the PL/SQL cartridge?
null

WLS 8.1 and JMX 1.2 remote API

I am developing a web app that uses JMX 1.2 remote API to manager remote MBean
servers. Even I put the JMX 1.2 jar files to the classpath, WLS still loads the
previous version (1.0) of JMX bundled in weblogic.jar file, I think. And I am
not eager to mess up weblogic.jar file either.
Is there anyway to use JMX 1.2 remote API in WLS 8.1? If not, is there a patch
from BEA? And when will JMX 1.2 be supported by WLS? Thanks,
Jack

The next release of WLS is tentatively scheduled some time early next
year. JMX 1.2 will be supported in that release.
Thanks,
-satya
Jack Liu wrote:
Thanks for the reply. I heard BEA will release WLS 8.1 SP3 in June. Based on your
message, JMX 1.2 will not be supported by any WLS 8.1. So can you give me an estimate
of which release and when will JMX 1.2 be supported? Thanks!
Satya Ghattu <[email protected]> wrote:
Jack,
JMX 1.2 Remote API will be supported in the next version of WLS. There
is no patch available for 8.1 and as of now there are no intentions to
support 8.1 with JMX 1.2.
Thanks,
-satya
Jack Liu wrote:
I am developing a web app that uses JMX 1.2 remote API to manager remoteMBean
servers. Even I put the JMX 1.2 jar files to the classpath, WLS stillloads the
previous version (1.0) of JMX bundled in weblogic.jar file, I think.And I am
not eager to mess up weblogic.jar file either.
Is there anyway to use JMX 1.2 remote API in WLS 8.1? If not, is therea patch
from BEA? And when will JMX 1.2 be supported by WLS? Thanks,
Jack

WLS 8.1SP2 and "already released" warning

Similar Messages

Maybe you are looking for