ThreadDeath Error

Hi,
My program works fine initially, but it encounters the following error after running the program for sometime. It can occur at any time and page, thus cannot be predicted.
My program is actually of j2ee structure where it will read from a .txt file and populate the contents into a jsp. Opened quite a number of files in a single page. Dunno if thats the caused of the problem.
Can someone advise me what caused the error or how shld i go abt resolving it...
Thanks ALOT!!!
ERROR com.dso.businessDelegate.FileReader - CORBA UNKNOWN 1398079690 Maybe; nested exception is:
     org.omg.CORBA.UNKNOWN: ----------BEGIN server-side stack trace----------
org.omg.CORBA.UNKNOWN: vmcid: SUN minor code: 202 completed: Maybe
     at com.sun.corba.ee.impl.logging.ORBUtilSystemException.runtimeexception(ORBUtilSystemException.java:8539)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.convertThrowableToSystemException(CorbaMessageMediatorImpl.java:1947)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleThrowableDuringServerDispatch(CorbaMessageMediatorImpl.java:1897)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleThrowableDuringServerDispatch(CorbaMessageMediatorImpl.java:1850)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:261)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1709)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1569)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:951)
     at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:181)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:721)
     at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:473)
     at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1262)
     at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:409)
Caused by: java.lang.InternalError: Error loading com.sun.corba.ee.impl.io.IIOPOutputStream
     at com.sun.corba.ee.impl.io.ValueHandlerImpl$StreamFactory.run(ValueHandlerImpl.java:844)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.corba.ee.impl.io.ValueHandlerImpl.createOutputStream(ValueHandlerImpl.java:800)
     at com.sun.corba.ee.impl.io.ValueHandlerImpl.writeValueWithVersion(ValueHandlerImpl.java:199)
     at com.sun.corba.ee.impl.io.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:147)
     at com.sun.corba.ee.impl.encoding.CDROutputStream_1_0.writeRMIIIOPValueType(CDROutputStream_1_0.java:801)
     at com.sun.corba.ee.impl.encoding.CDROutputStream_1_0.write_value(CDROutputStream_1_0.java:850)
     at com.sun.corba.ee.impl.encoding.CDROutputStream_1_0.write_value(CDROutputStream_1_0.java:864)
     at com.sun.corba.ee.impl.encoding.CDROutputStream_1_0.write_value(CDROutputStream_1_0.java:659)
     at com.sun.corba.ee.impl.encoding.CDROutputStream.write_value(CDROutputStream.java:246)
     at com.sun.corba.ee.impl.presentation.rmi.DynamicMethodMarshallerImpl$14.write(DynamicMethodMarshallerImpl.java:338)
     at com.sun.corba.ee.impl.presentation.rmi.DynamicMethodMarshallerImpl.writeResult(DynamicMethodMarshallerImpl.java:430)
     at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:127)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:648)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:192)
     ... 8 more
Caused by: java.lang.ThreadDeath
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1274)
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1234)
     at com.sun.corba.ee.impl.orbutil.ORBClassLoader.loadClass(ORBClassLoader.java:20)
     at com.sun.corba.ee.impl.io.ValueHandlerImpl$StreamFactory.run(ValueHandlerImpl.java:838)
     ... 22 more
----------END server-side stack trace---------- vmcid: SUN minor code: 202 completed: MaybeRemoteException while opening file

I am seeing the exact same problem, intermittently, when I do a remote ejb lookup. If anyone found the answer to this, it would be much appreciated.

Similar Messages

Attempt to rebind results in ThreadDeath error

I'm having an odd error that seems to only be thrown when I attempt to run my server on my Debian box (it works fine on Windows). It's a minimal server at the moment which just initializes the registry if it's not available and then attempts to bind a copy of itself to the registry with the line
registry.rebind(name, new LobbyServer());
this causes the following to be thrown:
java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.ThreadDeath
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:382
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
60)
I''m not sure what's going on, since the same program works fine in other environments. It's a simple server at the moment which simply extends UnicastRemoteObject and contains one remote method which returns the date.
Thanks,
Mark McKay
http://www.kitfox.com

Hey Chash. Have you tried restarting the computer and the printer? I would try that first.
Restart your computer.
With the product turned on, unplug the power cord from the back of the product.
Unplug the power cord from the electrical outlet.
Wait 15 seconds.
Reconnect the power cord to the product, and then reconnect the power cord to the electrical outlet.
If the product does not automatically turn on, press the Power button ( ).
Wait a couple of minutes to make sure that the product is ready, and then try scanning again from the product control panel.
If this does not solve the issue then I would start at Solution 2 in this document: 'Error: LCD List needs to be upgraded' Message Displays on the Computer in Windows during Scanning
Hope this helps!
-SeanS
-------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

Muxer error on WLS shutdown on Solaris 8

Hi,
We're running WLS 5.1.0 (sp9) on Solaris 8 with JDK 1.2.2_07. When we shut WLS
down we get the following muxer ThreadDeath errors at the end of the shutdown:
Tue Oct 30 20:16:08 GMT+01:00 2001: <WebLogicServer> Waiting: '20' seconds
for threads to complete shutdown
Tue Oct 30 20:16:08 GMT+01:00 2001: <SSLListenThread> Shutting down Thread[SSLListenThread,5,]
Tue Oct 30 20:16:08 GMT+01:00 2001: <ListenThread> Shutting down Thread[ListenThread,5,]
Tue Oct 30 20:16:28 GMT+01:00 2001: <WebLogicServer> Invoking garbage collection
Tue Oct 30 20:16:28 GMT+01:00 2001: <GC> GC: Before free/total=62504072/67108864
(93%)
Tue Oct 30 20:16:28 GMT+01:00 2001: <GC> GC: After free/total=64015832/67108864
(95%)
Tue Oct 30 20:16:28 GMT+01:00 2001: <WebLogicServer> Invoking garbage collection
Tue Oct 30 20:16:28 GMT+01:00 2001: <GC> GC: Before free/total=64004336/67108864
(95%)
Tue Oct 30 20:16:28 GMT+01:00 2001: <GC> GC: After free/total=64020208/67108864
(95%)
Tue Oct 30 20:16:28 GMT+01:00 2001: <WebLogicServer> Shutting down execute
threads
Tue Oct 30 20:16:28 GMT+01:00 2001: <WebLogicServer> Shutdown completed
Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
java.lang.ThreadDeath
Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
java.lang.ThreadDeath
Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
java.lang.ThreadDeath
WLS doesn't then actually shut down so we have to kill the process to get rid
of it. When we try to restart WLS we get the following error (note that I've inserted
asterisks where our IP address was displayed):
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** Unable to create server
socket for: ********, port: '7001'. Perhaps the address is incorrect or another
process is using the port.
java.net.BindException: Address already in use
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
 at java.net.ServerSocket.<init>(ServerSocket.java:173)
 at weblogic.t3.srvr.ListenThread.newServerSocket(ListenThread.java:215)
 at weblogic.t3.srvr.ListenThread.run(Compiled Code)
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** The WebLogic Server
is no longer listening for connections.
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** You should probably
restart it.
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** Unable to create
server socket for: ********, port: '7002'. Perhaps the address is incorrect or
another process is using the port.
java.net.BindException: Address already in use
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
 at java.net.ServerSocket.<init>(ServerSocket.java:173)
 at weblogic.security.SSL.SSLServerSocket.<init>(SSLServerSocket.java:67)
 at weblogic.t3.srvr.SSLListenThread.newServerSocket(SSLListenThread.java:473)
 at weblogic.t3.srvr.ListenThread.run(Compiled Code)
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** The WebLogic Server
is no longer listening for connections.
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** You should probably
restart it.
Tue Oct 30 19:47:43 GMT+00:00 2001: <WebLogicServer> Server shutdown by system
Tue Oct 30 19:47:43 GMT+00:00 2001: <WebLogicServer> Server shutdown by system
Tue Oct 30 19:48:44 GMT+00:00 2001: <WebLogicServer> WebLogic Server started
Tue Oct 30 19:48:44 GMT+00:00 2001: <WebLogicServer> Server shutdown commencing
NOW
Tue Oct 30 19:48:45 GMT+00:00 2001: <HTTP> Destroying servlets in default servlet
context.
Tue Oct 30 19:48:45 GMT+00:00 2001: <WebLogicServer> Requesting thread shutdown
Tue Oct 30 19:48:45 GMT+00:00 2001: <WebLogicServer> Waiting: '20' seconds
for threads to complete shutdown
Tue Oct 30 19:48:45 GMT+00:00 2001: <SSLListenThread> Shutting down Thread[SSLListenThread,5,]
Tue Oct 30 19:48:45 GMT+00:00 2001: <ListenThread> Shutting down Thread[ListenThread,5,]
Tue Oct 30 19:49:05 GMT+00:00 2001: <WebLogicServer> Invoking garbage collection
Tue Oct 30 19:49:05 GMT+00:00 2001: <GC> GC: Before free/total=64963208/67108864
(96%)
Tue Oct 30 19:49:05 GMT+00:00 2001: <GC> GC: After free/total=65159344/67108864
(97%)
Tue Oct 30 19:49:05 GMT+00:00 2001: <WebLogicServer> Invoking garbage collection
Tue Oct 30 19:49:05 GMT+00:00 2001: <GC> GC: Before free/total=65147696/67108864
(97%)
Tue Oct 30 19:49:05 GMT+00:00 2001: <GC> GC: After free/total=65159944/67108864
(97%)
Tue Oct 30 19:49:05 GMT+00:00 2001: <WebLogicServer> Shutting down execute
threads
Tue Oct 30 19:49:05 GMT+00:00 2001: <WebLogicServer> Shutdown completed
WLS is the onle process using these ports so it shouldn't hit this problem. Our
only recourse is then to reboot the server itself after which WLS starts okay.
Obviously we don't want to have to reboot the server everytime we shut down WLS.
Has anyone else encountered this problem? Any help greatly appreciated.
Thanks,
Garry

Hi.
Please open a case with support for this issue.
Thanks,
Michael
Garry Baird wrote:
Hi,
We're running WLS 5.1.0 (sp9) on Solaris 8 with JDK 1.2.2_07. When we shut WLS
down we get the following muxer ThreadDeath errors at the end of the shutdown:
Tue Oct 30 20:16:08 GMT+01:00 2001: <WebLogicServer> Waiting: '20' seconds
for threads to complete shutdown
Tue Oct 30 20:16:08 GMT+01:00 2001: <SSLListenThread> Shutting down Thread[SSLListenThread,5,]
Tue Oct 30 20:16:08 GMT+01:00 2001: <ListenThread> Shutting down Thread[ListenThread,5,]
Tue Oct 30 20:16:28 GMT+01:00 2001: <WebLogicServer> Invoking garbage collection
Tue Oct 30 20:16:28 GMT+01:00 2001: <GC> GC: Before free/total=62504072/67108864
(93%)
Tue Oct 30 20:16:28 GMT+01:00 2001: <GC> GC: After free/total=64015832/67108864
(95%)
Tue Oct 30 20:16:28 GMT+01:00 2001: <WebLogicServer> Invoking garbage collection
Tue Oct 30 20:16:28 GMT+01:00 2001: <GC> GC: Before free/total=64004336/67108864
(95%)
Tue Oct 30 20:16:28 GMT+01:00 2001: <GC> GC: After free/total=64020208/67108864
(95%)
Tue Oct 30 20:16:28 GMT+01:00 2001: <WebLogicServer> Shutting down execute
threads
Tue Oct 30 20:16:28 GMT+01:00 2001: <WebLogicServer> Shutdown completed
Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
java.lang.ThreadDeath
Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
java.lang.ThreadDeath
Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
java.lang.ThreadDeath
WLS doesn't then actually shut down so we have to kill the process to get rid
of it. When we try to restart WLS we get the following error (note that I've inserted
asterisks where our IP address was displayed):
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** Unable to create server
socket for: ********, port: '7001'. Perhaps the address is incorrect or another
process is using the port.
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
at java.net.ServerSocket.<init>(ServerSocket.java:173)
at weblogic.t3.srvr.ListenThread.newServerSocket(ListenThread.java:215)
at weblogic.t3.srvr.ListenThread.run(Compiled Code)
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** The WebLogic Server
is no longer listening for connections.
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** You should probably
restart it.
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** Unable to create
server socket for: ********, port: '7002'. Perhaps the address is incorrect or
another process is using the port.
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
at java.net.ServerSocket.<init>(ServerSocket.java:173)
at weblogic.security.SSL.SSLServerSocket.<init>(SSLServerSocket.java:67)
at weblogic.t3.srvr.SSLListenThread.newServerSocket(SSLListenThread.java:473)
at weblogic.t3.srvr.ListenThread.run(Compiled Code)
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** The WebLogic Server
is no longer listening for connections.
Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** You should probably
restart it.
Tue Oct 30 19:47:43 GMT+00:00 2001: <WebLogicServer> Server shutdown by system
Tue Oct 30 19:47:43 GMT+00:00 2001: <WebLogicServer> Server shutdown by system
Tue Oct 30 19:48:44 GMT+00:00 2001: <WebLogicServer> WebLogic Server started
Tue Oct 30 19:48:44 GMT+00:00 2001: <WebLogicServer> Server shutdown commencing
NOW
Tue Oct 30 19:48:45 GMT+00:00 2001: <HTTP> Destroying servlets in default servlet
context.
Tue Oct 30 19:48:45 GMT+00:00 2001: <WebLogicServer> Requesting thread shutdown
Tue Oct 30 19:48:45 GMT+00:00 2001: <WebLogicServer> Waiting: '20' seconds
for threads to complete shutdown
Tue Oct 30 19:48:45 GMT+00:00 2001: <SSLListenThread> Shutting down Thread[SSLListenThread,5,]
Tue Oct 30 19:48:45 GMT+00:00 2001: <ListenThread> Shutting down Thread[ListenThread,5,]
Tue Oct 30 19:49:05 GMT+00:00 2001: <WebLogicServer> Invoking garbage collection
Tue Oct 30 19:49:05 GMT+00:00 2001: <GC> GC: Before free/total=64963208/67108864
(96%)
Tue Oct 30 19:49:05 GMT+00:00 2001: <GC> GC: After free/total=65159344/67108864
(97%)
Tue Oct 30 19:49:05 GMT+00:00 2001: <WebLogicServer> Invoking garbage collection
Tue Oct 30 19:49:05 GMT+00:00 2001: <GC> GC: Before free/total=65147696/67108864
(97%)
Tue Oct 30 19:49:05 GMT+00:00 2001: <GC> GC: After free/total=65159944/67108864
(97%)
Tue Oct 30 19:49:05 GMT+00:00 2001: <WebLogicServer> Shutting down execute
threads
Tue Oct 30 19:49:05 GMT+00:00 2001: <WebLogicServer> Shutdown completed
WLS is the onle process using these ports so it shouldn't hit this problem. Our
only recourse is then to reboot the server itself after which WLS starts okay.
Obviously we don't want to have to reboot the server everytime we shut down WLS.
Has anyone else encountered this problem? Any help greatly appreciated.
Thanks,
Garry--
Developer Relations Engineer
BEA Support

Exception -- with CustomSecurityRealm on WL6.0

I started the weblogic server with my caching realm which incorporates the
clone of RDBMSRealm. everything ran fine and i checked the security node on
the console and the users node on the same. Shutdown the server from the
monitoring tag on the Server node.
The weblogic server threw an exception while shutting down.
The detailed messages are as below. Wondering if the customSecurityRealm could
have caused it and why?
Did anybody else encounter this problem ? and if so, did you find the reason
and how were you able to correct it ?
thx,
veena.
C:\bea\wlserver6.0sp1\config\mydomain>startWebLogic.cmd
C:\bea\wlserver6.0sp1>set
PATH=.\bin;C:\bea\wlserver6.0sp1\bin;C:\bea\jdk130\bin
;C:\bea\wlserver6.0sp1\bin;C:\bea\jdk130\bin;D:\oracle\ora81\bin;D:\oracle\o
ra81
\Apache\Perl\5.00503\bin\mswin32-x86;C:\Program
Files\Oracle\jre\1.1.7\bin;C:\WI
NNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program
Files\Perforce;c:\vslick
\win;d:\jdk13\bin;C:\Program Files\Common Files\WebGain
Shared;d:\j2sdkee1.3\bin
;C:\Program
Files\WinZip;C:\bea\wlserver6.0sp1\lib;c:\bea\wlserver6.0sp1\bin\oci
816_8;d:\oracle\ora81\bin;
C:\bea\wlserver6.0sp1>set PMLOGGER=d:\myprojects\pm
C:\bea\wlserver6.0sp1>set
LOG4J=d:\myprojects\log4j\log4j.jar;d:\myprojects\log4
j\log4j-core.jar
C:\bea\wlserver6.0sp1>set
CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;d
:\myprojects\pm;d:\myprojects\pm;d:\myprojects\log4j\log4j.jar;d:\myprojects
\log
4j\log4j-core.jar;.\lib;c:\bea;
C:\bea\wlserver6.0sp1>"C:\bea\jdk130\bin\java" -hotspot -ms64m -mx64m
-classpath
.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;d:\myprojects\pm;d:\myprojects\pm
;d:
\myprojects\log4j\log4j.jar;d:\myprojects\log4j\log4j-core.jar;.\lib;c:\bea;
-Dw
eblogic.Domain=mydomain -Dweblogic.Name=myserver "-Dbea.home=C:\bea"
"-Djava.sec
urity.policy==C:\bea\wlserver6.0sp1/lib/weblogic.policy"
-Dweblogic.management.p
assword= weblogic.Server
<Apr 12, 2001 11:04:27 AM PDT> <Info> <Security> <Getting boot password from
use
r.>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
<Apr 12, 2001 11:04:33 AM PDT> <Notice> <Management> <Loading configuration
file
.\config\mydomain\config.xml ...>
log file: C:\bea\wlserver6.0sp1\.\config\mydomain\logs\weblogic.log
<Apr 12, 2001 11:04:35 AM PDT> <Info> <Logging> <Only log messages of
severity "
Error" or worse will be displayed in this window. This can be changed at
Admin C
onsole> mydomain> Servers> myserver> Logging> General> Stdout severity
threshold
>
Starting Loading jDriver/Oracle .....
<Apr 12, 2001 11:04:46 AM PDT> <Notice> <WebLogicServer> <ListenThread
listening
on port 7001>
<Apr 12, 2001 11:04:46 AM PDT> <Notice> <WebLogicServer> <SSLListenThread
listen
ing on port 7002>
<Apr 12, 2001 11:04:46 AM PDT> <Notice> <WebLogicServer> <WebLogic Server
starte
d>
<Apr 12, 2001 11:06:10 AM PDT> <Alert> <WebLogicServer> <Server shutdown has
bee
n requested by system>
<Apr 12, 2001 11:06:10 AM PDT> <Alert> <WebLogicServer> <The shutdown
sequence h
as been initiated.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '14' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '0' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '1' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '2' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '3' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '4' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '5' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '6' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '7' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '8' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '9' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '10' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '11' for queue: 'default'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '0' for queue: '__weblogic_admin_html_queue'' stopped.>
<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel> <Execute Thread:
'ExecuteThre
ad: '1' for queue: '__weblogic_admin_html_queue'' stopped.>
# HotSpot Virtual M<Apr 12, 2001 11:06:31 AM PDT> <Critical> <Kernel>
<Execute T
hread: 'ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue''
stopped.>
achine Error, EXCEPTION_ACCESS_VIOL<Apr 12, 2001 11:06:31 AM PDT>
<Emergency> <W
ebLogicServer> <ListenThread.run() failed: java.lang.ThreadDeath>
[error occured during error repo<Apr 12, 2001 11:06:31 AM PDT> <Emergency>
<WebL
ogicServer> <The WebLogic Server is no longer listening for connections. You
sho
uld probably restart it.>
<Apr 12, 2001 11:06:31 AM PDT> <Alert> <WebLogicServer> <Server shutdown has
bee
n requested by system>
<Apr 12, 2001 11:06:31 AM PDT> <Alert> <WebLogicServer> <The shutdown
sequence h
as been initiated.>
ATION
# Please report this error atrting]
# http://java.sun.com/cgi-bin/bugreport.cgi
# Error ID: 4F533F57494E13120E43505002D4
abnormal program termination
C:\bea\wlserver6.0sp1>goto finish
C:\bea\wlserver6.0sp1>cd config\mydomain
C:\bea\wlserver6.0sp1\config\mydomain>ENDLOCAL

Sean,
The WebLogic Integration 2.0 B2Bi server contains both a RosettaNet 1.0 and
RosettaNet 2.0 support. It is integrated into the product. There is no
separate c-enabler per se.
Michael
"Sean Koontz" <[email protected]> wrote in message
news:[email protected]..
>
Michael,
Are you saying that the Weblogic Integration 2.0 evaluation downloadincludes
an updated RosettaNet c-enabler?
I have downloaded Weblogic Integration 2.0 and am in the process ofinstalling/configuring
it. I haven't come across any RosettaNet stuff yet.
Like the original poster, I'm wanting to evaluate the RosettaNetfunctionality.
It is my main objective (i.e., my company has already purchased WeblogicServer
6.0).
Please advise.
Regards,
Sean Koontz
"Michael Cincinatus" <[email protected]> wrote:
Khaitan,
This newsgroup is intended for questions about WebLogic Integration
(which
includes a new version of RosettaNet for WLS 6.0). WebLogic Integration
version 2.0 will be available for download from the BEA website today
(June
29, 2001). You might want to try using the latest version of theproduct.
>>
If you are still experiencing difficulty, you should contact BEA Support
for
help. Details on BEA support can be found on the world wide web at:
http://www.bea.com/support/index.jsp. If you are evaluating BEA WebLogic
Integration, you can get support from BEA EvalNet. Details for EvalNet
can
be found at http://www.bea.com/evalnet/index.shtml.
Thanks,
Michael
"I Khaitan" <[email protected]> wrote in message
news:[email protected]..
Hi,
Has anybody installed RosettaNet for WL6.0 ?
I'm trying to make it work but unsuccessful, so far. I'm trying to
install the full
version (RosettaNet C-Enabler 1.0 with WLC1.0)
Also, the relase notes and the installation say that it supports
WL5.1sp8 and above.
Thanks and cheers.
Khaitan

RunTimeException Question

Hi!
I'm still learning java and I have a question that so far none of my friends was able to answer.
If you to the hierarchy of java Throwable is like this:
Object
I
Throwable
I I
Error Exception
... I
... RunTimeException
Why RunTimeException is under Exception and not under Error? RunTimeException is a unchecked and not check like Exception.
Shouldn't it be under Error instead?
Best regards

skalster wrote:
Why RunTimeException is under Exception and not under Error? RunTimeException is a unchecked and not check like Exception.Shouldn't it be under Error instead?Hi,
An Error is a subclass of Throwable that indicates serious problems that a reasonable application should not try to catch. Most such errors are abnormal conditions. The ThreadDeath error, though a "normal" condition, is also a subclass of Error because most applications should not try to catch it.
A method is not required to declare in its throws clause any subclasses of Error that might be thrown during the execution of the method but not caught, since these errors are abnormal conditions that should never occur.
These are the subclassses of Error > AssertionError, AWTError, CoderMalfunctionError, FactoryConfigurationError, LinkageError, ThreadDeath, TransformerFactoryConfigurationError, VirtualMachineError
But RuntimeException is the superclass of those exceptions that can be thrown during the normal operation of the Java Virtual Machine.
A method is not required to declare in its throws clause any subclasses of RuntimeException that might be thrown during the execution of the method but not caught.
Checked Exception are used for recoverable conditions But UnChecked exceptions are caused by programmer
mistake by violating some contract.
hope i have clarified something

Error when starting Weblogic in debug mode

Hi there
Has anyone experienced any difficulties when starting weblogic in debug mode.
More specifically, it cannot start correctly because it thinks that another instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unable to create
a server socket for port: 8320. java.net.BindException: Address already in use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <The WebLogic
Server is no longer listening for connections. You should probably restart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Server shutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdown sequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Server shutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unable to load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)

Thanks for the suggestion.
Unfortunatley the port is definately free/available during startup.
Stephane Kergozien <[email protected]> wrote:
Maark,
Before starting your server, please could you check that the port is
not used by one
other process. You can use the netstat command to do this.
Regards
Stephane
Mark wrote:
Hi there
Has anyone experienced any difficulties when starting weblogic in debugmode.
More specifically, it cannot start correctly because it thinks thatanother instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unableto create
a server socket for port: 8320. java.net.BindException: Address alreadyin use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <TheWebLogic
Server is no longer listening for connections. You should probablyrestart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Servershutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdownsequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Servershutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unableto load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)--
Regards,
Stephane Kergozien
BEA Support

Getting a runtime error on SAP R/3 System in Portal 6.0 SP6

Hi,
I just installed EP6.0SP6 on WAS6.0SP7 in Windows 2000/SQL2000.
When trying to config "SAP R/3 System" tab by going to System Administration -> System Configuration -> UM Configuration:
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : pcd:portal_content/administrator/system_admin/system_admin_role/com.sap.portal.system_admin_ws/com.sap.portal.system_configuration/com.sap.portal.uMPropertyEditor
Component class : com.sapportals.portal.prt.component.usermanagement.admin.UMPropertyEditorComponent
User : Administrator
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
 at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
 at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
 at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:109)
 at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:627)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:337)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:315)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:815)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:151)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:124)
 at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:250)
 at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:100)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:931)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
 ... 38 more
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in executing a process for compilation, D:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3812: code too large for try statement
 } catch(IOException _jspioex) {}
 ^
D:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:88: code too large for try statement
 try {
 ^
D:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:73: code too large for try statement
 try {
 ^
D:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:68: code too large for try statement
 try {
 ^
D:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3804: code too large for try statement
 } catch (ThreadDeath tde) { throw tde;
 ^
D:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3805: code too large for try statement
 } catch (Throwable t) {
 ^
D:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:49: code too large for try statement
 try {
 ^
D:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:22: code too large
 public void doContent(IPortalComponentRequest componentRequest, IPortalComponentResponse aResponse)
 ^
8 errors
 at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.launchCompilerProcess(J2eeCompiler_6_30.java:541)
 at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compileExternal(J2eeCompiler_6_30.java:370)
 at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compile(J2eeCompiler_6_30.java:649)
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2143)
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:76)
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:119)
 ... 43 more
Any idea? Also, I notice some forum thread that mentions we cannot setup R/3 4.6c connection within Portal. Our user store/CUA is on R/3 4.6c.
Is this true?
Thanks,
Edmond

Hi Edmond,
it's not the ume, it's the com.sap.portal.usermanagement.admin package.
In order to redeploy it, go to following directory:
<drive>\usr\sap\<SAPSID>\JC<instance number>\j2ee\cluster\server0 \apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
look for the com.sap.portal.usermanagement.admin.par.bak, remove the suffix .bak and restart your engine.
Don't know of this helps, but maybe it's worth a try.
Regards, Karsten

Error when accessing "SAP SYSTEM" tab in UM configuration

Hi,
I'm trying to define a new SAP SYSTEM using the portal System Administration. When I click to the SAP SYSTEM tab I have a " code too large for statement" error. Does anyone know how to avoid that or another way to define a new system not using the portal interface
TIA
log:
An exception occurred while processing a request for :
iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_configuration/com.sap.portal.uMPropertyEditor
Component Name : com.sap.portal.usermanagement.admin.UMPropertyEditor
Error in executing a process for compilation, D:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3812: code too large for try statement } catch(IOException jspioex) {} ^ D:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servletjsp/irj/root/WEB-INF/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_TabStrip3.java:88: code too large for try statement try { ^ D:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:73: code too large for try statement try { ^ D:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:68: code too large for try statement try { ^ D:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3804: code too large for try statement } catch (ThreadDeath tde) { throw tde; ^ D:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3805: code too large for try statement } catch (Throwable t) { ^ D:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:49: code too large for try statement try { ^ D:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:22: code too large public void doContent(IPortalComponentRequest componentRequest, IPortalComponentResponse aResponse) ^ 8 errors .
Exception id: 01:06_04/11/04_0014_7568250
See the details for the exception ID in the log file

Hi Andre,
please compare code too large for try statement
Please open an OSS message.
Hope it helps
Detlev

Error in UM Configuration

Hi
When I click on the link "UM Configuration" under "System Administration - System Configuration" I get the following error message:
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_configuration/com.sap.portal.uMPropertyEditor
Component Name : com.sap.portal.usermanagement.admin.UMPropertyEditor
Error in executing a process for compilation, C:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3812: code too large for try statement } catch(IOException jspioex) {} ^ C:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servletjsp/irj/root/WEB-INF/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_TabStrip3.java:88: code too large for try statement try { ^ C:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:73: code too large for try statement try { ^ C:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:68: code too large for try statement try { ^ C:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3804: code too large for try statement } catch (ThreadDeath tde) { throw tde; ^ C:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:3805: code too large for try statement } catch (Throwable t) { ^ C:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:49: code too large for try statement try { ^ C:/usr/sap/P66/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.sap.portal.usermanagement.admin/work/pagelet/_sapportalsjsp_tabstrip3.java:22: code too large public void doContent(IPortalComponentRequest componentRequest, IPortalComponentResponse aResponse) ^ 8 errors .
Exception id: 10:32_14/02/05_0001_2099450
See the details for the exception ID in the log file
I did not change this iView before. Please help.
Thanks
Sriram

Hi Sriram,
see Error when accessing "SAP SYSTEM" tab in UM configuration
Maybe try ask in this thread if a response to the opened OSS message has been given.
Hope it helps
Detlev

Java.lang.ThreadDeath

Hello
I have got the following error when I try to close the frame or when I try to stop the applet.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:715)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.forciblyStop(BridgeImpl.java:329)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.stop(BridgeImpl.java:321)
at org.apache.tools.ant.module.run.TargetExecutor.stopProcess(TargetExecutor.java:312)
at org.apache.tools.ant.module.run.StopBuildingAction.performAction(StopBuildingAction.java:96)
at org.openide.util.actions.CallableSystemAction$1.run(CallableSystemAction.java:100)
at org.netbeans.modules.openide.util.ActionsBridge.doPerformAction(ActionsBridge.java:53)
at org.openide.util.actions.CallableSystemAction.actionPerformed(CallableSystemAction.java:96)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
Could some one help how to handle it ...is it possible to handle like an exception.

Hi Nilanshu
Please log a TAR for this ... we think its conc manager related ... was waiting for someone out there to hit it ... we could not reproduce consistently. Log TAR against XMLP it will be BI Publisher (1479) in Metalink and we can then get it routed to the CP team if needed. Please provide as much info as possible about your env, esp java heap, java versions, etc.
Tim

ThreadDeath

I have a class that sits in a loop listening for incoming socket connections and spawns a new thread to handle each incoming connection. Even if I never receive an incoming connection and a new thread is never spawned, if I stop execution of the server (by clicking the "Stop" button in NetBeans), I get the following error:
C:\MyProject\nbproject\build-impl.xml:417: The following error occurred while executing this line:
C:\MyProject\nbproject\build-impl.xml:284: java.lang.ThreadDeath
BUILD FAILED (total time: 5 minutes 0 seconds)
Here is my the only method in my class:
public void listenForConnections(int port)
            throws IOException {
        ServerSocket serverSocket = new ServerSocket(port);
        while (true) {
            try {
                Socket socket = serverSocket.accept();
                RequestHandler requestHandler
                        = new RequestHandler(socket);
                Thread thread = new Thread(requestHandler);
                thread.start();
            } catch (IOException ioe) {
                LOGGER.log(Level.SEVERE, "An error has occurred accepting a new"
                        + " socket connection.", ioe);
            } catch (RuntimeException re) {
                LOGGER.log(Level.SEVERE, "An unexpected error has occurred.",
                        re);
    }Any ideas why I'm getting this and how I can handle it? Is there a better hook I can build in to exit the while loop and terminate nicely?

balforth wrote:
I never accept an incoming connection, I just let this run for 5 - 10 minutes and then stop the application. And there is no full stack trace...the three lines I posted are all that's displayed. It's interesting that it says the "build failed". Isn't it already built since it's running? Is there any way to catch and handle the JVM being stopped?Alright, well, I'm not sure how exactly NetBeans runs its build, but what you have looks something like Ant.
Ant is a build scripting engine that runs in Java. If your Ant build file is executing your Java program, then there are two options. Either it is forking the JVM (running your program in a new process), or it is running your program in the same JVM.
It is possible that the way NetBeans' build works is that your configuration is to run the program in the same process. If that's the case, it might very well be that when you stop the program, instead of just killing the JVM (which would also kill the build), it kills the thread which was running your program. If this is what is happening, the error might go away if you configure your build to fork the JVM instead (this would probably be done through a NetBeans dialog or by editing the build-impl.xml file directly--show us the relevant parts of build-impl.xml if you have trouble). Either way, it doesn't really seem like something you need to worry about; this error likely would not be thrown if you were launching the program in a production environment.

Getting Virtual Function Call runtime error R6025 from iexplore.exe

Hi all,
I am getting an virtual function call runtime error from iexplore.exe. The IE will then crash. I have checked the log in java console. It shows
basic: Removed progress listener: sun.plugin.util.GrayBoxPainter@4607b5
basic: Finding information ...
basic: Releasing classloader: sun.plugin.ClassLoaderInfo@314585, refcount=3
basic: Done ...
basic: Joining applet thread ...
basic: Destroying applet ...
basic: Disposing applet ...
basic: Quiting applet ...
basic: Joined applet thread ...
basic: Unregistered modality listener
--> basic: Stopping applet ...
--> basic: Stopping applet ...
basic: Removed progress listener: sun.plugin.util.GrayBoxPainter@cbb7db
basic: Finding information ...
basic: Releasing classloader: sun.plugin.ClassLoaderInfo@314585, refcount=2
basic: Done ...
basic: Joining applet thread ...
basic: Destroying applet ...
basic: Disposing applet ...
basic: Quiting applet ...
basic: Joined applet thread ...
basic: Unregistered modality listener
I have implemented the stop() in all the applet classes. However, I do not know where this stop() called?
Also, from the java debugger, it always stops and shows:
Exception occurred: java.lang.ThreadDeath (uncaught)"thread=TimerQueue", javax.s
wing.TimerQueue.run(), line=-1 bci=63
TimerQueue[1] cont
>
Exception occurred: java.lang.Exception (uncaught)"thread=main", sun.plugin.com.
JavaClass.getIdForName(), line=-1 bci=72
main[1] cont
>
Exception occurred: java.lang.Exception (uncaught)"thread=main", sun.plugin.com.
JavaClass.getIdForName(), line=-1 bci=72
main[1] cont
>
Exception occurred: java.lang.Exception (uncaught)"thread=main", sun.plugin.com.
JavaClass.getIdForName(), line=-1 bci=72
main[1] cont
>

What version of 5.0 are you running? There were some problems new in 5.0 seen mainly with the Java Plug-In and other apps which embed the JVM which were fixed in 5.0u6.

Error: Timeout for content=#number#

RDBMS 8.1.6.3.
Sun solaris 2.6
My previous installation was OAS9i 1.0.2.0 with portal 3.0.6.x
Then yesterday I installed the OAS9i 1.0.2.2 (the runInstaller chose what software had to be deleted, upgraded or installed as new) and I upgraded the portal schemas with the script found here in OTN.
The whole process seemed all ok, but now when I access to the main portal page usually have the error in subject in the place of every portlet. Sometime the error is "Error: The portlet could not be located".
I think both are related to the upgrade process, but I checked the upgrade log produced by the script and found only errors about installing/upgrading Intermedia, but for me it is normal, as I have never installed it.
Does someone have suggestions/comments?
Thanks
Mauro
null

Hi all
First of all, I want to thank you for your suggestions.
Then I would inform you about my progress.
Following Hyundeok's suggestion (I don't use SSL), I checked the jserv.log and I found these errors:
1) Repository /pandorino_home/3rdsw/oradba/product/OAS9I/Apache/Jserv/servlets/Parallel.jar doesn't exist!
2) page/JNI: Exception when trying to connect in 1.
page/Timeout occurred, label=510 url=http://pandorino:7777/pls/dad_portal/!WWW_PORTAL.wwpro_app_provider.execute_portlet
page/ContentFetcher InterruptedIOException Caught, Fetcher Timedout name=content-fetcher5
3) (EMERGENCY) ajp12: ping: no reply (0) Please make sure that the wrapper.classpath is pointing to the correct version of ApacheJServ.jar
(EMERGENCY) ajp12[1]: cannot scan servlet headers (500)
(ERROR) an error returned handling request via protocol "ajpv12"
(ERROR) an error returned handling request via protocol "balance"
4) page/UncaughtException in thread name=content-fetcher2, starting a new fetcher after exception java.lang.ThreadDeath
My comments/actions:
About (1), very strange, the Parallel.jar file doesn't exist! But I don't think that
it is related to the error in subject. In any case this error is raised only at Apache startup.
About (2), when it occurs, I see the error "Error: Timeout for content=#number#" in the place of portlet.
following Randy's suggestion, I increased the timeout of:
(-) "Login Server" portlet provider (from 10 to 20 seconds),
(-) "Oracle Report Security" portlet provider (from 1(one) to 20 seconds),
(-) "Monitor" portlet provider (from 10 to 20 seconds).
About (3), I increased the timeout in the jserv.conf file: ApJServVMTimeout 20
About (4), when it occurs, I see the error "Error: The portlet could not be contacted" in the place of portlet.
No action performed.
After a week of tests, It seems that (2) and (3) have been fixed thanks to the increased timeout.
Concerning (4), it is still experienced by me and other users. I think that in this case the
last thing to try is to apply the patch fix suggested by John.
But at the moment I don't have time to do this, so in the meantime I will press the browser's "reload" button until the portlet is displayed.
Thanks again.
Mauro

Two unexplained compile errors in build-impl.xml

Hi, I am encountering two errors when trying to run my programs from NetBeans 6.0 (Run Main Project F6):
...\Java\Generics_1_0_0\nbproject\build-impl.xml:412: The following error occurred while executing this line:
 
 <target depends="init,compile" description="Run a main class." name="run">
 <j2seproject1:java> <-------- HERE !!!
 <customize>
 <arg line="${application.args}"/>
 </customize>
 </j2seproject1:java>
 </target>
 <target name="-do-not-recompile">
 <property name="javac.includes.binary" value=""/>
 </target>...\Java\Generics_1_0_0\nbproject\build-impl.xml:279: java.lang.ThreadDeath
 <target name="-init-macrodef-java">
 <macrodef name="java" uri="http://www.netbeans.org/ns/j2se-project/1">
 <attribute default="${main.class}" name="classname"/>
 <element name="customize" optional="true"/>
 <sequential>
 <java classname="@{classname}" dir="${work.dir}" fork="true"> <------------- HERE
 <jvmarg line="${run.jvmargs}"/>
 <classpath>
 <path path="${run.classpath}"/>
 </classpath>
 <syspropertyset>
 <propertyref prefix="run-sys-prop."/>
 <mapper from="run-sys-prop.*" to="*" type="glob"/>
 </syspropertyset>
 <customize/>
 </java>
 </sequential>
 </macrodef>
 </target>Yet, when I Clean and Build Main Project (Shift+F11), I get no errors. I have been restructuring my application recently by creating several java library project and moving class files. Anybody knows what is happening? How can I solve this issue? Thanks !!

The problem disappeared, I don't how and I don't know how...!!!

Very strange Java error!!

Hi,
I have been trying to make the migration workbench run, for the past one week!
I have been consistently getting 'class not found' error(see listing below) when I try to run the startMWB script. Please note the last few lines of the listing; the class loader loads the MigrationApp class and then it says that it can't find it.
-----------------output of startMWB script---
bbd-orac1./export/app/workbench/Omwb/bin> startMWB
Info: ORACLE_HOME= /export/app/oracle/product/7.3.4
Info: JAVA_HOME= /usr/java1.1
Warning: ODBC_HOME not set, assuming default /opt/odbc path.
Info: SYBASE_JDBCHOME= /export/app/jConnect-4_2
Starting Migration Workbench.....
[Loaded java/lang/Thread.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Object.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Class.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/String.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/Serializable.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/ThreadDeath.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Error.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Throwable.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Exception.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/RuntimeException.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Cloneable.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Runnable.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/ThreadGroup.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/StringBuffer.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/System.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Integer.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Number.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/NoClassDefFoundError.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/LinkageError.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/OutOfMemoryError.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/VirtualMachineError.class from /usr/java1.1/lib/classes.zip]
[Loaded java/util/Properties.class from /usr/java1.1/lib/classes.zip]
[Loaded java/util/Hashtable.class from /usr/java1.1/lib/classes.zip]
[Loaded java/util/Dictionary.class from /usr/java1.1/lib/classes.zip]
[Loaded java/util/HashtableEntry.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/FileInputStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/InputStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/FileDescriptor.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/FileOutputStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/OutputStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/BufferedInputStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/FilterInputStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/PrintStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/FilterOutputStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/BufferedOutputStream.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/OutputStreamWriter.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/Writer.class from /usr/java1.1/lib/classes.zip]
[Loaded sun/io/CharToByteConverter.class from /usr/java1.1/lib/classes.zip]
[Loaded sun/io/CharacterEncoding.class from /usr/java1.1/lib/classes.zip]
[Loaded java/util/Locale.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Character.class from /usr/java1.1/lib/classes.zip]
[Loaded sun/io/CharToByteISO8859_1.class from /usr/java1.1/lib/classes.zip]
[Loaded java/io/BufferedWriter.class from /usr/java1.1/lib/classes.zip]
[Loaded java/lang/Compiler.class from /usr/java1.1/lib/classes.zip]
[Loaded oracle/mtg/migrationUI/MigrationApp.class from /export/app/workbench/Omwb/jlib/omwb-1_3_0_0_1.jar]
[Loaded oracle/sysman/emSDK/client/appContainer/WebApplication.class from /export/app/workbench/Omwb/jl ib/omwb-1_3_0_0_1.jar]
Class not found: oracle.mtg.migrationUI.MigrationApp
bbd-orac1./export/app/workbench/Omwb/bin>
OS: Solaris (Ultra 5)
jvm: 1.1.8_10
oracle:7.3.4
Regards
Manu

Thanks OMW_Support. That was real neat support. Thanks, it worked!
Essentially, OMW gives an error if you try to install it into 7.3.4 home, so I had actually installed it into a different home. But while running the startOMW script, as you pointed out the ORACLE_HOME variable was set to 7.3.4; changed it to the second ORACLE_HOME and it worked.
Kind regards
Manu
<BLOCKQUOTE>quote:<HR>Originally posted by Oracle Migration Workbench Support:
If you are not running Oracle 8.1.7, then you need to install Oracle Migration Workbench 1.3.0.0.1 into a separate Oracle Home.
The installer will install the required 8.1.7. client libraries and you can then use it to migrate to an Oracle8 or Oracle8i database. The key issue here is that when the Installer asks you to select or enter an Oracle Home, that you enter a new Oracle Home. (If you already had 8.1.7, then you'd have been able to install into an existing 8.1.7 Oracle Home. However, because you are not, then you need to install into a separate Oracle Home).
ORACLE_HOME needs to point to this new Oracle Home when starting the Migration Workbench. Your log shows that it is pointing to an Oracle 7.3 home, which is incorrect.
Please note that the Migration Workbench only supports migrations to Oracle8 and Oracle8i.<HR></BLOCKQUOTE>
null

ThreadDeath Error

Similar Messages

Maybe you are looking for