Wrapper connection for jboss exception
Hi
The url below says how to extract a Oracle type Connection from JBOSS Wrapper
"http://forums.oracle.com/forums/thread.jspa?messageID=1384788 "
No problem is getting the connection, but Do Not know hoe to close the same for the obtained
connection to be returned
Exception : "CAN'T CLOSE CONNECTION FOR POOL " is thrown ?
The code is as given below
* To get a connection
private WrappedConnection WCP = null;
public synchronized Connection getConnection() {
Connection conn = null;
OracleConnection connection;
try {
WCP = (WrappedConnection) ODS.getConnection();
connection = (OracleConnection) WCP.getUnderlyingConnection();
} catch (SQLException sqlex) {
System.out.println("<<<<<<<<<<< NO CONNECTION>>>>>>>>>>>>");
//sqlex.printStackTrace();
return conn;
* Return the Connection to Connectioon pool
public synchronized void freeConnection(Connection con) throws Exception {
System.out.println("RELEASING THE USED CONNECTION TO POOL");
try {
con.close();
}catch (Exception ex) {
System.out.println("CAN'T CLOSE CONNECTION FOR POOL ");
ex.printStackTrace();
Any help would be appreciated
SPEC
JBOSS 4.2.1
ORACLE DB : 10G DB
jar : ojdbc14.jar
j2sdk 1.4 for development
j2sdk1.6 for jboss runtime
with regards
Karthik
Edited by: user6161490 on Nov 25, 2008 8:40 PM
Well, it would be good if you showed us what exception was printed out when
you failed to close 'con'... Also, your getConnection() seems to return an unset
variable, not what you unwrapped.... And if you put the WCP variable in the
method, it won't have to be synchronized...
Edited by: [email protected] on Nov 26, 2008 8:22 AM
Similar Messages
-
Hi all!
In a simple two node cluster (Solaris cluster 3.2) with quorum server I've created a resource for jboss 5.1.0 using SUNW.gds. It is supposed to be load-balanced. To achieve that I've followed instructions from [http://download.oracle.com/docs/cd/E18728_01/html/821-1258/gds-25.html]
The command I've used to create the resource was:
clresource create -g scalable-rg -t SUNW.gds -p resource_dependencies=vip -p Scalable=TRUE -p Start_timeout=400 -p Stop_timeout=400 -p Probe_timeout=30 -p Port_list=8080/tcp -p Start_command="/opt/jboss-5.1.0.GA/bin/run.sh -b 0.0.0.0" -p Child_mon_level=0 -p Failover_enabled=TRUE -p Stop_signal=15 -p Load_balancing_policy=LB_STICKY_WILD jboss-rs
The whole configuration seems to work, but when the second node joins cluster, resource with jboss can't bind to shared ip address. There are many entries in /var/adm/messages like:
Jan 19 13:46:35 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:35 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
Jan 19 13:46:37 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:37 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
Jan 19 13:46:39 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:39 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
Jan 19 13:46:41 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:41 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
Jan 19 13:46:43 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:43 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
However, after some time, it finally somehow binds to shared ip and port 8080.
Is this something I should be worried about? Or it is a normal thing, since e.g. it takes some time to bring the interface with shared ip up? I've never had to install such configuration, and I don't have neither intuiton, nor the experience. Any help would be very appreciated.
Thanks a bunch,
BartHi, a couple of things to check:
- did you check that both JBOSS instances were up and running?
- can you check in the logs (on both nodes) when a message saying something like "service .... registered..." showed up. This should show up for both JBOSS instances. From the time of the second "registered" message, the load balancer should sending incoming requests to both instances using its distribution mechanism
- did you check the vip address on one of the nodes on an external interface and on lo0 on the other
- connection refused looks like a server problem; can you connect to the JBOSS instance locally?
Hth
Hartmut -
Hi,
I am using ant tasks wlserver and wlconfig to configure my weblogic server. while creating a connection pool as shown below
<target name="jdbcinfo">
<wlconfig password="weblogic"
username="weblogic"
url="${url}"
<query domain="mydomain" type="Server"
name="myserver" property="serverbean"
/>
<create type="JDBCConnectionPool"
name="jdbcpoolA"
property="jdbcPoolProp">
<set value="false"
attribute="ShrinkingEnabled"
<set value
attribute="
<set value="${serverbean}"
attribute="Targets"/>
The JDBCConnectionPool is created as long as I don't specified the attribute "Targets"
Once I add the target I get the following error
<JDBC> <BEA-001129> <Received exception while creating connection for pool "poolname" invalid arguments in call>
Please any help will be greatly appreciated.
ThanksIn your applicaion module configurations check if you are using 'JDBC URL' or 'JDBC DataSource'. You should use JDBC DataSource. Then make sure that your deployment descriptor (menu 'Application->Application Properties->Deployment) has the 'Auto Generate ...' checkbox set.
Timo -
[JTA_Start_0]Exception getting connection for Oracle DB
Hi All,
I am facing a problem when I am going to insert data in a table (Oracle DB) using JTA Command Action block. I have deployed the Oracle JDBC driver and Configured the data source in http://<server<:port>>/nwa->Configuration Management -> Infrastructure. But when I am trying to insert data using the JTA Command Action block for inserting data in a table it is throwing error.I am running with XMII 12.1 SP5 and Oracle 11g.
Here is the error details.
[ERROR] [JTA_Start_0]Exception getting connection for jdbc/ODS_ORACLE_SBX was ResourceException occurred in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 0 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine) or they are allocated from a non transactional ConnectionFactory. In case of transactional ConnectionFactory used from Application Thread there is an automatic mechanism which detects unclosed connections, 2)The pool size of adapter "ODS_ORACLE_SBX" is not enough according to the current load of the system . In case 1) the solution is to check for cached connections using the Connector Service list_conns command or in case 2), to increase the size of the pool.
Note: ODS_ORACLE_SBX is the Data source name which I have configured.
If I increase the min pool size from 0 to 5 or more than 0 then Data source is getting red means not Available.
Can anybody provide any help.
Thanks in advance
Chandan
Edited by: Chandan Jash on May 3, 2011 4:25 AMYou set up your Oracle DB connection by following the path 'xMII Menu -> Data Services -> Data Servers -> New'.
Re: Configure Oracle in MII 12.0
Regards,
Chanti. -
Getting Error:closing a connection for you. Please help
Hello All,
I'm using jboss3.2.6. I used ejb2.1 (session bean and entity bean[BMP]). I did few data base transations in cmp and few in simple data source connection.
I'm getting below errors occasionally
'No managed connection exception
java.lang.OutOfMemoryError: Java heap space
[CachedConnectionManager] Closing a connection for you. Plea
se close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@11ed0d
5
I've given below my dao connection code here,
package com.drtrack.util;
import java.sql.Connection;
import java.sql.SQLException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
public class DAOUtil {
private static DataSource _ds;
public Connection con;
public DAOUtil() throws SQLException {
try {
if (_ds == null)
assemble();
if(_ds != null && con == null) {
con = _ds.getConnection();
}catch(SQLException ex) {
ex.printStackTrace();
private void assemble() {
Context ic = null;
try {
ic = new InitialContext();
DrTrackUtil drutil = new DrTrackUtil();
_ds = (DataSource) ic.lookup("java:/" + drutil.getText("SOURCE_DIR"));
drutil = null;
}catch (Exception e) {
e.printStackTrace();
}finally {
try {
ic.close();
}catch(NamingException ne) {}
public void closeConnection() throws SQLException {
if(con != null)
con.close();
con = null;
}below is the code with get connection and doing transaction in it.
public static AccountMasterValueBean getAccountMasterByAcctId(String acctId) {
AccountMasterValueBean bean = null;
DAOUtil dao = null;
CallableStatement cst = null;
ResultSet rs = null;
try {
dao = new DAOUtil();
cst = dao.con.prepareCall(DrTrackConstants.MSSQL_USP_ACCOUNTMASTER_BY_ACCTID);
cst.setObject(1, acctId);
rs = cst.executeQuery();
if(rs != null && rs.next()) {
bean = new AccountMasterValueBean(
Integer.valueOf(rs.getString("accountkeyid")),
rs.getString("latitude"),
rs.getString("longitude"));
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
if(rs != null){
try {
rs.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
rs = null;
if(cst != null) {
try{
cst.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
cst = null;
if(dao != null) {
try {
dao.closeConnection();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
dao = null;
return bean;
}I closed connections, resultsets and statements properly.
Why I'm getting these errors.? Where I'm doing wrong. ? Please help me. I have to fix them ASAP.
Thanks.Hello All,
I'm using jboss3.2.6. I used ejb2.1 (session bean and entity bean[BMP]). I did few data base transations in cmp and few in simple data source connection.
I'm getting below errors occasionally
'No managed connection exception
java.lang.OutOfMemoryError: Java heap space
[CachedConnectionManager] Closing a connection for you. Plea
se close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@11ed0d
5
I've given below my dao connection code here,
package com.drtrack.util;
import java.sql.Connection;
import java.sql.SQLException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
public class DAOUtil {
private static DataSource _ds;
public Connection con;
public DAOUtil() throws SQLException {
try {
if (_ds == null)
assemble();
if(_ds != null && con == null) {
con = _ds.getConnection();
}catch(SQLException ex) {
ex.printStackTrace();
private void assemble() {
Context ic = null;
try {
ic = new InitialContext();
DrTrackUtil drutil = new DrTrackUtil();
_ds = (DataSource) ic.lookup("java:/" + drutil.getText("SOURCE_DIR"));
drutil = null;
}catch (Exception e) {
e.printStackTrace();
}finally {
try {
ic.close();
}catch(NamingException ne) {}
public void closeConnection() throws SQLException {
if(con != null)
con.close();
con = null;
}below is the code with get connection and doing transaction in it.
public static AccountMasterValueBean getAccountMasterByAcctId(String acctId) {
AccountMasterValueBean bean = null;
DAOUtil dao = null;
CallableStatement cst = null;
ResultSet rs = null;
try {
dao = new DAOUtil();
cst = dao.con.prepareCall(DrTrackConstants.MSSQL_USP_ACCOUNTMASTER_BY_ACCTID);
cst.setObject(1, acctId);
rs = cst.executeQuery();
if(rs != null && rs.next()) {
bean = new AccountMasterValueBean(
Integer.valueOf(rs.getString("accountkeyid")),
rs.getString("latitude"),
rs.getString("longitude"));
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
if(rs != null){
try {
rs.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
rs = null;
if(cst != null) {
try{
cst.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
cst = null;
if(dao != null) {
try {
dao.closeConnection();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
dao = null;
return bean;
}I closed connections, resultsets and statements properly.
Why I'm getting these errors.? Where I'm doing wrong. ? Please help me. I have to fix them ASAP.
Thanks. -
Error allocating PM connection in jboss
Hi
Running beta 4 I get this error when attempting to get persistence manager
connection from jboss.
10:28:28,340 ERROR [STDERR] javax.ejb.EJBException: An Exception occured
when at tempting to lookup and call the
RepositoryManagerjavax.transaction.TransactionRolledbackException: An
Exception occured when attempting to allocate a PersistenceManager
connection: javax.naming.NamingException: Could not dereference object
[Root exception is java.lang.IllegalAccessException: Class
javax.naming.spi.NamingManager can not access a member of class
com.solarmetric.kodo.impl.jdbc.ee.JDOObjectFactory with modifiers ""];
nested exception is:
javax.ejb.EJBException: An Exception occured when attempting to
allocate a PersistenceManager connection: javax.naming.NamingException:
Could not dereference object [Root exception is
java.lang.IllegalAccessException: Class javax.naming.spi.NamingManager can
not access a member of class
com.solarmetric.kodo.impl.jdbc.ee.JDOObjectFactory with modifiers ""]
It worked fine with the older beta version.
Any ideas?
Regards
JesperDid you install "Oracle Developer Tools for Visual Studio 11.2.0.3.60"? ODP.NET is not enough.
-
How do I set miminum # of connections for pool with Oracle and Tomcat?
Hi,
I can't seem to find any attribute to initialize the number of connections for my connection pool. Here is my current context.xml file under my /App1 directory:
<Context path="/App1" docBase="App1"
debug="5" reloadable="true" crossContext="true">
<Resource name="App1ConnectionPool" auth="Container"
type="oracle.jdbc.pool.OracleDataSource"
driverClassName="oracle.jdbc.driver.OracleDriver"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="jdbc:oracle:thin:@127.0.0.1:1521:oddjob"
user="app1" password="app1" />
</Context>
I've been googling and reading forums, but haven't found a way to establish the minimum number of connections. I've tried all sorts of parameters like InitialLimit, MinLimit, MinActive, etc, with no success.
Here is some sample code that I am testing:
package web;
import oracle.jdbc.pool.OracleDataSource;
import oracle.jdbc.OracleConnection;
import javax.naming.*;
import java.sql.SQLException;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
public class ConnectionPool {
String message = "Not Connected";
public void init() {
OracleConnection conn = null;
ResultSet rst = null;
Statement stmt = null;
try {
Context initContext = new InitialContext();
Context envContext = (Context) initContext.lookup("java:/comp/env");
OracleDataSource ds = (OracleDataSource) envContext.lookup("App1ConnectionPool");
message = "Here.";
String user = ds.getUser();
if (envContext == null)
throw new Exception("Error: No Context");
if (ds == null)
throw new Exception("Error: No DataSource");
if (ds != null) {
message = "Trying to connect...";
conn = (OracleConnection) ds.getConnection();
Properties prop = new Properties();
prop.put("PROXY_USER_NAME", "adavey/xxx");
if (conn != null) {
message = "Got Connection " + conn.toString() + ", ";
conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME,prop);
stmt = conn.createStatement();
rst = stmt.executeQuery("SELECT username, server from v$session where username is not null");
while (rst.next()) {
message = "DS User: " + user + "; DB User: " + rst.getString(1) + "; Server: " + rst.getString(2);
rst.close();
rst = null;
stmt.close();
stmt = null;
conn.close(); // Return to connection pool
conn = null; // Make sure we don't close it twice
} catch (Exception e) {
e.printStackTrace();
} finally {
// Always make sure result sets and statements are closed,
// and the connection is returned to the pool
if (rst != null) {
try {
rst.close();
} catch (SQLException e) {
rst = null;
if (stmt != null) {
try {
stmt.close();
} catch (SQLException e) {
stmt = null;
if (conn != null) {
try {
conn.close();
} catch (SQLException e) {
conn = null;
public String getMessage() {
return message;
I'm using a utility to repeatedly call a JSP page that uses this class and displays the message variable. This utility allows me to specify the number of concurrent web requests and an overall number of requests to try. While that is running, I look at V$SESSION in Oracle and occassionaly, I will see a brief entry for app1 or adavey depending on the timing of my query and how far along the code has processed in this example. So it seems that I am only using one connection at a time and not a true connection pool.
Is it possible that I need to use the oci driver instead of the thin driver? I've looked at the javadoc for oci and the OCIConnectionPool has a setPoolConfig method to set initial, min and max connections. However, it appears that this can only be set via Java code and not as a parameter in my context.xml resource file. If I have to set it each time I get a database connection, it seems like it sort of defeats the purpose of having Tomcat maintain the connection pool for me and that I need to implement my own connection pool. I'm a newbie to this technology so I really don't want to go this route.
Any advice on setting up a proper connection pool that works with Tomcat and Oracle proxy sessions would be greatly appreciated.
Thanks,
AlanWell I did some more experiments and I am able to at least create a connection pool within my example code:
package web;
import oracle.jdbc.pool.OracleDataSource;
import oracle.jdbc.OracleConnection;
import javax.naming.*;
import java.sql.SQLException;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
public class ConnectionPool {
String message = "Not Connected";
public void init() {
OracleConnection conn = null;
ResultSet rst = null;
Statement stmt = null;
try {
Context initContext = new InitialContext();
Context envContext = (Context) initContext.lookup("java:/comp/env");
OracleDataSource ds = (OracleDataSource) envContext.lookup("App1ConnectionPool");
message = "Here.";
String user = ds.getUser();
if (envContext == null)
throw new Exception("Error: No Context");
if (ds == null)
throw new Exception("Error: No DataSource");
if (ds != null) {
message = "Trying to connect...";
boolean cache_enabled = ds.getConnectionCachingEnabled();
if (!cache_enabled){
ds.setConnectionCachingEnabled(true);
Properties cacheProps = new Properties();
cacheProps.put("InitialLimit","5");
cacheProps.put("MinLimit","5");
cacheProps.put("MaxLimit","10");
ds.setConnectionCacheProperties(cacheProps);
conn = (OracleConnection) ds.getConnection();
Properties prop = new Properties();
prop.put("PROXY_USER_NAME", "adavey/xyz");
if (conn != null) {
message = "Got Connection " + conn.toString() + ", ";
conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME,prop);
stmt = conn.createStatement();
//rst = stmt.executeQuery("SELECT 'Success obtaining connection' FROM DUAL");
rst = stmt.executeQuery("SELECT user, SYS_CONTEXT ('USERENV', 'SESSION_USER') from dual");
while (rst.next()) {
message = "DS User: " + user + "; DB User: " + rst.getString(1) + "; sys_context: " + rst.getString(2);
message += "; Was cache enabled?: " + cache_enabled;
rst.close();
rst = null;
stmt.close();
stmt = null;
conn.close(OracleConnection.PROXY_SESSION); // Return to connection pool
conn = null; // Make sure we don't close it twice
} catch (Exception e) {
e.printStackTrace();
} finally {
// Always make sure result sets and statements are closed,
// and the connection is returned to the pool
if (rst != null) {
try {
rst.close();
} catch (SQLException e) {
rst = null;
if (stmt != null) {
try {
stmt.close();
} catch (SQLException e) {
stmt = null;
if (conn != null) {
try {
conn.close();
} catch (SQLException e) {
conn = null;
public String getMessage() {
return message;
In my context.xml file, I tried to specify the same Connection Cache Properties as attributes, but no luck:
<Context path="/App1" docBase="App1"
debug="5" reloadable="true" crossContext="true">
<Resource name="App1ConnectionPool" auth="Container"
type="oracle.jdbc.pool.OracleDataSource"
driverClassName="oracle.jdbc.OracleDriver"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="jdbc:oracle:thin:@127.0.0.1:1521:oddjob"
user="app1" password="app1"
ConnectionCachingEnabled="1" MinLimit="5" MaxLimit="20"/>
</Context>
These attributes seemed to have no effect:
ConnectionCachingEnabled="1" ; also tried "true"
MinLimit="5"
MaxLimit="20"
So basically if I could find some way to get these attributes set within the context.xml file instead of my code, I would be a happy developer :-)
Oh well, it's almost Miller time here on the east coast. Maybe a few beers will help me find the solution I'm looking for. -
Performance degradation using Jolt ASP Connectivity for TUXEDO
We have a customer that uses Jolt ASP Connectivity for TUXEDO and is suffering
from a severe performance degradation over time.
Initial response times are fine (1 s.), but they tend to increase to 3 minutes
after some time (well, eh, a day or so).
Data:
- TUXEDO 7.1
- Jolt 1.2.1
- Relatively recent rolling patch installed (so no there are probably no JSH performance
issues and memory leaks as fixed in earlier patches)
The ULOG shows that during the night the JSH instances notice a timeout on behalf
of the client connection and do a forced shutdown of the client:
040911.csu013.cs.kadaster.nl!JSH.234333.1.-2: JOLT_CAT:1185: "INFO: Userid:
[ZZ_Webpol], Clientid: [AP_WEBSRV3] timed out due to inactivity"
040911.csu013.cs.kadaster.nl!JSH.234333.1.-2: JOLT_CAT:1198: "WARN: Forced
shutdown of client; user name 'ZZ_Webpol'; client name 'AP_WEBSRV3'"
This happens every 10 minutes as per configuration of the JSL (-T flag).
The customer "solved" the problem for the time being by increasing the connection
pool size on the IIS web server.
However, they didn't find a "smoking gun" - no definite cause for the problem.
So, it is debatable whether their "solution" suffices.
It is my suspicion the problem might be located in the Jolt ASP classes running
on the IIS.
Maybe the connection pool somehow loses connections over time, causing subsequent
users having to queue before they get served (although an exception should be
raised if no connections are available).
However, there's no documentation on the functioning of the connection pool for
Jolt ASP.
My questions:
1) What's the algorithm used for managing connections with Jolt ASP for TUXEDO?
2) If connections are terminated by a JSH, will a new connection be established
from the web server automatically? (this is especially interesting, because the
connection policy can be configured in the JSL CLOPT, but there's no info on how
this should be handled/configured by Jolt ASP connectivity for TUXEDO)
Regards,
Winfried ScheuldermanHi,
For ASP connectivity I would suggest looking at the .Net client facility provided in Tuxedo 9.1 and later.
Regards,
Todd Little
Oracle Tuxedo Chief Architect -
ISA B2B logon Error: No valid private connection for internet user
Hello ,
i used isauseradm to create a user zzweb with all authorizations for B2B..
now when i try to log to
http://host:port/b2b/b2b/init.do with the user zzweb
i have a runtime error with the logs :
EXCEPTION]
#1#com.sap.isa.businessobject.BORuntimeException: Error getting private connection for internet user:com.sap.isa.core.eai.BackendException: Error: No valid private connection for internet userzzweb
at com.sap.isa.businessobject.BusinessObjectHelper.splitException(BusinessObjectHelper.java:78)
at com.sap.isa.user.businessobject.UserBase.login(UserBase.java:313)
at com.sap.isa.businessobject.User.login(User.java:143)
at com.sap.isa.user.action.UserActions.performLogin(UserActions.java:295)
at com.sap.isa.user.action.UserActions.performLogin(UserActions.java:368)
at com.sap.isa.user.action.UserBaseAction.performLogin(UserBaseAction.java:126)
at com.sap.isa.user.action.LoginBaseAction.ecomPerform(LoginBaseAction.java:77)
at com.sap.isa.isacore.action.EComBaseAction.doPerform(EComBaseAction.java:353)
at com.sap.isa.core.BaseAction.execute(BaseAction.java:211)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:674)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
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.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
at com.tealeaf.capture.LiteFilter.doFilter(Unknown Source)
at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:373)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
what does this error means..?
i also realised that zzweb was not created in CRM backen? should it be created ?
many thnx for help ..
Message was edited by: BlackmanIts a late response... but if someone gets the same issue here is the solution.
When you register try uppercase password . That should take care of that issue.
The problem is with function module CRM_ISA_IUSER_SWITCH , Note 946536.
Although the note says 5.0 the problem exists with ISA 4.0 too -
Unable to get a connection for pool - ResourceUnavailableException
Hi
I have a BPEL process which starts a child instance of another asynchronous BPEL process for each message in an XML file. The child BPEL process makes a call to the Oracle Apps JCA Adapter to push the data into E-Business Suite.
All works perfectly except when the number of messages exceeds a certain limit (15 or so). The error received is as follows:
"Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'SyncPersonRecord' failed due to:
JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection.
ebsPeoplesoftEmployees:SyncPersonRecord [ SyncPersonRecord_ptt::SyncPersonRecord(InputParameters,OutputParameters) ] :
The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue:
javax.resource.spi.ApplicationServerInternalException:
Unable to get a connection for pool = 'eis/Apps/Apps',
weblogic.common.resourcepool.ResourceUnavailableException:
No resources currently available in pool eis/Apps/Apps to allocate to applications.
Either specify a time period to wait for resources to become available, or increase the size of the pool and retry.. Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections.
Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution."
Obviously what is happening is the connection pool maximum is reached (currently 15) and this is throwing the error.
What I need to do is to implement the suggestion of "specifying a time period to wait" and I was hoping someone could tell me how I do this?
I have tried setting the 'Connection Creation Retry Frequency' parameter to 30 seconds which made no difference and also have checked the documentation on "Configuring and Managing JDBC Data Sources for Oracle WebLogic Server".
Does anyone know if this is something that is implemented directly in the BPEL process/composite or in the connection source itself.
Many thanksOpen the jndi : eis/Apps/Apps in /console - config tab - increase the initial and max conn capacity and save it. Retry the scenario
-
Error while creating jco connection for metadata?
Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: 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:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) 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(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) 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:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) 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(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) 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:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) 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(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
RajendraHello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh. -
Error while creating connection for Application server in Jdeveloper
Hi,
I am trying to create a new connection for my weblogic server from JDeveloper
I am using weblogic 6.1
The error is :javax.naming.AuthenticationException [Root exception is java.lang.SecurityException : attemting to add an object which is not an instance 0f java.security.Principal to a subject's Principal set
I am currectly passing my userID and password. but still it is giving the above exception.
Please advise me.
With thanks
Murthy
HI
In JDeveloper 10.1.3.1.0,
1. Click on the tab for the Connections navigator.
2. Right click on Application Server and select New Application Server Connection.
3. Enter a descriptive name for the new connection, and select the appropriate connection type from the drop down list. Click Next.
4. Specify oc4jadmin for User Name, then enter the oc4jadmin password. Click Next.
5. Select Single Instance for Connect To, then provide the host name where BPEL is installed, the OPMN port number, and the OC4J instance name (the default for 10.1.3.1 is oc4j_soa). Click Next.
6. Click Test Connection. If you have been successful, you should see "Success!"
7. Now, right click on Integration Server and select New Integration Server Connection.
8. Specify a connection name and click Next.
9. In the drop down list by Application Server, select the Application Server Connection you just created. Again, specify the host name where BPEL is installed and the port number. This port number will be the same that you specified for the Integration Server Connection to the home OC4J container. Click Next.
10. Test the connection. You should see something like:
Application Server: OK
BPEL Process Manager Server: OK
ESB Server: OK
11. Now, return to the Applications navigator, and try to redeploy your process using the Integration Server Connection just created. (It is possible that you will have to close JDeveloper and then reopen it for this to work.)
Cheers
Anirudh Pucha -
Not able to connect to Jboss 4.2.3 from Jdeveloper 11.1.1.0
I am using Jboss 4.2.3 and Jdeveloper 11.1.1.0 and trying to connect to Jboss from Jdeveloper, my OS is Windows vista.
I started Jboss and tried creating a Application Server creation from Jdeveloper.
Gave connection name as "youHomeApp", selected connection type as "Jboss 4.x", and deploy directory as "D:\Program Files\Jboss\jboss-4.2.3.GA\server\default\deploy".
Now I am getting "Connection error" with the message "Presentation not available: oracle.rc.adapter.connection.presentationType$Default"
How to resolve this issue?
regds
-rajuFor tomcat have a look at the video linked here:
http://blogs.oracle.com/shay/2009/01/tomcat_extensions_for_jdevelop_1.html
There is a section there that shows you the information for a connection to Tomcat. -
Unable to create Metadata connection for Dictionary Provider
Hi,
I am getting the following error while I try to run a Web Dynpro Application;
The initial exception that caused the request to fail, was:
com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
... 37 more
The JCo Connections are tested and pinged, they work fine.
Can anyone please tell what the error could be?The details exception list is as below:
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.dow.dc.model.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
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.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 34 more -
Firefox works well, except will not connect for updates
If there are problems with updating or with the permissions then best is to download the full version and trash the currently installed version to do a clean install of the new version.
Download a new copy of the Firefox application and save the disk image file to the desktop
*Firefox 30.0: http://www.mozilla.org/en-US/firefox/all.html
*Trash the current Firefox application (open the Applications folder in the Finder and drag the Firefox application to the Trash) to do a clean (re)install
*Install the new version that you have downloaded
*https://support.mozilla.org/kb/Installing+Firefox+on+Mac
Your personal data is stored elsewhere in the Firefox profile folder, so you won't lose your bookmarks and other personal data when you uninstall and (re)install Firefox.
*http://kb.mozillazine.org/Profile_folder_-_Firefox
Maybe you are looking for
-
I have no external devices connected to my Mac mini but still everytime I use it after about half hour to an hour in whatever I'm using wether it's the Internet or iPhoto or iTunes the beach ball appears and I cannot get it to stop I always have to p
-
Hi all, Apologies if any of the following sounds at all silly but I am fairly new to this so here goes... I have 3 tables that require data insertion at the same time. The first table is the customers table, I then want to take the automatically gene
-
I do not have Wifi at my home. I was at a place with free wifi, and I was going to be there for a while so I decided to update my apps. Well, it took my iPod 2 days to update about 15 apps; probably because the wifi connection was very slow. But I ha
-
Client side load balancing and server side load balancing
Hello Team, I need to know how to set up client and server side load balancing in oracle rac. What all things to be implemented like creating a service, tnsnames.ora settings etc. And also if i used SCAN ip instead of VIP. how the settings will chan
-
In Mac OS X, what do I use instead of Microsoft Office?
Does Mac OS X come with a suite like Microsoft Office or do I buy something? What do I use to replace it? On email is email and calendaring built in and ready for OS X Server so that I don't need to buy something else to start using Apple's iCal sche