No Listener During Net8 Test
Hi! i installed Oracle 8i Pe ver 8.1.6 on Win98. all went fine but the problem is on the connection part.
When i tried to configure the service Net8 using Net8 Assistant, i just cannot connect to the database service with the error of "No Listener" (i'm using userid "scott" and password "tiger")
my host name is pingchian
below is my tnsnames.ora listing:
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
ORACLE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = pingchian)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = oracle)
and this is my listener.ora listing:
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = pingchian)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = oracle)
(ORACLE_HOME = C:\Oracle\Ora81)
(SID_NAME = oracle)
(SID_DESC =
(PROGRAM = extproc)
(SID_NAME = PLSExtProc)
(ORACLE_HOME = c:\Oracle\Ora81)
what went wrong??
pls help..
thank you.
null
Hi,
Have u started the listener?? check wether the listener is started or not by using the below command..
D:/> lsnrctl status
If the listener is not started start it using,
D:/> lsnrctl start <listener_name>
Hope this helps,
null
Similar Messages
-
Toplink problem during stress tests
Hello
I have created simple Three tier application, where SLSBs connects using Toplink to Oracle database. During stress tests I'm having very offen following exception:
Wyj¦tek [TOPLINK-4002] (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)): oracle.toplink.exceptions.DatabaseException
Opis wyj¦tku: java.sql.SQLException: Wyj?tek we-wy: The Network Adapter could not establish the connection
Wyj¦tek wewnÅtrzny: java.sql.SQLException: Wyj?tek we-wy: The Network Adapter could not establish the connection
Error code: 17002
at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:221)
at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:105)
at oracle.toplink.sessions.DatabaseLogin.connect(DatabaseLogin.java:218)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1323)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.incrementCallCount(DatabaseAccessor.java:1198)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:633)
at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:506)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:131)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:115)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeSelectCall(CallQueryMechanism.java:194)
at oracle.toplink.internal.queryframework.CallQueryMechanism.selectAllRows(CallQueryMechanism.java:565)
at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRowsFromTable(ExpressionQueryMechanism.java:733)
at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRows(ExpressionQueryMechanism.java:708)
at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:447)
at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:493)
at oracle.toplink.queryframework.ReadQuery.execute(ReadQuery.java:125)
at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:1958)
at oracle.toplink.threetier.ServerSession.internalExecuteQuery(ServerSession.java:629)
at oracle.toplink.threetier.ClientSession.internalExecuteQuery(ClientSession.java:392)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1086)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1038)
at petstore.ejb.OrderFacadeBean.getUserOrders(OrderFacadeBean.java:190)
at OrderFacadeLocal_StatelessSessionBeanWrapper8.getUserOrders(OrderFacadeLocal_StatelessSessionBeanWrapper8.java:615)
at petstore.wmodule.OrderFacadeBusinessDelegate.getUserOrders(OrderFacadeBusinessDelegate.java:50)
at petstore.wmodule.struts.OrderListAction.execute(OrderListAction.java:57)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at petstore.wmodule.servlet.EncodingFilter.doFilter(EncodingFilter.java:32)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
at petstore.wmodule.servlet.SecurityFilter.doFilter(SecurityFilter.java:43)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:600)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:793)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: Wyj?tek we-wy: The Network Adapter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:189)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:231)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:345)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:431)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:515)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:345)
at com.evermind.sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:116)
at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:102)
... 40 more
Toplink session is configured to use external transaction controller and data source. Application run on OC4J 9.0.4.1. Using jdbc debug options I wasn't able to find any causes. Has anyone faced this problem before?
Regards
JarekHi Jarek,
TopLink uses the datasource similar to any other java application would, so there are no additional restrictions. From the error, you can see that the datasource is attempting to create a new connection and that is what is causing the exception. All TopLink did was call getConnection on the datasource ( DriverManagerDataSource.getConnection ).
This could be a problem/glitch with the network or that the listener when down temporarily. Things to check would be:
-how frequently this occurs
-if it occurs for all connections after this point
-the state of the database listener (can other applications connect to it, is it up, etc)
-how many connections to the DB are active at this point
-how many connections/sessions are active from this application
-the OC4J and JDBC versions. Latest patches are better with regards to connection pools.
What is strange though is that you have the min=max, so it should never create new connections after the first time the pool is accessed. Each connection should already have been created, which is why I suggest that you contact OC4J/JDBC support.
Best Regards,
Chris -
How to measure memory consumption during unit tests?
Hello,
I'm looking for simple tools to automate measurement of overall memory consumption during some memory-sensitive unit tests.
I would like to apply this when running a batch of some test suite targetting tests that exercise memory-sensitive operations.
The intent is, to verify that a modification of code in this area does not introduce regression (raise) of memory consumption.
I would include it in the nightly build, and monitor evolution of summary figure (a-ah, the "userAccount" test suite consumed 615Mb last night, compared to 500Mb the night before... What did we check-in yesterday?)
Running on Win32, the system-level info of memory consumed is known not to be accurate.
Using perfmon is more accurate but it seems an overkill - plus it's difficult to automate, you have to attach it to an existing process...
I've looked in the hprof included in Sun's JDK, but it seems to be targetted at investigating problems rather than discovering them. In particular there isn't a "summary line" of the total memory consumed...
What tools do you use/suggest?However this requires manual code in my unit test
classes themselves, e.g. in my setUp/tearDown
methods.
I was expecting something more orthogonal to the
tests, that I could activate or not depending on the
purpose of the test.Some IDEs display mmeory usage and execution time for each test/group of tests.
If I don't have another option, OK I'll wire my own
pre/post memory counting, maybe using AOP, and will
activate memory measurement only when needed.If you need to check the memory used, I would do this.
You can do the same thing with AOP. Unless you are using an AOP library, I doubt it is worth additional effort.
Have you actually used your suggestion to automate
memory consumption measurement as part of daily builds?Yes, but I have less than a dozen tests which fail if the memory consumption is significantly different.
I have more test which fail if the execution time is siginificantly different.
Rather than use the setUp()/tearDown() approach, I use the testMethod() as a wrapper for the real test and add the check inside it. This is useful as different test will use different amounts of memory.
Plus, I did not understand your suggestion, can you elaborate?
- I first assumed you meant freeMemory(), which, as
you suggest, is not accurate, since it returns "an
approximation of [available memory]"freeMemory gives the free memory from the total. The total can change so you need to take the total - free as the memory used.
- I re-read it and now assume you do mean
totalMemory(), which unfortunately will grow only
when more memory than the initial heap setting is
needed.more memory is needed when more memory is used. Unless your test uses a significant amount of memory there is no way to measure it reliably. i.e. if a GC is perform during a test, you can have the test appear to use less memory than it consumes.
- Eventually, I may need to inlcude calls to
System.gc() but I seem to remember it is best-effort
only (endless discussion) and may not help accuracy.if you do a System.gc(); followed by a Thread.yield() at the start it can improve things marginally. -
AppContainers_test fails with error during pre-test configuration checks
Hello,
AppContainers_test fails with error during pre-test configuration checks:
"[FAIL] The machine is not properly configured for testing: the test directory "C:\Windows\SYSTEM32\" is not ACL'd to allow execute permission for "APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES"
But that kind of permission for APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES was allowed, also i tried to allow full access, but error was the same.
In the test WindowsFilteringPlatform_Tests, the same requirement "REQ - Wfp-based products must not block App Container apps operating within their declared network intentions by default" was checked successfully.
How can i pass successfully AppContainers_test?
I installed lastest versions of QFE and filters on my server, but it didn't help.Hi M'Alerter,
I have the same issue, have you found a solution to your problem ?
Cheers,
Ghalem -
Errors encountered during perfromance testing
While doing some stress testing on our WLS server we kept seeing the
following errors:
1) NullPointerException on NTSocketMuxer, error log follows:
Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux> failure in processSockets()
loop: GetData: fd=16764 numBytes=23
Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux>
java.lang.NullPointerException: null native pointer - socket was closed
at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
This error doesn't seem to have any immediate impact, although it can't
be a good thing and it seems to happen even at times when we are not
doing stress testing. Also, it is very frequent that we see the above
messages. We are running WLS 4.51 w/ Service Pack 5. I am wondering if
this is a problem w/ Service Pack 5 since I don't see this on another
machine running WLS 4.51 with Service Pack 4. Both are using JDK 1.2.2.
2) Connection Rejected, error log follows:
Tue Feb 22 07:08:16 EST 2000:<W> <ListenThread> Connection rejected:
Login timed out after 15000 msec. The socket came from
[host=207.17.47.141,port=11929,localport=443] See property
weblogic.login.readTimeoutMillis.
I know how to adjust this for this one. My questions on this are:
If I set my readTimeoutMillisSSL (SSL in this case) from 15000 to 30000
what does this exactly mean. Does this mean that instead of allowing a
max 15 seconds for a connection to be established, now I am allowing 30
seconds? Also, is this only for the initial connection establishment (ie
user login), or does this parameter effect other aspects of the
connection later on? What negative side effects would I encounter if I
set this to 60000 (1 minute)?
Finally, what can I do so that a connection does not take over 15
seconds to establish? Note this is not the norm, just happens more often
during stress testing.
3) Creating & Closing connection & DGCserver, log follows:
Tue Feb 22 07:08:44 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
144.14.157.204/144.14.157.204 2864292845294268830
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:51 EST 2000:<I> <DGCserver> tried to renew lease for
lost ref: 902
Tue Feb 22 07:08:52 EST 2000:<I> <RJVM> Heartbeat/PublicKey resend
detected
Tue Feb 22 07:08:54 EST 2000:<I> <DGCserver> tried to renew lease for
lost ref: 904
Tue Feb 22 07:08:58 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Why the constant trying to create connection, close connection?
What is DGCserver?
4) Ignoring message from a previous JVM, log follows:
Tue Feb 22 08:29:50 EST 2000:<E> <RJVM> Ignoring message from a previous
generation: JVMMessage from 8729925219143181234C138.8.222.21 to
-3465797227003769874C192.168.100.61 with CMD_ONE_WAY, prtNum=6, ack=103,
seqNum=1384
Tue Feb 22 08:30:15 EST 2000:<I> <HTTPTunneling> Sending DEAD response
What does this mean?
5) PeerGoneExceptions
What causes these?
Our environment is set up as follows:
WLS Server
WLS 4.51 w/ Service Pack 5
NativeIO = true
ExecuteThreadCount = 40
readTimeoutMillis=5000
readTimeoutMillisSSL=10000
Dell Pentium III 600 w/ 512 MB memory
NT 4.0
JavaSoft 1.2.2
-ms128 -mx350
WLS Client
Java Application
t3s and https (using WLS RMI)
JavaSoft 1.1.7b
typically Pentium 200 MHz or better w/ 64MB or more
Basically our clients connect to our WLS server using RMI. Each client
also has a callback object where the server sends event notification
back to the clients. Most of the communication is back through these
client callback objects. Its similar to a stock trading application in
that 1 client incoming requests will generate 200 outgoing events (if
for example there are 200 users on the system). The above observations
where made while 25 very active users where on the system.
Thanks very much for any and all help,
Edwin Marcial
Continental Power ExchangeHi Kim,
Thanks for the response, but which problem in particular did you solve, I've
listed a couple here.
Edwin
kim hyun chan wrote:
hi,
I met the problem like you before.
so I reduce executeThreadCount from 50 to 20 , and then I solved my proplem.
"Edwin Marcial" <[email protected]> wrote in message
news:[email protected]...
While doing some stress testing on our WLS server we kept seeing the
following errors:
1) NullPointerException on NTSocketMuxer, error log follows:
Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux> failure in processSockets()
loop: GetData: fd=16764 numBytes=23
Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux>
java.lang.NullPointerException: null native pointer - socket was closed
at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
This error doesn't seem to have any immediate impact, although it can't
be a good thing and it seems to happen even at times when we are not
doing stress testing. Also, it is very frequent that we see the above
messages. We are running WLS 4.51 w/ Service Pack 5. I am wondering if
this is a problem w/ Service Pack 5 since I don't see this on another
machine running WLS 4.51 with Service Pack 4. Both are using JDK 1.2.2.
2) Connection Rejected, error log follows:
Tue Feb 22 07:08:16 EST 2000:<W> <ListenThread> Connection rejected:
Login timed out after 15000 msec. The socket came from
[host=207.17.47.141,port=11929,localport=443] See property
weblogic.login.readTimeoutMillis.
I know how to adjust this for this one. My questions on this are:
If I set my readTimeoutMillisSSL (SSL in this case) from 15000 to 30000
what does this exactly mean. Does this mean that instead of allowing a
max 15 seconds for a connection to be established, now I am allowing 30
seconds? Also, is this only for the initial connection establishment (ie
user login), or does this parameter effect other aspects of the
connection later on? What negative side effects would I encounter if I
set this to 60000 (1 minute)?
Finally, what can I do so that a connection does not take over 15
seconds to establish? Note this is not the norm, just happens more often
during stress testing.
3) Creating & Closing connection & DGCserver, log follows:
Tue Feb 22 07:08:44 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
144.14.157.204/144.14.157.204 2864292845294268830
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:51 EST 2000:<I> <DGCserver> tried to renew lease for
lost ref: 902
Tue Feb 22 07:08:52 EST 2000:<I> <RJVM> Heartbeat/PublicKey resend
detected
Tue Feb 22 07:08:54 EST 2000:<I> <DGCserver> tried to renew lease for
lost ref: 904
Tue Feb 22 07:08:58 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Why the constant trying to create connection, close connection?
What is DGCserver?
4) Ignoring message from a previous JVM, log follows:
Tue Feb 22 08:29:50 EST 2000:<E> <RJVM> Ignoring message from a previous
generation: JVMMessage from 8729925219143181234C138.8.222.21 to
-3465797227003769874C192.168.100.61 with CMD_ONE_WAY, prtNum=6, ack=103,
seqNum=1384
Tue Feb 22 08:30:15 EST 2000:<I> <HTTPTunneling> Sending DEAD response
What does this mean?
5) PeerGoneExceptions
What causes these?
Our environment is set up as follows:
WLS Server
WLS 4.51 w/ Service Pack 5
NativeIO = true
ExecuteThreadCount = 40
readTimeoutMillis=5000
readTimeoutMillisSSL=10000
Dell Pentium III 600 w/ 512 MB memory
NT 4.0
JavaSoft 1.2.2
-ms128 -mx350
WLS Client
Java Application
t3s and https (using WLS RMI)
JavaSoft 1.1.7b
typically Pentium 200 MHz or better w/ 64MB or more
Basically our clients connect to our WLS server using RMI. Each client
also has a callback object where the server sends event notification
back to the clients. Most of the communication is back through these
client callback objects. Its similar to a stock trading application in
that 1 client incoming requests will generate 200 outgoing events (if
for example there are 200 users on the system). The above observations
where made while 25 very active users where on the system.
Thanks very much for any and all help,
Edwin Marcial
Continental Power Exchange -
Error during connection test in C4C
Hi,
during connection test in C4C i receive Service-Ping-Error: Internal Server Error (500).
The following error shown in HCI.
Inbound processing in endpoint at https://iflmapgbt104xxxxavtaio-xxxx.intaas.hana.ondemand.com/cxf/COD/ERP/SimpleConnect failed with message "Error reading XMLStreamReader.", caused by "WstxEOFException:Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]"
Message Processing Log{
IntermediateError = true
MessageGuid = AFUUKFubmbS4sE_0LvLxGiXTI0v4
Node = xxxxxxxx.od.sap.biz
OverallStatus = FAILED
StartTime = Thu Mar 26 15:40:11 UTC 2015
StopTime = Thu Mar 26 15:40:11 UTC 2015
Children [
An error has occurred in CXF Inbound Request{
Error = Inbound processing in endpoint at https://iflmapgbt104xxxxxavtaio-xxxxx.intaas.hana.ondemand.com/cxf/COD/ERP/SimpleConnect failed with message "Error reading XMLStreamReader.", caused by "WstxEOFException:Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]"
StartTime = Thu Mar 26 15:40:11 UTC 2015
Status = FAILED
Can anyone help me on this issue?
Cheers
FlorianHi Ginger,
somehow, yes :-) I deployed the iFlow for customer master replication. After creating a customer the trace looked different and terminated at the reverse proxy. So the simple connect somehow is not able to do the same...
Cheers
Florian -
Monitoring WebLogic During Performance Test
I am running performance tests on our WebLogic Server and would like to be able
to pull the Thread Queue Length, Thread Queue Throughput and Java Heap % statistics
that are displayed in the WebLogic Console and put them in a text file every so
often during the test. This way I can use those statistics with others I collect.
I assume that if the console is able to display this information that it must
be available. Does anyone know how I could do this?
Thanks In Advance"Dimitri" == Dimitri Rakitine <[email protected]> writes:
Dimitri> I don't know of a recommended way in 5.1. You may find this (crude)
Dimitri> example helpful in illustrating how to obtain runtime info from 5.1:
Dimitri> http://dima.dhs.org/misc/WLStats.jsp
Wow, thanks! I didn't realize how easy it was to get to some of this
information. This is a real help.
Dimitri> Also, there is a severinfo utility on http://developer.bea.com which
Dimitri> can be used to obtain server runtime information.
I couldn't find this utility. Any tips on how to find it on this site?
Thanks, this stuff is a real help.
-Ben
Dimitri> It is much easier in 6.x with it's JMX architecture.
Dimitri> Benjamin Simon <[email protected]> wrote:
>>>>>>> "Dimitri" == Dimitri Rakitine <[email protected]> writes:
Dimitri> It is certainly possible, but ways of doing this are
Dimitri> different for 5.1 and 6.x - which version do you use?
>> Ooh, this is something I want to be able to do. What's the recommended
>> way to do this for 5.1?
>> Thanks,
>> Ben
Dimitri> Robin Conklin <[email protected]> wrote:
>> >> I am running performance tests on our WebLogic Server and would like
>> >> to be able to pull the Thread Queue Length, Thread Queue Throughput
>> >> and Java Heap % statistics that are displayed in the WebLogic Console
>> >> and put them in a text file every so often during the test. This way
>> >> I can use those statistics with others I collect. I assume that if
>> >> the console is able to display this information that it must be
>> >> available. Does anyone know how I could do this?
>> >> Thanks In Advance
Dimitri> --
Dimitri> Dimitri
Dimitri> --
Dimitri> Dimitri -
WLS dies during stress testing
We're using JMeter to send continuous requests to the server. It creates
1500 threads and each requests Hello.jsp (see below) 500 times.
The server runs fine for about 6.5 minutes (serviced ~120000 requests)
before locking up. We let it sit for a while and about 4 minutes later, it
starts spewing out the following (bottom part of weblogic.log)
Fri May 19 10:48:37 GMT-04:00 2000:<I> <WebLogicServer> WebLogic Server
started
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: init
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
verbose initialized to: true
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
packagePrefix initialized to: jsp_servlet
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
compileCommand initialized to: /opt/Solaris_JDK_1.2.2_05a/bin/javac
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
srcCompiler initialized to weblogic.jspc
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
superclass initialized to null
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
workingDir initialized to: /opt/ejbserver/weblogic/myserver/classfiles
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
pageCheckSeconds initialized to: 1
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:
initialization complete
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> Generated
java file:
/opt/ejbserver/weblogic/myserver/classfiles/jsp_servlet/testpages/hello.java
Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=15123,localport=7111]''
Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=15172,localport=7111]''
Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=11312,localport=7111]''
Fri May 19 10:51:20 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=14368,localport=7111]''
Fri May 19 10:51:20 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=14385,localport=7111]''
Fri May 19 10:51:24 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=15294,localport=7111]''
Fri May 19 10:51:27 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=15291,localport=7111]''
Fri May 19 10:51:55 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=28068,localport=7111]''
Fri May 19 10:51:56 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=28385,localport=7111]''
Fri May 19 10:52:00 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=28421,localport=7111]''
Fri May 19 10:53:45 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=63711,localport=7111]''
Fri May 19 10:53:45 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=63709,localport=7111]''
Fri May 19 10:58:26 GMT-04:00 2000:<E> <WebLogicServer> Exception invoking
weblogic.time.server.ScheduledTrigger@d2573f
java.lang.RuntimeException: <UTIL> UnsyncCircularQueue was full!
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 java.lang.RuntimeException.<init>(Compiled Code)
at weblogic.utils.UnsyncCircularQueue.expandQueue(Compiled Code)
at weblogic.utils.UnsyncCircularQueue.put(Compiled Code)
at weblogic.kernel.ExecuteThreadManager.execute(Compiled Code)
at weblogic.kernel.Kernel.execute(Compiled Code)
at weblogic.time.common.internal.ScheduledTrigger.private_execute(Compiled
Code)
at weblogic.time.server.ScheduledTrigger.private_execute(Compiled Code)
at weblogic.time.common.internal.TimeTable.execute(Compiled Code)
at weblogic.time.common.internal.TimeEventGenerator.run(Compiled Code)
at java.lang.Thread.run(Thread.java:479)
We get a steady stream of this exact same RuntimeException for about 20
minutes before the whole thing dies.
Any ideas would be great!
Jason
The setup is the following:
Sun E250 with 1 CPU at 400MHz, 512 MB
Solaris 2.6
WLS 5.1 with SP3
Solaris Performance Pack is used
Sun JDK 1.2.2
min heap size is 128MB and max as 128MB with options
"-native -verbosegc"
other changed to the OS:
rlim_fd_max=4096
rlim_fd_cur=4096
tcp_close_wait_interval=10000
tcp_flush_fin_wait_2=10000
No paging/swapping takes place during the test.
Hello.jsp is as follows:
<html>
<head>
<title>A simple JSP file</title>
</head>
<body>
<%
out.print("<p><b>Hello World!</b>");
%>
</body>
</html>Comments inline.
Cheers - Wei
Jason <[email protected]> wrote in message
news:[email protected]...
Thanks, that definitely sheds some light on the problem.
We monitored the server and came up with the following. The queue isindeed
growing and probably accounts for the eventual failure (does anyone know
what the limit is?). The throughput is constant but just can't keep upwith
the requests. Another thing is that the heap slowly increases along with
the queue and it took a while for it to hit 100% and have GC occur.I am not sure about the limit. Either 32K or 64K, I guess. If you monitor
your queue lenght frequently, you might have a chance to spot that limit.
Every request need memory to hold. So the heap slowly increases along with
the queue.
>
Now, we duplicated the test but accessed a Servlet directly instead of a
JSP. This servlet simply did some out.print(...) statements to displaythe
same page as Hello.jsp. This ran without a hitch. We had about 5 times
more throughput and the queue wasn't growing out of control. Also, theheap
would reach 100% much quicker and GC occured more frequently. I can't see
how handling a JSP request is that much more resource intensive than a
Servlet request...
We then tried the original test again (accessing JSP) but this timeremoved
Service pack 3. We were running straight WLS 5.1 (no service packs).
Everything behaved nicely (just like the Servlet test did). Could it then
be that SP3 introduced a bug relating to how JSP requests are handled?Well, if this was the case, you might need to address this with support.
>
Finally, all the tests ran without changing the default number of execute
threads (15). I don't think increasing the number will help seeing how
short-lived these requests are. I think more execute threads would just
increase the context-switching.I agree. I've seen 15 to 60 threads in production. Might be worth a try to
use larger number of threads in your test to see if it alleviated the
problem.
>
Thanks again,My pleasure.
Jason
Wei Guan <[email protected]> wrote in message
news:[email protected]...
WebLogic has its interal request queue to enqueue all requests. Therequest
refers to an unit of work for weblogic to process, such as a triggeredtime
service, http request, etc. The finite number of worker threads defined
in
your weblogic.properties file will dequeue the requests inside therequest
queue and process the work.
There is an upper limit on the size of this queue. The message you gotmeans
that your test hit that limit. In practice, if there were lots of
requests
inside that queue, every request need to wait for lots of time beforebeing
processed (the queue is FIFO I believed). Open your WebLogic Console and
monitor the size of the queue, in your test or in your production, if
you
see the size of the queue increases constantly, there is somethingwrong.
You might need to increase the number of threads to handle the load. If
tuning up the number of threads doesn't help, you might need useweblogic
clustering (or add more servers in your clustering) to share the load.
WebLogic engineers might be able to lift up the upper limit of the sizeof
the queue. However, the larger upper limit on the queue might not helpyou
in practice. Tuning your configuration and making sure the number of
requests inside the queue do not increase constantly might be a good
practice to follow.
My 2 cents.
Cheers - Wei
Jason <[email protected]> wrote in message
news:[email protected]...
We're using JMeter to send continuous requests to the server. It
creates
1500 threads and each requests Hello.jsp (see below) 500 times.
The server runs fine for about 6.5 minutes (serviced ~120000 requests)
before locking up. We let it sit for a while and about 4 minutes
later,
it
starts spewing out the following (bottom part of weblogic.log)
Fri May 19 10:48:37 GMT-04:00 2000:<I> <WebLogicServer> WebLogic
Server
started
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:init
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
verbose initialized to: true
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
packagePrefix initialized to: jsp_servlet
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
compileCommand initialized to: /opt/Solaris_JDK_1.2.2_05a/bin/javac
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
srcCompiler initialized to weblogic.jspc
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
superclass initialized to null
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
workingDir initialized to: /opt/ejbserver/weblogic/myserver/classfiles
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
pageCheckSeconds initialized to: 1
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:
initialization complete
Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General>
Generated
java file:
/opt/ejbserver/weblogic/myserver/classfiles/jsp_servlet/testpages/hello.java
Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=15123,localport=7111]''
Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=15172,localport=7111]''
Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=11312,localport=7111]''
Fri May 19 10:51:20 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=14368,localport=7111]''
Fri May 19 10:51:20 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=14385,localport=7111]''
Fri May 19 10:51:24 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=15294,localport=7111]''
Fri May 19 10:51:27 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=15291,localport=7111]''
Fri May 19 10:51:55 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=28068,localport=7111]''
Fri May 19 10:51:56 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=28385,localport=7111]''
Fri May 19 10:52:00 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=28421,localport=7111]''
Fri May 19 10:53:45 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=63711,localport=7111]''
Fri May 19 10:53:45 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
'Login timed out after: '5000' ms on socket:
'Socket[addr=47.187.230.161/47.187.230.161,port=63709,localport=7111]''
Fri May 19 10:58:26 GMT-04:00 2000:<E> <WebLogicServer> Exceptioninvoking
weblogic.time.server.ScheduledTrigger@d2573f
java.lang.RuntimeException: <UTIL> UnsyncCircularQueue was full!
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 java.lang.RuntimeException.<init>(Compiled Code)
at weblogic.utils.UnsyncCircularQueue.expandQueue(Compiled Code)
at weblogic.utils.UnsyncCircularQueue.put(Compiled Code)
at weblogic.kernel.ExecuteThreadManager.execute(Compiled Code)
at weblogic.kernel.Kernel.execute(Compiled Code)
atweblogic.time.common.internal.ScheduledTrigger.private_execute(Compiled
Code)
at weblogic.time.server.ScheduledTrigger.private_execute(Compiled
Code)
at weblogic.time.common.internal.TimeTable.execute(Compiled Code)
at weblogic.time.common.internal.TimeEventGenerator.run(CompiledCode)
at java.lang.Thread.run(Thread.java:479)
We get a steady stream of this exact same RuntimeException for about20
minutes before the whole thing dies.
Any ideas would be great!
Jason
The setup is the following:
Sun E250 with 1 CPU at 400MHz, 512 MB
Solaris 2.6
WLS 5.1 with SP3
Solaris Performance Pack is used
Sun JDK 1.2.2
min heap size is 128MB and max as 128MB with options
"-native -verbosegc"
other changed to the OS:
rlim_fd_max=4096
rlim_fd_cur=4096
tcp_close_wait_interval=10000
tcp_flush_fin_wait_2=10000
No paging/swapping takes place during the test.
Hello.jsp is as follows:
<html>
<head>
<title>A simple JSP file</title>
</head>
<body>
<%
out.print("<p><b>Hello World!</b>");
%>
</body>
</html> -
Can i run the free version of Adobe Acrobat DC across more than one of my laptops during this test run
You mean the trial version? Yes, you can run it on as many devices you want. Each device will have its own 30-day trial limit.
-
Best way to remove/add server from farm during LB testing
Hi All,
I've been tasked to assist dev team perform load balancing test. There will be two servers in the server farm. What is the CLI command to toggle a server out of a server farm during the test? Also what is the show command for verifying which server in the pool have the sessions?
This is the test plan:
•1. Open sessions to each of the Test servers to verify that they are working
•2. Open session to the VIP for the Test environment, and identify which server has the VIP connection
•3. Take down server #1 (assumed) of the Test environment
•4. Verify that #1 server is down, and that the VIP session switched over to #2 server with minimal interruption
•5. (consider interfaces to other systems)
•6. Start new session and verify that it goes to #2 server
•7. Bring up #1 server and take down #2 server
•8. Verify that #2 session down, and both VIP sessions switched back to #1 server
•9. (consider interfaces to other systems)
•10. Bring up #2 server
Thanks in advance,
AdilHi Adil,
To get the server out of loadbalancing equation, you can simply go to serverfarm and do "no inservice" for the server you intend to take out or you can make the probe to fail or you can simply take the server out of serverfarm by doing "no rserver .
Also, regarding your testing, if you have two servers to which traffic will be loadbalanced, connection failover will not happen. Existing connections would be dropped or RST(depending upon what you configure) and new connections would be sent to server 2. Once the server 1 comes back up, the connections would again start getting loadbalanced to both servers. You cannot have failover of connections from 1 server to another in same serverfarm.
Let me know if you have any questions.
Regards,
Kanwal -
Fan Activity during hardware test
hi everyone,
when i start the hardware-test, the fan of my mac is speeding up to maximum level. it happens when i hit the hardware-test button in the "start-up-disk window". is this okay?Dear klangapparat,
Welcome to Apple Discussions.
The fan are running high during the Hardware test because the unit is in the firmware mode which is at a very basic level , kind of only assembly code runnig to let the unit do some task. However when you load the OS then the the OS has a code and a driver running for each and every hardware. There is a code which is responsiable for the speed of fans that code is missing during the test so the fans run at full speed. There is nothing controling the fans speed.
Hope this information helps.
Good Day!
Ravi Dimri. -
My macbookpro has frozen during the probe part of the hardware test (start using disk in drive, hold down "d"). It's been something like half an hour...
This is NOT during the test part. It's not even giving me those options yet (button greyed out).
What do I do now?Just hit the power key. It seems to have started ok.
-
Revision: 23085
Revision: 23085
Author: [email protected]
Date: 2011-10-21 07:49:33 -0700 (Fri, 21 Oct 2011)
Log Message:
Fix test to explicitly remove an event listener after the test is finished. Not doing this was causing the test to throw an RTE.
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/MessagingAuthProSendTest.mxmlThanks for the ideas regarding beforeInvoke, Ben. I will try to check that out. In my situation, here's essentially how my script is working...
BeforeSave is invoked.
Script makes a change to the document, which should be captured in the saved file.
Document saves.
Document appears saved for a moment, and then appears unsaved (asterisk in the document title).
My biggest problem is that this behavior isn't consistent. I have dozens of users, all running the same script, and the problem only occurs with certain users and at random times. I can move a problematic document from a user's machine to a different machine, and the problem doesn't occur there. It's very difficult to troubleshoot because I can't reproduce it consistently. -
Hi all,
I really hope someone can help me with my problem. I recently purchased a Yamaha A/V Receiver that has a Multi-Channel Input (Model: HTR-5835). I have an Audigy 2zs gamer card and I am running three Mini (3 pole) to RCA adapters into the three seperate channels on the multi channel input.
I assume all the speakers are set up correctly because during both the Receiver's AND the THX control panel speaker tests I could heard audible noise coming from my subwoofer. I can also set the receiver to tuner and listen to the radio with the subwoofer.
I have CMSS turned on and I have listened to MP3's through winamp and WMP and there was no subwoofer, but all other channels (including center) worked fine. I also tried playing BF942, WoW, guild Wars and Doom 3 with no subwoofer sound at all.
Does anyone have any ideas or a solution to figuing out this issue? I have been wracking my brains and searching the net for 3 days to no avail.
Thank you.
NdyIt's in Bass Management section of the Speaker Settings. Bass Boost will be greyed out with 5.1/6.1 or 7.1 speakers as it is meant for 2.1 and 4.1 systems.
<IMG height=335 src="mk:angry:MSITStore:C:\Documents and Settings\Paul Cook\Local Settings\Temporary Internet Files\Content. IE5\WDA3CDI7\A2ZS[].chm::/images/spkr settings.gif" width=499 border=0>
It should be possible to get a decent output from the sub when using the bass redirection. This will give you 5.1 when upmixing with CMSS or playing games and 2.1 with stereo sources. If your sub can't amplify the signal enough, you may need to put a small preamp in between the soundcard and receiver to boost it. You could make one yourself if you're into electronics, there will probably be lots of preamp circuit diagrams on the web. DWH explains why the sub output is lower than the rest here:
http://forums.creative.com/creativel...id=8533&page=2.
You could also go for a more expensive fix, which would be to use a crosover like this one in between the soundcard and receiver:
http://www.outlawaudio.com/products/icbm_about.html -
Apex listener installed no test and set bind variables buttons
I have installed Apex listener and while creating restful service module i dont see test and set bind variables buttons in the source region.
I went through the many posts. Installed apex listener successfully.
getting http://localhost:8080/ords/ started message when i start the listener.
and using Apex URL as http://localhost:7780/pls/htmldb.
What are the possibilities for this issues?
Please help me on this.
Thanks
ChandranApex listener version is 2.0.9
Apex version is 4.2
Maybe you are looking for
-
Connect macbook pro to my mac pro tower
I have a new macbook pro that I was using during an extended vacation. Now I need to go back to using my mac pro and I'd like to grab files as needed off my macbook pro. Currently my system is only using a wireless router with DSL service from Verizo
-
Arch Linux for Google Compute Engine
Hi Arch users, I’ve created a tool that can create an Arch Linux image for Google Compute Engine. It has the compute-image-packages software preinstalled so basic GCE integration works. I’m working to improve the boot times and shrink the image since
-
Control/Observe Mode Windows 10
BirdLaw wrote: For Windows 7 and 2008 R2, there's something called Remote Assistance or MSRA.exe /expert (allows unsolicited remote assistance) that will allow you to do this. I would imagine that they have it in Windows 10 and Windows 2012 as well.T
-
Mac CS5 Illustrator rectangle/round rectangle stroke problem...
I have an IMac with 10.6.3. and have CS5 installed. But i have encountered a problem in Illustrator. When I draw a rectangle or round cornered rectangle I can't stroke it below 1 point. It just snaps back to 1pt. It is fine though when drawing a circ
-
OWB 10gr2 - Location Login and Password
I can't find in which tables are stored login and password of locations. Thanks, Marco