An error on WLS on UNIX

Hi,
I just started to run WLS on Solaris on Port 80 with SP5, and I say the
following exception:
weblogic.utils.ParsingException: nested IOException:
java.io.EOFException: Unexpected end of ZLIB input stream
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at weblogic.utils.ParsingException.<init>(Compiled Code)
at weblogic.servlet.jsp.JspLexer.parse(Compiled Code)
at weblogic.servlet.jsp.JspParser.doit(Compiled Code)
at weblogic.servlet.jsp.JspParser.parse(Compiled Code)
at weblogic.servlet.jsp.Jsp2Java.outputs(Compiled Code)
at weblogic.utils.compiler.CodeGenerator.generate(Compiled Code)
at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.getServlet(Compiled
Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled
Code)
at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
(I am running a web app on it).
Does anybod know what it is? The thing is now it is no long print out
the log anymore on the console.
thanks
Xiaodong

Hi- I'm Sarie and no this didn't help. I actually tried to log in to respond and it said I wasn't registered. Not really all that cool.

Similar Messages

Error Generating PDF under Unix

Error Generating PDF under Unix
I am calling one report from another,
My requirement is when i run the first report the second report should generate pdf in unix directory ('/ora1/app/1.pdf').
If i use my local drive pdf is getting created but, if I use unix directory in the desname (dynamically) , iam getting error SCABA 14.
Please guide me !!!

Hi,
has the oracle user respectively the User that starts the Oracle Reports process on your unix machine the right to write in the specified unix directory? If this doens´t help you make sure you give the report the right directory values and try some variants of this directory values.
If you´re running Oracle Reports 6i, what I hope is not the case, this might be interessting for you: http://www.oracle.com/technology/documentation/forms/6idocs/bugfix_p11_s.html
regards

Unable to find information on WS data binding error on WLS 9.2.03 startup

Frustratingly, when I Google for "WS data binding error" I get 'old' links to BEA forum issues which may help but these are nowhere to be seen on the read-only copies now on Oracle forums here :- http://forums.oracle.com/forums/category.jspa?categoryID=202.
The link I'm looking for is:-
forums.bea.com/thread.jspa?threadID=600017135
Is there anywhere I can get access to this information or should I just post new items on the new WLS forum?
Many thanks.
p.s. the errors I am trying to research are as follows:-
<WS data binding error>could not find schema type '{http://xmlns.oracle.com/apps/otm}Transmission
<WS data binding error>Ignoring element declaration {http://xmlns.oracle.com/apps/otm}Transmission because there is no entry for its type in the JAXRPC mapping file.

Check this..
http://docs.oracle.com/cd/E10291_01/doc.1013/e10538/weblogic.htm
you can ignore those warnings
The following data type binding warnings and errors are displayed during deployment and start of Decision Service (Business Rules) Applications. These errors and warnings can be ignored.
<WS data binding error>could not find schema type '{http://www.w3.org/2001/XMLSchema}NCName
<WS data binding error>could not find schema type
'{http://websphere.ibm.com/webservices/}SOAPElement
java.lang.IllegalStateException
at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalElementNode.
getSchemaProperty(AnonymousTypeFinder.java:253)

Error in WLS 7.0

I have in my WLS 7.0 cluster enviroment error like this:
 java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext Start server side stack trace: java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext at weblogic.servlet.internal.session.SessionData.getContext(SessionData.java:359) at weblogic.servlet.internal.session.ReplicatedSessionData.becomeSecondary(ReplicatedSessionData.java:180) at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34) at weblogic.cluster.replication.ReplicationManager$wroManager.create(ReplicationManager.java:339) at weblogic.cluster.replication.ReplicationManager.create(ReplicationManager.java:1059) at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:346) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:300) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:762) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:295) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133) End server side stack trace


Have you defined a defaultwebapp for your WLS cluster ?
 Kumar Allamraju wrote:
 > Pls provide more details.
 > when does it happen? Can you consistently reproduce this stacktrace?
 >
 > thx
 > Kumar
 >
 > Marek wrote:
 >
 > > I have in my WLS 7.0 cluster enviroment error like this:
 > >
 > > java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext Start server side stack trace: java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext at weblogic.servlet.internal.session.SessionData.getContext(SessionData.java:359) at weblogic.servlet.internal.session.ReplicatedSessionData.becomeSecondary(ReplicatedSessionData.java:180) at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34) at weblogic.cluster.replication.ReplicationManager$wroManager.create(ReplicationManager.java:339) at weblogic.cluster.replication.ReplicationManager.create(ReplicationManager.java:1059) at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:346) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:300) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:762) at weblogic.rmi.internal.Bas
 > icServerRef.handleRequest(BasicServerRef.java:295) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133) End server side stack trace
 > >
 Rajesh Mirchandani
 Developer Relations Engineer
 BEA Support

Compatibility error with WLS 10.3.5 and OSB 11.1.1.4.0

As per out project requirement I am using WLS 10.3.5, OSB 11.1.1.4.0, and OEPE 11.1.1.6.1, but this oepe does not support these two WLS and OSB.
when I am trying to create a new Oracle Service Bus Configuration Project, i am getting a error:
Plug-in "com.bea.alsb.ui" was unable to instantiate class "com.bea.alsb.ui.wizards.NewALSBContainerWizard".
com/bea/alsb/core/containers/exceptions/ContainerException
Can anyone please suggest the correct version of OEPE if any.
Thanks in advance,
Jai

Thanks Rene, but as I said we are not using the same version of WLS and OSB so in that case is there any option that which version of OEPE i should download which support these two versions of WLS 10.3.5 and OSB 11.1.1.4.0.

Error in WLS console

Hi,
Am getting the below error in my wls console .
please help how to resolve this.
<Mar 20, 2012 2:44:38 AM PDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "WebCenter-CustomPortalDS": IO Error: The Network Adapter could not establish the connection>
<Mar 20, 2012 2:44:38 AM PDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "Activities-CustomPortalDS": IO Error: The Network Adapter could not establish the connection>
<Mar 20, 2012 2:44:39 AM PDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "WebCenter-CustomPortalDS": IO Error:

Check if you are able to login with the users for all the schema's for the data-sources.
If you get account locked exception then unlock it.
http://ramannanda.blogspot.in/2012/02/oracle-database-account-unlocker.html
Else check the connection properties in your application.

Error using wldeploy in unix environment

I am trying to use wldeploy ant task to deploy and undeploy applications from my server in a unix environment, and keep getting errors there, and not locally on a XP development workstation. Below are my buildfile and the error that I am getting. Anyone have any ideas as to what may be wrong?
build.xml
<target name="undeploy" description="Undeploys app">
<wldeploy user="${user}" password="${password}"
adminurl="${adminurl}" remote="true"
action="stop" name="${appname}" debug="true"
verbose="true"/>
</target>
And here is the error:
[wldeploy] weblogic.Deployer -debug -remote -verbose -noexit -name ${appname} -adminurl iiop://${host}:${port} -user ${user} -password ${password} -stop
[wldeploy] weblogic.Deployer invoked with options: -debug -remote -verbose -noexit -name broker-co
ntact.ear -adminurl iiop://${host}:${port} -user ${user} -stop
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE v
ersion V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at a
lice.healthpartners.com:8001, as user system
[wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
[wldeploy] [Debug.say():43] : getting context using iiop://alice.healthpartners.com:8001
[wldeploy] [Debug.say():43] : Connecting to MBeanServer at service:jmx:iiop://${host}:${port}/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] java.io.IOException
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProvide
rBase.java:135)
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProvid
erBase.java:79)
[wldeploy] at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.j
ava:341)
[wldeploy] at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:262)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(Serve
rConnectionImpl.java:240)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForTyp
e(ServerConnectionImpl.java:191)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectio
nImpl.java:147)
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(Web
LogicDeploymentManagerImpl.java:148)
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeplo
ymentManagerImpl.java:118)
[wldeploy] at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentMan
ager(DeploymentFactoryImpl.java:84)
[wldeploy] at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:4
32)
[wldeploy] at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:302
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[wldeploy] at weblogic.Deployer.run(Deployer.java:70)
[wldeploy] at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
:43)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:615)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:364)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:341)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[wldeploy] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[wldeploy] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:4
0)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[wldeploy] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[wldeploy] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[wldeploy] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[wldeploy] Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
[wldeploy] java.io.EOFException]
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:189)
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:195)
[wldeploy] at javax.naming.InitialContext.lookup(InitialContext.java:363)
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProvide
rBase.java:126)
[wldeploy] ... 35 more
[wldeploy] Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nest
ed exception is:
[wldeploy] java.io.EOFException
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:293)
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:190)
[wldeploy] at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:321)
[wldeploy] at weblogic.jrmp.BaseRemoteRef.invoke(BaseRemoteRef.java:221)
[wldeploy] at weblogic.jrmp.RegistryImpl_Stub.lookup(Unknown Source)
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:185)
[wldeploy] ... 38 more
[wldeploy] Caused by: java.io.EOFException
[wldeploy] at java.io.DataInputStream.readByte(DataInputStream.java:269)
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:234)
[wldeploy] ... 43 more
[wldeploy] [Debug.say():43] : Closing DM connection
[wldeploy] [Debug.say():43] : Unregistered all listeners
[wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'iiop://${host}:${port}': null. Ensure the url represents a running admin server and that the crede
ntials are correct. If using http protocol, tunneling must be enabled on the admin server.
Thanks.
Scott

Hi Richard,
I had the same issue using Eclipse. I just tried to run the
ant script outside of Eclipse and it worked fine.
This is an Eclipse-Ant Class Loader issue.
In order to make it work in Eclipse, You have to :
1. Open the External Tool Run Configuration.
2. Select your Ant script.
3. Select JRE Tab.
4. In Runtime JRE section, choose Seperate JRE.
Hope this helps !
Eric

Error connecting WLS 10.3.1 JMS & MDBs with Oracle Advanced Queuing

I followed the guide at http://blogs.oracle.com/imc/2010/12/how_to_use_oracle_aq_with_message-driven_beans_in_weblogic.html. Since the AQ queues were already set up by SAs and had been working with stateless session beans, I assume they're OK for use with MDBs. Names had to be changed in the WLS foreign server definition, destinations & connection factories to match.
My MDB is:
package xxxx;
import javax.ejb.MessageDriven;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
@MessageDriven(name = "TestQueueListenerEJB")
public class TestQueueListener implements MessageListener
public void onMessage(Message message)
if ( message instanceof TextMessage )
try
System.out.println("AQMDBTest: text message " + ((TextMessage)message).getText() + " processed");
catch (JMSException e)
e.printStackTrace();
else
System.out.println("AQMDBTest: generic message " + message.toString() +
" of type " + message.getClass().getName() + " processed");
And the relevant portion of the weblogic-ejb-jar.xml is:
<weblogic-enterprise-bean>
<ejb-name>TestQueueListenerEJB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>TestQueue</destination-jndi-name>
<connection-factory-jndi-name>TestQueueConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
So when I deploy this to my test domain I get an error:
<Feb 23, 2011 3:11:28 PM CST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: TestQueueListenerEJB is unable to connect to the
JMS destination: TestQueue. The Error was:
Can not get destination information. The destination JNDI name is TestQueue, the provider URL is null>
The test connection of the datasource is successful.
What else could I have wrong? This is my first post to this topic. Please let me know what additional information I need to provide about this. Or if I've provided too much.
Thanks very much,
Jim Greetham

OK. So I got my DBAs to create a new user with the necessary privs. Created a new queue, table, etc. I have been able to receive messages from it. So I have some looking to do in my production database queue definitions.
Jim

CMD_IDENTIFY_REQUEST error on WLS 10.0 MP1

Hello,
We just started running a WLS 10.0 MP1 cluster (IBM JVM/AIX). We see this error getting logged in the WLS log file every few minutes. I found some old CR (WLS 7.0) which talks about this and this has been supposedly fixed. Any pointers?
<Oct 16, 2008 10:29:46 AM PDT> <Error> <RJVM> <BEA-000506> <Closing: weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@36813681 because of Server expected to route a message received over an uninitialized connection: 'JVMMessage from: '4317822236859844709S:esbprod02:[7010,7010,-1,-1,-1,-1,-1]:esbprod01:7010,esbprod02:7010:prod_domain:esbprod02' to: '817180548870097230C:10.192.32.117R:-8825084390572923574S:esbprod01:[7010,7010,-1,-1,-1,-1,-1]:prod_domain:esbprod01' cmd: 'CMD_IDENTIFY_REQUEST', QOS: '101', responseId: '-1', invokableId: '-1', flags: 'JVMIDs Sent, TX Context Not Sent, 0x1', abbrev offset: '180''>
<Oct 16, 2008 10:31:46 AM PDT> <Error> <RJVM> <BEA-000506> <Closing: weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@4020402 because of Server expected to route a message received over an uninitialized connection: 'JVMMessage from: '4317822236859844709S:esbprod02:[7010,7010,-1,-1,-1,-1,-1]:esbprod01:7010,esbprod02:7010:prod_domain:esbprod02' to: '8431435963259375603C:10.192.32.134R:-8825084390572923574S:esbprod01:[7010,7010,-1,-1,-1,-1,-1]:prod_domain:esbprod01' cmd: 'CMD_IDENTIFY_REQUEST', QOS: '101', responseId: '-1', invokableId: '-1', flags: 'JVMIDs Sent, TX Context Not Sent, 0x1', abbrev offset: '180''>
Thanks
Santosh

I struggled with the same problem for weeks and found that a very likely solution was running <wlst> from within ant.
We got this problem when our deploy scripts changed from shell scripts (windows cmd files) into a single ant script where wlst was called repeatedly using the <wlst>supplied target.
Our scripts are used to create the domain and all resources from scratch and invokes wlst several times during the process.
When the ant script was changed into <exec> .. where wlst was invoked in a forked process, the problem disappeared.
I would think that the problem is wlst ant target not performing a proper cleanup.
Or, if you have another external jvm that opens an rjvm connection to the server, you might want to turn this program off during domain creation and configuration.
Hope this helps
Niels Gylling, IT Practice

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

Error Installing 8i in UNIX Open Server 5.0.5

Dear Friends,
When I installing Oralce8i in Unix open Server 5.0.5 box,I am getting this error.
relocation error: symbol not found:real path.
I copied the entire oracle 8i disk to location /orasoft and from there I am running the ./runInstaller
Installtion starts with the message
Initializing Java Virtual Machine from ../stage.Components/oracle.swd.jre.1.1.7/DataFiles/Expanded/jre/unixware/bin/../bin/i386/green_threads/jre:relocation error:symbol not found: real path
Pl. Help to overcome this problem
Thanx,
Rams.
null

user4306972 wrote:
Hi all,
I need help in installing 8i on win 2000 server.What should i do???????/
Hardware is Intel(R) Xeon(TM) cpu 3.40 GHz, RAM =2GB.
Is the above hardware is compitible with 8i installation
I would appreciate your valuable suggestions.
Regards,
Asma.
Edited by: user4306972 on Dec 9, 2009 1:02 AMI've already given you several suggestions: "surely you realize that Win 2000 server didn't even exist until long after 8i was fully *DE*-supported ..."
That means 8i was never certified on Win 2000. That means there's no guarantee that you can install it, or that it will work after installed.
But if you are determined to go down this totally uncertified, unsupported path, my only suggestion is to go back and read ... and heed ... all the points in the fine installation guide. Particularly the part about installing the loopback. Don't assume "I don't need that". Just do what the install guide says.

URGENT:: errors with WLS Portal GA

Hi,
I just installed the GA version of WebLogic Platform and tried to create a Portal
using WorkShop.
I selected a "Portal Application" and then a "Portal Web Project". The WebLogic
console (stdout) shows many errors. It is not able to find some skins, portlets
etc. The files seems to be there in the Web Project.
When i create a Portal and try to run it, it comes up with a error (/framework/skeletons/default/desktop.jsp)
not found. Even this file is present.
These were working in the beta version.
Anybody got the same errors. Any solutions??
Attached is the error file.
Raghu
[Portal_Errors.txt]

hi Raghu
this happens if you have the WLS running while working with the workshop.
The "update" - feature of WLW is not realy reliable and can cause errors.
if you will be shure all updates commit with WLS .. restart the server through
WLW.
Greetings
fear
"Raghu Subramaniam" <[email protected]> wrote:
>
>
>
Hi,
I just installed the GA version of WebLogic Platform and tried to create
a Portal
using WorkShop.
I selected a "Portal Application" and then a "Portal Web Project". The
WebLogic
console (stdout) shows many errors. It is not able to find some skins,
portlets
etc. The files seems to be there in the Web Project.
When i create a Portal and try to run it, it comes up with a error (/framework/skeletons/default/desktop.jsp)
not found. Even this file is present.
These were working in the beta version.
Anybody got the same errors. Any solutions??
Attached is the error file.
Raghu

WLS on Unix recommendation

We at my company are in the process of possibly using WLS for a intranet
application.
We are leaning towards one of three camps : Solaris, Linux. Using Unix is a
must, we
need remote administration of the box ( telnet ) and NT's uptime isn't the
greatest in the world :).
I have been perusing the weblogic newsgroups for a couple weeks now and have
seen alot
of posts in regards to incompatibilities/problems with Solaris. Is this
still the case? Java2 is also a must.
Which of the below sounds good, or if anyone has any other thoughts I would
love to hear them.
Remember, stability then performance is the key.
Sparc Solaris 2.6 or 2.7 using Sun's JDK 1.2.1_04
or
Intel Redhat Linux 6.2 using IBM JDK 1.3rc
or
Intel Redhat Linux 6.2 using Sun's JDK 1.2.2
Now am I wrong in thinking NT/2000 is not a good option? Should I consider
it?
Is it stable and fast?
Carl J. Collin
[email protected]

"Carl J. Collin" wrote:
>
We at my company are in the process of possibly using WLS for a intranet
application.
We are leaning towards one of three camps : Solaris, Linux. Using Unix is a
must, we
need remote administration of the box ( telnet ) and NT's uptime isn't the
greatest in the world :).
I have been perusing the weblogic newsgroups for a couple weeks now and have
seen alot
of posts in regards to incompatibilities/problems with Solaris. Is this
still the case? Java2 is also a must.
Which of the below sounds good, or if anyone has any other thoughts I would
love to hear them.
Remember, stability then performance is the key.
Sparc Solaris 2.6 or 2.7 using Sun's JDK 1.2.1_04Sounds good.
or
Intel Redhat Linux 6.2 using IBM JDK 1.3rc
The jvm is not currently certified / supported.
or
Intel Redhat Linux 6.2 using Sun's JDK 1.2.2
Sun's 1.2 for Linux uses green threads. It's allright for development,
but I'm not sure that I would use it in production.
-- Rob
Now am I wrong in thinking NT/2000 is not a good option? Should I consider
it?
Is it stable and fast?
Carl J. Collin
[email protected]

Cannot determine cause of Transaction Error in WLS 5.1 sp10

Upgrading to sp10 for WebLogic, an ejbCreate() via CMP throws an
          javax.transaction.TransactionRolledbackException if an error occurs
          without any stack trace or details!!! Why or when does this happen?
          Is this specific to sp10? Current environment is Sun Solaris 7, Oracle
          8.1.6, thin driver


WLS 6.0 is the first WebLogic Server version which supports XA/2PC. If you need to enlist
          multiple resources in a single transaction, you will need WLS 6.x. (I would recommend
          6.1)
          You should get your JDBC connections from TxDataSources.
          -- Rob
          Brendan wrote:
          > Hi,
          >
          > I'm looking for some definitive information on the support for distributed transactions
          > in wls 5.1 sp10.
          >
          > We are currently experiencing problems since we try to get connections from multiple
          > connectionPools in the one transaction, which seems to be disallowed.
          >
          > I have seen various posts commenting on the lack of support for 2pc/ distributed
          > transactions in wls 5.1 etc, but have not seen any definitive bea documentation
          > describing what is and is not supported.
          >
          > Before we decide to jump to 6.0 or 6.1 we'd like to ensure that 1) we need to,
          > and 2) it will support getting connections from multiple pools in the one transaction.
          >
          > Any pointers greatly appreciated.
          >
          > Brendan
          AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
          by Michael Girdley, Rob Woollen, and Sandra Emerson
          http://learnWebLogic.com
          [att1.html]

Sporadic errors in wls 61

I just rolled out wls 6.1 two days ago and sporadically users are reporting "403
forbidden" errors. Can someone shed the lights and point me to the dirction for
fixes ? It's less than 10% of users experiencing the problems.
Thanks,
Jessie

Thanks. Mike.
Could it be something else since I've run into the same problem in development
about a month ago and permenant key with ANY is used for production.
Jessie
"Michael Reiche" <[email protected]> wrote:
>
The demo license only allows browsers from 3 unique IP address to access
it.
If it is accessed by a fourth, it gives a 403 error.
Mike
"Jessie yau" <[email protected]> wrote in message
news:3c113fe2$[email protected]..
I just rolled out wls 6.1 two days ago and sporadically users arereporting "403
forbidden" errors. Can someone shed the lights and point me to thedirction for
fixes ? It's less than 10% of users experiencing the problems.
Thanks,
Jessie

An error on WLS on UNIX

Similar Messages

Maybe you are looking for