Connection timeout errn 238 after reboot server invoking Ws

Hi
I have been looking for a solution for the following during last two weeks and i´am becoming almost crazy, so any help will be welcomed
I have a Web Service with Axis2 that publish several methods. One of this methods call two external (Internet) Web Services so for this web services i am a client. The client for this Web Services is made with Axis 1.4.
I can say that all works fine but when we boot the web server (tomcat and i have also test in JBoss) the client for this web services don´t work it raises
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection timed out (errno:238)
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection timed out (errno:238)
When trying to connect to the external Web Services. The rest of the methods i publish in Axis2 if they don´t have to call these external web services, works fine.
Tomcat server 6 and jdk 1.5 (also tested with 1.6)
I´m becoming crazy because this source code works fine until a boot is made and after that calling external web services don´t work. To make it work i have to undeploy mi Web Service un Axis2 an redeploy and sometimes i also have to redeploy Axis2.
Any idea please?
Thanks in advance

Similar Messages

Connection timeout when using iPlanet web-server uses Weblogic 6.1 proxy server to proxy requests to an HTTP server

Hi all,
My configuration is as follows: I have an iPlanet web-server that uses a WebLogic
6.1 (sp1) server to proxy requests to another HTTP server. The HTTP request runs
for 120 seconds. This causes Weblogic to timeout after a while. The error I get
is as follows:
<Aug 25, 2003 3:37:09 PM GMT+00:00> <Warning> <HttpClient> <Couldn't open connection
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:194)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
at weblogic.net.http.HttpClient.New(HttpClient.java:149)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
at com.db.gmr.dcm.DebtIssueServlet.getVectorFromConnection(DebtIssueServle
t.java:285)
at com.db.gmr.dcm.IssuesUSThread.run(IssuesUSThread.java:29)
>
I get the same error when I added the following plug-in configuration parameters
(in obj.conf):
ConnectTimeoutSecs="170" ConnectRetrySecs="170".
What do I need to do to extend this timeout? Any help you can provide will be
greatly appreciated..
Thanks
Manish

Hi all,
My configuration is as follows: I have an iPlanet web-server that uses a WebLogic
6.1 (sp1) server to proxy requests to another HTTP server. The HTTP request runs
for 120 seconds. This causes Weblogic to timeout after a while. The error I get
is as follows:
<Aug 25, 2003 3:37:09 PM GMT+00:00> <Warning> <HttpClient> <Couldn't open connection
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:194)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
at weblogic.net.http.HttpClient.New(HttpClient.java:149)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
at com.db.gmr.dcm.DebtIssueServlet.getVectorFromConnection(DebtIssueServle
t.java:285)
at com.db.gmr.dcm.IssuesUSThread.run(IssuesUSThread.java:29)
>
I get the same error when I added the following plug-in configuration parameters
(in obj.conf):
ConnectTimeoutSecs="170" ConnectRetrySecs="170".
What do I need to do to extend this timeout? Any help you can provide will be
greatly appreciated..
Thanks
Manish

OCS 10.1.2 on Win2003 - mail application cannot start after rebooting serve

Hi
We have installed OCS 10.1.2 on Win2003 (single box) and the mail appln was running OK after the installation. On rebooting the server, we found some components that were not started (eg Internet directory for Infra) which we started manually via EM.
The Mail application however cannot be started giving the error message for all the mail components:
- failed to start a managed process after the maximum retry limit
We tried to start it manually using
- oesctl startup midtierhost:um_system:xxx
and even got the message:
- All processes already started for midtierhost:um_system:xxx
However, in EM, or when doing a
- oesctl show status midtierhost:um_system:xxx, we get the error message:
- midtierhost:um_system:nntp_in:116107583446856959 <no response>
Any idea of where we can check to see what's going wrong? I'm not sure of where to check the logs for possible errors.
Thanks for your assistance

Glad I could be of help - maybe you could help me out too, please? I have the following problem: when I create an appointment with Calendar, and add some participants to it (with email notifications option checked), at first everything seems to go the right way.
But if I delete the appointment/meeting, the following happens:
- the notifications regarding the delete of the meeting are not sent
- the whole mail system seems to hang, and I am not able to send emails anymore
Do you have the same behaviour on your installation? It would be useful to me just to know if other people are having this trouble....
Thank you!

Trace flow is stoped in timer event after reboot server

Hi friends
I have a flow where there are three elements:
The first one is a service task that looks for an event in a database using a database adapter
The second is a gateway, if the event was found, the flow continues otherwise the flow goes to a timer event
Timer event waits for 10 minutes and, after that, returns to the first element (the service task).
The flow has a perfect job, doing a cycle until the field or event in database have been found.
After restart the server in the EM console, the instance's state is running but when i open the trace i can see that the flow is stooped just in the timer event. Timer event only shows "Has been introduced in the activity instance".
Can anyone tell me what's going on?
Thanks

Hi friends
I have a flow where there are three elements:
The first one is a service task that looks for an event in a database using a database adapter
The second is a gateway, if the event was found, the flow continues otherwise the flow goes to a timer event
Timer event waits for 10 minutes and, after that, returns to the first element (the service task).
The flow has a perfect job, doing a cycle until the field or event in database have been found.
After restart the server in the EM console, the instance's state is running but when i open the trace i can see that the flow is stooped just in the timer event. Timer event only shows "Has been introduced in the activity instance".
Can anyone tell me what's going on?
Thanks

Why does connection not reconnect automatically after reboot?

When I had the security set to WPA, the Mac would reconnect automatically when booting. But when using WEP, which I have to with my son's Nintendo DS, I have to go to the Airport menu to choose the network after I boot. In the Network System Preferences, I tried choosing 'Automatic' or 'Preferred networks' but no difference. Any other settings I should check?
Andre
PowerBook 15", 1.67 GHz, 1.5 GIG RAM Mac OS X (10.4.3) G4 QuickSilver 733Mhz, G4 400 Mhz, G3 Desktop

See if this thread might help:
http://discussions.apple.com/thread.jspa?threadID=313041

WRT54G Would connect to internet only after rebooting

Keeps randomly disconnecting from internet. reseting works sometimes, sometimes you have to manual reset ips from provider. today disconected everyone from net and would not come back. It works fine for 1 computer but not others...Help? wont log into 192.168.1.1, wireless wont work. Any suggestions? Thanks!
(Mod note: Edited post for guideline compliance. Thanks!)
Message Edited by JOHNDOE_06 on 12-07-2008 09:44 AM

Don't click on the above link...Instead click here and select the correct version of your router, download the firmware and upgrade it...
Once you are done...reset your router :
1. Press and hold the reset button for 30 seconds.
2. Then, unplug the power keep holding down the reset button for
another 30 Seconds.
3. Plug back the power back in, and keep holding down the reset button
for 30 Seconds.
4. Release the reset button.
5. Re-configure your router.

Oracle 9.0.1 on Solaris/SPARC infinite connection timeouts

Hello, All!
I have the following system configuration:
Solaris 5.9 Maintenance Update 4;
Sun Ultra 10, 1 UltraSPARC IIi 440Mhz CPU, 1024M RAM;
Oracle 9.0.1 (9i Release 1).
The database was created with JServer option turned on (we're using the integrated CORBA functionality); archive log mode is OFF, database cache advice is ON.
In a nutshell,
==============
the problem is in really infinite connection timeouts of Oracle after a long time of inactivity (say, on Monday after two weekend days).
Long description.
=================
Client-side symptoms.
First, I tried to establish a connection to a published CORBA object, and received no response (I am already waiting for 1 hour 40 minutes).
Then, I tried to connect to the database with SQLPlus, remotely:
$ sqlplus /nolog
SQL> CONNECT SYS/change_on_install@ORCL AS SYSDBA;
All the same, I receive no reply. However, the listener is alive, I can establish a network connection to both ports 1521 and 2481. Client-side logs (specified via sqlnet.ora) say the following:
=========== skipped ===========
[09-АВГ-2004 10:27:24:770] nioqsn: entry
[09-АВГ-2004 10:27:24:770] nioqsn: exit
[09-АВГ-2004 10:27:24:770] nioqrc: entry
[09-АВГ-2004 10:27:24:771] nsdo: cid=0, opcode=84, bl=0, what=1, uflgs=0x20, c
[09-АВГ-2004 10:27:24:771] nsdo: rank=64, nsctxrnk=0
[09-АВГ-2004 10:27:24:771] nsdo: nsctx: state=8, flg=0x400d, mvd=0
[09-АВГ-2004 10:27:24:771] nsdo: gtn=127, gtc=127, ptn=10, ptc=2011
[09-АВГ-2004 10:27:24:771] nsdofls: DATA flags: 0x0
[09-АВГ-2004 10:27:24:771] nsdofls: sending NSPTDA packet
[09-АВГ-2004 10:27:24:771] nspsend: plen=770, type=6
[09-АВГ-2004 10:27:24:771] nttwr: entry
[09-АВГ-2004 10:27:24:771] nttwr: socket 12 had bytes written=770
[09-АВГ-2004 10:27:24:771] nttwr: exit
[09-АВГ-2004 10:27:24:771] nspsend: 770 bytes to transport
[09-АВГ-2004 10:27:24:772] nsdo: nsctxrnk=0
[09-АВГ-2004 10:27:24:772] nsdo: cid=0, opcode=85, bl=0, what=0, uflgs=0x0, cf
[09-АВГ-2004 10:27:24:772] nsdo: rank=64, nsctxrnk=0
[09-АВГ-2004 10:27:24:772] nsdo: nsctx: state=8, flg=0x400d, mvd=0
[09-АВГ-2004 10:27:24:772] nsdo: gtn=127, gtc=127, ptn=10, ptc=2011
[09-АВГ-2004 10:27:24:772] nsdo: switching to application buffer
[09-АВГ-2004 10:27:24:772] nsrdr: recving a packet
[09-АВГ-2004 10:27:24:772] nsprecv: reading from transport...
[09-АВГ-2004 10:27:24:772] nttrd: entry
If I try to connect to the database locally, I receive the same result:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA;
-- no reply.
Server-side symptoms.
Oracle logs in ${ORACLE_BASE}/admin/ORCL have no entries referring the last two days. Oracle server debug log (specified via sqlnet.ora) says the following:
========== skipped ===================
nttrd: socket 20 had bytes read=181
nttrd: exit
nsprecv: 181 bytes from transport
nsprecv: tlen=181, plen=181, type=6
nsrdr: got NSPTDA packet
nsrdr: NSPTDA flags: 0x0
nsdo: what=1, bl=2009
nsdo: nsctxrnk=0
nioqrc: exit
nioqsn: entry
nioqrc: entry
nsdo: cid=0, opcode=84, bl=0, what=1, uflgs=0x20, cflgs=0x3
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=8, flg=0x420c, mvd=0
nsdo: gtn=156, gtc=156, ptn=10, ptc=2019
nsdofls: DATA flags: 0x0
nsdofls: sending NSPTDA packet
nspsend: plen=93, type=6
nttwr: entry
nttwr: socket 20 had bytes written=93
nttwr: exit
nspsend: 93 bytes to transport
nsdo: nsctxrnk=0
nsdo: cid=0, opcode=85, bl=0, what=0, uflgs=0x0, cflgs=0x3
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=8, flg=0x420c, mvd=0
nsdo: gtn=156, gtc=156, ptn=10, ptc=2019
nsdo: switching to application buffer
nsrdr: recving a packet
nsprecv: reading from transport...
nttrd: entry
nttrd: socket 20 had bytes read=770
nttrd: exit
nsprecv: 770 bytes from transport
nsprecv: tlen=770, plen=770, type=6
nsrdr: got NSPTDA packet
nsrdr: NSPTDA flags: 0x0
nsdo: what=1, bl=2009
nsdo: nsctxrnk=0
nioqrc: exit
Oracle local client debug log (oracle enterprise manager runs on the same machine) says:
...nsevwait: nsevwait: nsevwait: nsevwait: nsevwait:
nsevwait: nsevwait: nsevwait: nsevwait: nsevwait:
nsevwait: nsevwait: nsevwait: nsevwait: nsevwait: ...
ps -e -o "user,pid,pcpu,pmem,rss,vsz,args" says there're several (3) processes running as oracle, with "args" oracle_ORCL, which eat up nearly all available memory (they have "pmem" values of 25, 25 and 17 per cent, respectively). One of these processes has "pcpu" value varying from 97% to 100%, moreover, this is a user, NOT system time (according to sdtperfmeter, disk/page/swap activity is extremely low; system load holds at value of 4). Here is a sample vmstat output:
cpu
cs us sy id
287 99 1 0
285 100 0 0
280 100 0 0
272 100 0 0
298 98 2 0
275 99 1 0
267 100 0 0
307 97 3 0
282 100 0 0
270 100 0 0
307 98 2 0
287 100 0 0
Here cs is the number of cpu context switches per second;
us is cpu user time;
sy is cpu system time.
The question is: what oracle may be doing and how can I fix the problem?
Thanks in advance.

Now, 3 hours later, the first two (of three) connections got established, but subsequent database queries are in the same nearly dead state.
CPU usage remains about 100%, system load 4.
I know that oracle restart (and/or system restart) will cure the problem -- but only until next weekend.
Can this be oracle misconfiguration?

Tomcat 4.1:connection timeout error

Hi. I got a HTML form that allows a user to enter freehand SQL statements and send them to an DB2 database via a SQL Java servlet. After the query executes, it returns an Excel file containing the resultset of my query. Unfortunately, I got a query that when executed, my browser returns "The page could not be found..." due to connection timeout. With another query with different set of criteria, it runs fine-so my Tomcat is running fine. I've executed the same exact query in Excel via JDBC-ODBC bridge Java application and it ran fine and also executed the same query in QMF for Windows, and it ran fine also. So this lends me to believe I need to configure my Tomcat somehow, I presume the connection timeout limit.
Is there a way to remove or increase the connection timeout limit?
Thanks in advance.

Arrrggg!!! That didn't work. Here's the error message:
"The page cannot be displayed There is a problem with the page you are trying to reach and it cannot be displayed.
Please try the following:
Click the Refresh <javascript:location.reload()> button, or try again later.
Open the home page, and then look for links to the information you want.
If you believe you should be able to view this directory or page, please contact the Web site administrator by using the e-mail address or phone number listed on the home page.
10060 - Connection timeout
Internet Security and Acceleration Server
Technical Information (for support personnel)
Background:
The gateway could not receive a timely response from the Web site you are trying to access. This might indicate that the network is congested, or that the Web site is experiencing technical difficulties.
ISA Server: MMPINF17
Via:
Time: 1/27/2003 1:04:11 PM GMT"
Does this mean my company's firewall administrator has set a connection timeout limit? Or is it still my Tomcat's configuration?

Set HTTP Connection timeout to avoid Deny Of Service attack

Hi,
Is there a way to set a HTTP Connection timeout in Sun Java Application Server Platform Edition ?
I need this because many clients are holding an HTTP Connection too long on my Application Server causing a Deny Of Service because of file descriptor leak.
Regards,
Laurent.

All,
At the application server level, there is a timeout setting in httpd.conf. The default value has been set to 300 seconds.
Regards,
Suhas.

10060 - Connection timeout

Hello,
Please can anyone give me solution for the below error message
10060 - Connection timeout
Internet Security and Acceleration Server
This is regarding MIS report access.Connection failure is thrown while trying to access SAP reports.
Regards,
PKR

Hi PKR,
I'm not sure your question is related to the SAP Internet Transaction Server. You mention a Microsoft product - the Microsoft ISA Server if I understand you correctly. I don't know if many people in this forum are experts on this product. Can you describe your problem more detailed, please?
Best regards
Henning

Acfs not mounted after rebooting..

Hi,
I have create acfs filesystem . but that filesystem is not mounted after rebooting server? how to enable auto mount?
OS version : RHEL 5
Grid Version : 11.2.0.2
ASMCMD> volinfo -G ACFS_U06 ORAHOMEVG
Diskgroup Name: ACFS_U06
Volume Name: ORAHOMEVG
Volume Device: /dev/asm/orahomevg-92
State: ENABLED
Size (MB): 7168
Resize Unit (MB): 256
Redundancy: UNPROT
Stripe Columns: 4
Stripe Width (K): 128
Usage: ACFS
Mountpath: /u06/app/oracle/product/11.2.0.2
Thanks

Register the mount point with acfsutil utility.
oracle@rmdydbitdb1 $ acfsutil registry -h
Usage: acfsutil [-h] registry [-l]                     - Display registry contents
                -l <mountpoint>          - Display a specific mount point
                -l <device>              - Display a specific device
                -m <device>              - Display a specific mount point associated with a device
                -a [-f] [-o <opts>] [-n <nodes>] <device> <mountpoint> - Add a mount point
                -d [<mountpoint> | <device>] - Delete a mount point or a devicehttp://docs.oracle.com/cd/E11882_01/server.112/e18951/asmfs_util010.htm#CACGHBHI
Thanks
Kuljeet Pal Singh

Mac OS 8.6 Auto network connect to a server after reboot is not working

We have multiple old blue and white systems on a network. All but one will automatically connect to the network when rebooted. I have gone into Chooser, Appletalk, put in the server IP address, put in the server password, checked the boxes that say remember Server name and password for next startup. I can connect at that time with no problem. When I reboot, the server does not automatically hook up. I have to go back into Chooser, etc. I created an alias on the desktop, but it still prompts me for a password to connect. I have performed a clean install of the Mac OS 8.6. It still does not connect to the server after reboot (after configuring all the settings again after the clean install). Please help..

Hi,
Thank you for posting in Windows Server Forum.
Can you please create the database manually with below command and verify.
PS C:\> Set-RDConnectionBrokerHighAvailability –DatabaseConnectionString
"DRIVER=SQL Server Native Client 11.0;SERVER=<SQL Server
Name>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;
DATABASE=<DB Name>" -DatabaseFilePath "C:\DbFiles\<DbName>.mdf"
-ClientAccessName "<DNS RR Name>"
Grant DBO permissions to the service account on the RDS server and try to run your wizard again.
More information.
RD Connection Broker High Availability in Windows Server 2012
http://blogs.msdn.com/b/rds/archive/2012/06/27/rd-connection-broker-high-availability-in-windows-server-2012.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

2012 r2 rds deployment cannot connect to sql server after reboot

We have a ha connection broker setup with 2 connection brokers and everything was working fine up untill the servers were rebooted for updates. Now users cannot connect to thier collections and I have an error in the event log that the deployment could not
connect to the sql database.
at this point I am assume that the issue is related to security. I am able to query the database as admin from the effected servers and other services that use other databases in the same sql instance are no5 having issues.
I have checked the security group that both cb servers should be in and they are in the group and the group has sysadmin and dbo within sql
any ideas?
Please remember to mark my replies as answers if they help

Hi,
Thank you for posting in Windows Server Forum.
Can you please create the database manually with below command and verify.
PS C:\> Set-RDConnectionBrokerHighAvailability –DatabaseConnectionString
"DRIVER=SQL Server Native Client 11.0;SERVER=<SQL Server
Name>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;
DATABASE=<DB Name>" -DatabaseFilePath "C:\DbFiles\<DbName>.mdf"
-ClientAccessName "<DNS RR Name>"
Grant DBO permissions to the service account on the RDS server and try to run your wizard again.
More information.
RD Connection Broker High Availability in Windows Server 2012
http://blogs.msdn.com/b/rds/archive/2012/06/27/rd-connection-broker-high-availability-in-windows-server-2012.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Webservice Connection Timeout Error in Sun Java System Application server

I have a java code to connect to Ebay Shopping Webservice that uses the client stub generated through Axis. The code works fine when I run it from the main method of a stand alone Java application. Which means there is no issue with the Proxy settings or any other network setting that could block the webservice from my system. However when I use the same code inside a JSF based Web Application, a connection timeout error comes up. The Web application is deployed on the Sun Java System Application server. The stacktrace of the exception is
java.net.ConnectException: Connection timed out: no further information
     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
     at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:527)
     at com.sun.enterprise.server.ss.provider.ASClientSocketImpl.connect(ASClientSocketImpl.java:206)
     at java.net.Socket.connect(Socket.java:520)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:125)
     at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
     at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.ebay.api.soap.ShoppingBindingStub.findProducts(ShoppingBindingStub.java:1217)
     at com.shopping.ebay.EbayServiceUtility.performEBaySearch(EbayServiceUtility.java:66)
     at searchProduct.SearchProductBean.search(SearchProductBean.java:98)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sun.el.parser.AstValue.invoke(AstValue.java:151)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:96)
     at javax.faces.component.UICommand.broadcast(UICommand.java:383)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:450)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:759)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:113)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
The JDK version on my machine is 1.5.0_14. Can somebody point me as where I should be looking for errors?

You need to delete all the files under the 'generated' directory to force the server to recompile them after the JDK upgrade. Also check in domain.xml and make sure the JVM parameter is pointing to the JDK that you have installed. It is also worthwhile to check asenv.conf to see which JDK that file is pointing to as well.

WebLogic Admin server fails to start after reboot

Hi Gurus,
Weblogic Admin server won't start up after a server reboot. Note that weblogic was gracefully shutdown before the restart.
Also note that the following files were accidentally deleted after the reboot (but I don't think that should cause an issue..):
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
Looking at the AdminServer.log:
*####<Oct 11, 2012 11:27:53 AM EDT> <Critical> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969273846> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: weblogic.management.provider.EditFailedException:*
java.lang.AssertionError: weblogic.management.provider.EditFailedException:
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:79)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: weblogic.management.provider.EditFailedException:
     at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1754)
     at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: org.xml.sax.SAXParseException: Premature end of file.
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
     at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
     at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
     at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
     at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
     at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
     at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:70)
     at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:64)
     at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1917)
     at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1807)
     at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1740)
     at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:81)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:232)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:154)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:26)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274051> <BEA-000365> <Server state changed to FAILED>
####<Oct 11, 2012 11:27:54 AM EDT> <Error> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274053> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274069> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274138> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.domainruntime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274140> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.edit .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274141> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.runtime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274146> <BEA-220028> <Web Service reliable agents are suspended.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274153> <BEA-220029> <Web Service reliable agents are shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <MessagingBridge> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274318> <BEA-200001> <The messaging bridge service has successfully shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274426> <BEA-040308> <JMS service is suspending.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274506> <BEA-040107> <Undeployed 8 default connection factories.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274510> <BEA-040015> <JMS shutdown is complete.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274530> <BEA-001144> <Force Suspending the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274536> <BEA-001146> <Force suspend of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274538> <BEA-001147> <Shutting down the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274552> <BEA-001149> <Shutdown of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274694> <BEA-000236> <Stopping execute threads.>
Kindly guide me with this. Thanks!
Edited by: Kent Pawar. on Oct 11, 2012 8:51 AM

Issue is :
Caused By: weblogic.management.provider.EditFailedException:
One probable reason can be some change made to the config.xml file . If you have previous backup for the config.xml file then try to replace the config.xml file and restart the server .
Another reason for this exception may be that there were some changes made to configuration through the Admin Console which were not activated completely and Admin Server was restarted . under this scenario weblogic will create a /pendig dir and have a config.xml file created there with the un-activated changes .
some workaround you can try to restore the Admin Server :
Under domain dir ,
\pending directory -- take backup and delete the dir .
Under Admin Server Dir :
data\store --- take backup and delete the dir .
thanks,
Sandeep

Connection timeout errn 238 after reboot server invoking Ws

Similar Messages

Maybe you are looking for