Patch problem in SUNWappserver under Solaris 10
When attempting to install the patch 119166-15 for AppServer 8.1, I get the following info and error:
<--- Begin Session text --->
# patchadd -G 119166-15.jar
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SUNWaslb from directory SUNWaslb in patch 119166-15 is not installed on the system.
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
119166-15
Verifying signed patch <119166-15>...
Verifying digital signature for signer <es-signature>
ERROR: Signature verification failed while verifying certificate <subject=Sun Microsystems Inc Root CA, issuer=GTE CyberTrust Root>:<unable to get local issuer certificate>.
ERROR: Unable to verify signature for signer <es-signature>
Signature invalid on signed patch <119166-15>.
Patchadd is terminating.
<---End Session test --->
Also having problems running "asadmin" ; I cannot determine which port the Admin Server is running on or needs to be running on. Fairly new to SUN OS, so any "dummy" pointers would probably help...
Regatds...
Texas Mike....
You might want to ask about patching issue on Solaris update forums since as far as I can tell issue is not related to the fact that patch is for Application Server - it seems to be generic problem with patch signature verification. Solaris update and patching forum URL:
http://forum.sun.com/jive/forum.jspa?forumID=316
As for the asadmin question: first you need to start your server using 'asadmin start-domain' command and you do not need to know the port number to do that. After that you can try accessing https://localhost:4849 (4849 is the default value for admin application URL port number).
Similar Messages
-
How to apply signed patches to Studio 11 under Solaris 10?
I'm running Solaris 10 6/06 on a Sun W2100z (x86_64) workstation. I have a long history of experience with Solaris, but I'm not terribly familiar with the things that are new or different with 10, including zones and the new patch management tools.
I want to apply the latest patches to the various components of Studio 11, e.g. 120759-08,
121018-04, etc. Since all the other patches I've applied (for other OS subsets) have been "signed" patches, I was hoping to stay consisent and apply signed patches to Studio 11 too. I've been foiled at every attempt, though, so I'm looking for some help.
- if I use /usr/bin/updatemanager to select and attempt to apply the patches, I just get error
messages saying that the patches could not be applied:
121016-03 Sun Studio 11_x86: Patch for Sun C_x86 5.8 Compiler Failed
Utility used to install the update failed with exit code {0}.
120762-02 Sun Studio 11_x86: Patch for Performance Analyzer Tools Failed
Install of update failed. Utility used to install the update is not able to add packages. Utility used to install the update failed with exit code 5.... and so on.
- if I try using "smpatch" to add the patch, I get this error:
$sudo smpatch add -i 120759-08
add patch 120759-08
Transition old-style patching.
Patch 120759-08 failed to install due to a failure produced by pkgadd.
pkgadd: ERROR: The package <SPROlang> is currently installed on the system in the
global zone. To install the new instance of this package in the global
zone only, you must specify the -G option. To install the new instance
of this package in all zones you must first remove the existing instance
of this package from the global zone first (via pkgrm) and then install
the new instance of this package in all zones.
pkgadd: ERROR: package <SPROlang> cannot be installed on this system/zone- if I try to use "patchadd" directly with the jar file in the current directory, I get this:
$sudo patchadd 120759-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
120759-08
Verifying signed patch <120759-08>...
Verifying digital signature for signer <es-signature>
ERROR: Signature verification failed while verifying certificate <subject=Sun Microsystems Inc Root CA, issuer=GTE CyberTrust Root>:<unable to get local issuer certificate>.
ERROR: Unable to verify signature for signer <es-signature>
Signature invalid on signed patch <120759-08>.
Patchadd is terminating.That's three strikes, and I'm out of ideas. Any suggestions for how one goes about applying signed patches for Studio 11? I'll switch to unsigned if I have to, but this seems like it shouldn't be this hard.
Thanks,
TimI started a new thread on the updatemanager forum.
http://forum.sun.com/jive/thread.jspa?threadID=107410
I found that forum by googling for "updatemanager" and "zones", but
I couldn't find any recent information on this issue. It seems the
problem has been known about for a while now.
--chris -
Problems starting SunMC Agent 3.6 under Solaris 10
Hi folks,
I just did a test installation of the new SunMC 3.6 Server which worked fine. Afterwards, I did a fresh install of the 3.6 agent on a Sun Enterprise 420R running Solaris 10. I installed the agent in the global zone.
At the end of the setup, when the system asks me if I want to start the agent, which I affirmed. But this didn't work, system says just laconically "Could not start agent". Unfortunately, I can't even find the logs, since there is no log subdirectory under /var/opt/SUNWsymon. Have they moved this under Solaris 10?
Any ideas somebody how to dig into this?
Regards,
PeterHi Mike,
This sounds a lot like a post just a few days ago:
http://forum.sun.com/thread.jspa?threadID=27785&tstart=0Well, yes and no...I read this thread and I found some similarities but it's not the same problem. Besides, this was Solaris 8, I've 10 and my guess is that it has something to do with Sol10.
What do you see when you start the Agent with this command:
/opt/SUNWsymon/sbin/es-start -aiNo error...I end up in a prompt:
bash-3.00# /opt/SUNWsymon/sbin/es-start -ai
info Dec 05 17:48:19 agent Sun Management Center Version: 3.6, Build: 18, H491, (c) 2003 Sun Microsystems, Inc.
info Dec 05 17:48:19 agent registering import actions
info Dec 05 17:48:19 agent loading standard services
info Dec 05 17:48:19 agent standard services load complete
info Dec 05 17:48:19 agent agent host and port: cngaer:1161
info Dec 05 17:48:19 agent trap handler destination host and port: SunMC_server:162
info Dec 05 17:48:19 agent event trap destination host and port: SunMC_server:163
agent:>
I've really no idea what to enter at this prompt. A simple "help" doesn't give me anything but I got something from "ls"
agent:> ls
classes templates _config config services iso shadow contexts rules -
NIC install problem under Solaris 10
I have an old 3Com NIC card (ISA) under Solaris 10. 3C509B Etherlink III card and prtconf -pv command shows correct PNP80f7 device id, all correct
resources, IRQ, I/O address .... But fail to work. Is it sun does not support elx driver or something I misconfigured?
My installation as follows:
elx "PNP80F7" entry to /etc/driver_aliases
PNP80F7|TCM5094.... elx net isa elx.bef "3Com"
entry to /boot/solaris/devicedb/master
#devlinks
#touch reconfigure ; rebootI use these cards for my x86 installations as well. The one thing that I've had to do is force the speed and duplex using the 3Com driver diskettes before installing the operating system. For whatever reason, Solaris 10 finds the card but will not initialize it properly whenever I the card is programmed to auto-negotiate. Forcing the card to half-duplex on the card itself works almost all of the time for me.
Get the driver diskettes from 3Com's site, boot from a bootable floppy, run 3c9x5cfg (if I recall correctly), and change the duplex and speed to whatever is appropriate. I've had the best luck with half-duplex. (If you need a boot diskette, you can get them from http://www.bootdisk.com.) -
Compile occi under solaris using g++/gcc problem
Hi Expert:
I got some link error when i tried to compile a demo occi code under solaris using g++. Please share experience.
Thanks.Namespaces are not supported in -compat=4 mode. The only effect of -features=namespace is to recognize "namespace" as a keyword, and disallow it as an identifier. You don't actually get namespace semantics.
The pupose of -compat=4 is to allow code written for C++ 4.x to compile and run until the code can be updated to conform to the C++ Standard. If you want to use features from the C++ standard, like namespaces, you must use Sun C++ in the default standard mode.
If you remove -compat=4, the code compiles and links. If you need to use -compat=4 mode, remove uses of namespace, and fix the code to remove name conflicts.
BTW, we recommend against using -features=bool in -compat=4 mode. It can cause odd behavior when part of the code expects boolean expressions to have type int and part of the code expects bool to be a different type.
It appears you are using C++ 5.0, a product that has been obsolete for several years and which is no longer supported. You should consider updating to Sun Studio 11 (C++ 5.8), at no cost.
http://developers.sun.com/sunstudio/ -
Problems with ViaVoice under Leopard, especially key mapping problems
ViaVoice's behavior has changed considerably under Leopard. First I will discuss the key mapping problem, since I'm eagerly looking for an answer to this problem. At the end of this post, I will voice some of the other problems I've experienced for those who may be interested. The key mapping problem may be specific to the fact that I use a foreign keyboard with a US version of ViaVoice.
INTRO:
I have used ViaVoice on my Mac for years, more or less without problems (ViaVoice's bugginess is notorious).
Those who know ViaVoice will know that one has two general options for dictation. One can dictate into ViaVoice's so-called SpeakPad, which allows special formatting, editing and dictation error correction within the dictated text, or one can dictate into "external" software such as Microsoft Word, in which case ViaVoice just sends a string of characters to that software. SpeakPad appears to make strong use of the operating system's built-in functionality for character formatting, document formatting, etc.
*MY PROBLEM*
I have a German keyboard on my PowerBook, yet dictate in US English. When I dictated into SpeakPad under Tiger, all characters appeared correctly. However, when I dictated into Microsoft Word using Tiger, I had to switch the keyboard mapping from German to US to get all characters (that means including the characters that are located at different positions on a German keyboard than they are on a US keyboard such as y, z, apostrophes and parentheses) to appear correctly.
Under Leopard, things have changed. Now it doesn't matter whether I dictate into SpeakPad or Word; the results are the same and many characters do not appear correctly.
If set to a German keyboard, y and z appear as expected. To name a few irregularities:
"(" appears as ")"
")" appears as "="
apostrophes appear as "#" and
";" appears as ","
If set to a US keyboard, y and z are interchanged. "(" and ")" appear as expected. Apostrophes appear as "\" and ";" appears as ","
By comparison, if typed (as opposed to dictated, as in the examples above) "correctly" (i.e. based on the letters printed on the keyboard) on a German keyboard set to imitate a US keyboard:
y and z are interchanged
apostrophes appear as "|"
"(" appears as "*"
")" appears as "(" and
";" appears as the symbol for "less than"
Since I don't have a US keyboard, I can't say how it would behave if set to imitate a German keyboard, i.e. if there's a correlation to the results I get when I dictate.
Since I was previously able to dictate correctly into SpeakPad by setting the keyboard to "German" and into Word by setting the keyboard to "US," I presume that this is a problem in Leopard, not ViaVoice.
*OTHER PROBLEMS WITH VIAVOICE UNDER LEOPARD*
In addition to the aforementioned key mapping problems (that may be specific to those of us with foreign keyboards), ViaVoice appears to have lost considerable functionality in Leopard. I cannot access SpeakPad's Preferences and the correction window. Moreover, the traffic-light like window buttons have disappeared from the VoiceCenter (although they work if you click where they should be). SetupAssistent appears to function.
I've written to Nuance about these problems, but have little hope that they will invest the time in producing a patch since they haven't released any updates since 2003.Thrums1,
I've never had to "register" ViaVoice after updating the system. I thus suspect you haven't fully followed my above, three-step advice (particularly step 3).
1) Reinstall ViaVoice from CD.
2) Update to the latest version (using the patch downloadable from Nuance's website).
3) Replace the “temp” and “users” folders (in the "ViaVoice" folder at the upper level of your home directory) by a previous copy thereof. When I say previous copy, I mean a copy from when ViaVoice was still working properly, e.g. a copy from when it was running under Tiger.
As I said, I've gotten ViaVoice to survive several system updates by following the above steps. To my knowledge, the last step is critical since it saves you from having to reconfigure ViaVoice under the new operating system (in this case Leopard). I suspect that ViaVoice is crashing on your system because it's trying to start some module of the SetUpAssistant that is incompatible with Leopard (as many are). If you instead use old copies of the "temp" and "users" folders (from the previous system), then ViaVoice doesn't have to go through the initial "registration" process; ViaVoice doesn't need the SetUpAssistant; and all is (more or less) fine.
Good luck!
BTW, to my knowledge, Dictate only runs on Intel Macs. It thus won't run on a G4 iBook, just as it won't run on my PowerBook G4. -
How to start ftp under solaris 10
Hi,
if I try to enable ftp under Solaris 10, I get the message "unsatisfied dependencies":
root@u015ad2a:.../>svcadm -v enable -rst svc:/network/ftp:default
svc:/network/ftp:default temporarily enabled.
svc:/network/inetd:default temporarily enabled.
svc:/network/loopback temporarily enabled.
svc:/system/filesystem/local temporarily enabled.
svc:/milestone/single-user temporarily enabled.
svc:/system/identity:node temporarily enabled.
svc:/system/filesystem/minimal temporarily enabled.
svc:/system/filesystem/usr temporarily enabled.
svc:/system/filesystem/root temporarily enabled.
svc:/system/device/local temporarily enabled.
svc:/milestone/devices temporarily enabled.
svc:/system/manifest-import temporarily enabled.
svc:/milestone/sysconfig temporarily enabled.
svc:/milestone/name-services temporarily enabled.
svcadm: Instance "svc:/network/ftp:default" has unsatisfied dependencies.
root@u015ad2a:.../>svcs svc:/network/ftp:default
STATE STIME FMRI
uninitialized 9:40:09 svc:/network/ftp:default
How can I enable ftp?This looks sort of like what happened to me just now. I tried svcs -x
and got:
# svcs -x
svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Mon Apr 18 13:01:12 2005
Reason: Restarter svc:/network/inetd:default has not initialized service state.
See: http://sun.com/msg/SMF-8000-4D
See: gssd(1M)
Impact: 10 dependent services are not running. (Use -v for list.)
svc:/network/service:default (layered network services)
State: offline since Mon Apr 18 13:01:29 2005
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: ifconfig(1M)
See: /var/svc/log/network-service:default.log
Impact: 4 dependent services are not running. (Use -v for list.)
svc:/application/print/server:default (LP print server)
State: disabled since Mon Apr 18 13:01:12 2005
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 1 dependent service is not running. (Use -v for list.)
I tried all kinds of things to get gss to run, but I finally realized that
it was really ifconfig that was the problem. The system has two
network interfaces, and during installation I gave both of them
a name. However, hme1 was not really connected to anything.
All I did to get it to work was
# cd /etc
# mv hostname.hme1 no.hme1
After that, I rebooted, and everything came up OK. I don't know
if the original problem was the same, but this solved my problem. -
How to install a LPR Printer under Solaris 10 01/06
Hi,
I just installed Solaris 10 01/06 2 days ago and so far I'm pretty impressed, really a nice system!
I have one problem, though:
I have a Kyocera FS-1010 printer in my office which is connected to a CNet Printserver.
I'm able to print from other Linux and *BSD boxes to this printer by using CUPS and adding the Printer as a LPR Printqueue.
My question is: Is there a way to do the same under Solaris? As far as I know, Solaris doesn't use CUPS as the default printing system, unlike OSX for example.
Thanks in advance,
DominikIs there any reason you haven't ftp'd and then configued cups on Solaris?
http://www.sun.com/bigadmin/content/submitted/install_cups.html
alan -
LSI1030 scsi adapter does not work under solaris 10 on t5240 sparc server
hi all,
i have following LSI1030 scsi pci-x card in t5240 server with solaris 10u8 ..
## prtpicl -v ## director's cut
LSILogic,scsi (scsi-2, ad0000061e)
:DeviceID 0x8
:UnitAddress 8
:vendor-id 0x1000
:device-id 0x30
:revision-id 0xc1
:subsystem-vendor-id 0x103c
:subsystem-id 0x322a
:class-code 0x10000
:cache-line-size 0x10
:interrupts 00 00 00 01
:min-grant 0x10
:max-latency 0x6
:latency-timer 0x40
:devsel-speed 0x1
:66mhz-capable
:fcode-rom-offset 0xa800
:device_type scsi-2
:wide 0x10
:version 1.00.38
:reg
00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01 07 40 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00
03 07 40 14 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00
03 07 40 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00
02 07 40 30 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00
:model LSI,1030
:compatible pci103c,30
:assigned-addresses
81 07 40 10 00 00 00 00 00 00 10 00 00 00 00 00 00 00 01 00
82 07 40 14 00 00 00 00 05 20 00 00 00 00 00 00 00 02 00 00
82 07 40 1c 00 00 00 00 05 22 00 00 00 00 00 00 00 02 00 00
82 07 40 30 00 00 00 00 05 30 00 00 00 00 00 00 00 10 00 00
:mpt-version 1.02
:firmware-version 1.03.39.00
:devfs-path /pci@500/pci@0/pci@c/pci@0/LSILogic,scsi
:binding-name LSILogic,scsi
:instance -1
:_class scsi-2
:name LSILogic,scsi
## prtdiag -v # director's cut
MB lsilOGICLSILogic,scsi LSI,1030
/pci@500/pci@0/pci@c/pci@0/LSILogic,scsi
## prtconf -v # director's cut
LSILogic,scsi (driver not attached)
tape (driver not attached)
disk (driver not attached)
{0} ok probe-scsi-all
/pci@500/pci@0/pci@c/pci@0/LSILogic,scsi@8
MPT Version 1.02, Firmware Version 1.03.39.00
Initiator ID is 7
Target 3
Unit 0 Removable Tape HP Ultrium 2-SCSI S63Di am unable to run this controller under solaris 10, is it even possible ??
regards, daniel
ps. i did reconfigure reboot and tried to tweak a mpt driver by hand, i also checked a patches for mpt driver ..# prtconf -v | grep LSI
LSILogic,scsi, instance #0
dev_path=/pci@500/pci@0/pci@c/pci@0/LSILogic,scsi@8:devctl
dev_path=/pci@500/pci@0/pci@c/pci@0/LSILogic,scsi@8:scsi
# cfgadm -lv c2
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c2 connected unconfigured unknown
unavailable scsi-bus n /devices/pci@500/pci@0/pci@c/pci@0/LSILogic,scsi@8:scsi
# iostat -En ## cut
rmt/0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: HP Product: Ultrium 2-SCSI Revision: S63D Serial No:thanks, resolved .. i added this device (mpt "pci103c,30") in /etc/driver_aliases
regards -
What is the limit of the size of a disk under Solaris 8?
Hello,
I have a problem when I try to run format command to label a disk of 1TB under solaris 8.
# format.......
114. c9t14d3 <DGC-RAID3-0322 cyl 32766 alt 2 hd 1 sec 0>
/pci@8,700000/lpfc@4/sd@e,3
Specify disk (enter its number)[115]: 114
selecting c9t14d3
[disk formatted]
Disk not labeled. Label it now? y
Warning: error writing VTOC.
Warning: no backup labels
Write label failed
format> print
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> p
Current partition table (default):
Total disk cylinders available: 32766 + 2 (reserved cylinders)
Arithmetic Exception - core dumpedI think maybe if you split it into two luns, you can
stitch them back together with svm.
But even thats not certain.Depends on what you're going to do with the device at that point. UFS on Solaris also does not support volumes 1TB or larger. So you'd have to use it as a raw slice space or a filesystem that did support larger sizes.
You need later versions of Solaris 9 to get mutli-terabyte UFS support. (a separate issue from multi-terabyte LUN support).
Darren -
WebLogic 5.1.0 crashes under Solaris
Hi,
I am using weblogic 5.1.0 under Solaris 8. Database is Oracle 8i Enterprise Edition Release 8.1.6.0.0.
WebLogic crashes with following dump. I will be very thankful if someone can help me out.
Thanks,
Viresh
Dump is as follows :
SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x14]
stackpointer=E9CAEA68
"Thread-69" (TID:0x4873e90, sys_thread_t:0x4873dc8, state:CW, thread_t: t@138, threadID:0xe9c81d78, stack_bottom:0xe9c82000, stack_size:0x20000) prio=5
[1] java.lang.Thread.sleep(Native Method)
[2] com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:173)
"Thread-8" (TID:0x41c5a48, sys_thread_t:0x41c5980, state:R, thread_t: t@47, threadID:0xe9cb1d78, stack_bottom:0xe9cb2000, stack_size:0x20000) prio=5 current thread
[1] weblogic.db.oci.OciCursor.exec(Native Method)
[2] weblogic.db.oci.OciCursor.oci_exec(OciCursor.java:1816)
[3] weblogic.jdbcbase.oci.Statement.executeUpdate(Statement.java:823)
[4] weblogic.jdbcbase.oci.Statement.execute(Statement.java:1351)
[5] weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:33)
[6] com.zaplet.schema.GetNextDeliveriesSP.execute(GetNextDeliveriesSP.java:142)
[7] com.zaplet.core.DigestThread.getNextBatch(DigestThread.java:194)
[8] com.zaplet.core.DigestThread.deliverDigests(DigestThread.java:131)
[9] com.zaplet.core.DigestThread.run(DigestThread.java:109)
"Thread-1" (TID:0x3f292e0, sys_thread_t:0x3f29218, state:CW, thread_t: t@37, threadID:0xe9ce1d78, stack_bottom:0xe9ce2000, stack_size:0x20000) prio=5
[1] java.lang.Thread.sleep(Native Method)
[2] com.zaplet.util.WorkerThread.run(WorkerThread.java:32)
"SSLListenThread" (TID:0x3d05d08, sys_thread_t:0x3d05c40, state:R, thread_t: t@36, threadID:0xe9d41d78, stack_bottom:0xe9d42000, stack_size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
[4] java.net.ServerSocket.accept(ServerSocket.java:224)
[5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
[6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
[7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
"ListenThread" (TID:0x742500, sys_thread_t:0x742438, state:R, thread_t: t@35, threadID:0xe9f01d78, stack_bottom:0xe9f02000, stack_size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
[4] java.net.ServerSocket.accept(ServerSocket.java:223)
[5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
"NBExecuteThread-1" (TID:0x8ee3d0, sys_thread_t:0x8ee308, state:CW, thread_t: t@31, threadID:0xe9f31d78, stack_bottom:0xe9f32000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"NBExecuteThread-0" (TID:0x8d8cc8, sys_thread_t:0x8d8c00, state:CW, thread_t: t@30, threadID:0xe9f81d78, stack_bottom:0xe9f82000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-19" (TID:0x8ec930, sys_thread_t:0x8ec868, state:MW, thread_t: t@29, threadID:0xe9fb1d78, stack_bottom:0xe9fb2000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-18" (TID:0x8d94c8, sys_thread_t:0x8d9400, state:R, thread_t: t@28, threadID:0xea001d78, stack_bottom:0xea002000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
[2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-17" (TID:0x8f5100, sys_thread_t:0x8f5038, state:MW, thread_t: t@27, threadID:0xea031d78, stack_bottom:0xea032000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-16" (TID:0x8a1508, sys_thread_t:0x8a1440, state:CW, thread_t: t@26, threadID:0xea081d78, stack_bottom:0xea082000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-15" (TID:0x8d8738, sys_thread_t:0x8d8670, state:MW, thread_t: t@25, threadID:0xea0b1d78, stack_bottom:0xea0b2000, stack_size:0x20000) prio=5
[1] java.sql.DriverManager.getConnection(DriverManager.java:104)
[2] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
[3] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
[4] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
[5] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
[6] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
[7] jsp._layout3._snippets._author._defaultEndWire._jspService(_defaultEndWire.java:69)
[8] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[9] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[10] weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:200)
[11] weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:172)
[12] weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:105)
[13] jsp._sending._sentokay._jspService(_sentokay.java:69)
[14] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[15] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[16] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[17] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[18] com.zaplet.StoreCreateServlet.sendMessage(StoreCreateServlet.java:510)
[19] com.zaplet.StoreCreateServlet.handleSend(StoreCreateServlet.java:272)
[20] com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:163)
[21] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:78)
[22] javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
[23] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[24] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[25] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
[26] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[27] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
[28] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
[29] javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
[30] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
[31] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
... remainder of stack truncated ...
"ExecuteThread-14" (TID:0x8e40d0, sys_thread_t:0x8e4008, state:CW, thread_t: t@24, threadID:0xea101d78, stack_bottom:0xea102000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-13" (TID:0x8facd8, sys_thread_t:0x8fac10, state:CW, thread_t: t@23, threadID:0xea131d78, stack_bottom:0xea132000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-12" (TID:0x8e0cf8, sys_thread_t:0x8e0c30, state:CW, thread_t: t@22, threadID:0xea181d78, stack_bottom:0xea182000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-11" (TID:0x938018, sys_thread_t:0x937f50, state:CW, thread_t: t@21, threadID:0xea1b1d78, stack_bottom:0xea1b2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-10" (TID:0x936e40, sys_thread_t:0x936d78, state:MW, thread_t: t@20, threadID:0xea201d78, stack_bottom:0xea202000, stack_size:0x20000) prio=5
[1] java.sql.DriverManager.getConnection(DriverManager.java:104)
[2] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
[3] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
[4] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
[5] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
[6] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
[7] jsp._errors._index._jspService(_index.java:69)
[8] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[9] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[10] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[11] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[12] com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:160)
[13] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:41)
[14] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[15] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[16] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[17] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[18] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[19] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
[20] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
[21] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[22] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[23] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[25] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[26] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:102)
[27] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[28] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[29] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-9" (TID:0x8a2ce8, sys_thread_t:0x8a2c20, state:CW, thread_t: t@19, threadID:0xea231d78, stack_bottom:0xea232000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-8" (TID:0x934cb0, sys_thread_t:0x934be8, state:CW, thread_t: t@18, threadID:0xea281d78, stack_bottom:0xea282000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-7" (TID:0x885108, sys_thread_t:0x885040, state:CW, thread_t: t@17, threadID:0xea2b1d78, stack_bottom:0xea2b2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-6" (TID:0x8a6cf8, sys_thread_t:0x8a6c30, state:CW, thread_t: t@16, threadID:0xea2f1d78, stack_bottom:0xea2f2000, stack_size:0x20000) prio=5
[1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
[2] weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:561)
[3] weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:555)
[4] weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:544)
[5] weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:162)
[6] weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:145)
[7] weblogic.jdbcbase.pool.Driver.connect(Driver.java:65)
[8] java.sql.DriverManager.getConnection(DriverManager.java:433)
[9] java.sql.DriverManager.getConnection(DriverManager.java:104)
[10] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
[11] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
[12] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
[13] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
[14] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
[15] jsp._authorpages._contacts._jspService(_contacts.java:96)
[16] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[17] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[18] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[19] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[20] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:102)
[21] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[22] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[23] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-5" (TID:0x92be00, sys_thread_t:0x92bd38, state:CW, thread_t: t@15, threadID:0xeadb1d78, stack_bottom:0xeadb2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-4" (TID:0x897cf8, sys_thread_t:0x897c30, state:MW, thread_t: t@14, threadID:0xeadf1d78, stack_bottom:0xeadf2000, stack_size:0x20000) prio=5
[1] java.sql.DriverManager.println(DriverManager.java:364)
[2] weblogic.jdbcbase.oci.Statement.private_parse(Statement.java:687)
[3] weblogic.jdbc.oci.Connection.prepareCall(Connection.java:52)
[4] weblogic.jdbc.pool.Connection.prepareCall(Connection.java:71)
[5] com.zaplet.schema.UserSP.execute1(UserSP.java:185)
[6] com.zaplet.schema.UserSP.execute(UserSP.java:159)
[7] com.zaplet.UserUtils.checkAndAddUser(UserUtils.java:51)
[8] com.zaplet.Zaplet.createMessageObject(Zaplet.java:1588)
[9] com.zaplet.Zaplet.storeZaplet(Zaplet.java:1083)
[10] com.zaplet.StoreCreateServlet.handleStoreCreate(StoreCreateServlet.java:246)
[11] com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:158)
[12] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:41)
[13] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[14] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[15] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[16] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[17] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
[18] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
[19] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
[20] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[21] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:102)
[26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-3" (TID:0x8980f8, sys_thread_t:0x898030, state:CW, thread_t: t@13, threadID:0xeafd1d78, stack_bottom:0xeafd2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-2" (TID:0x8b94f8, sys_thread_t:0x8b9430, state:CW, thread_t: t@12, threadID:0xeb3b1d78, stack_bottom:0xeb3b2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-1" (TID:0x92f978, sys_thread_t:0x92f8b0, state:CW, thread_t: t@11, threadID:0xeb3e1d78, stack_bottom:0xeb3e2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-0" (TID:0x921968, sys_thread_t:0x9218a0, state:CW, thread_t: t@10, threadID:0xebea1d78, stack_bottom:0xebea2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"TimeEventGenerator" (TID:0x8d9aa8, sys_thread_t:0x8d99e0, state:CW, thread_t: t@9, threadID:0xebed1d78, stack_bottom:0xebed2000, stack_size:0x20000) prio=5
[1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
[2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
[3] java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" (TID:0x8a7500, sys_thread_t:0x8a7438, state:CW, thread_t: t@8, threadID:0xed041d78, stack_bottom:0xed042000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:102)
[3] weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:116)
Exiting Thread (sys_thread_t:0xff30e2e8) : no stack
"Finalizer" (TID:0x2cfa80, sys_thread_t:0x2cf9b8, state:CW, thread_t: t@6, threadID:0xfe3e1d78, stack_bottom:0xfe3e2000, stack_size:0x20000) prio=8
[1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
[3] java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:124)
"Reference Handler" (TID:0x2cd2a0, sys_thread_t:0x2cd1d8, state:CW, thread_t: t@5, threadID:0xfec41d78, stack_bottom:0xfec42000, stack_size:0x20000) prio=10
[1] java.lang.Object.wait(Object.java:424)
[2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
"Signal dispatcher" (TID:0x2aa5f0, sys_thread_t:0x2aa528, state:MW, thread_t: t@4, threadID:0xfed41d78, stack_bottom:0xfed42000, stack_size:0x20000) prio=10
"main" (TID:0x38280, sys_thread_t:0x381b8, state:CW, thread_t: t@1, threadID:0x25118, stack_bottom:0xffbf0000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1787)
[3] java.lang.reflect.Method.invoke(Native Method)
[4] weblogic.Server.startServerDynamically(Server.java:107)
[5] weblogic.Server.main(Server.java:65)
[6] weblogic.Server.main(Server.java:55)
Yup, try toggling between Solaris JDK 1.2.2 and 1.3. We've also experienced
seg fault problems with a certain JDK + JDBC driver combo.
Gene
"sumanth" <[email protected]> wrote in message
news:[email protected]...
> seg fault errors according to weblogic can be caused by the following 3
> reasons
> 1) native muxer
> 2) jdbc 2 drivers
> 3) jvm
>
> I dont know what the first one means. We had faced one similar problem
but
> when we upgraded our jdk to 1.3 things were back to normal. (weblogic
> supports 1.2)
>
> -Sumanth
>
> "Viresh Jain" <[email protected]> wrote in message
> news:[email protected]...
> >
> > Hi,
> > I am using weblogic 5.1.0 under Solaris 8. Database is Oracle 8i
> Enterprise Edition Release 8.1.6.0.0.
> >
> > WebLogic crashes with following dump. I will be very thankful if someone
> can help me out.
> >
> > Thanks,
> > Viresh
> >
> > Dump is as follows :
> >
> > SIGSEGV 11 segmentation violation
> > si_signo [11]: SEGV
> > si_errno [0]:
> > si_code [1]: SEGV_MAPERR [addr: 0x14]
> >
> > stackpointer=E9CAEA68
> > "Thread-69" (TID:0x4873e90, sys_thread_t:0x4873dc8, state:CW, thread_t:
> t@138, threadID:0xe9c81d78, stack_bottom:0xe9c82000, stack_size:0x20000)
> prio=5
> >
> > [1] java.lang.Thread.sleep(Native Method)
> > [2] com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:173)
> > -------------------
> > "Thread-8" (TID:0x41c5a48, sys_thread_t:0x41c5980, state:R, thread_t:
> t@47, threadID:0xe9cb1d78, stack_bottom:0xe9cb2000, stack_size:0x20000)
> prio=5 current thread
> >
> > [1] weblogic.db.oci.OciCursor.exec(Native Method)
> > [2] weblogic.db.oci.OciCursor.oci_exec(OciCursor.java:1816)
> > [3] weblogic.jdbcbase.oci.Statement.executeUpdate(Statement.java:823)
> > [4] weblogic.jdbcbase.oci.Statement.execute(Statement.java:1351)
> > [5]
> weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:33)
> > [6]
>
com.zaplet.schema.GetNextDeliveriesSP.execute(GetNextDeliveriesSP.java:142)
> > [7] com.zaplet.core.DigestThread.getNextBatch(DigestThread.java:194)
> > [8] com.zaplet.core.DigestThread.deliverDigests(DigestThread.java:131)
> > [9] com.zaplet.core.DigestThread.run(DigestThread.java:109)
> > -------------------
> > "Thread-1" (TID:0x3f292e0, sys_thread_t:0x3f29218, state:CW, thread_t:
> t@37, threadID:0xe9ce1d78, stack_bottom:0xe9ce2000, stack_size:0x20000)
> prio=5
> >
> > [1] java.lang.Thread.sleep(Native Method)
> > [2] com.zaplet.util.WorkerThread.run(WorkerThread.java:32)
> > -------------------
> > "SSLListenThread" (TID:0x3d05d08, sys_thread_t:0x3d05c40, state:R,
> thread_t: t@36, threadID:0xe9d41d78, stack_bottom:0xe9d42000,
> stack_size:0x20000) prio=5
> >
> > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> > [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
> > [4] java.net.ServerSocket.accept(ServerSocket.java:224)
> > [5]
>
weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
> :121)
> > [6]
weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
> > [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> > -------------------
> > "ListenThread" (TID:0x742500, sys_thread_t:0x742438, state:R, thread_t:
> t@35, threadID:0xe9f01d78, stack_bottom:0xe9f02000, stack_size:0x20000)
> prio=5
> >
> > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> > [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
> > [4] java.net.ServerSocket.accept(ServerSocket.java:223)
> > [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> > -------------------
> > "NBExecuteThread-1" (TID:0x8ee3d0, sys_thread_t:0x8ee308, state:CW,
> thread_t: t@31, threadID:0xe9f31d78, stack_bottom:0xe9f32000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "NBExecuteThread-0" (TID:0x8d8cc8, sys_thread_t:0x8d8c00, state:CW,
> thread_t: t@30, threadID:0xe9f81d78, stack_bottom:0xe9f82000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-19" (TID:0x8ec930, sys_thread_t:0x8ec868, state:MW,
> thread_t: t@29, threadID:0xe9fb1d78, stack_bottom:0xe9fb2000,
> stack_size:0x20000) prio=5
> >
> > [1]
> weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> > [2]
> weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-18" (TID:0x8d94c8, sys_thread_t:0x8d9400, state:R,
> thread_t: t@28, threadID:0xea001d78, stack_bottom:0xea002000,
> stack_size:0x20000) prio=5
> >
> > [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
> > [2]
> weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> > [3]
> weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> > [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-17" (TID:0x8f5100, sys_thread_t:0x8f5038, state:MW,
> thread_t: t@27, threadID:0xea031d78, stack_bottom:0xea032000,
> stack_size:0x20000) prio=5
> >
> > [1]
> weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> > [2]
> weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-16" (TID:0x8a1508, sys_thread_t:0x8a1440, state:CW,
> thread_t: t@26, threadID:0xea081d78, stack_bottom:0xea082000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-15" (TID:0x8d8738, sys_thread_t:0x8d8670, state:MW,
> thread_t: t@25, threadID:0xea0b1d78, stack_bottom:0xea0b2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.sql.DriverManager.getConnection(DriverManager.java:104)
> > [2] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
> > [3] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
> > [4] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
> > [5] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
> > [6] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
> > [7]
>
jsp._layout3._snippets._author._defaultEndWire._jspService(_defaultEndWire.j
> ava:69)
> > [8] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > [9]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [10]
>
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
> l.java:200)
> > [11]
>
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
> l.java:172)
> > [12]
> weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:105)
> > [13] jsp._sending._sentokay._jspService(_sentokay.java:69)
> > [14] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > [15]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [16]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:96)
> > [17] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [18]
> com.zaplet.StoreCreateServlet.sendMessage(StoreCreateServlet.java:510)
> > [19]
com.zaplet.StoreCreateServlet.handleSend(StoreCreateServlet.java:272)
> > [20]
>
com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:163)
> > [21] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:78)
> > [22] javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
> > [23] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [24]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [25]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:154)
> > [26] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [27] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
> > [28] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
> > [29] javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
> > [30] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> > [31]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > ... remainder of stack truncated ...
> > -------------------
> > "ExecuteThread-14" (TID:0x8e40d0, sys_thread_t:0x8e4008, state:CW,
> thread_t: t@24, threadID:0xea101d78, stack_bottom:0xea102000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-13" (TID:0x8facd8, sys_thread_t:0x8fac10, state:CW,
> thread_t: t@23, threadID:0xea131d78, stack_bottom:0xea132000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-12" (TID:0x8e0cf8, sys_thread_t:0x8e0c30, state:CW,
> thread_t: t@22, threadID:0xea181d78, stack_bottom:0xea182000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-11" (TID:0x938018, sys_thread_t:0x937f50, state:CW,
> thread_t: t@21, threadID:0xea1b1d78, stack_bottom:0xea1b2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-10" (TID:0x936e40, sys_thread_t:0x936d78, state:MW,
> thread_t: t@20, threadID:0xea201d78, stack_bottom:0xea202000,
> stack_size:0x20000) prio=5
> >
> > [1] java.sql.DriverManager.getConnection(DriverManager.java:104)
> > [2] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
> > [3] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
> > [4] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
> > [5] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
> > [6] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
> > [7] jsp._errors._index._jspService(_index.java:69)
> > [8] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > [9]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [10]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:96)
> > [11] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [12]
>
com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:160)
> > [13] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:41)
> > [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> > [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [16]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [17]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:96)
> > [18] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [19] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
> > [20] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
> > [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> > [22] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [23]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [24]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:723)
> > [25]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:707)
> > [26]
>
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
> Manager.java:102)
> > [27]
>
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
> > [28]
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
> > [29] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-9" (TID:0x8a2ce8, sys_thread_t:0x8a2c20, state:CW,
> thread_t: t@19, threadID:0xea231d78, stack_bottom:0xea232000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-8" (TID:0x934cb0, sys_thread_t:0x934be8, state:CW,
> thread_t: t@18, threadID:0xea281d78, stack_bottom:0xea282000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-7" (TID:0x885108, sys_thread_t:0x885040, state:CW,
> thread_t: t@17, threadID:0xea2b1d78, stack_bottom:0xea2b2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-6" (TID:0x8a6cf8, sys_thread_t:0x8a6c30, state:CW,
> thread_t: t@16, threadID:0xea2f1d78, stack_bottom:0xea2f2000,
> stack_size:0x20000) prio=5
> >
> > [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
> > [2]
>
weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:56
> 1)
> > [3]
>
weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:55
> 5)
> > [4]
>
weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator
> .java:544)
> > [5]
>
weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:162
> )
> > [6]
>
weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.
> java:145)
> > [7] weblogic.jdbcbase.pool.Driver.connect(Driver.java:65)
> > [8] java.sql.DriverManager.getConnection(DriverManager.java:433)
> > [9] java.sql.DriverManager.getConnection(DriverManager.java:104)
> > [10] com.zaplet.data.DataManager.getConnection(DataManager.java:98)
> > [11] com.zaplet.db.DbTrans.<init>(DbTrans.java:244)
> > [12] com.zaplet.schema.UserQuery.execute(UserQuery.java:97)
> > [13] com.zaplet.UserUtils.findByUserId(UserUtils.java:289)
> > [14] com.zaplet.ZapletSession.isLoggedIn(ZapletSession.java:36)
> > [15] jsp._authorpages._contacts._jspService(_contacts.java:96)
> > [16] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > [17]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [18]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:723)
> > [19]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:707)
> > [20]
>
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
> Manager.java:102)
> > [21]
>
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
> > [22]
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
> > [23] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-5" (TID:0x92be00, sys_thread_t:0x92bd38, state:CW,
> thread_t: t@15, threadID:0xeadb1d78, stack_bottom:0xeadb2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-4" (TID:0x897cf8, sys_thread_t:0x897c30, state:MW,
> thread_t: t@14, threadID:0xeadf1d78, stack_bottom:0xeadf2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.sql.DriverManager.println(DriverManager.java:364)
> > [2] weblogic.jdbcbase.oci.Statement.private_parse(Statement.java:687)
> > [3] weblogic.jdbc.oci.Connection.prepareCall(Connection.java:52)
> > [4] weblogic.jdbc.pool.Connection.prepareCall(Connection.java:71)
> > [5] com.zaplet.schema.UserSP.execute1(UserSP.java:185)
> > [6] com.zaplet.schema.UserSP.execute(UserSP.java:159)
> > [7] com.zaplet.UserUtils.checkAndAddUser(UserUtils.java:51)
> > [8] com.zaplet.Zaplet.createMessageObject(Zaplet.java:1588)
> > [9] com.zaplet.Zaplet.storeZaplet(Zaplet.java:1083)
> > [10]
>
com.zaplet.StoreCreateServlet.handleStoreCreate(StoreCreateServlet.java:246)
> > [11]
>
com.zaplet.StoreCreateServlet.storeCreateHelper(StoreCreateServlet.java:158)
> > [12] com.zaplet.StoreCreateServlet.doPost(StoreCreateServlet.java:41)
> > [13] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> > [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [15]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [16]
>
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:96)
> > [17] com.zaplet.ZServlet.forwardRequest(ZServlet.java:46)
> > [18] com.zaplet.PreviewServlet.processInputs(PreviewServlet.java:284)
> > [19] com.zaplet.PreviewServlet.doPost(PreviewServlet.java:33)
> > [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
> > [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> > [22]
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :114)
> > [23]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:723)
> > [24]
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.java:707)
> > [25]
>
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
> Manager.java:102)
> > [26]
>
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
> > [27]
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
> > [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-3" (TID:0x8980f8, sys_thread_t:0x898030, state:CW,
> thread_t: t@13, threadID:0xeafd1d78, stack_bottom:0xeafd2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-2" (TID:0x8b94f8, sys_thread_t:0x8b9430, state:CW,
> thread_t: t@12, threadID:0xeb3b1d78, stack_bottom:0xeb3b2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-1" (TID:0x92f978, sys_thread_t:0x92f8b0, state:CW,
> thread_t: t@11, threadID:0xeb3e1d78, stack_bottom:0xeb3e2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "ExecuteThread-0" (TID:0x921968, sys_thread_t:0x9218a0, state:CW,
> thread_t: t@10, threadID:0xebea1d78, stack_bottom:0xebea2000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> > -------------------
> > "TimeEventGenerator" (TID:0x8d9aa8, sys_thread_t:0x8d99e0, state:CW,
> thread_t: t@9, threadID:0xebed1d78, stack_bottom:0xebed2000,
> stack_size:0x20000) prio=5
> >
> > [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
> > [2]
>
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
> :131)
> > [3] java.lang.Thread.run(Thread.java:479)
> > -------------------
> > "SpinnerRandomSource" (TID:0x8a7500, sys_thread_t:0x8a7438, state:CW,
> thread_t: t@8, threadID:0xed041d78, stack_bottom:0xed042000,
> stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2]
>
weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:10
> 2)
> > [3]
weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:116)
> > -------------------
> >
> > Exiting Thread (sys_thread_t:0xff30e2e8) : no stack
> > "Finalizer" (TID:0x2cfa80, sys_thread_t:0x2cf9b8, state:CW, thread_t:
t@6,
> threadID:0xfe3e1d78, stack_bottom:0xfe3e2000, stack_size:0x20000) prio=8
> >
> > [1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
> > [2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
> > [3]
>
java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:1
> 24)
> > -------------------
> > "Reference Handler" (TID:0x2cd2a0, sys_thread_t:0x2cd1d8, state:CW,
> thread_t: t@5, threadID:0xfec41d78, stack_bottom:0xfec42000,
> stack_size:0x20000) prio=10
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
> > -------------------
> > "Signal dispatcher" (TID:0x2aa5f0, sys_thread_t:0x2aa528, state:MW,
> thread_t: t@4, threadID:0xfed41d78, stack_bottom:0xfed42000,
> stack_size:0x20000) prio=10
> >
> > -------------------
> > "main" (TID:0x38280, sys_thread_t:0x381b8, state:CW, thread_t: t@1,
> threadID:0x25118, stack_bottom:0xffbf0000, stack_size:0x20000) prio=5
> >
> > [1] java.lang.Object.wait(Object.java:424)
> > [2] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1787)
> > [3] java.lang.reflect.Method.invoke(Native Method)
> > [4] weblogic.Server.startServerDynamically(Server.java:107)
> > [5] weblogic.Server.main(Server.java:65)
> > [6] weblogic.Server.main(Server.java:55)
> > -------------------
> >
> >
>
-
Swedish chars ��� not working under Solaris
Hi All,
I created the following little code and it is not working under Solaris 7, JDK1.4.1_01. (also tested some other but does not work)
public class HelloSweden
public static void main(String [] args)
String newName="���";
String charsetName = "iso-8859-2";
byte [] s = {(byte)229, (byte)228, (byte)246};
try
newName = new String(s, 0, s.length, charsetName);
catch ( java.io.UnsupportedEncodingException e )
System.err.println(e.getMessage());
e.printStackTrace();
System.out.println("new name is: "+newName);
for(int i=0; i<newName.getBytes().length; i++)
System.out.println(i+"."+":"+newName.getBytes());
The problem is that on Solaris 7 the output is:
new name is: ???
0.:63
1.:63
2.:63
Whereas on Linux it works fine:
new name is: ���
0.:-27
1.:-28
2.:-10
I also tried the "javac -encoding iso8859-1" option but no use.
Could anybody help?
Thnx,
GFI also tried the "javac -encoding iso8859-1" option
but no use.
Was the output exactly the same or were the numbers correct, at least?
You may need to compile with:
javac -encoding ISO-8859-1 ClassName.java
and then run with:
java -Dfile.encoding=ISO-8859-1 ClassName
You can set the character encoding explicitely like that. The character encoding depends on locale settings; if you set LC_ALL to a Swedish locale ("sv_SE"?) javac and java should start using the correct encodings automatically. -
No interfaces up under solaris 8
hi,
I have a small problem with interfaces and configuring the net under solaris 8. The first thing is that there is a massage while the system is coming that there are no interfaces up.
When i use the ifconfig -a command to check it, the result is as follows:
lo0: FLAGS = 1000849 (up, loopback,running, multicast, ipv4) mtu 8232 index 1 inet 127.0.0.1 netmask ff000000
my hardware is:
x86 family 6 Model 8 Stepping 6
AT/AT Compatibile
260 330 KB RAM
VGA: Intel Corporation 810 Graphics Controller Hub
NC: 3Com 3C920 Integrated Fast Ethernet ( 3C905C - TX Compatibile)
the next thing is that i dont even have the hostname file (e.g hostname.elxl0) in the etc directory.
What can i do about this. how can i create interfaces in order to b e able to configure the network?
Thaks for help in addvance
Dotiread Solaris x86 faq at http://sun.drydog.com/
-
Hi everybody,
I'm a newbie and I created four data bases on Oracle 9i under
Solaris. Ech data bases uses about 400 MB of memory. Is that a
normal value? Basically there is no data in the data bases, yet.
I created them as general data bases with the wizard.
Thanks for any comments or hints.
Best regards,
IngoMichael ,
If you are looking for the amount of physical memory on your system,
use the 'prtconf' command. If you would like to get some virtual
memory page statistics, use the 'vmstat' command. If you would like to
find out about the memory allocated to a particular process, use
'ps -e -opid,vsz,rss,args'. The only problem is the different behavior on
different versions of Solaris. Check the man pages to find out about
the usage of each command.
A good tool is 'prtmem' in the MemTool package which can be
downloaded anonymously from playground.sun.com in /pub/memtool/
or goto www.solarisinternals.com . The MemTool tools are reported to
work on Solaris 2.6 to 2.8. The 'prtmem' tool will break down the
memory usage as follows.
1) Total Memory - approx. total memory
2) Kernel Memory - memory allocated to the kernel
3) Application - amount of anonymous pages in memory
4) Executable & libs - amount of executable and shared library pages
in memory
5) File Cache - amount of file cache not on free list
6) Free, file cache - amount of file cache on free list
7) Free, free - memory that is free
Please note that the "Free, free" number is usually very close,
if not equal, to zero. This is due to the VM systems use of the free
memory to cache files.
The ultimate resource for this type of info, from a kernel perspective, is
the "Solaris Internals" book written by Mauro and McDougall. I
recommend it highly!
HTH,
Rob -
Libsh.so appears unlinked under Solaris 7 after 4.15 upgrade
Hello,
I began upgrading our directory servers from 4.14 to 4.15 this morning.
I started with the backup server, a SparcServer 10 running Solaris 7.
Everything went ok during the install but the server would not restart,
with the following error message:
# ./start-slapd
ld.so.1: ./ns-slapd: fatal: libsh.so: open failed: No such file or
directory
Killed
Upon further investigation, I found:
# ldd /usr/netscape/server4/lib/libsh.so
ld.so.1: /usr/lib/lddstub: fatal: /usr/netscape/server4/lib/libsh.so:
mmap failed: No such device
Using the libsh.so library from older installs allows the directory
server to operate fine (although at what cost, I'm not sure).
I copied the libsh.so file from Directory Server 4.15 to our master
server (an Ultra 2 running Solaris 8 MU4) and ldd shows its linked
fine. I have not upgraded the master server until I'm confident that it
will go smoothly though.
Am I missing patches or packages for my Solaris 7 install? Can anyone
explain what the error message from ldd means? I'm not as familiar with
the Solaris linker as I am the Linux one.
I'd appreciate any help anyone can offer.
Thanks,
Kevin
Kevin M. Myer
Systems Administrator
Lancaster-Lebanon Intermediate Unit 13
(717)-560-6140I ran into the same issue with Solaris 8 and upgrading from DS 4.13 to
4.15. You need to apply the lastest Solaris recommended patch cluster and
then perform the upgrade. I tried patching after applying the upgrade and
that didn't solve the problem. I even re-ran the upgrade over top of the
first one, after applying the Solaris patches and still had the same
problem. So you will need to revert back to 4.1x and apply the patches and
then perform the 4.15 upgrade.
"Kevin M. Myer" wrote:
Hello,
I began upgrading our directory servers from 4.14 to 4.15 this morning.
I started with the backup server, a SparcServer 10 running Solaris 7.
Everything went ok during the install but the server would not restart,
with the following error message:
# ./start-slapd
ld.so.1: ./ns-slapd: fatal: libsh.so: open failed: No such file or
directory
Killed
Upon further investigation, I found:
# ldd /usr/netscape/server4/lib/libsh.so
ld.so.1: /usr/lib/lddstub: fatal: /usr/netscape/server4/lib/libsh.so:
mmap failed: No such device
Using the libsh.so library from older installs allows the directory
server to operate fine (although at what cost, I'm not sure).
I copied the libsh.so file from Directory Server 4.15 to our master
server (an Ultra 2 running Solaris 8 MU4) and ldd shows its linked
fine. I have not upgraded the master server until I'm confident that it
will go smoothly though.
Am I missing patches or packages for my Solaris 7 install? Can anyone
explain what the error message from ldd means? I'm not as familiar with
the Solaris linker as I am the Linux one.
I'd appreciate any help anyone can offer.
Thanks,
Kevin
Kevin M. Myer
Systems Administrator
Lancaster-Lebanon Intermediate Unit 13
(717)-560-6140
Maybe you are looking for
-
How do I run a video in one cell of a table when a user clicks a button in another cell?
In other words, I want to put 3 buttons in one cell of a table so that the user can run one of three Flash videos in a cell beside the buttons. How do I do that? Header 1 Header 2 button 1 runs video 1 button 2 runs video 2 button 3 runs video 3
-
Why do photos I moved offline in PSE11 not have a preview file available?
I moved photos offline in PSE11 and now the photos all have a "missing" icon rather than an "offline" icon. If I try to use them in a slideshow it says they are missing. I know I can connect the hard drive they are on, but I used to be able to do t
-
Database Control - Dynamically setting the @jc.sql statement 'attribute' ?
Hi, I have a JCX file that extends a database control. I wan't to be able to set the @jc.sql statement 'attribute' value dynamically. There does not seem to be a setProperty() api in the DatabaseControl (interface) like there is in some other types o
-
ITunes Home Share file transfer occasionally very slow
Hello... I just wanted to ask a question about a situation that occasionally occurs with my iTunes Home Sharing. Sometimes, the transfer of files from my Windows to my Mac is extremely slow. It does eventually finish successfully but this only happen
-
Purging DQM Sync Index 1 (DQM Sync Index)
I have just noticed that lots of the above concurrent programs run every minute or so and seems to be accounting for the large records in fnd_concurrent_requests table leading to performance issues. Since I keep some c.request for weeks, I cannot pur