Skip to Main Content

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

listener class not invoked after deploying to weblogic server

Salman5Jul 23 2014 — edited Jul 27 2014

I have a third party class(Quartz Scheduler) which implements ServletContextListener which I have added in my weblogic-application.xml and web.xml files as a listener .This class Should loads certain data during server start up. But is not get invoked.

Technology used:

Jdeveloper 11.1.2.3

Weblogic 10.3.5

Third party Library: Quartz 1.6

Every thing works fine from Jdeveloper and the listener class get invoked when deploying the application in the weblogic with in local machine. But the Listener class is not invoked when deploying application as .ear file in the weblogic server on external server.

Snippet of weblogic-application.xml and web.xml files:

 <listener> <listener-class>scheduler.WebListener</listener-class> </listener>

where scheduler is a packge name and WebListener is the listener class

--------------------Important Updates-----------------------------

The application that I am trying to deploy consist of two project the view and the model projects. For the purpose of testing I remove the model project from the application and deploy the application again. Quartz scheduler is working and the listener class in invoked WORKING without model project and without DB interaction.

I double check the data source with the web-logic nothing seem wrongs to me. I am using the same data source name in the application and as said before the application works from JDeveloper

I also checked the server logs. No exception or error is showing up. just showing that the application is running in Active mode. But the listener class is not called from weblogic when the model project is exists in the application where the DB interaction is occurred.

Any idea what possible cause of this issue

-------------------------------Update 2---------------------------------

I think this update will give clue about the issue. After clouse look to the server log after deploying I found this line.

NewSchedulerApplication-ViewController-context-root has context-root specified in application.xml: "NewSchedulerApplication-ViewController-context-root". The context-root specified in weblogic.xml: "NewSchedulerApplication-ViewController-context-root" will be ignored

where NewSchedulerApplication is the application name.

This post has been answered by Salman5 on Jul 27 2014
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 24 2014
Added on Jul 23 2014
3 comments
701 views