Solaris 2.6 - System Call faults

Hi Sun Forums.
Machine Description : SunOS serv-sif 5.6 Generic_105181-28 sun4u sparc SUNW,Ultra-Enterprise
Number of CPU's : 4 (400Mhz)
Physical Memory : 5120 Mb
Top Output :
PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
11115 syb119 2 10 0 506M 498M cpu4 179.6H 24.89% dataserver
5078 syb119 1 0 0 1696K 1408K cpu0 0:00 0.51% top
11113 syb119 2 58 0 506M 498M sleep 146.3H 0.09% dataserver
3592 syb119 2 59 0 1030M 1023M sleep 282.6H 0.07% dataserver
1193 root 1 58 0 7536K 3144K sleep 159:38 0.02% jre
1199 root 1 59 0 3144K 1064K sleep 0:00 0.01% httpd
3596 syb119 2 59 0 1030M 1023M sleep 110.6H 0.01% dataserver
11114 syb119 2 58 0 506M 498M sleep 168.6H 0.00% dataserver
3595 syb119 2 58 0 1030M 1022M sleep 151.6H 0.00% dataserver
1182 root 1 58 0 5128K 2768K sleep 17:53 0.00% jre
1 root 1 58 0 1648K 384K sleep 5:40 0.00% init
19230 syb119 1 58 0 10M 1968K sleep 0:43 0.00% backupserver
1253 root 1 58 0 16M 1624K sleep 0:43 0.00% ecoad
1052 root 18 23 0 4736K 1608K sleep 0:42 0.00% syslogd
1026 root 1 48 0 1904K 1144K sleep 0:41 0.00% inetd
Possible Problem : vmstat
procs memory page disk faults cpu
r b w swap free re mf pi po fr de sr s6 s9 s1 sd in sy cs us sy id
0 0 0 4710944 80856 0 0 392 0 0 0 0 0 0 0 0 3208 512747 1557 49 51 0
The value Faults for System call = 512747 very high value.
The process running in Solaris are working slowly ...
Any idea ?
PID

It is possible that this card may not be compatible with this Solaris
system.
You may want to check these sites out for driver related information:
http://soldc.sun.com/developer/support/driver/
http://soldc.sun.com/developer/support/driver/IO_kit/PCI.html
Thx
Tushar Patel.

Similar Messages

Solaris 10: intercepting system calls

Hello,
I have a problem: I don't manage to intercept system calls (as described in this document http://packetstormsecurity.org/groups/thc/slkm-1.0.html). Is it because solaris 10 doesn't use the syscall table ?
Another problem that I have is that I don't manage to perform a simple printf() on the screen when I use a load my kernel module. Has someone got an explanation ?
In fact I need to intercept some syscall like SYS_open, SYS_read, ... to perform custom actions. Do you have another way to do this ?
Thanks in advance for you help.

BTW, I'm running 64-bit Solaris as a VirtualBox (3.0.10) guest VM on a 32-bit WinXP host.

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().

Need guidance on using ddi_regs_map_setup solaris system call

Hi all,
Am a beginner in using Sun Solaris.
I am working on porting our source code from linux to solaris.
In Linux we are using inb/outb to read/write to keyboard data port(0x60) .
I know that there is an equivalent system call for inb/outb in solaris. But in man page(of sun os) it is mentioned that inb/ outb are obsolete. It was mentioned that we can use ddi_get8/ddi_put8 functions respectively.
ddi_get8 call requires ddi_acc_handle_t as a parameter which we can get it from ddi_regs_map_setup system call.
Syntax for this call is:
int ddi_regs_map_setup(dev_info_t *dip, uint_t rnumber,
caddr_t *addrp, offset_t offset, offset_t len,
ddi_device_acc_attr_t accattrp, ddi_acc_handle_t handlep);
Please let me know where does the 0x60 port number fits in the above system call and what does these parameters rnumber, offset, len corresponds to ?

Hi,
The Fault_PC 0x13575e8 tells you exactly where you
die. I assume you have used this in mdb on
the core file to find you are dying in the ddi_get8 call?
Are you checking return value of ddi_regs_map_setup?
Are you sure the register you are accessing is in register set 1?
Are there other places prior to the panic where
the ddi_get/ddi_put routines work correctly? A bus error
here generally means the location you are trying to access
does not exist on the device. (It could also be alignment,
but not with ddi_get8). The address
looks like 1fe.02001400, which looks like a possibly
valid address in I/O space.
I would print the value of wc->ioaddr to make sure
it is a valid virtual address.
Hi,
I'm in the middle of porting a device driver for a
PCI card from linux to solaris (it's wcfxo from
zaptel - part of asterisk).
>
WARNING: [AFT1] Bus Error on System Bus in privileged
mode from CPU0 Data access at TL=0, errID
0x0000000b.985ccf88
AFSR 0x00000000.84000000<PRIV,BERR> AFAR
AFAR 0x000001fe.02001400
AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00
0x00 Fault_PC 0x13575e8
UDBH 0x0000 UDBH.ESYND 0x00 UDBL 0x0000
0000 UDBL.ESYND 0x00
panic[cpu0]/thread=2a10007dd40: [AFT1] errID
0x0000000b.985ccf88 BERR Error(s)
See previous message(s) for detailsThe actual code which seems to cause the panic is:
#define inb(a) ddi_get8(wc->devhandle, a)
ints = inb(wc->ioaddr + WC_INTSTAT);where there initialisation includes:
static struct ddi_device_acc_attr dev_attr = {
DDI_DEVICE_ATTR_V0,
DDI_STRUCTURE_LE_ACC,
DDI_STRICTORDER_ACC
ddi_regs_map_setup(wc->dip, 1, &wc->ioaddr, 0, 255,
&dev_attr,
&dev_attr, &wc->devhandle);I've tested the same card in a linux x86 box, and it
works fine, so I'm happy it's not a hardware
problem.
Any suggestions on what might be causing this?
Thanks,
Simon

List of Non-thread safe system calls in Solaris 2.6??

Hi,
I'm searching for a list of system calls which are known to be non thread safe in a multithreaded process in Solaris 2.6. Anyone know of such a list?

I'm not aware of any list but you can easily find the list by looking for the following pattern in the man pages :-)
| ATTRIBUTE TYPE| ATTRIBUTE VALUE|
|__________________________________
| MT-Level | Unsafe |
|_______________|_________________|
HTH
Angelo
Sun Developer Support.

Problems with accept () system call in Solaris 10

We are doing some prototyping in Solaris 10/Zones using TCP sockets and have encountered the problem the "accept" system call in Solaris 10 always seem to return immediately without waiting for clients to connect to it. The same program works fine under Solaris 9 without any problems.
So in the following call:
ssock = accept( sockfd, (struct sockaddr*)bind_address, &alen );
if( ssock < 0 )
printf( "Accept failed: ...\n" );
the program always prints "accept failed: " continuously. Is this a known issue?

The problem only occurs when we use INADDR_ANY to bind a socket. The program works as expected when we use real as well as virtual IP address configured for an interface on any Solaris Zone. When we use INADDR_ANY, error number is 14 (EFAULT, Bad Address).
Just wondering if we need to make any configuration changes in order to allow INADDR_ANY to work.

How to add new system call in solaris ?

Hi,
I want to add new system call in solaris. please inform me steps for adding new system call in solaris.
Thanks in advance,
Mahantesh.

Here's a Solaris 7 example I know there are others ...
http://access1.sun.com/cgi-bin/rinfo2html?267899.faq
I haven't seen a good example of how to support both the 32 and 63-bit environment.

Issuing Solaris system calls through Java

How can I issue a system call to Solaris using Java? (i.e. Start a script, open a file, and similar)

Hi Srini,
This is just a suggestion, but try entering the following commands (in your SQL*Plus session) before executing your stored procedure:
set serveroutput on size 1000000
exec dbms_java.set_output(1000000)Hope this helps.
Good Luck,
Avi.

How to get the size of physical memory by using system call ?

how to get the size of physical memory by using system call ?What system call can be used for me to get the size of physical memor? thanks.

%vmstat 3
procs memory page disk faults cpu
r b w swap free re mf pi po fr de sr s0 -- -- -- in sy cs us sy id
0 0 0 3025816 994456 4 19 6 0 0 0 0 8 0 0 0 459 253 139 1 1 99
0 0 0 2864688 777408 0 2 0 0 0 0 0 3 0 0 0 428 134 175 0 1 99
0 0 0 2864688 777408 0 0 0 0 0 0 0 7 0 0 0 448 112 166 0 0 100
one interesting observation about vmstat I found out is (mostly on Solaris)
the first line of information always off chart, so I usually do a few interval to get constant result.
if you use linux
just
cat /proc/meminfo

How to intercept system calls in JVM?

Hi, everyone. I am looking for a way to intercept system calls in JVM, a way do something like ptrace does in Linux. Because I wanna log all function calls a specified application made, and I may modify the arguments and the return value.
And then i search the internet but nothing found except this article:
[ http://java.sun.com/developer/technicalArticles/Programming/jvmti/#Authors| http://java.sun.com/developer/technicalArticles/Programming/jvmti/#Authors]
It's seems that JVMTI is a perfect tools to manipulate Java VM and i can achieve my goal with it. I download the sample code you written and modify a bit to adopt my environment (I use Linux and Sun JDK 6). It works well.
And then I add a function to get stacktrace like the case in your article. I also read the sample code in JVMIT Refenerce, but it doesn't work.
So, I am puzzled. I wanna know is there any way to intercept system calls in JVM? If JVMTI can do it, is there any tutorial or sample code to review? And, is that possible to use this way in J2ME?
Thanks a lot :)
Best Regard.

jschell wrote:
Nelly_Zeltser wrote:
I do not know if there are any tools similar to solaris truss is available to trace system and library calls in j2me world.Well, I want to trace the jvm system calls to OS (UNIX), not java.Are you using j2me?No, to say more I'm not "using" java at all. My program (written on C) just monitors all system calls from another program that I define as the parameter.
It may not be java. It may be any program:for example my simple .o file made by myself.
Can we continue this topic at [http://forums.sun.com/thread.jspa?messageID=10746765&#10746765|http://forums.sun.com/thread.jspa?messageID=10746765&#10746765]
I've written my shared library and defined LD_PRELOAD. But it doesn't help, cuz JVM, afaik, uses LD_PRELOAD for its own purposes, so
I can't use my shared library.That of course is not what the poster of this thread wanted to do.

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)

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)

Init 5 doesn't shutdown Solaris 8 Sparc system

Hi,
I am trying to bring down the Solaris 8 Sparc system using the command # init 5 but it doesn't do anything whereas the command # shutdown brings down the system. What could be the problem of init 5 command not functioning.
Thanks & Regards

ok, i should have caught this earlier
looks like, your program is not able to start because of not finding a symbol called __res_state. This symbol is found in /usr/lib/libresolv.so.2
the most likely reason is that u probably do not have some required patches installed
if u r open to install the sun patch cluster , then that is probably the best way to go
visit the below url
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
and look for solaris 9 (around 180 mb of size) download this patch cluster and install them in single user mode
btw, when u have installed the jes version of web server,it is already running only in 32 bit.
hope this helps

System call "copy" for C++ compiler 4.2?

System call "rename" is very close to what I am looking for but "copy" is better because I need to keep the original file. Where I can find it, or any equivalent?
MM
[email protected]

I don't know of a Solaris system call to copy files. I do know there is no such C or C++ standard library function.
It's easy enough to write a file copy routine, however.
C++ 4.2 is obsolete and no longer supported. It predates the 1998 C++ standard by a few years.
But using old-style C++, here is a copy-file routine:
#include <fstream.h>
int copyfiles(const char* i, const char* o)
ifstream in(i, ios::in|ios::binary);
ofstream out(o, ios::out|ios::binary);
out << in.rdbuf();
return !(!in && !out);
You pass it the names of the input and output files. It opens the files in binary mode, copies input to output if possible, and reports status by returning 1 for success and 0 for failure.
Using standard C++, the routine looks like this:
#include <fstream>
bool copyfiles(const char* i, const char* o)
std::ifstream in(i, std::ios::binary);
std::ofstream out(o, std::ios::binary);
out << in.rdbuf();
return !(!in && !out);

System call support for unicodes

Hi Solaris guru,
One of my application (C,Solaris2.7) is required to work in multiple languages. This application makes use of system & C library calls. Is it possible for a japanese user to create file names in japanese? if so how will I able to use these names (let's assume unicodes) with standard system calls and library routines which consider file names has char *?
I have noticed that Solaris provides wchar_t and (wchar.h) wide string library calls (Ex, wprintf, wscanf, wcstrcmp etc). are there any similar w-version of system calls?
I greatly appreciate your help.
Cheers
Ramesh

I don't know of a Solaris system call to copy files. I do know there is no such C or C++ standard library function.
It's easy enough to write a file copy routine, however.
C++ 4.2 is obsolete and no longer supported. It predates the 1998 C++ standard by a few years.
But using old-style C++, here is a copy-file routine:
#include <fstream.h>
int copyfiles(const char* i, const char* o)
ifstream in(i, ios::in|ios::binary);
ofstream out(o, ios::out|ios::binary);
out << in.rdbuf();
return !(!in && !out);
You pass it the names of the input and output files. It opens the files in binary mode, copies input to output if possible, and reports status by returning 1 for success and 0 for failure.
Using standard C++, the routine looks like this:
#include <fstream>
bool copyfiles(const char* i, const char* o)
std::ifstream in(i, std::ios::binary);
std::ofstream out(o, std::ios::binary);
out << in.rdbuf();
return !(!in && !out);

Solaris 2.6 - System Call faults

Similar Messages

Maybe you are looking for