Response committed - server restart

Hi. I am just corrrecting a progamm by me which had the problem that it invoked the " response already committed" exception ( why was this implemented in this way; it did cost me a lot of nerves until now). But my problem now, is that due to the fact that it is a lot of code there are some error producing lines still in the code. So i constantly test parts of the program. But now the Exception occurred and when i restart my prog it does not run but only throws this exception. When i programmed at home i had to restart my tomcat server to correct this problem, but in the moment I am working a the university with a server serving all studcents. So I cannot restart it :(
How can I solve this problem.
Best regards,
Mathias

If it needs a restart then it needs a restart, nothing to do about that, go ask the admin to restart, expalin carefully why and it shouldnt be a problem.
If they refuse you always can resort to more malicious ways to force a shutdown

Similar Messages

No Response from Server at end of day: 4.03

We're using Weblogic 4.03 on Solaris. At the end of a busy day, users
start submitting their transactions and some users start calling the
help desk saying that performance is very slow and I believe they are
getting "No Response from Server" from their browser.
We think it's the number of Execute Threads defined. I have provided
the settings when we received HelpDesk calls. We have also modified the
settings as mentioned below.
Some questions.
When does an Execute thread get used?
Can an execute thread be used for a long period of time (many seconds)
based on weblogic property settings?
Do the keepAlive properties keep a thread alive?
Does a connection keep a thread alive?
Does anyone know a way to monitor thread usage in 4.03?
In what situations can a connection use more than 1 thread?
Does anyone think we're on the right track?
We have defined the JRE to have a 64 meg heap.
We looked at the T3AdminMain console and at one point and saw 27
connections being used. It's hard for us to determine if this was the
high point for the day. We're not sure how to capture this type of
info. We're thinking if there were 27 connections and each of those
connections was somehow using 2 threads, this might explain the problem.
About our application, we have HTTP and HTTP requests coming through a
browser client and we also have a Java UI client executing T3s
connections.
The browser version sees a user login to the application without being
timed out for 20 minutes (1200 seconds). We have reduced this to 900
seconds.
Basically, we're not sure how Weblogic handles threads based on the
properties we've used. We have looked for documentation on this, but
have not found any. Any help would be much appreciated.
Please reply to my email id as well, if that's not too much trouble.
Thanks in advance for any help...
Mike
Here are some of our property file settings when we received the
problem:
weblogic.httpd.http.keepAliveSecs: 60
weblogic.httpd.https.keepAliveSecs: 360
weblogic.httpd.session.cacheEntries: 1024
weblogic.httpd.session.invalidationIntervalSecs: 60
weblogic.httpd.session.jdbc.connTimeoutSecs: 120
weblogic.httpd.session.swapIntervalSecs: 10
weblogic.httpd.session.timeoutSecs: 1200
weblogic.system.executeThreadCount: 42
weblogic.system.percentSocketReaders: 33
We have changed the settings below and restarted the server. We have
not received any feedback yet.
weblogic.httpd.http.keepAliveSecs: 30
weblogic.httpd.https.keepAliveSecs: 180
weblogic.httpd.session.timeoutSecs: 900
weblogic.system.executeThreadCount: 60

I've read previous threads about the problem with 4.5 and the rebuilding of the
bean cache on each method call resulting in slowdown of the system over time. I
also see that patches have been provided. Is this also an issue with 4.0.3 and
have fixes been made there? We also are seeing significant degradation of
performance over time during our load testing and have been unable to determine
the cause. We are running on a 4 processor NT machine with 1 gigabyte of RAM.
When we see the degradation of performance, one processor is operating at 100%
and memory is maxed out.
Thanks,
Jim Gish
Venkatesh Iyer wrote:
Mike
To begin with, can you
a) please check the access.log to determine the the "arrival rate" of the
HTTP request. If the requests are not arriving fast enough, tuning WLS will
not help.
b) monitor the WLS server through the console to check the # of requests in
the queue waiting to be processed. This will give an idea of the potential
source of the bottlenecks in the system.
Mike Upton wrote:
We're using Weblogic 4.03 on Solaris. At the end of a busy day, users
start submitting their transactions and some users start calling the
help desk saying that performance is very slow and I believe they are
getting "No Response from Server" from their browser.
We think it's the number of Execute Threads defined. I have provided
the settings when we received HelpDesk calls. We have also modified the
settings as mentioned below.
Some questions.
When does an Execute thread get used?
Can an execute thread be used for a long period of time (many seconds)
based on weblogic property settings?
Do the keepAlive properties keep a thread alive?
Does a connection keep a thread alive?
Does anyone know a way to monitor thread usage in 4.03?
In what situations can a connection use more than 1 thread?
Does anyone think we're on the right track?
We have defined the JRE to have a 64 meg heap.
We looked at the T3AdminMain console and at one point and saw 27
connections being used. It's hard for us to determine if this was the
high point for the day. We're not sure how to capture this type of
info. We're thinking if there were 27 connections and each of those
connections was somehow using 2 threads, this might explain the problem.
About our application, we have HTTP and HTTP requests coming through a
browser client and we also have a Java UI client executing T3s
connections.
The browser version sees a user login to the application without being
timed out for 20 minutes (1200 seconds). We have reduced this to 900
seconds.
Basically, we're not sure how Weblogic handles threads based on the
properties we've used. We have looked for documentation on this, but
have not found any. Any help would be much appreciated.
Please reply to my email id as well, if that's not too much trouble.
Thanks in advance for any help...
Mike
Here are some of our property file settings when we received the
problem:
weblogic.httpd.http.keepAliveSecs: 60
weblogic.httpd.https.keepAliveSecs: 360
weblogic.httpd.session.cacheEntries: 1024
weblogic.httpd.session.invalidationIntervalSecs: 60
weblogic.httpd.session.jdbc.connTimeoutSecs: 120
weblogic.httpd.session.swapIntervalSecs: 10
weblogic.httpd.session.timeoutSecs: 1200
weblogic.system.executeThreadCount: 42
weblogic.system.percentSocketReaders: 33
We have changed the settings below and restarted the server. We have
not received any feedback yet.
weblogic.httpd.http.keepAliveSecs: 30
weblogic.httpd.https.keepAliveSecs: 180
weblogic.httpd.session.timeoutSecs: 900
weblogic.system.executeThreadCount: 60
[jgish.vcf]

Composite with dependency not working after soa server restart

Hello,
I have composite application that invokes another composite application. After deploying those work fine. But after restarting soa server the one having dependency does not work any more. To soa server log I get following:
<Jul 1, 2010 11:45:29 AM EEST> <Error> <oracle.integration.platform> <SOA-20003> <Unable to register service.
oracle.fabric.common.FabricException: Error in getting XML input stream: http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL: Response: '503: Service Unavailable' for url: 'http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL'
at oracle.fabric.common.metadata.MetadataManagerImpl.getInputStreamFromAbsoluteURL(MetadataManagerImpl.java:276)
Caused By: java.io.FileNotFoundException: Response: '503: Service Unavailable' for url: 'http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL'
<Jul 1, 2010 11:45:30 AM EEST> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "POProcessing" failed: Unable to find a WSDL that has a definition for service {http://oracle.com/sca/soapservice/POProcessing/POProcessing/receivePO}receivePO and port execute_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server..>
So POProcessing does not work any more after server restart. validationForCC works fine also after server restart. Url http://...validationForCC/getStatusByCC?WSDL points to wsdl file and is visible by browser.
I use soa suite 11g patch set 2 (11.1.1.3) running on redhat enterprise linux 5.
Any idea what is the problem?
Is it somehow possible to configure which composites are started first during server startup?
regards, Matti
Edited by: user10197965 on Jul 1, 2010 2:28 AM

Yes, I did that. I'm not all that happy about this as a solution either, but it's better than making multiple copies.
We have since found out that his is a known bug and that it is fixed in some, but not all, deployments.
-------- see below -------------
Composites With WSDL Dependencies Fail To Deploy Following SOA Server Restart [ID 1272070.1]
Modified:Jul 19, 2012 Type:PROBLEM Status:MODERATED Priority:3
In this Document
     Symptoms
     Cause
     Solution
     References
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
Applies to:
Oracle SOA Platform - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
Symptoms
A SOA Project has an external reference to a Web Service or a reference to another Composite.
When the SOA Server is started, the Composite is trying to access the WSDL of it's referenced Web Service in order to load data structures. If SOA can not find the WSDL then the Composite fails to load/deploy.
Once this happens the Composite can not be started, or shutdown, from Enterprise Manager Fusion Middleware Control Application.
Related Error Messages:
[ERROR] [SOA-20020] ... Unable to find a WSDL that has a definition for service ... Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.]
javax.wsdl.WSDLException: WSDLException: faultCode=INVALID_WSDL: Error reading import of oramds
Cause
When SOA Server is restarting the Composite can not access the WSDL of it's referenced Web Service (it is not available).
In the first scenario there are two Composites on the same server: CompositeA and CompositeB.
In SOA Suite 11g there is no possibility to specify the load order for the composites. If CompositeA references CompositeB and if CompositeA is firstly loaded then it can not access the WSDL from CompositeB and the issue occurs.
In the second situation there is one Composite on the server (CompositeA) which references an external WebService (ExternalWS). If the ExternalWS is not available when the SOA Server is starting then this issue occurs.
Solution
Solution 1
Redeploy the affected Composite into the SOA Server.
You can do that but it is not advisable in a production environment and in a development environment it will take a lot of time to redeploy the composite manually
Solution 2
Copy the abstract WSDL locally into the project.
This is documented in these articles in our Knowledge base:
•     Document:1155033.1 Node Restart Cause Composites To Become Unavailable. Response: '503: Service Unavailable'
•     Document:1151973.1 Boot Order Of The Composites Upon Soa Suite Restart
Steps:
o     a. Copy and use the WSDL file in the Project
o     b. Edit the WebService Adapter
o     c. Change the "WSDL URL" to point to the WSDL copied into the project
o     d. Redeploy the Project
o     e. Make this configuration with all the Projects that have a references with other Web Services
Solution 3
Use shared artifacts in Metadata Service (MDS). A WSDL used by more than one composite is a shared artifact per definition. If the WSDL structure is changed (that is not happening frequently in a production environment), you will normally deploy a composite with a new version because overwriting it will break your production environment. Moreover, in a development environment you will need a proper process in place where different developers access the same artifacts within MDS. In addition, when you use external WSDLs (owned by third parties), you will have a proper process/agreement in place to be notified about modifications affecting your applications.
1.     In order to use shared artifacts a MDS connection must be configured in jDeveloper:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#SOASE85488
2.     Deploy the shared artifacts:
o     a. Create a JAR profile and include the artifacts to share
o     b. Create a SOA bundle that includes the JAR profile
o     c. Deploy the SOA bundle to the application server
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#SOASE85472
If the shared artifacts (WSDLs) needed are from other composites this step can be skipped
3.     Create a new WebService
o     a. When completing the "WSDL URL" click on "Find existing WSDL's"
o     b. Select "Resource Palette"
o     c. Go to the SOA-MDS
o     d. Select a WSDL from a Composite or the one deployed at step 2.
Known Restriction 1
The port and the location for the WSDL reference is not completed automatically by jDeveloper in the composite.xml file. This information must be inserted manually. In Bug:10287325 is raised this issue and it is available for SOA 11gPS2+.
Known Restriction 2
Another issue regarding MDS caching is raised in Bug:10218147 - the MDS cache is not refreshed when an artifact is deployed or deleted.
In order to refresh this cache the server must be restarted. This Bug resolves the issue but in a production environment the server restart will be the preferred option. The reason for that is because in a production environment you never deploy single composites under the same version after artifacts (WSDLs) have been modified.
The fix for the Bug:10218147 can be an acceptable solution in development environment where redeployment would be quicker than restarting the server.
Bug:10218147 is available for SOA 11gPS2+.
To find out more information about how to use Shared Metadata check the following documentation:
Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g
41 Deploying SOA Composite Applications
41.7.3 Deploying and Using Shared Metadata Across SOA Composite Applications in Oracle JDeveloper
URL:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#CACFEAJJ
Solution 4
The last solution is to use an UDDI (Universal Description Discovery and Integration).
Oracle recommends Oracle Service Registry 11g (OSR). The advantage is that you can use OSR and SOA Suite in a Shared WebLogic Domain.
http://www.oracle.com/technetwork/middleware/registry/overview/index.html
http://blogs.oracle.com/governance/2010/05/oracle_service_registry_11gr1.html
To find out more information about Oracle Service Registry check the following documentation:
Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite 11g
33 Configuring Service and Reference Binding Components
33.1.3 Changing the Endpoint Reference and Service Key for Oracle Service Registry Integration
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10226/bc_config.htm#SOAAG37248
Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g
A BPEL Process Activities and Services
A.4 Publishing and Browsing the Oracle Service Registry
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/bp_appx_ref.htm#SOASE85561
Oracle Fusion Middleware Service Registry 11g
http://download.oracle.com/otndocs/tech/soa/OSR11gR1ProductDocumentation.pdf
Solution 5
In case you have BPM Components in the Composites deployed check the following note:
Document 1317803.1 Soa Suite Composite Fails To Deploy Upon Restart Of Managed Server
The issue is caused by the Bug:11822470 SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
References
BUG:10218147 - WSDL CHANGES NEED SOA SUITE SERVER RESTART
BUG:10278478 - WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
BUG:10287325 - ABSTRACT WSDL NOT AVAILABLE WHEN COMPOSITE STARTED
BUG:10311698 - WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES CAN NOT BE STARTUP / SHUTDOWN
BUG:11822470 - SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
@ BUG:9267312 - MDS ARTIFACTS ARE STILL CACHED AFTER DELETING
@ BUG:9708488 - AFTER SOA RESTART, ALL PROCESSES HAVE TO BE REDEPLOYED
@ BUG:9749845 - SCHEMA CACHE STARTS EMPTY AFTER RE-START, BUT NOT AFTER DEPLOYMENT
NOTE:1151973.1 - Boot Order Of The Composites Upon Soa Suite Restart
NOTE:1155033.1 - Node Restart Cause Composites To Become Unavailable. Response: '503: Service Unavailable'
NOTE:1317803.1 - Soa Suite Composite Fails To Deploy Upon Restart Of Managed Server
Bug 11822470 : SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
               Bug Attributes
Type     B - Defect     Fixed in Product Version     11.1.1.6
Severity     2 - Severe Loss of Service     Product Version     11.1.1.4
Status     80 - Development to QA/Fix Delivered Internal     Platform     912 - Microsoft Windows (32-bit)
Created     Mar 1, 2011     Platform Version     2003
Updated     Oct 12, 2012     Base Bug     N/A
Database Version     N/A     Affects Platforms     Generic
Product Source     Oracle
Abstract: SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
*** 03/01/11 08:07 am ***
Customer has a project consists of two services for interaction with the
process and one reference to an external service.
On deployment of the process to an Enterprise Environment, the process works
as expected. However, upon a restart of the managed server, the process will
then fail to deploy.
Workaround used is to redeploy the project again.
Bug 10278478 : WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
               Bug Attributes
Type     B - Defect     Fixed in Product Version
Severity     2 - Severe Loss of Service     Product Version     11.1.1.3.0
Status     92 - Closed, Not a Bug     Platform     226 - Linux x86-64
Created     Nov 10, 2010     Platform Version     RED HAT ENTERPRISE LINUX 5
Updated     Dec 10, 2010     Base Bug     N/A
Database Version     N/A     Affects Platforms     Generic
Product Source     Oracle
Abstract: WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
Detailed Problem Description
====================
When a SOA composite get dependencies with other SOA composites located on the same server, if the dependency is still not loaded, the SOA composite will not be loaded, and there is no possibilities for Entreprise Manager console to restart it (EM crash). The only way to make it working is to redeployed the SOA composite from jDeveloper that is not acceptable in a production environment.
The composite that has the issue cannot be start-up or shut-down, although the Enterprise Manager do not show any errors with it.

Production server restarted automatically

Hi ,
I am new to the production enviorment .
Our production server restarted automatically ,i am unable to find out the reason.
Where we can see the log for cause of restart .
IN SAP SERVER/OPERATING SYSTEM LEVEL .
Ths is on very urgent basis
Hoping earliest response.
Thanks in advance .
RohitK
<b></b>
Message was edited by:
Rohit Kawankar

Hi Manoj,
Thanks for your reply ,
My current configuration is ecc 5 ,oracle 9i ,win2k3 .
I had checked in sm21 ,but i did not found anything related to restart of server .
What are all checks where i can find the log to analysis the problem.
Thanx & Regards
RohitK

JDBC Connection pool recovery after DB server restart

I am finding that Kodo is throwing the following exception after I restart
my database server (mysql). I am doing the database server restart while my
application server is idle, so it is not during a transaction.
Communication link failure: java.net.SocketException [code=0;state=08S01]
NestedThrowables:
com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code? For example, WebLogic Server's JDBC connection pool has a setting that
enables testing a connection and recovering from such failures before
allocating it from the pool.
Ben

This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code?Not right now. You can log an enhancement request with our bug database:
http://bugzilla.solarmetric.com/

BPEL Server Restarts intermittently

Hi All,
I have got a strange problem with my BPEL Server. Every once in a while the BPEL Server restarts on its own. I do not know if it has to do something with memory leaks or performance or some other reason.
I have made my logs to roll at every 2 GB. I also noticed that the BPEL Domains are reloaded everytime the logs are rolled. If during this restart there is some process on the go then i get erroneous results.
I am not able to reproduce the issue but it does happen intermittently. Has anyone else faced this issue?

Also check logs in $OAS_HOME/opmn/logs/ for "Restart" messages, then check the timeouts for the BPEL instance in $OAS_HOME/opmn/config/opmn.xml. These are maybe too low.
--olaf

Missing version field in response from server when accessing resource

HY
I have a problem to use the version option of the webstart. All files are included into a war file (created with jar cvf xx.war *). This file is in the webapps folder of the Tomcat 5. The jar files from the dev. kit (jnlp-servlet.jar, jaxp.jar, parser.jar are in the WEB-INF/lib folder).
Every time I get the same message:
Category: Download Error
Missing version field in response from server when accessing resource: (http://localhost:8080/version/ademo.jar, 1.1)
Do I need a aditional file or must Iwrite a servlet???
Whats wrong
my JNLP file
<?xml version="1.0" encoding="utf-8"?>

<jnlp codebase="http://localhost:8080/version/" href="wstest.jnlp">
<information>
<title>HJP3 WebStart Demo Application</title>
<vendor>Guido Krueger</vendor>
<homepage href="http://www.javabuch.de"/>
<description>HJP3 WebStart Demo Application</description>
<icon href="wstest.gif"/>
<offline-allowed/>
</information>
<information locale="de">
<description>HJP3 WebStart Demo-Applikation</description>
<offline-allowed/>
</information>
<security>

</security>
<resources>
<j2se version="1.4+"/>
<jar href="ademo.jar" version="1.1"/>
</resources>
<application-desc main-class="Listing3813"/>
</jnlp>
my version.xml file
<jnlp-versions>
<resource>
<pattern>
<name>ademo.jar</name>
<version-id>1.1</version-id>
</pattern>
<file>application.jar</file>
</resource>
</jnlp-versions>
my web.xml file
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
     <servlet>
          <servlet-name>JnlpDownloadServlet</servlet-name>
          <servlet-class>com.sun.javaws.servlet.JnlpDownloadServlet</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>JnlpDownloadServlet</servlet-name>
          <url-pattern>*.jnlp</url-pattern>
     </servlet-mapping>
</web-app>

The log file (jnlpdownloadservlet.log) would show the calls for the jar files if the servlet is called for the jar files (did you correct the url mapping ?). Here are a few lines from a log file
JnlpDownloadServlet(4): Initializing
JnlpDownloadServlet(3): Request: /maportal/wfe/wfeguiv.jnlp
JnlpDownloadServlet(3): User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
JnlpDownloadServlet(4): DownloadRequest[path=/wfe/wfeguiv.jnlp isPlatformRequest=false]
JnlpDownloadServlet(4): Basic Protocol lookup
JnlpDownloadServlet(4): JnlpResource: JnlpResource[WAR Path: /wfe/wfeguiv.jnlp lastModified=Tue Mar 23 17:06:56 CET 2004]]
JnlpDownloadServlet(3): Resource returned: /wfe/wfeguiv.jnlp
JnlpDownloadServlet(4): lastModified: 1080058016000 Tue Mar 23 17:06:56 CET 2004
JnlpDownloadServlet(3): Request: /maportal/wfe/wfegui.gif
JnlpDownloadServlet(3): User-Agent: JNLP/1.0.1 javaws/1.4.2_03 (b02) J2SE/1.4.2_03
JnlpDownloadServlet(4): DownloadRequest[path=/wfe/wfegui.gif isPlatformRequest=false]
JnlpDownloadServlet(3): Request: /maportal/wfe/wfegui.jar
JnlpDownloadServlet(3): User-Agent: JNLP/1.0.1 javaws/1.4.2_03 (b02) J2SE/1.4.2_03
JnlpDownloadServlet(4): DownloadRequest[path=/wfe/wfegui.jar isPlatformRequest=false]
JnlpDownloadServlet(4): Basic Protocol lookup
JnlpDownloadServlet(4): JnlpResource: JnlpResource[WAR Path: /wfe/wfegui.jar lastModified=Tue Mar 23 17:06:30 CET 2004]]
JnlpDownloadServlet(3): Resource returned: /wfe/wfegui.jarYou should see all the resources (including jar files) being requested, and whether a specific version was requested or not (in above sample, not).
I put my problems down to my application server (Orion) as other people seem to have this working. The deployment in Orion keeps the original timestamps of the jars, so I explicitly set the timestamps in my build so that the unchanged jars do not have to be downloaded all the time. This is not really a good solution, so maybe someone else can give further advice.
Brendan

PI 7.0 Production server restarts automatically

Hi guys,
We have installed and configured correctly a PI 7.0 system on Windows 2003 Standard Edition X64-bit with SQL Server 2005. We are on SP12. Everything, SLD, RFC connections work properly.
The problem is that 4-5 days after the installation the Windows Server restarts automatically in unexpected time during the day (unexpected shutdown), even when anybody doesn't do anything in the system. In the Event Viewer we get the following message/error "System Error: Category 102 EventID 1003". There are no other messages/errors.
This is a production system and we are supposed to go live within the next days! So I need your help ASAP.
Any ideas?
Thank you.
Best Regards.
Evaggelos

1) update your network card drivers to the latest and for all devices including your motherboard chipset drivers.
2) Are you using ethernet instead of USB?
3) This URL might help you
http://www.pcreview.co.uk/forums/thread-1885463.php
Regards
Sangeetha

Socket Problem, Problem about printing the response from server

Or even I am not sure if there is a response from server. My code is like that
               //Connection between, httpProxy and target adress
               Socket clientSocket= new Socket("some host", 80);
               DataOutputStream outToServer= new DataOutputStream(clientSocket.getOutputStream());
               BufferedReader inFromServer= new BufferedReader(new     InputStreamReader(clientSocket.getInputStream()));
               //The first way
               //outToServer.writeBytes("GET http://www.somehost.com/ HTTP/1.1"+ '\n');
               //System.out.println("FROM SERVER: "+inFromServer.readLine());
               //The second way
               PrintWriter out_writer = new PrintWriter(outToServer, false);
               out_writer.println("GET http://www.somehost.com/ HTTP/1.1");
               out_writer.println("Host: localhost:80");
               out_writer.println("Connection: Close");
               out_writer.println();
                                    //The second way cont.
               String s = null;
               while ((s = inFromServer.readLine()) != null)
               System.out.println(s);
               inFromServer.close();There are the two ways that I tried, and both of them didn't work. Why they are not working ? How can I solve it ?

problem is solved, the reason it doesn't work is i didn't write the parts correctly. I mean it should be exactly the same packetIf you mean that the entire request must be sent in a single IP packet, this isn't true.
and host name must also be exactly sent to server.Of course.
They must be like in the wireshark.No. The actual data you send must be the same, but the server has no way of telling about what the IP packet looks like or how many there were.
One of your problems is that newlines in HTTP are defined as \r\n. In one case you're just using \n and in the other case you're using whatever the platform line terminator is. Neither is correct.

Canceling timers after server restart

hi,
i create a couple of timers. while the application server is up i can cancel them by getting the TimerService object of the bean it's associated with, calling getTimers() and cancelling the Timer objects returned from it.
if i restart the server (let's say it crashed), the timers created in the previous session are back to run - they are persistent by definition. but now i can't cancel them anymore: same getTimers() returns an empty Collection. i think this happens because the old timers from the previous session were not rebound to the new ejbcontext, or something like this.
my question is: how can i cancel timers, that were re-invoked after server restart.
thank you.
Message was edited by:
cyclid

Below are my tests that show canceling of timers working as expected:
Session bean methods:
public void createTimers()
{      System.out.println("### CREATE - a single-action timer that expires in 4s");
ctx.getTimerService().createTimer(4000, "single-action timer that expires in 4s");
System.out.println("### CREATE - an interval timer that expires in every 2s");
ctx.getTimerService().createTimer(2000, 2000, "interval timer that expires in every 2s");
public void cancelAllTimers() {
     System.out.println("### CANCEL - timers:");
     for (java.util.Iterator iter = ctx.getTimerService().getTimers().iterator(); iter.hasNext();) {
          Timer timer = (Timer) iter.next();
          System.out.println(" canceling ... " + timer.getInfo());
          timer.cancel();
public void logCurrentTime() {
     System.out.println("### CURRENT TIME - " + java.util.Calendar.getInstance().getTime());
public void ejbTimeout(Timer timer)
{     System.out.println("### EJB TIMEOUT - " + timer.getInfo());
Java Client test:
ejb.cancelAllTimers();
Thread.sleep(4000);
ejb.logCurrentTime();
ejb.createTimers();
Thread.sleep(8000);
ejb.cancelAllTimers();
ejb.logCurrentTime();
Thread.sleep(8000);
ejb.logCurrentTime();
Logs:
1. Shutdown servers while there is an interval timer
The log shows the interval timer came back and then was cancel after server restart
07/02/06 13:46:23 ### CANCEL - timers:
07/02/06 13:46:27 ### CURRENT TIME - Tue Feb 06 13:46:27 EST 2007
07/02/06 13:46:27 ### CREATE - a single-action timer that expires in 4s
07/02/06 13:46:27 ### CREATE - an interval timer that expires in every 2s
07/02/06 13:46:29 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:46:31 ### EJB TIMEOUT - single-action timer that expires in 4s
07/02/06 13:46:31 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:46:32 Shutting down OC4J...
C:\oc4j\10131_061009\j2ee\home>java -jar oc4j.jar
07/02/06 13:48:12 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
07/02/06 13:48:13 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:15 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:17 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:48:18 ### CANCEL - timers:
07/02/06 13:48:18 canceling ... interval timer that expires in every 2s
07/02/06 13:48:22 ### CURRENT TIME - Tue Feb 06 13:48:22 EST 2007
2. Cancel timers right after they were created
07/02/06 13:50:11 ### CANCEL - timers:
07/02/06 13:50:15 ### CURRENT TIME - Tue Feb 06 13:50:15 EST 2007
07/02/06 13:50:15 ### CREATE - a single-action timer that expires in 4s
07/02/06 13:50:15 ### CREATE - an interval timer that expires in every 2s
07/02/06 13:50:17 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:19 ### EJB TIMEOUT - single-action timer that expires in 4s
07/02/06 13:50:19 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:21 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:23 ### EJB TIMEOUT - interval timer that expires in every 2s
07/02/06 13:50:23 ### CANCEL - timers:
07/02/06 13:50:23 canceling ... interval timer that expires in every 2s
07/02/06 13:50:23 ### CURRENT TIME - Tue Feb 06 13:50:23 EST 2007
07/02/06 13:50:31 ### CURRENT TIME - Tue Feb 06 13:50:31 EST 2007

Xsan 2 MDC server restart hangs

Xsan 2 MDC server restart/shutdown hangs and I am forced to do a manual shutdown everytime. Here is the log when trying to do a restart or shutdown
10/16/08 2:58:43 PM loginwindow[58] ERROR | -[ApplicationManager(AppleEventHandling) _tryQuitAllForRequestor:replyEvent:] | _tryQuitAllForRequestor - vproc_set_global_ondemand returned error -1787534507
Running:
Xserve 2x3GHz Multi-Core 4GB RAM
Running OS X S 10.5.5
Xsan 2.1 (184)
Also if I try to do a terminal reboot command the server will panic.
Message was edited by: spraguga

Do you have more than one controller? Does the volume failover? Have you tried reinstalling the OS on this particular Xserve?

Deployed Files getting overwritten every time when I do a server restart

Hi,
I have deployed a web application in weblogic server. For testing purpose, instead of placing the changed file inside the war our team will change the files directly in the deployed area. Once when we restart the application server, the new files are getting overwritten with the old one. Is there any setting with which we can stop the weblogic server deploying the old war file again?

Hi,
I am stopping and restarting the weblogic server through startManagedWeblogic.sh script. I am not using the weblogic console. Some of our application developers directly drag and drop the Units in the Deployed Area for testing Purpose. Even with nostage mode the war file in the upload folder is getting redeployed at the time of server restart.

How so we schedule a reports server restart

We want to schedule a reports server restart each night that is scheduled in windows. Does anyone know the command to do this?
The reason we want to do this is because our RDF reports often error out and a simple restart of the reports server solves the issue. Has anyone else encountered this issue and if so how did you get round it?

Hi
This is really a reports question. You can auto schedule with the queue manager to run reports on the 27th of the month in background, or have a batch script to initiate them or write a new report that initiates each ot the reports so that it can be user initiated
Brian

Web Service from stateful Session Bean deleted after server restart

Hi,
i created a stateful session bean and from this a web service.
I am able to deploy it and it works really fine.
My problem is: after a server restart the web service is gone and i
have to deploy it again.
I have some other web services (but these are web services from stateless session beans)
but they "survive" the server restart.
I don't want to deploy the web service after every server restart, did I forget something or
is it a general problem of stateful session beans or web services?
Thanks in advance
Jens

Hello Björn,
I am not quite sure what your problem is but did you have a look at these articles:
http://help.sap.com/saphelp_nw04/helpdata/en/4d/993441c73cef23e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/be/2e2c4142aef623e10000000a155106/frameset.htm
I hope they can give you some idea.
Regads
Vyara

Missing data after server restart

Hi,
We restarted our MDM server at the OS level last night. Everything seemed okay after the restart. However, when our users came in this morning, they found that some data was missing from a table. We have a Material repository with 3 main tables. Some data which have previously been populated was not appearing in our Products Detail table, the largest of the three. A large number of rows in the table had columns that failed to load with data on the repository auto-start that occured after the server restart. The auto start value in the mds.ini file was set at 300 (5 minutes) as we had seen this iisue happen once before, and thought that may help.
A stop and restart of the repository corrected the issue. Is there anything we could have done to prevent this? Is it worthwhile to try increasing the auto start delay again? Validating detail data after every server restart is not an effective option.
MDM version: 7.1 SP08
OS: AIX DB: Oracle 11g
Thanks!
Dave

Hi Dave,
I meant that when you load repository using Immediate data is loaded from .acl files (accelerator files) in a async manner.
Whereas when you load by Update Indices new acl files are generated.
Below men6tioned is a comparision between the 2 ways of laoding repository:
Load Repository Immediate
o Loads indexes from accelerator files instead of being regenerated by reading the data them from the DB and creating the index.
o Automatically builds indexes stored in out-of-date accelerator files.
o Is usually fast.
 Load Repository with Update Indices
o Rebuilds all MDM indexes files by reading and indexing data stored in the DB. The results are flushed on disk as accelerator files.
o Necessary by repository schema changes or if any error occurs.
o Might take significant amount of time to complete.
So when you observe some visual data impact in your repository it is good idea to rebuild indexes.
I guess we cannot schedule this as default behavior is to load by immediate even through the inin parameter.
as a best practice one can do this by fixing a time frame eg monthly depending on data/schema changes.
Thanks,
Ravi

Response committed - server restart

Similar Messages

Maybe you are looking for