• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4301
  • Last Modified:

Ibm websphere Application Server Deployment.....

Hi ,
    I have deplyed an EAR file in WAS6.1 Environment, and i have configured the obj.conf and the ACl file for sun one webserver.

when i am hitting the URL , i could see the page Loading, i mean Loading Sysmbol , after that i see some exceptions displaying in Page :


The System Out Log Shows the Error :

[3/25/10 13:00:42:793 EDT] 0000002d ServletWrappe E   Deregister the mbean because of uncaught init() exception thrown by servlet MessageBrokerServlet: javax.servlet.ServletException: SRVE0207E: Uncaught initialization exception thrown by servlet
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:270)
        at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:319)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:412)
        at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
        at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3440)
        at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
        at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
        at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1461)
        at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:118)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
        at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1037)
        at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:644)
        at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
---- Begin backtrace for Nested Throwables
flex.messaging.config.ConfigurationException: An error occurred trying to construct FlexFactory 'com.citi.gwm.rf.flex.SpringFactory'.   The underlying cause is: 'org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'dataSource' while setting bean property 'dataSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.citi.sps.common.db.BAWebSphereDataSourceAdapter]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: 'targetDataSource' must not be null'.
        at flex.messaging.config.FactorySettings.createFactory(FactorySettings.java:73)
        at flex.messaging.config.MessagingConfiguration.createFactories(MessagingConfiguration.java:94)
        at flex.messaging.config.MessagingConfiguration.configureBroker(MessagingConfiguration.java:81)
        at flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:105)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:218)
        at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:319)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:412)
        at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
        at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3440)
        at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
        at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
        at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1461)
        at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:118)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
        at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1037)
        at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:644)
        at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
,


0
chander72
Asked:
chander72
  • 3
  • 2
1 Solution
 
ponrajk22Commented:
is the Data source is configured properly and is the test connection is successful??

the first exception looks like a code issue.Check with the developer.....
0
 
HonorGodCommented:
The key exception is:

Cannot resolve reference to bean 'dataSource' while setting bean property 'dataSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.citi.sps.common.db.BAWebSphereDataSourceAdapter]:

The application needs to be changed/corrected
0
 
chander72Author Commented:
Yes the Test connection was successfull,


Honor God,
                 Thanks for your help, can you tell me like the application that connections to the mbean needs to be changed right? and  is it in the applicationCreationExceptions ?


as i can see in the above logs .........
0
KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

 
HonorGodCommented:
That would be my expectation.  The error indicates that the attempt to instantiate the dataSource failed.  The most likely reason being that the way the dataSource is configured, or the way the code tries to access it is wrong.
0
 
chander72Author Commented:
thanks your suggestion helped....
0
 
HonorGodCommented:
You are very welcome.  Thanks for the grade & points.

Good luck & have a great day.
0

Featured Post

Managing Security Policy in a Changing Environment

The enterprise network environment is evolving rapidly as companies extend their physical data centers to embrace cloud computing and software-defined networking. This new reality means that the challenge of managing the security policy is much more dynamic and complex.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now