Bug 777980 (SOA-509) - exceptions by shutdown (CP01)
Summary: exceptions by shutdown (CP01)
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-509
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Deployment
Version: 4.2 CP01
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3 GA
Assignee: nwallace
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-09 09:17 UTC by Aleksandar Kostadinov
Modified: 2013-01-11 02:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/jboss-soa-platform-win-scripts
Last Closed: 2008-12-15 13:30:49 UTC
Type: Bug


Attachments (Terms of Use)
server.log.gz (262.26 KB, application/x-gzip)
2008-04-09 09:19 UTC, Aleksandar Kostadinov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778378 0 medium CLOSED exceptions by shutdown (CP01) 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-509 0 None None None Never

Internal Links: 778378

Description Aleksandar Kostadinov 2008-04-09 09:17:55 UTC
Date of First Response: 2008-04-09 08:37:48
project_key: SOA

I see exceptions when shutting down SOA-P servers. Two of them:

2008-04-08 09:23:49,894 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Unable to retrieve orbjavax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered.
-----
2008-04-08 09:25:11,240 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[127.0.0.1:4457] caught exception in run()
java.net.SocketException: socket closed
	at java.net.PlainSocketImpl.socketAccept(Native Method)
	at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
	at java.net.ServerSocket.implAccept(ServerSocket.java:450)
	at java.net.ServerSocket.accept(ServerSocket.java:421)
	at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
	at java.lang.Thread.run(Thread.java:595)
-----

Comment 1 Aleksandar Kostadinov 2008-04-09 09:19:50 UTC
Attachment: Added: server.log.gz


Comment 2 Jehudi Castro Sierra 2008-04-09 12:37:48 UTC
On Linux there is the same exception SocketException and an other one (org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-68])

Comment 3 Len DiMaggio 2008-04-09 18:16:44 UTC
FYI - the GA bits also show this error:

2008-04-09 14:12:20,894 ERROR [org.hibernate.util.JDBCExceptionReporter] Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-66]
2008-04-09 14:12:20,894 ERROR [org.jbpm.db.JobSession] org.hibernate.exception.GenericJDBCException: could not execute query
2008-04-09 14:12:20,902 ERROR [org.jbpm.svc.Services] problem closing service 'persistence'
2008-04-09 14:12:20,902 ERROR [org.jbpm.job.executor.JobExecutorThread] exception in job executor thread. waiting 5000 milliseconds



Comment 4 Len DiMaggio 2008-05-09 18:14:48 UTC
Link: Added: This issue depends JBESB-1712


Comment 5 Len DiMaggio 2008-05-09 18:15:47 UTC
Link: Removed: This issue depends JBESB-1712 


Comment 6 Len DiMaggio 2008-05-09 18:15:58 UTC
Link: Added: This issue is related to JBESB-1712


Comment 7 Kevin Conner 2008-05-13 13:28:36 UTC
Link: Removed: This issue is related to JBESB-1712 


Comment 8 Len DiMaggio 2008-05-29 14:09:22 UTC
Link: Added: This issue is a dependency of JBESB-1777


Comment 9 Aleksandar Kostadinov 2008-08-26 11:21:34 UTC
As I reported the issue, the exception is thrown in DEBUG mode and AFAICT it is not really an issue.
Len reported a ERROR level exception that I don't see with the current IR2 bits. Should that be closed?

Comment 10 nwallace 2008-09-25 20:02:10 UTC
Link: Added: This issue related SOA-861


Comment 11 nwallace 2008-12-15 13:25:26 UTC
I've re-opened 509 as it's the original that 861 was cloned from. (861 having been re-opened)
Currently looking for a JBoss Remoting contact as ESB problem is fixed and the tomcat problem is not fixable. 

Comment 12 nwallace 2008-12-15 13:30:49 UTC
Shouldn't have re-opened this. Thought it's fix version was CP01. Sorry.


Note You need to log in before you can comment on or make changes to this bug.