Posix Perf Pack - Interrupted system call (WL6SP1)

Hi all,
I run Weblogic 6.0 SP1 on solaris 2.7.
My web application seems to work but randomly, Weblogic seems to
crash.
The logs say the following message.
Any help is welcome! =)
Guillaume
####<Jun 13, 2001 8:49:29 AM GMT+01:00> <Error> <Posix Performance
Pack> <intupc5> <clarify> <ExecuteThread: '12' for queue: 'default'>
<> <> <000000> <Uncaught Throwable in processSockets>
java.io.IOException: error in poll: Interrupted system call
 at weblogic.socket.PosixSocketMuxer.poll(Native Method)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

We apparently had quite a bit of premature thread death, about half of our threads
are MIA
"Mike Reiche" <[email protected]> wrote:
>
Ummmm.. so you set the executeThreadCount to what? 55? And PercentSocketReaders
to 50?
And you are missing execute threads 1 through 25. Where did they go?
The only
threads you have left are the ones listening for requests - and they
don't do
any work. Find out what happened to the missing threads.
Mike
"Joe" <[email protected]> wrote:
Here is our thread dump ...just FYI we took a thread dump every minute
for about
5-7 minutes. The thread dump did NOT change
------------------------begin thread dump-----------------------
Full thread dump:
"Thread-4" daemon prio=5 tid=0xc39fb8 nid=0x51 waiting on monitor [0xb3501000..0xb3501a28]
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:420)
 at javax.mail.EventQueue.dequeue(EventQueue.java:78)
 at javax.mail.EventQueue.run(EventQueue.java:97)
 at java.lang.Thread.run(Thread.java:484)
"HighPriority TimeEventGenerator" daemon prio=9 tid=0xaa7f30 nid=0x4e
waiting
on monitor [0xb1e81000..0xb1e81a28]
 at java.lang.Object.wait(Native Method)
 at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
 at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
 at java.lang.Thread.run(Thread.java:484)
"SSLListenThread" prio=5 tid=0x5b9ba8 nid=0x4d runnable [0xb2e81000..0xb2e81a28]
 at java.net.PlainSocketImpl.socketAccept(Native Method)
 at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
 at java.net.ServerSocket.implAccept(ServerSocket.java:243)
 at java.net.ServerSocket.accept(ServerSocket.java:222)
 at weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:126)
 at weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:117)
 at weblogic.t3.srvr.ListenThread.run(ListenThread.java:247)
"ListenThread" prio=5 tid=0x912768 nid=0x4c runnable [0xb2f81000..0xb2f81a28]
 at java.net.PlainSocketImpl.socketAccept(Native Method)
 at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
 at java.net.ServerSocket.implAccept(ServerSocket.java:243)
 at java.net.ServerSocket.accept(ServerSocket.java:222)
 at weblogic.t3.srvr.ListenThread.run(ListenThread.java:247)
"ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5
tid=0x2da950
nid=0x49 waiting on monitor [0xb3701000..0xb3701a28]
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:420)
 at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5
tid=0x2d9218
nid=0x48 waiting on monitor [0xb3801000..0xb3801a28]
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:420)
 at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
prio=5 tid=0x2d88f0
nid=0x47 waiting on monitor [0xb3901000..0xb3901a28]
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:420)
 at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
prio=5 tid=0x2d83c8
nid=0x46 waiting on monitor [0xb3a01000..0xb3a01a28]
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:420)
 at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"TimeEventGenerator" daemon prio=5 tid=0x379f58 nid=0x45 waiting onmonitor
[0xb3b01000..0xb3b01a28]
 at java.lang.Object.wait(Native Method)
 at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
 at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
 at java.lang.Thread.run(Thread.java:484)
"TimeEventGenerator" daemon prio=5 tid=0x349f58 nid=0x44 waiting onmonitor
[0xb3c01000..0xb3c01a28]
 at java.lang.Object.wait(Native Method)
 at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
 at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
 at java.lang.Thread.run(Thread.java:484)
"SpinnerRandomSource" daemon prio=5 tid=0x419698 nid=0x43 waiting on
monitor [0xb3d01000..0xb3d01a28]
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:420)
 at weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:92)
 at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:109)
"ExecuteThread: '54' for queue: 'default'" daemon prio=5 tid=0x416740
nid=0x42
waiting for monitor entry [0xb3e01000..0xb3e01a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '49' for queue: 'default'" daemon prio=5 tid=0x4130e0
nid=0x3d
waiting for monitor entry [0xb4301000..0xb4301a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '48' for queue: 'default'" daemon prio=5 tid=0x412600
nid=0x3c
waiting for monitor entry [0xb4401000..0xb4401a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '47' for queue: 'default'" daemon prio=5 tid=0x411b20
nid=0x3b
waiting for monitor entry [0xb4501000..0xb4501a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '46' for queue: 'default'" daemon prio=5 tid=0x410a38
nid=0x3a
waiting for monitor entry [0xb4601000..0xb4601a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '45' for queue: 'default'" daemon prio=5 tid=0x40ff58
nid=0x39
waiting for monitor entry [0xb4701000..0xb4701a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '44' for queue: 'default'" daemon prio=5 tid=0x40f478
nid=0x38
waiting for monitor entry [0xb4801000..0xb4801a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '43' for queue: 'default'" daemon prio=5 tid=0x40e998
nid=0x37
waiting for monitor entry [0xb4901000..0xb4901a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '42' for queue: 'default'" daemon prio=5 tid=0x40deb8
nid=0x36
waiting for monitor entry [0xb4a01000..0xb4a01a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '41' for queue: 'default'" daemon prio=5 tid=0x40d3d8
nid=0x35
waiting for monitor entry [0xb4b01000..0xb4b01a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '40' for queue: 'default'" daemon prio=5 tid=0x40c8f8
nid=0x34
waiting for monitor entry [0xb4c01000..0xb4c01a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '39' for queue: 'default'" daemon prio=5 tid=0x40be18
nid=0x33
waiting for monitor entry [0xb4d01000..0xb4d01a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '38' for queue: 'default'" daemon prio=5 tid=0x40b338
nid=0x32
waiting for monitor entry [0xb4e01000..0xb4e01a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '37' for queue: 'default'" daemon prio=5 tid=0x40a858
nid=0x31
waiting for monitor entry [0xb4f01000..0xb4f01a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '36' for queue: 'default'" daemon prio=5 tid=0x409970
nid=0x30
waiting for monitor entry [0xb5001000..0xb5001a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '35' for queue: 'default'" daemon prio=5 tid=0x408e90
nid=0x2f
waiting for monitor entry [0xb5101000..0xb5101a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '34' for queue: 'default'" daemon prio=5 tid=0x4083b0
nid=0x2e
waiting for monitor entry [0xb5201000..0xb5201a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '33' for queue: 'default'" daemon prio=5 tid=0x4078d0
nid=0x2d
waiting for monitor entry [0xb5301000..0xb5301a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '32' for queue: 'default'" daemon prio=5 tid=0x406df0
nid=0x2c
waiting for monitor entry [0xb5401000..0xb5401a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '31' for queue: 'default'" daemon prio=5 tid=0x406310
nid=0x2b
waiting for monitor entry [0xb5501000..0xb5501a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '30' for queue: 'default'" daemon prio=5 tid=0x405830
nid=0x2a
runnable [0xb5601000..0xb5601a28]
 at weblogic.socket.PosixSocketMuxer.poll(Native Method)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '29' for queue: 'default'" daemon prio=5 tid=0x404548
nid=0x29
waiting for monitor entry [0xb5701000..0xb5701a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '28' for queue: 'default'" daemon prio=5 tid=0x403a68
nid=0x28
waiting for monitor entry [0xb5801000..0xb5801a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '27' for queue: 'default'" daemon prio=5 tid=0x402f88
nid=0x27
waiting for monitor entry [0xb5901000..0xb5901a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '26' for queue: 'default'" daemon prio=5 tid=0x4024a8
nid=0x26
waiting for monitor entry [0xb5a01000..0xb5a01a28]
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"Signal Dispatcher" daemon prio=10 tid=0xf2320 nid=0x9 runnable [0..0]
"Finalizer" daemon prio=8 tid=0xef678 nid=0x7 waiting on monitor [0xb8b81000..0xb8b81a28]
 at java.lang.Object.wait(Native Method)
 at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:149)
 at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164)
 at java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:120)
"Reference Handler" daemon prio=10 tid=0xedd40 nid=0x6 waiting on monitor
[0xfad01000..0xfad01a28]
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:420)
 at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:129)
"main" prio=5 tid=0x298c0 nid=0x1 waiting on monitor [0xffbee000..0xffbee4cc]
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:420)
 at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:501)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
 at weblogic.Server.main(Server.java:35)
"VM Thread" prio=5 tid=0xecae0 nid=0x4 runnable
"VM Periodic Task Thread" prio=10 tid=0xf1020 nid=0x8 runnable
------------------end thread dump------------------------
"Mike Reiche" <[email protected]> wrote:
Post your thread dumps and I'll tell you where it's stuck.
(not in Object.wait())
Mike
Joe" <[email protected]> wrote:
Mike, how sure are you about this? How do you know what the poll
method
does
exactly..it is going into native code
Also, we can see our execute threads getting tied up on this methodfor
quite
some time. Im not sure that you are correct on this.
"Mike Reiche" <[email protected]> wrote:
The threads are not really 'stuck' in PosixSocketMuxer.poll - they
are
waiting
for socket connections such as an http request - that is normal.
Mike
"Joe" <[email protected]> wrote:
Did you get a respose about this one yet? We have seen this error
in
our logfiles,
and have had periodic server hangs (thread dumps show execute threads
stuck in
at weblogic.socket.PosixSocketMuxer.poll(Native Method))
Thanks for any info
-joe
[email protected] (Guillaume Morel) wrote:
Hi all,
I run Weblogic 6.0 SP1 on solaris 2.7.
My web application seems to work but randomly, Weblogic seems to
crash.
The logs say the following message.
Any help is welcome! =)
Guillaume
####<Jun 13, 2001 8:49:29 AM GMT+01:00> <Error> <Posix Performance
Pack> <intupc5> <clarify> <ExecuteThread: '12' for queue: 'default'>
<> <> <000000> <Uncaught Throwable in processSockets>
java.io.IOException: error in poll: Interrupted system call
 at weblogic.socket.PosixSocketMuxer.poll(Native Method)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Similar Messages

WL6SP1 - Posix Perf Pack - Interrupted system call

Hi all,
I run Weblogic 6.0 SP1 on solaris 2.7.
My web application seems to work but randomly, Weblogic seems to
crash.
The logs say the following message.
Any help is welcome! =)
Guillaume
####<Jun 13, 2001 8:49:29 AM GMT+01:00> <Error> <Posix Performance
Pack> <intupc5> <clarify> <ExecuteThread: '12' for queue: 'default'>
<> <> <000000> <Uncaught Throwable in processSockets>
java.io.IOException: error in poll: Interrupted system call
 at weblogic.socket.PosixSocketMuxer.poll(Native Method)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Hi all,
I run Weblogic 6.0 SP1 on solaris 2.7.
My web application seems to work but randomly, Weblogic seems to
crash.
The logs say the following message.
Any help is welcome! =)
Guillaume
####<Jun 13, 2001 8:49:29 AM GMT+01:00> <Error> <Posix Performance
Pack> <intupc5> <clarify> <ExecuteThread: '12' for queue: 'default'>
<> <> <000000> <Uncaught Throwable in processSockets>
java.io.IOException: error in poll: Interrupted system call
 at weblogic.socket.PosixSocketMuxer.poll(Native Method)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Zones not booting - failed to create devlinks: Interrupted system call

I just installed the latest 10_Recommended cluster with 118833-36 kernel patch and now my zones won't boot. I get the error:
(root)Yes Master?> zoneadm list -iv
ID NAME STATUS PATH
0 global running /
- samba installed /export/home/zones/samba
- web installed /export/home/zones/web
- dhcp installed /export/home/zones/dhcp
- dns installed /export/home/zones/dns
- vs1 installed /zdata/zones/vs1
- dss installed /zdata/zones/dss
- test installed /zdata/zones/test
(root)Yes Master?> zoneadm -z test boot
failed to create devlinks: Interrupted system call
console setup: device initialization failed
zoneadm: zone 'test': could not start zoneadmd
zoneadm: zone 'test': call to zoneadmd failed
Also, running devfsadm or drvconfig;devlinks from the global zone will core dump.
Any ideas..??
tia..

First, you gotta change your prompt to something less embarrassing when you post to a public forum :)
I'd forget about the zones problem and focus on why devfsadm core dumps -- that's the core of the problem (no pun intended...no, really!).
First, review the install logs of all the patches installed during the recent service (/var/sadm/patch/*/log). Even if they all show a good completion, check the messages they generated, sometimes they have errors that aren't bad enough to cause a complete failure of the patch. The KJP (118833-36) is probably a good one to start with.
Next I'd "truss" the devfsadm command while it core dumps then get a stack trace of the core (run "adb <corefile>" and type "$C" -- that's old school, I'm sure mdb is much cooler...).
Throw some of the strings from those against sunsolve and see if something sticks.
Good luck!

Posix perf pack: Got Exception for fd: 'nn' with no corr. table entry

 My log file is filling up with the following error on an HP9000 with HPUX 11.0
 running WL 5.1 SP9 and JRE 1.2.2-06
 <W> <Posix Performance Pack> Got exception for fd: '59' with no corresponding
 table entry
 Any help appreciated
 Please cc my email if possible
 Thanks
 Ricky


In most cases, these errors can be ignored. Please open a support case with BEA and
report this problem along with a description of any observed side effects (if any).
-Charlie
Krish wrote:
I got an error thrown in the weblogic log shown below
<Posix Performance Pack> Got exception for fd: '126' with no corresponding table
entry
I guess it has something to do with the File Descriptor.I ahve the file descriptor
count set to Max(8096).
Does any one know what this means.
Krish.

POSIX Performance Pack Error!

What's this means:
Fri Mar 16 13:00:36 CST 2001: <Posix Performance Pack> System has file
descriptor limits of - soft: '1024', hard: '1024'
Fri Mar 16 13:00:36 CST 2001: <Posix Performance Pack> Using effective
file descriptor limit of: '1024' open sockets/files.
Fri Mar 16 13:00:36 CST 2001: <Posix Performance Pack> Allocating: '3'
POSIX reader threads
Fri Mar 16 13:00:37 CST 2001: <WebLogicServer> WebLogic Server started
Fri Mar 16 13:01:06 CST 2001: <ServletContext-General>
seCurity_Haoyisheng: init
Fri Mar 16 13:01:24 CST 2001:<E> <HTTP> Connection failure
java.net.SocketException: Error in poll for fd: '59', revents: '59'
at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:293)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
My system:RedHat7,SUN JDK1.3(Hotspot Server Mode),WebLogic5.1Sp8

When we start application that connects to WLS we get this message. in the LOG.
####<Mar 18, 2002 10:23:49 AM EST> <Error> <Posix Performance Pack> <fiepnprod
<myserver> <ExecuteThread: '297' for queue: 'default'> <> <> <000000> <Uncaug
Throwable in processSockets>

Trex installation error FSL-00001 System call failed. Error 3

I am installing trex on multiple hosts for a Production setup. Trex is version 7.0 patch level 40. All hosts are Windows servers running on "Windows Server 2003 R2 Enterprise x64 Edition, Service Pack 2" Distribution of trex instances are as follows,
Index Server =1
Slave Server =1
Backup Server =1
File Server =1
I started of with installing Trex global filesystem which resulted in following error,
ERROR 2008-10-23 15:19:27
FSL-00001 System call failed. Error 3 (The system cannot find the path specified.
) in execution of system call 'FindFirstVolumeMountPoint' with parameter (
?\Volume{51f489f8-8ef6-11dd-886f-001e0beae60e}\), line (91) in file (synxcfsmit.cpp).
ERROR 2008-10-23 15:19:27
MUT-03025 Caught ESyException in Modulecall: The system cannot find the path specified.
ERROR 2008-10-23 15:19:27
FCO-00011 The step getMounts with step key |NW_TREX_Prepare|ind|ind|ind|ind|0|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|NW_getMounts|ind|ind|ind|ind|0|0|getMounts was executed with status ERROR .
Installation is performed by administrator user and so has full access rights. Has anyone encountered such an error before.
Regards,
Sandeep

I uninstalled the Python application via the Windows "Add/Remove" programs utility and that seems to have resolved the issue.
TREX has been installed successfully.

How to get swap size by using system call?

How can I get the size of swap.What system call or library Routines can be used? please help me.

Hi,
Threre's an interface called swap_ctl by wich you can get more information related to virtual memory. Here's an example:
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <sys/stat.h>
#include <sys/swap.h>
#include <sys/param.h>
int
main(int argc, char*argv[])
swaptbl_t *st;
int swap_count, i;
long long swap_total=0, swap_avail=0;
long pgsize_in_kbytes = sysconf(_SC_PAGE_SIZE) / 1024L;
if ((swap_count=swapctl(SC_GETNSWP, NULL)) == -1)
perror("swapctl(SC_GETNSWP)"), exit(-1);
if (swap_count == 0)
(void)printf("No swap files/partitions allocated\n"), exit(0);
* Although it's not particularly clear in the documentation, you're
* responsible for creating a variable length structure (ie. the
* array is within the struct rather than being pointed to
* by the struct). Also, it is necessary for you to allocate space
* for the path strings (see /usr/include/sys/swap.h).
st = (swaptbl_t*)malloc(sizeof(int) + swap_count * sizeof(struct swapent));
if (st == NULL)
perror(argv[0]), exit(-1);
st->swt_n = swap_count;
for (i=0; i < swap_count; i++) {
if ((st->swt_ent.ste_path = (char*)malloc(MAXPATHLEN)) == NULL)
perror(argv[0]), exit(-1);
if ((swap_count=swapctl(SC_LIST, (void*)st)) == -1)
perror("swapctl(SC_LIST)"), exit(-1);
for (i=0; i < swap_count; i++) {
swap_total += st->swt_ent.ste_pages * pgsize_in_kbytes;
swap_avail += st->swt_ent.ste_free * pgsize_in_kbytes;
(void)printf("Total swap = %lld available swap = %lld\n",
swap_total, swap_avail);
return 0;
There's a very interesting document about Solaris Kernel/Performance Stats available at http://www.idiom.com/~gford/admin/howto/perf.html. Very interesting.
Hope this helps

HPUX - can't load Perf Pack - WLS 5.1

What is the name of the Perf Pack .sl? I'm not sure I have it but I
have nativeIO turned on in the weblogic.properties file and have the
SHLIB_PATH
set to where the hpux libs are. Also, the file permissions look good as
well. This is WLS 5.1 SP8.
The Performance Pack couldn't be loaded- - here's the skinny:
weblogic.log:
Fri Oct 26 12:46:24 EDT 2001: <ListenThread> Listening on port: 83
Fri Oct 26 12:46:24 EDT 2001: <SSLListenThread> Listening on port: 446
Fri Oct 26 12:46:25 EDT 2001:<A> <Posix Performance Pack> Could not
initialize P
OSIX Performance Pack.
Fri Oct 26 12:46:25 EDT 2001:<E> <Performance Pack> Unable to load
performance p
ack, using Java I/O.
Fri Oct 26 12:46:25 EDT 2001: <WebLogicServer> WebLogic Server started
Environment:
# ls -lt | more
total 2454
drwxrwxr-x 2 prod prodadm 96 Oct 11 22:24 oci815_8
drwxrwxr-x 2 prod prodadm 96 Oct 11 22:24 oci805_8
drwxrwxr-x 2 prod prodadm 96 Oct 11 22:24 oci804_8
drwxrwxr-x 2 prod prodadm 96 Oct 11 22:24 oci804_7
-rwxrwxr-x 1 prod prodadm 281778 Aug 9 17:04 zac_hpux
-rwxrwxr-x 1 prod prodadm 24669 Aug 9 17:04 libmuxer.sl
-rwxrwxr-x 1 prod prodadm 12311 Aug 9 17:04 libwlenv.sl
-rwxrwxr-x 1 prod prodadm 16406 Aug 9 17:04
libweblogicunix1.sl
-rwxrwxr-x 1 prod prodadm 352048 Aug 9 17:03 mod_wl.so
-rwxrwxr-x 1 prod prodadm 212992 Aug 9 17:03 libproxy.sl
-rwxrwxr-x 1 prod prodadm 352048 Aug 9 17:03 mod_wl_ssl.so
This directory (weblogic/lib/hpux11) is in my SHLIB_PATH

Mike,
This is a known problem with SP 8. You may want to go to SP 10.
"Mike Sprague" <[email protected]> wrote:
What is the name of the Perf Pack .sl? I'm not sure I have it but I
have nativeIO turned on in the weblogic.properties file and have the
SHLIB_PATH
set to where the hpux libs are. Also, the file permissions look good
as
well. This is WLS 5.1 SP8.
The Performance Pack couldn't be loaded- - here's the skinny:
weblogic.log:
Fri Oct 26 12:46:24 EDT 2001: <ListenThread> Listening on port: 83
Fri Oct 26 12:46:24 EDT 2001: <SSLListenThread> Listening on port:
446
Fri Oct 26 12:46:25 EDT 2001:<A> <Posix Performance Pack> Could not
initialize P
OSIX Performance Pack.
Fri Oct 26 12:46:25 EDT 2001:<E> <Performance Pack> Unable to load
performance p
ack, using Java I/O.
Fri Oct 26 12:46:25 EDT 2001: <WebLogicServer> WebLogic Server started
Environment:
# ls -lt | more
total 2454
drwxrwxr-x 2 prod prodadm 96 Oct 11 22:24 oci815_8
drwxrwxr-x 2 prod prodadm 96 Oct 11 22:24 oci805_8
drwxrwxr-x 2 prod prodadm 96 Oct 11 22:24 oci804_8
drwxrwxr-x 2 prod prodadm 96 Oct 11 22:24 oci804_7
-rwxrwxr-x 1 prod prodadm 281778 Aug 9 17:04 zac_hpux
-rwxrwxr-x 1 prod prodadm 24669 Aug 9 17:04 libmuxer.sl
-rwxrwxr-x 1 prod prodadm 12311 Aug 9 17:04 libwlenv.sl
-rwxrwxr-x 1 prod prodadm 16406 Aug 9 17:04
libweblogicunix1.sl
-rwxrwxr-x 1 prod prodadm 352048 Aug 9 17:03 mod_wl.so
-rwxrwxr-x 1 prod prodadm 212992 Aug 9 17:03 libproxy.sl
-rwxrwxr-x 1 prod prodadm 352048 Aug 9 17:03 mod_wl_ssl.so
This directory (weblogic/lib/hpux11) is in my SHLIB_PATH

Posix Performance Pack Issues 5.1 sp6

I am currently running v5.1 sp6. Java is running with native threads.
Has anyone encountered this issue before:
Wed Oct 25 16:50:24 EDT 2000:<E> <Posix Performance Pack> Failure in
processSock
ets()
java.net.SocketException: Connection reset by peer: Connection reset by peer
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.socketRead(Compiled Code)
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
23)
at weblogic.kernel.ExecuteThread.run(Compiled Code)

These are innocuous. Don't worry about them.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Greg Panzer" <[email protected]> wrote in message
news:39f75188$[email protected]..
I am currently running v5.1 sp6. Java is running with native threads.
Has anyone encountered this issue before:
Wed Oct 25 16:50:24 EDT 2000:<E> <Posix Performance Pack> Failure in
processSock
ets()
java.net.SocketException: Connection reset by peer: Connection reset bypeer
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.socketRead(Compiled Code)
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
23)
at weblogic.kernel.ExecuteThread.run(Compiled Code)

Posix Performance Pack & file discriptor limitation

This question doesn't appear to relate to our Enterprise product, so I'm
responding to this message in the performance newsgroup as well. Please see
answers below:
Andy Ping wrote:
What is Posix Performance Pack about?This refers to the availability of enhanced I/O handling (enabled by default
with the Solaris version of WLS) and is documented at:
http://www.weblogic.com/docs51/admindocs/tuning.html#performance packs
>
And How to resolve the file dirscritor limitation? Is ulimit OK?The Solaris file descriptor limits are set using lines similar to:
set rlim_fd_cur = 1024
set rlim_fd_max = 8192
in your /etc/system file. In the above case, user processes are allowed 1K open
files by default and can up this limit to 8K files using the ulimit command.
You might have noticed that this command is used in the weblogic startup script
to accomplish this. Judging by your log entries, I'd guess that your tunables
are both set to 512. You might want to consider raising your maximum to 1K.
Perhaps other newsgroup readers can suggest/recommend better file descriptor
limits.
Environment: sun solaris 2.6, weblogic.5.1 jdk1.2.2_006, oracle815.
phenomena:
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < ListenThread > Listening on
port: 7001
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < Posix Performance Pack >
System has file descriptor limits of - soft: '512', hard: '512'
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < Posix Performance Pack >
Using effective file descriptor limit of: '512' open sockets/files.
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < Posix Performance Pack >
Allocating:'3' POSIX reader threads
If use jdk1.1.7b, the phenomena:
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < EJB > 0 deployed, 0 failed
to deploy.
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < HTTP > Log rotation is size
based
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < ZAC > ZAC ACLs initialized
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < ZAC > ZAC packages stored
in local directory exports
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < ListenThread > Listening on
port: 7001
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < Posix Performance Pack >
System has file descriptor limits of - soft: '512', hard: '512'
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < Posix Performance Pack >
Using effective file descriptor limit of: '512' open sockets/files.
D??¨²?? ¨º??? 26 10:51:20 GMT+08:00 2000: < Posix Performance Pack >
Allocating: '3' POSIX reader threads
D??¨²?? ¨º??? 20 00:58:28 GMT-05:00 2000:< E > < Posix Performance Pack >
Failure in processSockets()
java.net.SocketException: Connection reset by peer
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
D??¨²?? ¨º??? 20 00:58:28 GMT-05:00 2000:< E > < Posix Performance Pack >
Failure in processSockets()
java.net.SocketException: Connection reset by peer
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
D??¨²?? ¨º??? 20 00:59:23 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource 'high_tech_area/front/file/htprog.css' in document root
'/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 00:59:28 GMT-05:00 2000: < ServletContext-General >
Generated java file:
/opt/weblogic/weblogic/myserver/classfiles/jsp_servlet/_high_tech_area/_fron
t/_bbs/_bbs_list.java
D??¨²?? ¨º??? 20 00:59:32 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource 'high_tech_area/front/file/htprog.css' in document root
'/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 01:00:36 GMT-05:00 2000:< E > < Posix Performance Pack >
Failure in processSockets()
java.net.SocketException: Connection reset by peer
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
D??¨²?? ¨º??? 20 01:00:52 GMT-05:00 2000:< E > < Posix Performance Pack >
Failure in processSockets()
java.net.SocketException: Connection reset by peer
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
D??¨²?? ¨º??? 20 01:02:53 GMT-05:00 2000: < ServletContext-General >
Generated java file:
/opt/weblogic/weblogic/myserver/classfiles/jsp_servlet/_high_tech_area/_fron
t/_bbs/_bbs_list.java
D??¨²?? ¨º??? 20 01:02:54 GMT-05:00 2000: < ServletContext-General >
Generated java file:
/opt/weblogic/weblogic/myserver/classfiles/jsp_servlet/_high_tech_area/_back
/_hbk_perlaw/_hbk_perlaw_add.java
D??¨²?? ¨º??? 20 01:03:02 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource 'high_tech_area/front/file/htprog.css' in document root
'/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 01:03:11 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource 'high_tech_area/front/file/htprog.css' in document root
'/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 01:03:15 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource 'high_tech_area/front/file/htprog.css' in document root
'/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 01:03:21 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource 'high_tech_area/front/file/htprog.css' in document root
'/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 01:04:02 GMT-05:00 2000:< E > < Posix Performance Pack >
Failure in processSockets()
java.net.SocketException: Connection reset by peer
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
D??¨²?? ¨º??? 20 01:04:22 GMT-05:00 2000: < ServletContext-General >
Generated java file:
/opt/weblogic/weblogic/myserver/classfiles/jsp_servlet/_high_tech_area/_fron
t/_bbs/_bbs_list.java
D??¨²?? ¨º??? 20 01:04:28 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource 'high_tech_area/front/file/htprog.css' in document root
'/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 01:04:33 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource '/high_tech_area/back/hbk_perlaw/hbk_perlaw_list.jsp'
in document root '/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 01:04:45 GMT-05:00 2000:< E > < ServletContext-General >
Cannot find resource '/high_tech_area/back/hbk_perlaw/hbk_perlaw_list.jsp'
in document root '/opt/weblogic/weblogic/myserver/public_html'
D??¨²?? ¨º??? 20 01:05:31 GMT-05:00 2000:< E > < Posix Performance Pack >
Failure in processSockets()
java.net.SocketException: Connection reset by peer
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)You will probably want to select your WLS/JDK environment using the platform
support information at:
http://www.weblogic.com/platforms/index.html#solaris
Hope this helps.
-Charlie

Error during installation of ECC6- system call failed

Dear all,
i encounter the error as below during sap installation. its looks like the ID issue, but this id (fbqadm) is using by me to log into the windows. please help me.
thank
ERROR 2009-03-17 10:07:25.583 [syxxsyshlp.cpp:78]
 syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage)
FSL-00001 System call failed. Error 1326 (Logon failure: unknown user name or bad password.
) in execution of system call 'LogonUser' with parameter (fbqadm, SAPFBWDEV01, *******, LOGON32_LOGON_INTERACTIVE,LOGON32_PROVIDER_DEFAULT,&hUserToken), line (1014) in file (synxccuren.cpp).
TRACE 2009-03-17 10:07:25.813 [iaxxejsbas.hpp:408]
 handleException<ESyException>()
Converting exception into JS Exception ESyException.
TRACE 2009-03-17 10:07:25.813
Function setMessageIdOfExceptionMessage: modlib.jslib.caughtException

problem fix after reboot the server

Error on WAS no. 10054 SAP Basis System: Operating system call

Hi All,
Error on WAS no. 10054 SAP Basis System: Operating system call
we got the following error message in the syslog of the WAS:
SAP Basis System: Operating system call recv failed (error no. 10054)
The system still works. What can we do?
Thanks.
Best Regards,

Hi,
Please check the folloiwng notes
Error no. 10054
34116 - Syslog: "Operating System call xxxx failed"
Thanks
Adil

Correct Forum? CGI and Server behaviour on Solaris at system()-call

Hi to you all,
Do not know if i am in the correct forum, but maybe it is a Webserver problem.
I have Sun ONE Webserver 6.1 running on Solaris.
Craete some CGI`s in C.
Now I have a problem with one CGI, which have to call a Shellscript via system() call.
The Client just calls the CGI with some parameters, which will write the informations in a file with some additional informations from a database, after that, the script should be startet and do some printjobs in the background.
The CGI and the Shell-script is working fine. My Problem is, that the system() call always waits, until the ShellScript has finished, so the Webserver send the "data successful written" site after a couple of minutes, it should send it immeditatly to the client, so the session is closed.
I have tried to put the shellscript in background with "&", also with nohup and a second shell script which justs starts the first script, also with all combinations of nohup and "&" for background process.
also i tried with "pclose(popen(SCRIPT,"W");" to call the script, it is always the same, the session will close only, when the script has been finished.
In an other Forum I found an entry, that , however, IPlanet webserver always will do this in this way. The session will be closed, when all called processes has benn fisnished.
Any Ideas to solve my problem?

The web server reads from the CGI program's stdout. It knows the HTTP response is complete when the CGI program closes its stdout.
When you call system(), the child process inherits the CGI program's stdout and keeps it open until it finishes. If you want the child process to run asynchronously from the HTTP response, you should give the child process a new stdout with > /dev/null. (You'll still need to place the child process in the background with &.) Alternatively, you can fork(), close(1), then exec().

Tracing what is happening in the connect() system call

I've been playing around with some of the recipies in dtrace today trying to find out why it takes so long to connect from a linux machine to an ultra 5 running sendmail but I'm not having a lot of luck.
The one thing I can find is that the amount of time for the connect system call to return takes a long time. Here's the dtrace script I wrote (borrowing from Bryan Cantrill's blog):
bash-2.05b# cat functiontime.d
#!/usr/sbin/dtrace -s
#pragma D option flowindent
syscall::connect:entry
/execname == "sendmail"/
self->start = vtimestamp;
syscall:::entry,
syscall:::return
/self->start/
trace(vtimestamp - self->start);
syscall::connect:return
/execname == "sendmail"/
self->start = 0;
exit(0);
This is the output:
bash-2.05b# ./functiontime.d
dtrace: script './functiontime.d' matched 454 probes
CPU FUNCTION
0 => connect 0
0 | connect:return 303079
0 <= connect
I know there are other syscalls going on from the time connect enters to the time it returns but I have no idea how to get them to print.
Any ideas how I can make this script more useful to see exactly where sendmail is getting hung up?

You might also try something like
#!/usr/sbin/dtrace -s
#pragma D option flowindent
syscall::connect:entry
/execname == "sendmail"/
 self->depth = 1;
 self->syscallstart = timestamp
fbt:::entry
/self->depth/
 self->start[self->depth] = timestamp;
 trace(self->start[self->depth++] - self->syscallstart);
fbt:::return
/self->depth/
 this->delta = timestamp - self->start[--self->depth];
 @func[probefunc] = quantize(this->delta);
 printf("delta is %d\n", this->delta);
 self->start[self->depth] = 0;
syscall::connect:return
/self->depth/
 exit(0);
}This will give you the function call flow inside the kernel along with the following:
- on function entry, a time delta since connect was called
- on function exit, how long we spent in the function
- on return from the connect system call, a list of histograms showing the call times for all functions called
You are probably going to want to redirect the output as it gets big.
Also note, I've written this to give the information only for the first call to connect.
Alan.
Alan Hargreaves - http://blogs.sun.com/tpenta
Senior Technical Support Specialist/VOSJEC Engineer
Product Technical Support (APAC)
Sun Microsystems

Exchange 2007 SP3 Install on 2008R2 Fails with "The data passed to a system call is too small"

I'm installing Exchange 2007 SP3 onto Server 2008 R2. I have run this install in compatibility mode and in normal install mode with the same results. Error code 3221684346: The data area passed to a system call is too small. I am installing directly from
the SP3 files, this is not an upgrade. What do I have to do to get this to work?
[2/15/2011 7:24:18 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[2/15/2011 7:24:18 AM] [2] CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Processing file 'C:\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Registry file name: 'C:\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2] CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2] CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving ScSetupAtom
[2/15/2011 7:24:18 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] The following 1 error(s) occurred during task execution:
[2/15/2011 7:24:18 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[2/15/2011 7:24:18 AM] [1] Finished executing component tasks.
[2/15/2011 7:24:18 AM] [1] Ending processing.
[2/15/2011 7:42:08 AM] [0] End of Setup
[2/15/2011 7:42:08 AM] [0] **********************************************

I would probably rebuild the host machine. The Exchange installation should occur without any issues, and where a problem does occur that can be an indication of a more widespread problem. Rebuild the machine, reinstall the prerequisites and try again.
Simon.
Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Hello Poster.
I am having the same issue, however it is most likely NOT a host box problem. The above advice is not a fix. I have 3 servers that are cloned with the same setup. 2 were fixed by doing the Vista compatibility trick, this one gave a different error (which
happened to be the same as above). This org was a 5.5 to 2000. to 2003 coexistence with 2007 currently(because the mailbox role won't install). It has something to do with AD or permissions. Server 2008 r2 inherently has problems installing exchange.
Example, having to use vista compatibility to get the mailbox role to install. SP2 patch gives the same error to some people, and also doesn't upgrade the mailbox role properly in some cases. Some people have had luck restarting the IIS admin service, but
that did not solve my copy of this error. I will repost here if I find a solution to this issue...
Same exact setup log for me as well.
[3/4/2011 10:45:51 AM] [2] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services> -- ID:31259 --
[3/4/2011 10:45:51 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[3/4/2011 10:45:51 AM] [2] CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Processing file 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Registry file name: 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[3/4/2011 10:45:51 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[3/4/2011 10:45:51 AM] [2] CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[3/4/2011 10:45:51 AM] [2] CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[3/4/2011 10:45:51 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[3/4/2011 10:45:51 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
 Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving ScSetupAtom
[3/4/2011 10:45:51 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] The following 1 error(s) occurred during task execution:
[3/4/2011 10:45:51 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[3/4/2011 10:45:51 AM] [1] Finished executing component tasks.
[3/4/2011 10:45:51 AM] [1] Ending processing.
Just curious though, how long is your FQDN? Mine is 34 characters plus whatever exchange is adding to it during setup for this particular string. I found a post with the same error for ISA server and some buffer is only 100 characters for a system call.
ERROR_INSUFFICIENT_BUFFER 122 (0x7A) The data area passed to a system call is too small. http://msdn.microsoft.com/en-us/library/ms681382(v=vs.85).aspx Indicates a msft programming problem.
Outsource Technology Inc. MSFT Professional Consultant

Posix Perf Pack - Interrupted system call (WL6SP1)

Similar Messages

Maybe you are looking for