This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 140212 - GlassFish must be restarted after Bpel deployment
Summary: GlassFish must be restarted after Bpel deployment
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-16 07:50 UTC by siitpe
Modified: 2009-01-14 22:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description siitpe 2008-07-16 07:50:10 UTC
Using NB 6.1 patch2:
Create simple Bpel with first invoke to SQL se and second invoke to XSLT se.
Create Composite project and deploy. 
When test is run Bpel returns following error:
    <SOAP-ENV:Fault>
      <faultcode xmlns="">SOAP-ENV:Server</faultcode>
      <faultstring xmlns="">java.lang.Exception: Processing Error. Fault Name is
{http://sun.com/wsbpel/2.0/process/executable/fault}systemFault and Fault Value is
{http://sun.com/wsbpel/2.0/process/executable/fault}systemFault</faultstring>
      <faultactor xmlns="">sun-http-bc</faultactor>
    </SOAP-ENV:Fault>

Glassfish log reads error "Failed to send InOut message" at first invoke to SQL engine. 

Restart GlassFish.
Run Bpel again and works OK and every time since restart.
Same failure occurs with Sun Java System Application Server 9.1 update 2, too.
Comment 1 Sergey Lunegov 2008-10-01 14:30:25 UTC
Kir, please take a look.
Comment 2 Kirill Sorokin 2008-11-19 19:34:00 UTC
There've been several issues wrt the need to restart glassfish, which ended up in compapp. Reassigning there for evaluation.
Comment 3 Tientien Li 2009-01-14 22:21:51 UTC
This is not a compapp issue.. reassigned to bpel project/SE