Error in Obtaining Connection
I am getting the following error when trying to access to obtain a connection from the pool with Weblogic 8.1.
java.sql.SQLException: Transaction BEA1-012CEF2BD24F40EF5B94 not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
at weblogic.jdbc.jts.Driver.getTransaction(Driver.java:430)
at weblogic.jdbc.jts.Driver.connect(Driver.java:127)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
The client code which invokes this lookups a datasource and calls getConnection() method on the same.
The method which tries to obtain a connection is initiated from an MDB.
Any help is greatly appreciated
I agree with the previous post.
Here are some of my previous posts that might help. As a general rule, an a MVC design, your JDBC objects (connection, resultSet, preparedStatement) should not be exposed outside of the database layer.
Re: how to connect multiple databases
Re: can not get the right query result using JDBC
Similar Messages
-
Error while obtaining JCO connection when creating JCO connection
Hey,
im having a problem when creating a JCO connection in the Web Dynpro Content Administrator. Creating the Modeldata (Application Data Data type) JCO Worked but when creating the JCO for the RFC Metadata (Dictionary Meta data) there is a problem:
In step 3.2 Msg server connection I cannot specify a system name and logon group, only the message server can be selected with the dropdown box.
After pushing the finish button i get the following stacktrace:
Failed to create new JCO client connection WD_RFC_METADATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at
com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at
com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at
com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at
com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at
com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at
java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_RFC_METADATA_DEST at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more
We are running WebAS 640 SP 14 on Unix.
Greetings,
Hannes
Message was edited by: Hannes DeflooHi
Please configure your SLD. Your SLD holds the system definition. Define a SAP WebAS abap system and then try to create a Metadata connection using WebDynpro content administrator. Now you will be able to see the msg server defined in the dropdown. Also ensure that you have the message server entry in your services file.
Refer these links for SLD
http://help.sap.com/saphelp_nw04/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
Hope that helps.
regards
Ravi -
Error while obtaining JCO connection.
Hi I'm trying to put in place since BW-SEM RSPLAN the transaction, I'm pointing at my portal from the transaction RSPLSA
But when it signs the user gets the message Error while obtaining JCO connection.
I was reviewing my WebDynpro on my site by following these steps:
1 I will http://portal:port
2 I clicked Webdynpro
3 I click on Content Administrator
I clicked on 4 Maintain JCO destinations
and then I log shows the following:
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
... 39 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Version null
DOM version null
Client Type ns7
Client Type Profile nn7
ActiveX disabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0014.20071210061512.0000 (release=645_VAL_REL, buildtime=2007-12-10:05:23:29[UTC], changelist=470565, host=pwdfm101), build date: Wed Oct 01 12:15:02 CDT 2008
J2EE Engine 7.00 patchlevel 109886.44
Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation
Operating system AIX, version: 5.3, architecture: ppc64
Session & Other
Session Locale en_US
Time of Failure Thu Nov 06 16:00:23 CST 2008 (Java Time: 1226008823202)
Web Dynpro Code Generation Infos
sap.com/tcwdtools
No information available null
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:121)
at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:262)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
What should I do??Hi Antonio,
Follow the below note for Jco related troubleshooting.
https://service.sap.com/sap/support/notes/919850
Are you able to see the 4 Jco connections green?
Regards,
Debasis. -
Error in launching guided procedure: Error while obtaining JCO connection.
Hello experts,
we've a problem with webdynpro java calling a guided procedure.
We've defined an endpoint for our callable object, as you can see the test of the connection works fine:
In the configuration of our callable object we use the endpoint above:
And we can test the callable object: it works well, call the right BAPI and find the results.
But when the GP is called and this callable object try to call the BAPI in the background it doesn't work at all.
In the log and trace of the portal we find this:
A technical callable object exception ocurred: Le service RecupActeurs n'a pas pu être exécuté : La connexion pour le nom de connexion SAP_R3_HumanResources n'a pas pu être chargée à partir de System Landscape Directory (SLD) : Error while obtaining JCO connection.
com.sap.caf.eu.gp.model.co.tech.TechnicalCallableObjectException: Le service RecupActeurs n'a pas pu être exécuté : La connexion pour le nom de connexion SAP_R3_HumanResources n'a pas pu être chargée à partir de System Landscape Directory (SLD) : Error while obtaining JCO connection.
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceBackgroundCOContainer.execute(ExternalServiceBackgroundCOContainer.java:101)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor.run(BackgroundCOExecutorImpl.java:126)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl.execute(BackgroundCOExecutorImpl.java:504)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl.execute(BackgroundCOExecutorImpl.java:581)
at com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessorHelper.processAction(BackGroundActionProcessorHelper.java:183)
at com.sap.caf.eu.gp.model.pfw.wfc.local.impl.queue.BackgroundCOQueueProcessor.run(BackgroundCOQueueProcessor.java:263)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.caf.eu.gp.base.exception.EngineException: Connection that belongs to connection name SAP_R3_HumanResources could not be loaded from System Landscape Directory (SLD): Error while obtaining JCO connection.
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.getClientConnection(SLDConnectionManager.java:138)
at com.sap.caf.eu.gp.model.connect.rfc.impl.ConnectionDeliverRFC.analyseConnectionMode(ConnectionDeliverRFC.java:185)
at com.sap.caf.eu.gp.model.connect.rfc.impl.ConnectionDeliverRFC.deliverConnection(ConnectionDeliverRFC.java:91)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SAPSystemConnector.deliverMetaData(SAPSystemConnector.java:116)
at com.sap.caf.eu.gp.model.connect.pvd.saprfc.impl.SAPRFCServiceProvider.executeExternalService(SAPRFCServiceProvider.java:232)
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceManager.executeExternalService(ExternalServiceManager.java:139)
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceBackgroundCOContainer.execute(ExternalServiceBackgroundCOContainer.java:89)
... 9 more
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:160)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.getJCOClientConnection(WDSystemLandscape.java:41)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.resolveClientConnection(SLDConnectionManager.java:169)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.getClientConnection(SLDConnectionManager.java:102)
... 15 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for 'SAP_R3_HumanResources'
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:658)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:485)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:233)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
... 19 more
Caused by: com.sap.tc.webdynpro.services.sal.um.api.WDUMException: No client user defined for the current request (no regular Web Dynpro request as ITask is null.
at com.sap.tc.webdynpro.serverimpl.core.um.AbstractClientUserFactory.getCurrentUser(AbstractClientUserFactory.java:48)
at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.getCurrentUser(WDClientUser.java:67)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:591)
It seems that the GP could not connect to the SLD to call the JCO, but as said before, when we test the callable object, it calls the BAPI without any problem.
We tried to recreat either the JCO and the Endpoint but without success.
Any help will be appreciated.
Thank you.Hi.
Thanks for your answers.
Here are the things :
From the GP administration, the endpoint's test is working.
From the SLD, the JCO is working too.
From the Web Dynpro Content Administrator, the JCO's test is working too.
From the GP Desing Time, the callable object supposed to call the FM uses the right endpoint, and the test is working too, we retreive data from the backend.
From our app, calling the GP process that includes our callable object, we have errors pasted above...
Regards. -
Database Connection Error: Cannot obtain error message from the server
I have a SQL statement that wants to add a temp table to the database. The SQL statement works fine but when I try to add it via 'Add Command' feature in Crystal XI R2, I get the following error message:
Database Connection Error: Cannot obtain error message from the server
Any ideas?
Thanks in advance,
Zack H.Hi Raghavendra,
I am using this in the 'Add Command' feature but I get the error message displayed in the subject line:
CREATE TABLE #TibetanYaks(
YakID char(4),
YakName char(20) )
INSERT INTO #TibetanYaks (YakID, YakName)
SELECT LastName, FirstName
FROM Employee
WHERE EmployeeID between '2000' and '3000'
I haven't tried to add this as a stored procedure but I imagine it will work as I have no problems yet with stored procedures. I simply want to be able to use temporary tables for the sole purpose of that session and not creating anything static in the database.
By the way, even though I get the error message, when I look on the backend database, I see that the temporary table was successfully created...its just not brought across correctly in Crystal.
Any ideas?
Zack H. -
Error while obtaining JCO connection in t-code RSPLAN
Hi Gurus,
I have installed ECC 6.0 SR3 and i have added BI_CONT and updated all the patches. But while trying to access the t-code RSPLAN and after clicking on the START MODELER button it is opening in a browser . after giving the user id and password in the browser , while opening the page it is showing the error " Error while obtaining JCO connection". and how to create jco connections in visual admin.
can anybody please help me in this issue.
Thanks in advance.
Regards,
Babu.Hi,
when i was trying to open RSPLAN T-Code in BI, i able to open start modeller it says that http://udnubd1:8003/sap/public/myssocntl?sap-client=320 and says that cannot find server. So i request you please can anyone help me onthis issue.
Thanks,
Reddy -
TMADMIN_CAT:188: ERROR: Error while obtaining the Bulletin Board parameters
Hi ,everybody
When I created and configured a App server domanin with PSADMIN, these errors below occurred,but log files didn't have useful info:
PeopleSoft Domain Boot Menu
Domain Name: HCMDOM
1) Boot (Serial Boot)
2) Parallel Boot
q) Quit
Command to execute (1-2, q) [q]: 1
Archived a copy of the domain configuration to /appfs/people/opt/PS/PS_CFG_HOME/appserv/HCMDOM/Archive/psappsrv.cfg
Attempting to boot bulletin board...
tmadmin - Copyright (c) 2007-2008 Oracle.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by Oracle.
Tuxedo is a registered trademark.
TMADMIN_CAT:188: ERROR: Error while obtaining the Bulletin Board parameters
==============ERROR!================
Boot attempt encountered errors!. Check the TUXEDO log for details.
==============ERROR!================
Do you wish to see the error messages in the domain log file? (y/n) [n] :y
PSADMIN.23310 (0) [11/30/12 10:58:42](0) Begin boot attempt on domain HCMDOM
PSADMIN.23310 (0) [11/30/12 10:58:42](0) End boot attempt on domain HCMDOM
Do you wish to see the error messages in the Tuxedo log file? (y/n) [n] : y
105842.peoplesoft.ynby.cn!PSADMIN.23310: Begin attempt on domain HCMDOM
105842.peoplesoft.ynby.cn!PSADMIN.23310: End boot attempt on domain HCMDOM
Press Enter to continue...
Don't know how to solve it ...Hi,Nicolas
Before I booted up the app server ,I set the environment variable PS_CFG_HOME to /appfs/people/opt/PS/PS_CFG_HOME,and the above error occured,but when I unset the PS_CFG_HOME,it booted up successfully.But another error occured when booted up :
exec PSMONITORSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 232457 -D TESTSERV -S PSMONITORSRV : Failed.
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
exec tmshutdown -qy
I checked the pemission to boot up app server :
SQL> SELECT CLASSID, STARTAPPSERVER FROM PSCLASSDEFN WHERE CLASSID IN (SELECT OPRCLASS FROM PSOPRCLS WHERE OPRID='PS');
CLASSID STARTAPPSERVER
PSAPPS 1
EOEN9000 1
EOCO9000 1
PTPT1100 1
PTPT1200 1
PTPT1300 1
and update:
SQL> UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE CLASSID='PSAPPS';
1 row updated.
SQL> UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE
CLASSID='EOEN9000';
1 row updated.
SQL> UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE
CLASSID='EOCO9000';
1 row updated.
SQL> UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE CLASSID='PTPT1100';
1 row updated.
SQL> UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE CLASSID='PTPT1200';
1 row updated.
SQL> UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE CLASSID='PTPT1300';
1 row updated.
After doing these,it booted up with the error:
exec PSRENSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -D TESTSERV -S PSRENSRV :
Failed.
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
Then I configured the REN server :
Values for config section - PSRENSRV
log_severity_level=Warning
io_buffer_size=8192
default_http_port=7180
default_https_port=7143
default_auth_token=<my hostname>
Boot up app server again :
Booting server processes ...
exec PSWATCHSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 42933 -D TESTSERV -S PSWATCHSRV :
process id=24245 ... Started.
exec PSAPPSRV -o ./LOGS/stdout -e ./LOGS/stderr [email protected] -- -D TESTSERV -S PSAPPSRV :
process id=24246 ... Started.
exec PSAPPSRV -o ./LOGS/stdout -e ./LOGS/stderr [email protected] -- -D TESTSERV -S PSAPPSRV :
process id=24256 ... Started.
exec PSSAMSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -D TESTSERV -S PSSAMSRV :
process id=24266 ... Started.
exec PSRENSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -D TESTSERV -S PSRENSRV :
process id=24273 ... Started.
exec PSMONITORSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 42933 -D TESTSERV -S PSMONITORSRV :
process id=24279 ... Started.
exec WSL -o ./LOGS/stdout -e ./LOGS/stderr -A -- -n //<my hostname>:7000 -z 0 -Z 0 -I 5 -T 60 -m 1 -M 3 -x 40 -c 5000 -p 7001 -P 7003 :
process id=6834 ... Started.
7 processes started.
Here is my configurations:
OS:RHEL 5.4
DATABASE:ORACLE Database 11.2.0.1
Peoplesoft Tools: 8.52
Application version:HCM 9.1
Domain configuration:
Quick-configure menu -- domain: HCMAPP
Features Settings
========== ==========
1) Pub/Sub Servers : No 16) DBNAME :[PEOPDB]
2) Quick Server : No 17) DBTYPE :[ORACLE]
3) Query Servers : No 18) UserId :[PS]
4) Jolt : No 19) UserPswd :[PS]
5) Jolt Relay : No 20) DomainID :[TESTSERV]
6) WSL : Yes 21) AddToPATH :[.]
7) PC Debugger : No 22) ConnectID :[people]
8) Event Notification: Yes 23) ConnectPswd:[peop1e]
9) MCF Servers : No 24) ServerName :[<my hostname>]
10) Perf Collator : No 25) WSL Port :[7000]
11) Analytic Servers : No 26) JSL Port :[9000]
12) Domains Gateway : No 27) JRAD Port :[9100]
It seems OK,But when I tested the 3-tier connection :
It prompted: Could not connect to appliaction server HCMAPP.possible causes are:the server name/IP address and port for the application server alias are incorrect....
Contect your system administrator to check the Tuxedo log for more information
But I can sign on the database using Application Designer,and app server already booted up.
Additional ,the Tuxedo and Weblogic were installed within different directorys,does it matter?
Do you need more configuration info?
Thanks for you to reply my questions ~ -
Weblogic Server 6.1 SP2 is running fine. But unable to get XAConnections! I am getting following error
java.sql.SQLException: Internal error: Cannot obtain XAConnection Creation of XAConnection for pool ibesXaConnection Pool failed after waitSecs:300
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1063)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:236)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
-GoutamGHi Gautam!
Please make sure your refresh minutes is turned off in config.xml. You should put very large value like 999999 for RefreshMinutes parameter for
defination of connectionpool in config.xml instead of 0.
Thanks,
Mitesh
Goutam wrote:
Weblogic Server 6.1 SP2 is running fine. But unable to get XAConnections! I am getting following error
java.sql.SQLException: Internal error: Cannot obtain XAConnection Creation of XAConnection for pool ibesXaConnection Pool failed after waitSecs:300
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1063)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:236)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
-GoutamG -
Internal error: Cannot obtain XAConnection
I am porting my application from WL8.1-SQl2000 to Sql Server2005. I went in for the Microsoft’s <i><b>MS SQL Server Driver(Type 4 XA) Versions:2000</b></i> and the corresponding one for non-XA also. Then in the next step where we usually give the other DB properties like DB name, server name etc, there is a field called “Properties†which defines the basic properties which we have configured. In that field, there is a new property having name-value pair : dataSourceName=SQL2000JDBC. I am not sure what this would do, so I just left it to remain & continued with the other things.
This, in no way affected the proper execution of my application.
I have 1 XA datasource & 3 non-XA datasources configured for my application.
When I start my server, in the comman prompt, a resource limit exception appears & then the server proceeds to start successfully. I am also abe to save things into the DB & do all other tests properly. But this keeps hindering me. Our DB server is configured to accept infinite connections, so its absurd to get a connection not available exception.
I doubt whether the initial datasource property that I have mentioned can have anything to do with this exception during startup. Please help me.
Exception trace:
<Nov 15, 2006 12:29:34 PM EST> <Warning> <JDBC> <BEA-001064> <Ignoring property
'enableTwoPhaseCommit' for JDBCTxDataSource "TweDS". This property is used only
for those drivers that do not natively support XA.>
java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.commo
n.resourcepool.ResourceLimitException: No resources currently available in pool
ITestPool to allocate to applications, please increase the size of the pool and
retry..
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
315)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:305)
at com.taxware.twe.util.SQLConnection.getConnection(SQLConnection.java:1
68)
at com.taxware.twe.audit.AuditStartUp.main(AuditStartUp.java:333)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.j
ava:229)
at
weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.
java:160)
at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.j
ava:36)charu s wrote:
I am porting my application from WL8.1-SQl2000 to Sql Server2005. I went in for the Microsoft???
s <i><b>MS SQL Server Driver(Type 4 XA) Versions:2000</b></i> and the corresponding one for non-XA also. Then in the next step where we usually give the other DB properties like DB name, server name etc, there is a field called ???Properties??? which defines the basic properties which we have configured. In that field, there is a new property having name-value pair : dataSourceName=SQL2000JDBC. I am not sure w
hat this would do, so I just left it to remain & continued with the other things.
This, in no way affected the proper execution of my application.
I have 1 XA datasource & 3 non-XA datasources configured for my application.
When I start my server, in the comman prompt, a resource limit exception appears & then the server proceeds to start successfully. I am also abe to save things into the DB & do all other tests properly. But this keeps hindering me. Our DB server is configured to accept infinite connections, so its absurd to get a connection not available exception.
I doubt whether the initial datasource property that I have mentioned can have anything to do with this exception during startup. Please help me.
The pool's max capacity is defined as lower than the need at
the time. Please show me the full pool definition from the
config.xml. It may also have something to do with the fact
that your code is a startup class, and are you sure the
pool is ready at this time?
Joe
Exception trace:
<Nov 15, 2006 12:29:34 PM EST> <Warning> <JDBC> <BEA-001064> <Ignoring property
'enableTwoPhaseCommit' for JDBCTxDataSource "TweDS". This property is used only
for those drivers that do not natively support XA.>
java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.commo
n.resourcepool.ResourceLimitException: No resources currently available in pool
ITestPool to allocate to applications, please increase the size of the pool and
retry..
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
315)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:305)
at com.taxware.twe.util.SQLConnection.getConnection(SQLConnection.java:1
68)
at com.taxware.twe.audit.AuditStartUp.main(AuditStartUp.java:333)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.j
ava:229)
at
weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.
java:160)
at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.j
ava:36) -
Java.sql.SQLException: Internal error: Cannot obtain XAConnection
Hi,
I am getting this error .
I have a multi data source which serves two Data source and is using load balancing
I get the below error:
Cannot obtain XAConnection weblogic.common.ResourceException: No good connections available.
The complete error trace is below:
GWMDBBean [onMessage(Message)] 09_MAY 16:24:13:165->EXCEPTION
java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.common.ResourceException: No good connections available.
at weblogic.jdbc.common.internal.MultiPool.findPool(MultiPool.java:187)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:87)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1514)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1301)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:426)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:383)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:346)
at com.iflex.fcubs.gwutil.db.GWDBUtil.getConnection(GWDBUtil.java:119)
at com.iflex.fcubs.gwservices.db.GWMsgProcessor.getConnection(GWMsgProcessor.java:95)
at com.iflex.fcubs.gwservices.db.inbound.GWMsgSchemaProc.processMsg(GWMsgSchemaProc.java:165)
at com.iflex.fcubs.gw.mdb.GWMDBBean.processMessage(GWMDBBean.java:1051)
at com.iflex.fcubs.gw.mdb.GWMDBBean.onMessage(GWMDBBean.java:371)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:245)
at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:121)
at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:204)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at com.iflex.fcubs.gw.mdb.GWMDBBean.processMessage(GWMDBBean.java:1060)
at com.iflex.fcubs.gw.mdb.GWMDBBean.onMessage(GWMDBBean.java:371)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:245)
at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:121)
at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:204)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
The Data Sources Configuration are as below:
<initial-capacity>15</initial-capacity>
<max-capacity>15</max-capacity>This indicates that none of your datasources have been able to successfully connect to the database.
Please check the connectivity to your database from the datasources.
Also, you can login into the console and check if the connections are good, by doing test connection on the datasource.
http://docs.oracle.com/cd/E21764_01/apirefs.1111/e13952/taskhelp/jdbc/jdbc_datasources/TestDataSources.html
The error you get when you do test connection will help you to understand any connectivity issues.
Arun -
Using Weblogic Platform 7.0 (installed from platform700_win32.exe),
Running a BPM Doamin(WLIDomain with BPM only).
When I try to access my entity bean(CMP), the following exception is getting thrown.
I have seen a similar post in here, but the answer to that post, which says to
provide ACL. does not apply quite well my scenario.
To do this, I right clicked on the connection pool and selected define Ploicy..
It shows two options
RealmAdapterAuthorizer and DefaultAuthorizer; On DefaultAuthroizer i specified
role accessing the resource would be "everyone". - restarted the server - but
still the same error.
Please suggest a solution if any. Do i have to get some service pack for this?
TIA
Ranjith.We have never seen a case yet where this was not a permissions problem.
Do you have a fileRealm.properties file as part of your configuration?
"Ranjith" <[email protected]> wrote in message
news:3f0fdeb3$[email protected]..
>
java.sql.SQLException: Cannot obtain connection after 3600 seconds. ,Exception
= Access not allowed
java.sql.SQLException: Cannot obtain connection after 3600 seconds. ,Exception
= Access not allowed
atweblogic.jdbc.jts.Connection.wrapAndThrowSQLException(Connection.java:701)
atweblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:623)
atweblogic.jdbc.jts.Connection.prepareStatement(Connection.java:133)
atweblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
va:139)
atweblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:81
atservice.samplemgt.v1_0.ejb.entity.BanksampletypeCMP_ckv0ao__WebLogic_CMP_RDB
MS.ej
bFindAll(BanksampletypeCMP_ckv0ao__WebLogic_CMP_RDBMS.java:873)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.collectionFinder(RDBMSPersi
stenceManager
java:300)
atweblogic.ejb20.manager.BaseEntityManager.collectionFinder(BaseEntityManager.
java:715)
atweblogic.ejb20.manager.BaseEntityManager.collectionFinder(BaseEntityManager.
java:688)
atweblogic.ejb20.internal.EntityEJBLocalHome.finder(EntityEJBLocalHome.java:47
6)
at ... -
Cockpit doesnu0092t work (SAP AII 4.0) - Error in JCO connection
Hi all,
After some days working with the "Cockpit" in AII 4.0, today we can not access to it and we dont know why.
When we execute the transaction /AIN/DTUIURL - Auto-ID Cockpit, we do logon and after that it appears the error:
"Failed to process the request. Please contact your system administrator. Pressing on Show Details, in Error stacktrace we can see the following:
"com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.ain.model.utility.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection."
In fact, we have the same problem (an error in JCO connection) when IDOCs try to be sent from R3 to AII or vice versa. We can see in transaction sxmb_moni of XI system this error.
Does anybody know where the problem could be?
Thanks in advance,
XavierHi,
Thank you for this question. What you are reporting looks to me like a bug. The channel for such questions is the Service Marketplace http://service.sap.com/. Please post it there.
Best regards,
Steve -
Could not obtain connection to the central environment.
Hi,
I have just started using iSetup on 11.5.10.2.
Initially I intend to use the same instance as source and central one.My understanding is that Source,Central and Target Instance are more of logical grouping and the same instance can be mapped for all the three.
I have mapped the instance that I am using as Source Instance and after that I try to run an Extract.The report is ending with error "Could not obtain connection to the central environment".
Kindly guide on what needs to be done to map the same instance as Source,Central and Target.
Do i need to map in thrice?
Regards
VikasFind Below the Requested Sh run outputs
ADSL-ROUTER1#sh run | beg line vty
line vty 0 4
password 7 ***********
login
scheduler max-task-time 5000
end
I have removed the IP for security reasons
ADSL-ROUTER1#sh ip route
Gateway of last resort is 0.0.0.0 to network 0.0.0.0
x.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
S x.x.x.x/29 is directly connected, Vlan1
C x.x.x.x/32 is directly connected, Dialer0
x.0.0.0/32 is subnetted, 1 subnets
C x.x.x.x is directly connected, Dialer0
S* 0.0.0.0/0 is directly connected, Dialer0
I also keep getting the message below on the console done know if this is part of the problem
Mar 13 07:17:32.213: %IP_VFR-4-FRAG_TABLE_OVERFLOW: Vlan1: the fragment table h
as reached its maximum threshold 16
Hope this output helps
Thanks -
Database Connector error: 'cannot obtain error message from server'
I am using Oracle stored procedures and I have used IN parameters for input and INOUT parameter of REF_CURSOR TYPE for returning resultset in Crystal Report 2008 by using package. Now when I am trying to add the package in the Crystal Report, parameter input box prompts, I enter some values and gets Database Connector error: 'cannot obtain error message from server'.
But when I do not use INPUT parameters and use OUT parameter of REF_CURSOR type it runs well without any issues.
We are using ODBC connection for Oracle.
Kindly suggest.Hello,
Search the Knowledge Base for "oracle store procedures" and you'll find a document on how to write a SP so CR can use them.
Thank you
Don -
Hi Guys,
I need some help, I've already set up my datasource. It was working when i had only 1 EJB module.
But when i added another ejb module to be loaded. I started having this kind of problem:
##<Oct 11, 2007 9:07:17 AM GMT+08:00> <Error> <Deployer> <djao> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1192064837780> <BEA-149231> <Unable to set the activation state to true for the application 'Test.ear'.
weblogic.application.ModuleException: Exception activating module: EJBModule(MyEntityEJBs.jar)
Unable to deploy EJB: MyEntity from MyEntityEJBs.jar:
Cannot obtain connection after 30 seconds. : java.sql.SQLException: Data Source jdbc/DataSource does not exist.
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:422)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:352)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Cannot obtain connection after 30 seconds. : java.sql.SQLException: Data Source jdbc/DataSource does not exist. NestedException Message is :Cannot obtain connection after 30 seconds. : java.sql.SQLException: Data Source jdbc/DataSource does not exist.
at weblogic.ejb.container.cmp11.rdbms.PersistenceManagerImpl.verifyDatabaseType(PersistenceManagerImpl.java:251)
at weblogic.ejb.container.cmp11.rdbms.PersistenceManagerImpl.setup(PersistenceManagerImpl.java:148)
at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:295)
at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:244)
at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1379)
at weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:232)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1270)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:405)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:352)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Can anyone help me with this pls? Im sure that my datasource exist, I could even test the connection in the admin console.
DanielAre you sure you have your datasource in place? You can test connection pools, but not datasources.
Maybe you are looking for
-
How to install windows 8 onto an external hard drive connected with usb 2.0?
How to install windows 8 onto an external hard drive connected with usb 2.0?
-
When a C/Pro*C program makes a core file after core dumped, what is the significance of this file. How can I make sense of the reason the core dump occurred. That is, understand the error because of which the core dump occurred. Regards Krishnan
-
Usage of the xml string get from xsql
I can retrieve a string of xml from database like: <rowset> <row num="1"> <xml_string> <test>value1</test><test>value2</test> </xml_string> </row> </rowset> whereas xml_string is the fieldname and under <xml_string> is the field value. Question is I
-
IDOC Message type suitable for VA32
Hi, I am trying to investigate the automation of transaction VA32, "Change Schedule agreement ". Information relating to my updates from the customer are now available in an electronic format. I therefore wish to now automate this time consuming job
-
hi, recently purchased a x7. But i have issues on touch screen. Some options are not sensable for touch. Pls help.