EclipseLink-Redeploying a DBWS WS on PL/SQL package after changing return

Question

Issue concerning: EclipseLink 2.4.1 (DBWS) on WebLogic
Hi,
I've created a DBWS webservice based on a Oracle (10g) PL/SQL package, by using EclipseLink DBWS builder. The PL/SQL function exposed as a webservice call has a Object type return type, e.g.:
create or replace type eclipse_type as
object
num number
create or replace package test_eclipselink_pkg as
function test return eclipse_type;
end;
As I understand it, EclipseLink-DBWS translates this Oracle object type to an Java type when calling the PL/SQL function over JDBC and translates the Java object to XML to be encapsulated in a SOAP message.
The problem is that when changing the specification of the return type (e.g. changing the name of the field num to nmb in the Oracle type eclipse_type) of the Oracle PL/SQL function, regenerating the webservice (WAR-file) with DBWS builder and redeploying it on WebLogic 10.3.6, calling the webservice results in a java.lang.reflect.InvocationTargetException.
Restarting the WebLogic server (or the appropriate managed server) resolves the problem, what shouldn't be a problem in a development environment, but is not always possible in a production environment.
The problem seems to be that redeploying the webservice doesn't result in the XR Operations/Queries being recreated and as a result the old result type definition is used.
Has anybody a solution for this problem?
Kind regards,
Jan

Answer 1

Hi,
I checked the logging while redeploying the WAR file. This part of the output seems to indicate, as you suggested, that the EcliipseLink session is not correctly logged of (InstanceAlreadyExistsException):
*** <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, PLUS_WS [archive: P:\WS-I\eclipselink-2.4.0\runtime\eclipselink-2.4.1.v20120712-r11838\eclipselink\utils\dbws\output\PLUS_WS.war], to AdminServer .>
*** <Notice> <Stdout> <BEA-000000> <[EL Warning]: server: 2012-09-03 16:40:16.598--ServerSession(28419523)--Thread(Thread[[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Problem while unregistering MBean: weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: Configuration Action: unregister, Target: null>
*** <Notice> <Stdout> <BEA-000000> <[EL Config]: connection: 2012-09-03
*** <Notice> <Stdout> <BEA-000000> <[EL Info]: connection: 2012-09-03 16:40:16.599--ServerSession(28419523)--Thread(Thread[[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--schapkaarten-dbws-or-session logout successful>
*** <Info> <Deployer> <BEA-149060> <Module PLUS_WS.war of application PLUS_WS successfully transitioned from STATE_PREPARED to STATE_NEW on server AdminServer.>
*** <Notice> <Stdout> <BEA-000000> <[EL Info]: connection: 2012-09-03 16:40:17.07--ServerSession(9455819)--Thread(Thread[[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--schapkaarten-dbws-or-session login successful>
*** <Notice> <Stdout> <BEA-000000> <[EL Warning]: server: 2012-09-03 16:40:17.071--ServerSession(9455819)--Thread(Thread[[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Problem while registering MBean: javax.management.InstanceAlreadyExistsException: TopLink:Name=Development-schapkaarten-dbws-or-session,Type=Configuration>
*** <Notice> <Stdout> <BEA-000000> <[EL Warning]: server: 2012-09-03 16:40:17.071--ServerSession(9455819)--Thread(Thread[[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Problem while registering MBean: javax.management.InstanceAlreadyExistsException: TopLink:Name=Session(schapkaarten-dbws-or-session)>
What I cannot see, is: who is responsible for this logout? This must be clear so I know I have to log a bug for WebLogic or for EclipseLink.
Anyone a suggestion how to determine this?
Thanks,
Jan